Dilan Pathirana

> > Or, we move/copy this to the PEtab Result. > > That sounds wrong, since it clearly is input, not output. Whether it was used to obtain the given...

> @dilpath : Could you please check - is this expected to fail occasionally? I think so, only 10 starts were used. Since the test takes < 4 mins with...

Further feedback welcome in github issues.

Another suggestion is to allow arbitrary columns like `scale` and `offset` in the measurements table. These are treated as PEtab IDs and cannot appear anywhere else in the PEtab problem,...

Another suggestion is to support labels in the `observableParameters` column, where the labels cannot be reused for other observables nor appear anywhere else in the PEtab problem. _Measurements table_ |...

> It should be evident from the observables table which parameters are meant to be measurement-specific (i.e. overridable via the measurements table) I'm fine with this, but: it's not evident...

If we separate the IDs into two groups "PEtab IDs" and "placeholder IDs" (IDs in the `observablePlaceholders` column), there should be no overlap between the two groups (edit: as you...

> * Currently, we load them from GitHub, thus needing an internet connection. Another option would be to include the files, though this might add unnecessary files to the package...