-
As mentioned by @TimTaylor on the internal slack workspace, and as discussed on the [[R-pkg-devel] mailing list](https://stat.ethz.ch/pipermail/r-package-devel/2023q1/008924.html), we should be consci…
-
This vignette could be a good place to add references to these. They can inform users where to gather this information for their own purposes.
For example, here in the intro paragraph:
https://g…
-
About this line:
https://github.com/epiverse-trace/finalsize/blob/f0ac4127e54579754d08ee92754203f99c0f6ee9/vignettes/varying_susceptibility.Rmd#L256-L257
Please, confirm if the line 256 correspond…
-
About the input:
- This may inform users how to arrange their data in a certain format or why the code follows preliminary operations before using `final_size()`.
- This may also help to explain i…
-
The introductory paragraph is concrete and direct enough to grasp the aim of the package. However, I had the following doubts that I later clarified after reading the vignettes:
- Is final size ref…
-
After this https://github.com/epiverse-trace/finalsize/issues/119#issuecomment-1384492391 it would be nice to have in a new place a set of two or three examples of these, that would help to complement…
-
There might be a case for splitting up the package into multiple smaller ones, which could have benefits to usability, developer engagement and future sustainability. For example we could have a "core…
-
-
Not 100% sure but it looks like you have hardcoded a path, which means that malaria data will be fetched in `import_data_endemic_channel()`, no matter what the user passes as `disease_name`:
https:…
-
The current README structure is a bit awkward because it mixes a template for the README, as well as instructions on how to use this template & how to create a new R package from the command line.
…