8000 specify column name for simulation data for optional simulation.tsv · Issue #628 · PEtab-dev/PEtab · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

specify column name for simulation data for optional simulation.tsv #628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fbergmann opened this issue May 13, 2025 · 2 comments · May be fixed by #632
Open

specify column name for simulation data for optional simulation.tsv #628

fbergmann opened this issue May 13, 2025 · 2 comments · May be fixed by #632

Comments

@fbergmann
Copy link
Contributor

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

@dweindl
Copy link
Member
dweindl commented May 13, 2025

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).

@matthiaskoenig
Copy link
Contributor

+1 for proper description and keeping it

dweindl added a commit that referenced this issue May 21, 2025
* 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.
@dweindl dweindl linked a pull request May 21, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
0