Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Monitoring: start/activity/end time per resource #38
This is a very useful feature. In fact, I've received another email asking for it, so I've started the implementation, but I need your feedback, @Bart6114. Right now, we have this:
head( env %>% get_mon_arrivals() ) #> name start_time end_time activity_time finished replication #> 1 patient0 10.27215 53.74036 43.46821 TRUE 1 #> 2 patient1 16.27760 64.65632 38.13386 TRUE 1
In order to keep backward compatibility, we can add a parameter. For instance:
head( env %>% get_mon_arrivals(per_resource = TRUE) ) #> name start_time end_time activity_time finished resource replication #> 1 patient0 10.27215 12.74036 9.46821 TRUE nurse 1 #> 2 patient0 12.74036 33.65632 20.91596 TRUE doctor 1 #> ...
What do you think?