You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The simulation records the state of the system at each time step, capturing metrics such as completed rides, total distance traveled, and total cost.
These metrics are used to evaluate the performance of the system and compare different routing strategies.
Notes from Sean:
I have a few implementations of logging I can show that might be helpful
Also a feature I have added in the past is a DEBUG_MODE parameter for logging the entire state after blocks
But for larger simulations only saving the history of important metrics and variables will be a much better way to go, otherwise storage blows up
Metrics can be possibly handled post simulation with the metric functions feature of simulation running
From DIPR:
The simulation records the state of the system at each time step, capturing metrics such as completed rides, total distance traveled, and total cost.
These metrics are used to evaluate the performance of the system and compare different routing strategies.
Notes from Sean:
Tasks:
The text was updated successfully, but these errors were encountered: