-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Variable passing #58
Comments
n.b., switching to a |
I've addressed the comment on inheriting documentation in ff399d1. Currently,
Let me know if you'd like any particular changes with respect to this comment. |
What I meant was the opposite, outbreak_model <- function(num.initial.cases, ...) and later call outbreak_step(...) That said I think the approach suggested by @pearsonca in #58 (comment) is safer/preferable (also because we pass the parameters to two other functions). |
* inherit rather than redefine function arg documentation, fixes #58 * add @return documentation to functions missing it, fixes #67 * fix typo in @return of outbreak_model * update parameter_sweep @return from tibble to data.table output * monospace data.table in documentation * inherit documentation from outbreak_step in outbreak_setup * monospace type in function documentation and add type to arguments missing it * add column names and types of data.table returned by outbreak_model * add column names and types of data.table returned by outbreak_setup * Link to outbreak_setup in outbreak_step documentation Co-authored-by: Carl A. B. Pearson <pearsonca@users.noreply.github.com> * update outbreak_step.Rd * format function argument documentation as: [a <sign> <type> <dimension>: <description>] * indent continuation lines with two spaces in function documentation * remove browser --------- Co-authored-by: Carl A. B. Pearson <pearsonca@users.noreply.github.com>
The model parameters are defined multiple times across the package. It would be good to have a single reference in the documentation and use
@inheritParams
elsewhere, and to pass variables via...
where appropriate rather than redefining which will make future extensions difficult.The text was updated successfully, but these errors were encountered: