The CellMLTools plugin consists of various CellML-related tools, which can be accessed both through the CLI and the GUI.
A CellML file can be exported to different:
An export can be initiated by selecting the
CellML File Export To menu or by entering the following command:
$ ./OpenCOR -c CellMLTools::export <file> <format>|<language>
<file> either a local or a remote file and
<language> taking one of the following values:
cellml_1_0: to export a CellML 1.1 file to CellML 1.0
c: to export a CellML file to C
fortran_77: to export a CellML file to FORTRAN 77
matlab: to export a CellML file to MATLAB
python: to export a CellML file to Python
Thus, to export
myfile.cellml to CellML 1.0, you would use:
$ ./OpenCOR -c CellMLTools::export myfile.cellml cellml_1_0
while to export
https://mydomain.com/myfile.cellml to Python, you would use:
$ ./OpenCOR -c CellMLTools::export https://mydomain.com/myfile.cellml python
0. Then, due to 0- vs. 1-based indexing, that constant gets computed twice if there are other constants in the model. The end result is that \(dX/dt\) is not equal to
0but to the value of the other constant.
The validation of a CellML file can be done by entering the following command:
$ ./OpenCOR -c CellMLTools::validate myfile.cellml
Both errors and warnings, if any, get listed and an exit code value of
0 means that the CellML file is valid (i.e. no errors were found).