As discussed a bit here (though in place even before PR #974) right now the main simulation logic keeps a state variable - basically an integer counter - to track the current time step. This is entirely separate from the Simulation_Time object that is also used to model time. So the same state is being maintained independently in two places. It makes more sense for Simulation_Time to be entirely responsible for the time, and to have it manage and provide access to the time step information.
To avoid complicating the scope of #974 too much, tracking this as a separate issue.
As discussed a bit here (though in place even before PR #974) right now the main simulation logic keeps a state variable - basically an integer counter - to track the current time step. This is entirely separate from the
Simulation_Timeobject that is also used to model time. So the same state is being maintained independently in two places. It makes more sense forSimulation_Timeto be entirely responsible for the time, and to have it manage and provide access to the time step information.To avoid complicating the scope of #974 too much, tracking this as a separate issue.