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
For petab version 2, we will have to rewrite a large part of the current functionality, which gives us the opportunity to rethink the API. For v2, @dilpath and I would like to change the DataFrame based API to a proper object model (e.g., instead of observable_df: pd.DataFrame, we'd have observables: list[Observable]).
This will greatly simplify validation and dealing with default values as well setting proper data types.
The text was updated successfully, but these errors were encountered:
we could still have an observable_df property that serialises the observables to df's for those that need it, might also be handy for serialisation later
Update creation of PEtab problems, validation, conversion from v1 to v2,... to the new long condition table.
Many TODOs remain. To be continued after #337.
---------
Co-authored-by: Dilan Pathirana <59329744+dilpath@users.noreply.github.com>
For petab version 2, we will have to rewrite a large part of the current functionality, which gives us the opportunity to rethink the API. For v2, @dilpath and I would like to change the DataFrame based API to a proper object model (e.g., instead of
observable_df: pd.DataFrame
, we'd haveobservables: list[Observable]
).This will greatly simplify validation and dealing with default values as well setting proper data types.
The text was updated successfully, but these errors were encountered: