Key considerations for retiring/superseding an R package
https://epiverse-trace.github.io/posts/superseding-bpmodels/
Published: February 3, 2025 00:00
Most of our work in Epiverse TRACE involves either developing an R package from scratch or adopting and maintaining an existing R package. In the former case, decision-making during development is guided by internal policies documented in theā¦
Licensing R packages with code and data: learnings from submitting to CRAN
https://epiverse-trace.github.io/posts/data-licensing-cran.html
Published: January 20, 2025 00:00
Note
This is a follow-up blog post to the Dual licensing R packages with code and data post published in September 2024. It contains learnings from submitting epiparameter to CRAN with a dual license.
Overview of previous blog post on R packageā¦
simulist v0.4.0
https://epiverse-trace.github.io/posts/simulist_v0.4.0/
Published: January 10, 2025 00:00
We are very excited to announce the release of a new simulist version v0.4.0. This is the first version of simulist to be on CRAN (the package can now be installed with install.packages()). Here is an automatically generated summary of the changes in thisā¦
epiparameter v0.4.0
https://epiverse-trace.github.io/posts/epiparameter_v0.4.0/
Published: January 8, 2025 00:00
We are very excited to announce the release of a new epiparameter version v0.4.0. This is the first version of epiparameter to be on CRAN (the package can now be installed with install.packages()). Here is an automatically generated summary of the changesā¦
Things that can go wrong when using renv
https://epiverse-trace.github.io/posts/renv-complications/
Published: December 31, 2024 00:00
Throughout the Epiverse project, we use the renv R package to ensure reproducibility of the training materials and the pipelines we are providing. But we sometimes get reports from users who struggle to rebuild the environment and run the code.
In thisā¦