database interface for storing and merging partial (incremental) simulation results
a. How does this overlap with streaming results?
testing - see #1421
a. ensure that the inc sim git branch results for a first/single simulation are the same as for the develop branch
b. ensure that incremental simulations have the same results as if fully simulated. [This should be extensive and consider many interactions (of tasks and conditions), especially within a single time point.]
c. test with existing complex models (e.g., from clipper)
d. scheduling tests
e. performance tests (simulation and scheduling)
f. test with contrib streamline resources
scheduling integration -- Adrien suggested that most or all of a java class could be removed since it replicates what inc sim already does.
container-level management -- routing sim requests to the merlin-worker with the right SimulationEngine
inc sim user controls
a. override to do full simulation (and throw out past sims)
b. override to allow inc sim to apply across sim config changes (?)
inc sim core implementation (if re-doing the work in prototype/incremental-sim branch)
combine checkpoint restart and inc sim so that past sim can be loaded from DB and used with inc sim
provide user/modeler the ability to mark a task, activity, directive, cell, or resource as "always stale" so that inc sim knows to rerun/recompute it.
have a collapse mechanism to merge a chain of simulation engines in memory into one to avoid overhead of chaining
have a collapse mechanism to merge partial sim results in the database (related to bullet 1 above)
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
No response
Describe the feature request
Investigation into the features and implementation of incremental sim for AERIE
Become up to speed on the codebase
Update previous work:
Work items identified in discussion: https://github.com/NASA-AMMOS/aerie/discussions/669#discussioncomment-9136181