/simmer

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

Get seized amount from resources #179

Closed
Enchufa2 opened this Issue Nov 30, 2018 · 0 comments

Comments

Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
1 participant
@Enchufa2
@Enchufa2
Copy link
Member

Enchufa2 commented Nov 30, 2018

If an arrival is dropped from a resource (see #177) and several resources were seized, this may be needed in order to know which one was responsible.

Also, this should be always possible:

trajectory() %>%
  release("res1", function() get_seized(env, "res1")) %>%
  release("res2", function() get_seized(env, "res2")) %>%
  ...

@Enchufa2 Enchufa2 added the enhancement label Nov 30, 2018

Enchufa2 added a commit that referenced this issue Dec 1, 2018

@Enchufa2
implementation of #179
8831709

Enchufa2 added a commit that referenced this issue Dec 2, 2018

@Enchufa2
close #25, #179: mechanism to retrieve seized amounts and release all (… 
…#180)

* return immediately if seize/release amount=0

* provide get_seized method

* implementation of #25

* update docs

* implementation of #179

* don't allow negative id for get_*_selected

* some refactoring

* fix test

* update NEWS

* add tests
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.
GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Loading status checks…
6e02a74

@Enchufa2 Enchufa2 closed this Dec 2, 2018

@Enchufa2 Enchufa2 referenced this issue Dec 2, 2018

Closed

Handle unfinished arrivals #177

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