Skip to content

9-25 Meeting Recap: Code Clean-up #34

@WilliamIX

Description

@WilliamIX

In order to clean up code and follow the design constraints (briefly re-iterated below and discussed extensively elsewhere), existing code will be copied class by class and method by method into new files in order to clean up dependencies and inconsistencies.

Main Design Constraints:

  1. Create an internal representation to store CRNs (instead of using SBM's representation). This will require specie, reaction, and CRN classes which are distinct from Mixture, Component, and Mechanism. These classes are very minimal and functionally will work a lot like strings with certain safeguards.
  2. Implement the compile loop as described in the overview document -- all reactions are created by mechanisms. Most species are created by mechanisms with a few minor exceptions.
  3. Clean up parameter loading. Initially this will be done by storing all parameters as dictionaries within Mixture (Default) and Components (User override parameters). Config files put on hold but can later be parsed to dictionaries.
  4. Make sure all code is object oriented; ensure that code can work on its own without non-object based helper functions in order to define components and compile a CRN. Helper wrapper functions will be created later for special (common) use cases to streamline the user experience.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions