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

Broadcast signals with higher priority #135

Closed
Enchufa2 opened this Issue Jan 16, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@Enchufa2
Member

Enchufa2 commented Jan 16, 2018

Otherwise, an arrival may catch its own signal with a trap after send. Test case needed.

@Enchufa2 Enchufa2 added the bug label Jan 16, 2018

@Enchufa2

This comment has been minimized.

Member

Enchufa2 commented Jan 17, 2018

We have:

library(simmer)

t <- trajectory() %>%
  send("signal") %>%
  trap("signal") %>%
  timeout(1)

simmer() %>%
  add_generator("dummy", t, at(0, 0)) %>%
  run() %>%
  get_mon_arrivals()
#>     name start_time end_time activity_time finished replication
#> 1 dummy0          0        0             0     TRUE           1
#> 2 dummy1          0        0             0     TRUE           1

@Enchufa2 Enchufa2 changed the title from Broadcast signals with maximum priority to Broadcast signals with higher priority Jan 17, 2018

@Enchufa2 Enchufa2 closed this in 19e494d Jan 17, 2018

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