-
Notifications
You must be signed in to change notification settings - Fork 3
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
Change fill_NA behaviour in prepare_data()
#100
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! I especially like the use of mock testing.
Changes look good to me. Would also be good to get a quick look from @jamesmbaazam as he is quoted in the issue being resolved.
Another point, not about the code, it would be good to have an informative PR title, even though it relates back to the issue which contains the details, having it also be self-describing is useful for time saving.
Taking a closer look at the code around the diffs in this PR and building on what I interpret from issue #82, I'm wondering what role the |
I think |
Thanks for taking a look. The idea with this function is primarily to help with the aggregation and pivoting of incidence2 objects. People fall into two camps with zero filling, and I'm trying to cater to both. Users who are certain that their data are robust to zero filling can stick with the default option. Users who would prefer to be conservative and retain NAs can do that, although they would require intermediate steps (removing NAs and splitting into contiguous date blocks) before passing the data to |
Co-authored-by: Joshua Lambert <joshua.lambert@lshtm.ac.uk>
Thanks both for taking a look, this will be merged once checks pass. |
This PR makes some small changes to
prepare_data()
to fix #82, and to allow mocked testing of an error message when {incidence2} is not installed.