specify column name for simulation data for optional simulation.tsv · Issue #628 · PEtab-dev/PEtab · GitHub
More Web Proxy on the site http://driver.im/
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
Which problem would you like to address? Please describe.
Specs for v1 and v2 mention that we can have an optional simulation data file "in the same format as the measurement" file, however whenever they are used the measurement column has a different name. That name has not been consistent in the past it was either 'simulatedDataorsimulation`.
Describe the solution you would like
Add a clarification that the format has to be the same as the measurement file, with measurement replaced by simulation
The text was updated successfully, but these errors were encountered:
Agreed that this should be specified somewhere. I am not sure it should be in the PEtab specs, though. As long as there is no clear interaction with the rest of PEtab, I would rather remove any mention of that file.
We should (1) keep the simulation file in the specs and describe it properly, or (2) remove it from there completely. Either works for me, but I'd prefer (2).
* Remove the simulation from the list of PEtab files, because it is not part of the parameter estimation problem.
* Add a section under *measurement table* stating the expected column name.
Closes#628.
Which problem would you like to address? Please describe.
Specs for v1 and v2 mention that we can have an optional simulation data file "in the same format as the measurement" file, however whenever they are used the measurement column has a different name. That name has not been consistent in the past it was either 'simulatedData
or
simulation`.Describe the solution you would like
Add a clarification that the format has to be the same as the measurement file, with
measurement
replaced bysimulation
The text was updated successfully, but these errors were encountered: