Bisaloo
commented
6 months ago Two updates & new requirements on this:
- we should make sure parameter names are harmonized across templates
- we need to take into account "hidden" parameters, and also decide what to do with them. E.g., column names in https://github.com/epiverse-trace/episoap/blob/0c525bdeaebc460f7c560dd47f5974434024dd4d/inst/rmarkdown/templates/transmissibility/skeleton/skeleton.Rmd#L306-L311
The transmissibility pipeline currently has 10 parameters that the user can modify. As more parameters are added, e.g., to select specific studies within the {epiparameter} database or to specify the source of data using {readapi}, the flexibility of the templates increases, but so does the complexity for the users.
This issue is to keep track of the discussions and decisions made about this topic in {episoap}.
For now, @Bisaloo and myself have agreed to keep the template as it is, in its somewhat more rigid format (when compared to other, more modular approaches), with the intention of providing a resource that's readily available for users to test and provide feedback. The next step for deciding a manageable number of parameters is to check how many will be needed for the severity pipeline, and compare this number to that of the transmissibility pipeline.