This is not very useful:
env <- simmer() %>%
add_resource("resource_name", 1) %>%
set_capacity("resource_name", 2)
because it's stupid. These methods are interesting inside a trajectory. And although we may do the following:
env <- simmer()
t <- create_trajectory() %>%
timeout(function() set_capacity(env, "resource_name", 2))
and it works, turning set_capacity() (as well as set_queue_size()) into activities is far more intuitive to the user, so that the first (absurd) use is not possible anymore and the second one becomes the following:
t <- create_trajectory() %>%
set_capacity("resource_name", 2)
This is not very useful:
because it's stupid. These methods are interesting inside a trajectory. And although we may do the following:
and it works, turning
set_capacity()(as well asset_queue_size()) into activities is far more intuitive to the user, so that the first (absurd) use is not possible anymore and the second one becomes the following: