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
MTK models with synchronization and discrete subsystems need to store discrete solutions to be able to reconstruct the entire dynamics. It's easy to add a subsolutions field in ODESolution, but how should we attach the sub-solutions after __solve? Currently, MTK generates code that pushes the discrete states into a saving vector inside periodic callbacks. Should we add a higher order callback function like solution_post_processing after __solve in DiffEqBase to attach the sub-solutions?
The text was updated successfully, but these errors were encountered:
MTK models with synchronization and discrete subsystems need to store discrete solutions to be able to reconstruct the entire dynamics. It's easy to add a
subsolutions
field inODESolution
, but how should we attach the sub-solutions after__solve
? Currently, MTK generates code that pushes the discrete states into a saving vector inside periodic callbacks. Should we add a higher order callback function likesolution_post_processing
after__solve
in DiffEqBase to attach the sub-solutions?The text was updated successfully, but these errors were encountered: