When an exception is thrown during the simulation, a RAMTRJ trajectory is truncated and cannot be loaded again. It should be correctly stored - throwing an exception calls destructors, and a SimulationRecorder instance is stored as std::unique_ptr, so all appropriate closing methods should be executed. But it is not what actually happens.
When an exception is thrown during the simulation, a RAMTRJ trajectory is truncated and cannot be loaded again. It should be correctly stored - throwing an exception calls destructors, and a
SimulationRecorder
instance is stored asstd::unique_ptr
, so all appropriate closing methods should be executed. But it is not what actually happens.