Skip to content
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

Fix generate example #110

Merged
merged 2 commits into from
May 9, 2019
Merged

Fix generate example #110

merged 2 commits into from
May 9, 2019

Conversation

yannikschaelte
Copy link
Member

No description provided.

Copy link
Member

@dweindl dweindl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this experiment_id still a thing? I thought that became obsolete with the new plotting config files. Not sure though.

@yannikschaelte
Copy link
Member Author

@erikadudki @MerktSimon Is this still a thing (you were working on this, right?)?

@MerktSimon
Copy link
Member

At least for visualization the experimentID does not play a role, because plots are grouped by plotID and for everything else there is DataSetID.

@JanHasenauer
Copy link
Contributor

I think the experimentID can and should be removed. It has been replaced by the more fine-grained datasetID.

@yannikschaelte yannikschaelte merged commit 743d639 into develop May 9, 2019
@yannikschaelte yannikschaelte deleted the fix_generate_example branch May 9, 2019 15:38
@paulstapor
Copy link
Contributor

Okay, I'm a little confused...
Both things are actually new, right?

As a non-developer of PEtab, I have a rough idea what ExperimentId does: It's groups simulations and outputs into experiments, similar to what D2D does. However, I do not understand directly, what datasetID does. could we document that somehow?

Another point is, that the benchmark examples don't have these fields. So, if we want to make them mandatory, we need to rework he PEtab files of the benchmark examples. That's doable, but we have to keep it in mind...

@yannikschaelte
Copy link
Member Author

as far as I understand it, datasetId has in principle the same purpose, primarily for visualizing together data that belong together. If it's not documented, i.e. the full visualizationSpecification file, then this should be done in the petab docs indeed (@MerktSimon @erikadudki).

I think nothing will be mandatory, so the files/fields should be marked as optional in the docs.

elbaraim pushed a commit that referenced this pull request Oct 4, 2019
here just making the example work now, deletion of experimentId then in #111
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 this pull request may close these issues.

None yet

5 participants