The best way to proceed is to run the simulation for a time long enough so that a sufficiently large number of arrivals have finished their trajectories, so that you have all the information required at the output.
If your simulation is instead set up so that arrivals don't necessarily finish the entire trajectory, but they keep looping around, then get_mon_arrivals(per_resource = TRUE, ongoing = TRUE) is what you are looking for, because this reports timings per resource. Therefore, even if a particular arrival is still ongoing, this will report timings for the already visited resources.
Best,
Iñaki
--
You received this message because you are subscribed to the Google Groups "simmer-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simmer-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simmer-devel/d5b5af50-1d7f-420c-b201-a764aacd9a30n%40googlegroups.com.