Reduce / remove use of legacy t_state objects throughout modular simulator - Redmine #3419
In the first implementation of the modular simulator, we have been using a bunch of t_state objects to interface with legacy functionality. We want to move away from the legacy t_state object to allow for a purely modular implementation of functionality. Further, the number of allocated objects could hurt performance. Interfaces to legacy functionality include
- Checkpoint reading and writing
- Domain decomposition
- Trajectory writing (position, velocity, boxes)
(from redmine: issue id 3419, created on 2020-03-10 by ptmerz)
- Relations:
- parent #3418 (closed)