Use input file rather than command line for problem specification.
I personally prefer yaml, as it is highly expressive and compact.
Using yaml will require:
- C++ yaml library for reading it in Zodiac. We can use the modified version I have inside the ODT or LBMS codes.
- python yaml library for writing it from the web gui.
Things to do:
- Cantera input file specification
- Initialization of primitive variables & parameters through input file. See also issue #7
- Time integrator parameters
Output fields selection
- lock fields that are requested for output
- allow dualtime and real time output intervals to be specified. Dualtime perhaps should only keep the most recent entries?
- allow override of field names in output
Note that the residence time cannot presently be specified as a parametric variable - only a constant. Mike has some changes in the pipeline to relax this.