Latest COPASI version by default generates TSV file as result along with some additional metadata which is not useful for visualisation purposes.
From the above SED-ML, the user can able to define plot2D, plot3D or DataSet block.
In older versions <4.28.226, if there is no dataset block, COPASI lib throws error/fails if SED-ML doesn't have dataset definition so that we can create a default one.
But in versions >= 4.28.226, the COPASI lib doesn't notify/fail if there is no DataSet definition, rather it creates a TSV on its own (along with metadata).
How should we handle it? Should the user take care of it to provide a correct SED-ML? Or do we need to handle it in simulator code?
PFA zip archive, which contains a sample OMEX used to test the scenario, and old.csv and new.csv generated by the old and new version of COPASI respectively.
To reproduce the CSV files pull the latest and 4.27.214 docker images and run locally with the attached OMEX archive. Refer this.
Latest COPASI version by default generates TSV file as result along with some additional metadata which is not useful for visualisation purposes. From the above SED-ML, the user can able to define plot2D, plot3D or DataSet block. In older versions <4.28.226, if there is no dataset block, COPASI lib throws error/fails if SED-ML doesn't have dataset definition so that we can create a default one. But in versions >= 4.28.226, the COPASI lib doesn't notify/fail if there is no DataSet definition, rather it creates a TSV on its own (along with metadata).
How should we handle it? Should the user take care of it to provide a correct SED-ML? Or do we need to handle it in simulator code?
PFA zip archive, which contains a sample OMEX used to test the scenario, and
old.csv
andnew.csv
generated by the old and new version of COPASI respectively.To reproduce the CSV files pull the
latest
and4.27.214
docker images and run locally with the attached OMEX archive. Refer this.@moraru @jonrkarr @bilalshaikh42 Thoughts?
Archive.zip