-
Notifications
You must be signed in to change notification settings - Fork 5
Let the Simulation contain a limited timestep-CUDS history #287
Comments
Is the plan to have this as an optional functionality? Some simulations, like CFD simulations, can be very demanding on memory |
AFAIK, this is part of the plan as discussed in M24. Since this part should be provided by the wrappers, each wrapper can simply return the last CUDS, i.e. only one CUDS. This issue is only about laying the foundation of the work, customizing the process is up to wrapper developers. |
Ok. |
Just some idea, an engine wrapper should keep only one CUDS for one time step; the engine wrapper does not need to provide bookkeeping support. With that, I imagine one CUDS for each time step. So with many run steps you have many CUDS. The
For example, on initialisation, |
Correction: The |
Exactly! This is our purpose. Regarding the Simulation class' methods, one could delegate the task of persisting results to another entity:
Then we decouple the storage strategy from the CUDS entity and leave room for introducing more storage mechanisms in future. |
The Simulation class should be able to run a wrapper for a give number of times and keep the result for each internally. This requires implementing a simple workflow manager class, probably provided by each wrapper separately.
Related to #286 and #277
The text was updated successfully, but these errors were encountered: