Orange County, CA COVID Situation Report Jan 6, 2021 - Feb 10, 2021
Last updated: 2021-02-22
Checks: 6 1
Knit directory: uci_covid_modeling2/
This reproducible R Markdown analysis was created with workflowr (version 1.6.2.9000). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
The R Markdown is untracked by Git. To know which version of the R Markdown file created these results, you’ll want to first commit it to the Git repo. If you’re still working on the analysis, you can ignore this warning. When you’re finished, you can run wflow_publish to commit the R Markdown file and build the HTML.
Great job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.
The command set.seed(20201209) was run prior to running the code in the R Markdown file. Setting a seed ensures that any results that rely on randomness, e.g. subsampling or permutations, are reproducible.
Great job! Recording the operating system, R version, and package versions is critical for reproducibility.
Nice! There were no cached chunks for this analysis, so you can be confident that you successfully produced the results during this run.
Great job! Using relative paths to the files within your workflowr project makes it easier to run your code on other machines.
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.
The results in this page were generated with repository version 31485c4. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.
Note that you need to be careful to ensure that all relevant files for the analysis have been committed to Git prior to generating the results (you can use wflow_publish or wflow_git_commit). workflowr only checks the R Markdown file, but you know if there are other scripts or data files that it depends on. Below is the status of the Git repository when the results were generated:
Ignored files:
Ignored: .DS_Store
Ignored: .Rhistory
Ignored: .Rproj.user/
Ignored: analysis/.DS_Store
Ignored: code/.DS_Store
Ignored: code/.Rhistory
Ignored: code/models/.DS_Store
Ignored: code/models/model_death_reporting_delay/.DS_Store
Ignored: code/models/model_no_reporting_delay/.DS_Store
Ignored: code/results/.DS_Store
Ignored: code/results/2020-11-01_2020-12-06/.DS_Store
Ignored: code/results/2020-11-08_2020-12-13/.DS_Store
Ignored: code/results/2020-11-15_2020-12-20/.DS_Store
Ignored: code/results/2020-11-22_2020-12-27/.DS_Store
Ignored: code/results/2020-12-02_2021-01-06/.DS_Store
Ignored: code/results/2020-12-16_2021-01-20/.DS_Store
Ignored: code/results/2020-12-23_2021-01-27/.DS_Store
Ignored: data/.DS_Store
Ignored: data/from_OCHCA/
Ignored: renv/
Untracked files:
Untracked: alissa_missingness.R
Untracked: analysis/2021-01-06_2021-02-10.Rmd
Untracked: analysis/2021-01-06_2021-02-10_anaheim.Rmd
Untracked: analysis/2021-01-06_2021-02-10_irvine.Rmd
Untracked: analysis/2021-01-06_2021-02-10_santa-ana.Rmd
Untracked: code/results/2021-01-06_2021-02-10/
Unstaged changes:
Modified: analysis/_site.yml
Modified: code/models/model_death_reporting_delay/fit_new_model.R
Modified: code/results/2021-01-13_2021-02-17/anaheim/forecast.rds
Modified: code/results/2021-01-13_2021-02-17/anaheim/original.rds
Modified: code/results/2021-01-13_2021-02-17/forecast.rds
Modified: code/results/2021-01-13_2021-02-17/irvine/forecast.rds
Modified: code/results/2021-01-13_2021-02-17/irvine/original.rds
Modified: code/results/2021-01-13_2021-02-17/original.rds
Modified: code/results/2021-01-13_2021-02-17/santa-ana/forecast.rds
Modified: code/results/2021-01-13_2021-02-17/santa-ana/original.rds
Modified: code/update_site.R
Modified: data/data_for_calcat.csv
Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
There are no past versions. Publish this analysis with wflow_publish() to start tracking its development.
Orange County, CA COVID-19 Situation Report, February 15, 2021
Report period: Jan 06 - Feb 10 (we don’t use the most recent data due to reporting delays)
The goal of this report is to inform interested parties about dynamics of SARS-CoV-2 spread in Orange County, CA and to predict epidemic trajectories. Methodological details are provided below and in the accompanying manuscript. We are also contributing to COVID Trends by UC Irvine project that provides data visualizations of California County trends across time and space.
Summary (statements are made assuming 95% credibility levels)
- The number of reported cases (244,088, shown as black bars in the top-middle plot above) underestimates the actual number of infections by a factor that ranges between 4 and 11.3. This means that we estimate that the total number of infections which occurred by February 10, 2021 is between 982,255 and 2,747,475. We estimate that the total number of infections will be between 1,001,555 and 2,772,881 on March 12, 2021.
- Prevalence (number of infectious individuals at any time point) is decreasing and projected to be between 4,670 and 53,034 on March 12, 2021.
- Somewhere between 0.12% and 0.69% of all infections (not cases!) result in death.
- Basic reproductive number (\(R_0\)), defined as the average number of secondary infections one infectious individual produces in a completely susceptible population, is estimated to be between 0.3 and 1.9.
- Effective reproductive number (\(R_e\)), defined as its basic counterpart above, but allowing for some fraction of the population to be removed (recovered or deceased), is estimated to be between 0.1 and 0.5 on February 19, 2021. We want to keep \(R_e < 1\) in order to control virus transmission.
Note: We previously created a report using a similar model with a different implementation. Archives of the old report can be found here.
Abbreviated technical details (optional)
Our approach is based on fitting a mechanistic model of SARS-CoV-2 spread to multiple sources of surveillance data. A more fleshed out method description is in the manuscript.
Model inputs
Our method takes three time series as input: daily new tests, case counts, and deaths. However, we find daily resolution to be too noisy due to delay in testing reports, weekend effect, etc. So we aggregated/binned the three types of counts in 3 day intervals. These aggregated time series are shown below.
Model structure
We assume that all individuals in Orange County, CA can be split into 6 compartments: S = susceptible individuals, E = infected, but not yet infectious individuals, \(\text{I}_\text{e}\) = individuals at early stages of infection, \(\text{I}_\text{p}\) = individuals at progressed stages of infection (assumed 20% less infectious than individuals at the early infection stage), R = recovered individuals, D = individuals who died due to COVID-19. Possible progressions of an individual through the above compartments are depicted in the diagram below.
| Version | Author | Date |
|---|---|---|
| dcffe20 | Damon Bayer | 2020-12-16 |
Mathematically, we assume that dynamics of the proportions of individuals in each compartment follow a set of ordinary differential equations corresponding to the above diagram. These equations are controlled by the following parameters:
- Basic reproductive number (\(R_0\))
- mean duration of the latent period
- mean duration of the early infection period
- mean duration of the progressed infection period
- probability of transitioning from progressed infection to death, rather than to recovery (i.e., IFR)
We fit this model to data by assuming that case counts are noisy realizations of the actual number of individuals progressing from \(\text{I}_\text{e}\) compartment to \(\text{I}_\text{p}\) compartment. Similarly we assume that observed deaths are noisy realizations of the actual number of individuals progressing from \(\text{I}_\text{p}\) compartment to \(\text{D}\) compartment. A priori, we assume that death counts are significantly less noisy than case counts. We use a Bayesian estimation framework, which means that all estimated quantities receive credible intervals (e.g., 80% or 95% credible intervals). Width of these credible intervals encode the amount of uncertainty that we have in the estimated quantities.
Posterior Predictive Plots
R version 4.0.3 (2020-10-10)
Platform: x86_64-apple-darwin17.0 (64-bit)
Running under: macOS Big Sur 10.16
Matrix products: default
BLAS: /Library/Frameworks/R.framework/Versions/4.0/Resources/lib/libRblas.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/4.0/Resources/lib/libRlapack.dylib
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] patchwork_1.1.1 coda_0.19-4 cowplot_1.1.1 stemr_0.2.0
[5] glue_1.4.2 scales_1.1.1 tidybayes_2.3.1 forcats_0.5.1
[9] stringr_1.4.0 dplyr_1.0.4 purrr_0.3.4 readr_1.4.0
[13] tidyr_1.1.2 tibble_3.0.6 ggplot2_3.3.3 tidyverse_1.3.0
[17] fs_1.5.0 lubridate_1.7.9.2
loaded via a namespace (and not attached):
[1] Rcpp_1.0.6 lattice_0.20-41 odeintr_1.7.1
[4] assertthat_0.2.1 rprojroot_2.0.2 digest_0.6.27
[7] plyr_1.8.6 R6_2.5.0 cellranger_1.1.0
[10] backports_1.2.1 reprex_1.0.0 evaluate_0.14
[13] highr_0.8 httr_1.4.2 pillar_1.4.7
[16] rlang_0.4.10 readxl_1.3.1 rstudioapi_0.13
[19] whisker_0.4 rmarkdown_2.6 labeling_0.4.2
[22] munsell_0.5.0 broom_0.7.4 compiler_4.0.3
[25] httpuv_1.5.5 modelr_0.1.8 xfun_0.20
[28] pkgconfig_2.0.3 htmltools_0.5.1.1 tidyselect_1.1.0
[31] workflowr_1.6.2.9000 arrayhelpers_1.1-0 crayon_1.4.0
[34] dbplyr_2.1.0 withr_2.4.1 later_1.1.0.1
[37] ggdist_2.4.0 grid_4.0.3 distributional_0.2.2
[40] jsonlite_1.7.2 gtable_0.3.0 lifecycle_0.2.0
[43] DBI_1.1.1 git2r_0.28.0 magrittr_2.0.1
[46] cli_2.3.0 stringi_1.5.3 farver_2.0.3
[49] promises_1.1.1 xml2_1.3.2 ellipsis_0.3.1
[52] generics_0.1.0 vctrs_0.3.6 RColorBrewer_1.1-2
[55] tools_4.0.3 svUnit_1.0.3 hms_1.0.0
[58] yaml_2.2.1 colorspace_2.0-0 rvest_0.3.6
[61] knitr_1.31 haven_2.3.1