New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring: start/activity/end time per resource #38

Closed
Enchufa2 opened this Issue Dec 27, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@Enchufa2
Member

Enchufa2 commented Dec 27, 2015

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?

@Enchufa2 Enchufa2 added this to the v3.2.0 milestone Dec 27, 2015

@Enchufa2

This comment has been minimized.

Member

Enchufa2 commented Dec 27, 2015

And probably the finished column has no sense in a per-resource report.

@Enchufa2

This comment has been minimized.

Member

Enchufa2 commented Dec 28, 2015

The implementation is finished in dev-main. I'll wait for your feedback before merging it into the master branch. No hurry. 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment