When the simulation is aborted due to a critical error (e.g. NullPointer), the system should acknowledge this.
Currently, the simulation might finish in an invalid state, leading to errors, e.g. in the output logger plugin.
Currently, due to calling exp.finish in SimulationManager.run, the experiment status is always aborted, so it cannot be detect.
This might be a misuse of DesmoJ.
When the simulation is aborted due to a critical error (e.g. NullPointer), the system should acknowledge this.
Currently, the simulation might finish in an invalid state, leading to errors, e.g. in the output logger plugin.
Currently, due to calling
exp.finishinSimulationManager.run, the experiment status is always aborted, so it cannot be detect. This might be a misuse of DesmoJ.