Skip to content

monitoring of unfinished activities #73

@bart6114

Description

@bart6114

I've ran into some results that are unintuitive for me. Consider the following

library(simmer)

a <- create_trajectory() %>%
  timeout(11)

b <- create_trajectory() %>%
  timeout(1) %>%
  rollback(1, times=Inf)

c <- create_trajectory() %>%
  timeout(5)

simmer() %>%
  add_generator("a", a, at(0)) %>%
  add_generator("b", b, at(0)) %>%
  add_generator("c", c, at(0)) %>%
  run(until=10) %>%
  get_mon_arrivals()

Which results in:

  name start_time end_time activity_time finished replication
1   c0          0        5             5     TRUE           1

I would expect the a and b arrival to also show up with an end_time equal to until and a finished status of FALSE.

Not looked into it too deep, but I think we can relatively easily implement this by making a terminate call on all the active arrivals after the Simulator::run function runs out.

What do you think @Enchufa2?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions