-
Notifications
You must be signed in to change notification settings - Fork 14
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
samples based on population #751
Comments
@corneliusroemer has also pointed out the less use of the "estimated cases" in #748. As for me, I totally agree that the "estimated cases" might be hidden and replaced by "estimated share" weighted by population. Exemple of some typical countries for the week 2023-02-06 to 2023-02-12:
It would be troublesome to simply weight the 70 million population in Thailand based on only 5 sequences in a week, so I think the number of uploaded sequences should also be considered by weighting to avoid problematic brought by too low number of sequences in some countries. However, excluding countries with e.g. less than 10 sequences would not be a good idea, since even a small number of uploaded sequences show at least some circulation of a variant in that place. Therefore, I propose weighted_base = min(population, uploaded_sequences*1,000,000), calculated for 7-day intervals. A Webpage may be created to illustrate the sequencing intensity of different countries and divisions, allowing easier comparison. |
Hi, I see an "estimated case" feature on cov-spectrum.
Given that countries have stopped most testing and no longer reporting the real number of cases, this feature seems redundant.
As countries are heading towards a new norm of ”rising sea level with high/low tide", their infection rate are circling around a constant at maybe 0.3-1% daily.
Under such circumstance, I guess an "estimated share among global population" that weights each sample with its corresponding regional population may be more useful.
A rough estimation of country-wise population can be extracted from
worldometers
The text was updated successfully, but these errors were encountered: