You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reproducing Figure 1b.
The model has been curated using Copasi 4.27
Because COPASI doesn't clear track the task(s) that the are intended to be run, its not always immediately obvious to naive users which tasks they should run to reproduce published figures, or figures displayed in the curation notes. This is particularly the case for tasks other than time courses, such as parameter scans. Naive users will likely think that the image in the curation notes corresponds to a time course simulation, but this isn't always the case.
The text was updated successfully, but these errors were encountered:
There are 2 options in COPASI that would help to make this clearer:
in the plot specifications, it is possible to assign the plot precisely to the task that it should appear for (in newer COPASI versions we do that automatically for scans / parameter estimations). Once marked, the SED-ML exporter would only export the plots that apply to a given task.
it would be possible to export only those tasks that are marked as 'scheduled', while this is not the default behavior, it is available from the API.
As for the specific case, here it is the scan that should be run.
This is feedback for the BioModels team.
Example: https://www.ebi.ac.uk/biomodels/BIOMD0000000927
The curation note for this simply says:
Because COPASI doesn't clear track the task(s) that the are intended to be run, its not always immediately obvious to naive users which tasks they should run to reproduce published figures, or figures displayed in the curation notes. This is particularly the case for tasks other than time courses, such as parameter scans. Naive users will likely think that the image in the curation notes corresponds to a time course simulation, but this isn't always the case.
The text was updated successfully, but these errors were encountered: