Closed sgratzl closed 2 years ago
Name | Link |
---|---|
Latest commit | 420164a605fc026d59c61603deb1ba29babfd848 |
Latest deploy log | https://app.netlify.com/sites/cmu-delphi-covidcast/deploys/6271b810dd6bd60009f69293 |
Deploy Preview | https://deploy-preview-1164--cmu-delphi-covidcast.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Thanks for the fast turnaround. Unfortunately some things don't seem to work for me:
topline numbers for counties still say N/A for hospitalizations
choropleth map not showing anything for dates where it looks like we have data. Note now that we have county data, should be showing choropleth over counties not states (like all other signals---states was a special thing for HHS hospitalizations, before we had counties)
time series map showing very weird pattern of availability at the county level
time series map showing very weird pattern of availability at the county level
that is what the data seems to look like, see also https://api.covidcast.cmu.edu/epidata/covidcast/?signal=dsew-cpr%3Aconfirmed_admissions_covid_1d_prop_7dav&geo=county%3A42003&time=day%3A20220129-20220226&format=json&fields=value%2Cstderr%2Cgeo_type%2Cgeo_value%2Ctime_value
e.g. the last two entries:
which also explains the other observed behavior.
We're working on an interpolation fix to fill the gap at pipeline-time; this PR may need to be kept on hold until that is complete.
@dshemetov @korlaxxalrok When the interpolation fix for the county-level hospitalization signal is live, can one of you check the preview ("Browse the preview") to see that it's gone through as expected? (I checked just now and it hasn't yet.)
Once that's done, you could ping @sgratzl and I to confirm on this, and then I could look once more before we merge.
cc @duanecmu to help track.
@ryantibs county-level interpolation is live and looks good. Slack thread for the release.
Thanks! I played around with the main dashboard a bit and it looks good to me there as well.
@dshemetov @duanecmu @korlaxxalrok Can one of you play around with this between county, state, and national levels on the main dashboard as well to see that it all works are you expect?
Also, can you confirm: the earliest we have the county-level hospitalization data (from CPR) for is Dec 2020 or so? Because we have state and national hospitalization data (from HHS) going back earlier. See screenshot:
Also I realized that we don't describe (in the gray box data description box) the fact that at the county level, we're showing data from CPR. I believe it still says it's from HHS. We should fix this.
@krivard Can you please fix and/or delegate? Thank you!
Then, once fixed, and I hear back that at least one other person played with this staging dashboard, then I'm fine to merge (Katie you can approve yourself---it looks like it's on auto merge as soon as it's approved, so I won't approve yet).
Also, can you confirm: the earliest we have the county-level hospitalization data (from CPR) for is Dec 2020 or so?
The earliest Community Profile Report is dated 2020-12-17, but it does not include county-level hospital admissions. The first CPR including county-level hospital admissions is dated 2021-01-08, and includes the admissions count for the 7-day period ending 2021-01-07.
I checked all geo levels and it looks good:
(Great---thank you! So I think just the description is left.)
I'm going to go ahead and approve this since IIRC the description gets updated through a separate workflow.
@krivard I'm not sure what the current status of this PR is
(Thank you for checking Sam, I was also about to check on it right now!)
Just wanted to check to see if there were any status updates for this PR. Thanks!
@duanecmu you should be able to see the status updates:
This PR has been merged and will be deployed at the next release of www-covidcast. Would you like to do the honors?
Sure thing. I'll start the deployment today if that's OK.
closes #1139
Prerequisites:
dev
branchdev
Summary
option to override a signal with another one in the config for a specific geo level. The override is then patched in in both fetching the data and fetching the trend.
what is missing is adapting the text to notify the user about it at https://docs.google.com/document/d/1llv6xh8jMlmVv7WpyDSv4VgUpFAZQ6QjFUeRxxOinmk/edit#