Releases: r-simmer/simmer
Releases · r-simmer/simmer
simmer 3.1.2
New features:
- Monitor arrivals' start/activity/end times on a per-resource basis (#38). So far, the function
get_mon_arrivals()
returned the start/activity/end times per arrival for the whole trajectory. This behaviour remains, but additionally,get_mon_arrivals(per_resource = TRUE)
returns these times per resource, so that it is possible to retrieve queueing/system times per resource.
Minor changes and fixes:
- Fix testing ERRORs reported on platforms using clang and Sparc Solaris.
get_mon_*
functions accept a single simulation environment as well as a list of environments representing several replications (5ee2725). A new column (replication
) in the resulting data frame indicates the corresponding replication number.- Monitoring subsystem refactored (as a consequence of #38).
simmer 3.1.1
simmer 3.0.1
simmer 3.0.0
New features:
- First major release submitted to CRAN. The philosophy and workflow of the pre-release remain with a more robust event-based C++ backend and a more flexible frontend.
- Enhanced programmability. The timeout activity is more than just a delay. It admits a user-defined function, which can be as complex as needed in order to interact with the simulation model. The old v2.0 was no more than a queueing network simulator. This feature makes simmer a flexible and generic DES framework. Moreover, we have finally got rid of the infamous
add_skip_event
function to implement a more flexible and user-friendly branching method. - Robustness. The event-based core design is rigorous and simple, which makes simmer faster and less error-prone, at the same level of other state-of-the-art DES frameworks.
- Much better performance. Instead of creating
n
arrivals beforehand, this release leverages the concept of generator of arrivals, which is faster and more flexible. At the same time, the concept of trajectory as a chain of activities is implemented entirely in C++ internally. Our tests show that simmer is even faster than SimPy when it comes to simulate queueing networks. - Replication. In the pre-release, replication was implemented inside simmer. This no longer makes sense since, with the current design, it is more than straightforward to replicate and even parallelize the execution of replicas using standard R tools.
simmer 2.0
v2.0 first Rcpp based version