This violates basic paradigm of what the user inputs the user gets.
If this is necessary, this needs to be a cpp utility program that is run before the main simulation.
Switch to integrating using 'advance' instead of step to make output comparable,
independent of small changes in the integrator. Output only selected species and
trim the integration period to reduce the size of the output file (from 3 MB to
25 kB).
Add +M to the three-body reaction's reactants.
Update formatting of species names in the following paragraph.
Update formatting of 'units' arguments.
See Issue 196.
Matlab's practice of substituting an "8 byte integer" BLAS/LAPACK
library for the "4 byte integer" BLAS/LAPACK libraries that Cantera is
designed to use causes Cantera to crash. This can only be avoided by
statically linking Cantera to BLAS and LAPACK, e.g. by using the
BLAS/LAPACK implementations included with Cantera.
Since the Matlab toolbox itself needs to be a shared library, it is
not usually possible to link statically link it with vendor-provided
BLAS/LAPACK libraries, since they are not compiled with the
appropriate options, i.e. '-fPIC'.
Resolves Issue 34.
Change the variable named *species* to be named *component*. This
better matches the utility of this variable, since it can be used to
retrieve any of the state variables. Also, update the corresponding
documentation.
The name 'H' can mean either the species by that name or the entahlpy
of the reactor, in the case of ConstPressureReactor, and the previous
behavior always returned the index of the enthalpy.
This changes the behavior to preferentially return the species, and
adds alternative names for reactor state variables that are less
likely to generate namespace collisions: 'mass', 'volume',
'int_energy', 'enthalpy', 'temperature', 'distance', 'velocity'. The
single character names are still supported.
Resolves Issue 193.
The order of XML attributes within a node has no meaning, and is not
consistent when the attributes are represented as a Python dict, as in
ctml_writer.py. As a result, comparing the text representation of the
XML generates spurious errors when the order changes.
