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
After the discussion in the developers meeting, this issue is open to continue discussion for a higher-level API. I think this high level API would mimic PyBOP workflows, but could also provide other functionality. An example API for this package (pbx?) would be:
Sorry for the delayed response, still clearing off backlog from before Christmas. I am not sure I see all the advantages of having a separate package. If pbx just contains the wrapper classes to streamline the process, it will be quite light but still require PyBOP as a dependency, so we will only be shaving a few lines of codes from PyBOP but we now have 2 packages to maintain and keep synced.
IMO, these wrapper classes could coexist with the more detailed workflows. It would be similar of how PyBaMM can be easily streamlined with a simulation of a standard model, but you can also use the methods in it to solve your own models.
Feature description
After the discussion in the developers meeting, this issue is open to continue discussion for a higher-level API. I think this high level API would mimic PyBOP workflows, but could also provide other functionality. An example API for this package (pbx?) would be:
@martinjrobins @davidhowey @brosaplanella @NicolaCourtier
Motivation
This could provide a nice entry point for new-users; however, we would need more development resources to maintain both packages.
Possible implementation
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: