-
Notifications
You must be signed in to change notification settings - Fork 17
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
Truncation in UK test positive estimates. #88
Comments
Yes - add |
Great - yes I think that is a good idea but as you say low priority. |
This is now critical. Looking at the UK page it appears that Rt is decreasing for test-positive cases. We need to know if this is due to truncation or is a real signal. @kathsherratt any progress on data changes? @joeHickson can you open a dummy PR indicating how to set truncation for just UK data sets (each one likely needs to be different). Unfortunately, I am on annual leave until Thursday so not available but happy to make these changes/do the exploration if no one else has any time. |
Aims to address issue #88 by increasing truncation to 5 days in the UK test-positive cases data. Deaths and admissions Rts don't look like they are suffering the same issue so no changes there. Discussed this with @sbfnk, where we reviewed UK data and recent estimates of delays from test to report in a large UK study. Decision was to truncate at 5 days: truncation at 3 days looks insufficient, 4 days is enough to capture most of the data, plus 1 day feed through into the public PHE dataset. @joeHickson - from what I can see in the code it looks like all I need to do here is add an extra `truncation` parameter, that gets fed through into the cleaning functions (where the default param is set to 3). I have opened this PR to do this - would that work? (Great if so!)
raised the tangent as #102 |
yes! thanks for work on this everyone. |
Looking at UK test positive estimates looks like delay to report has increased and our real time estimates are now biased downwards in some regions. @kathsherratt have you seen any data changes? May need to increase the time lag for this dataset only in order to avoid this for now. @joeHickson that should be possible now right?
The text was updated successfully, but these errors were encountered: