AngusMcLure / PoolPoweR

Power and sample size calculations for surveys using pool testing (AKA group testing)
GNU General Public License v3.0
0 stars 1 forks source link

Throw warnings for some input variable ranges #3

Open fredjaya opened 8 months ago

fredjaya commented 8 months ago

Such as:

Will need to decide whether these should be in functions, depending on re-usability and need across functions.

AngusMcLure commented 8 months ago

Yes, most of the these should be warnings in most functions. Note that because we have functions calling functions and passing on some of these parameters, you might want to put the warning at just the first called function (or the last called function) to avoid getting the same warning twice (or more) for each function call. E.g. optimise_sN_prevalence works by calling optimise_s_prevalence repeatedly (and will use the same sensitivity, specificity, prevalence, and correlation across all these calls). So we'll need to think a bit carefully about where we put the warning

fredjaya commented 8 months ago

Adhere to the tidyverse style guide for error messages

AngusMcLure commented 8 months ago

Yes, this would be good. I hadn't read these before!

fredjaya commented 7 months ago

Refer to #27 for typical values