Skip to content
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

Allow reporting delay to be applied to different date events #203

Open
joshwlambert opened this issue Feb 26, 2025 · 1 comment
Open

Allow reporting delay to be applied to different date events #203

joshwlambert opened this issue Feb 26, 2025 · 1 comment
Milestone

Comments

@joshwlambert
Copy link
Member

Currently the $date_reporting column is the date of symptom onset plus any user-specified reporting delay distribution. Given in real outbreak scenarios that the reporting date can be after symptom onset, hospital admission or outcome it would be useful to allow the user to adjust what the reporting delay is added to.

This can be added as a option in config, e.g. config$reporting_trigger = "onset", but could alternatively accept "admission" or "outcome".

@joshwlambert joshwlambert added this to the v0.5.0 milestone Feb 26, 2025
@joshwlambert
Copy link
Member Author

Pushing this feature to v0.6.0 because the package is now ready for a new release to get the new functionality (incl. messy_linelist() and truncate_linelist()) and bug fixes on CRAN and available to all users.

@joshwlambert joshwlambert modified the milestones: v0.5.0, v0.6.0 Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant