-
Notifications
You must be signed in to change notification settings - Fork 276
Open
Labels
BacklogThings we'd like to get to somedayThings we'd like to get to somedayPriority:NormalNormal Priority Issue or PRNormal Priority Issue or PRStakeholder FeedbackFeedback and requests from stakeholdersFeedback and requests from stakeholders
Description
There are many outstanding issues with dynamic or multiperiod models that need to be resolved. They will be aggregated in this issue. This list is incomplete; you can help by expanding it.
- Standardize behavior of initialization routines when more than one time point is present
- Revisit
process_base.fix_initial_conditions
and roll out standardized methods to provide initial conditions for dynamic models by loading in a.json
file as well as solving a steady-state problem att0
. - Reevaluate whether every model that allows
dynamic=True
should allow it, or whether it should be retired (Heater
, I'm looking at you). - Add documentation explaining the concepts of setting
has_holdup=True
anddynamic=True
in a model - Add example where we take a simple unit model (maybe a CSTR?) and make it dynamic.
- Add a method to return the dynamic block sent to PETSc in the same way that Add function to PETSc interface to return initial condition problem #1443 returns the steady-state problem block
- Add a diagnostic method to see if variables at, say t=t1 appear in (non-discretization) equations at t=t2.
- Can we add a diagnostic method to check if a DAE has index greater than 1?
Metadata
Metadata
Assignees
Labels
BacklogThings we'd like to get to somedayThings we'd like to get to somedayPriority:NormalNormal Priority Issue or PRNormal Priority Issue or PRStakeholder FeedbackFeedback and requests from stakeholdersFeedback and requests from stakeholders