Last updated: 2020-08-26
Checks: 6 1
Knit directory: uci_covid_modeling/
This reproducible R Markdown analysis was created with workflowr (version 1.6.2). 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 file has unstaged changes. 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(20200727)
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 8d52b42. 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: .Rhistory
Ignored: .Rproj.user/
Untracked files:
Untracked: analysis/testing.Rmd
Unstaged changes:
Modified: analysis/index.Rmd
Modified: analysis/jun20_jul25.Rmd
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.
These are the previous versions of the repository in which changes were made to the R Markdown (analysis/index.Rmd
) and HTML (docs/index.html
) files. If you’ve configured a remote Git repository (see ?wflow_git_remote
), click on the hyperlinks in the table below to view the files as they were in that past version.
File | Version | Author | Date | Message |
---|---|---|---|---|
html | 8d52b42 | igoldsteinh | 2020-08-26 | more updates to website |
Rmd | 79a6fd6 | igoldsteinh | 2020-08-26 | updating about and license, experimenting with figure size |
Rmd | ddbef62 | igoldsteinh | 2020-08-26 | changing website layout |
html | ddbef62 | igoldsteinh | 2020-08-26 | changing website layout |
Rmd | 64adfeb | igoldsteinh | 2020-08-20 | cleaning up helper functions and index |
Rmd | 8abe830 | igoldsteinh | 2020-08-06 | fixed figure length, updated, tried a readme |
html | 8abe830 | igoldsteinh | 2020-08-06 | fixed figure length, updated, tried a readme |
Rmd | 99d68f7 | igoldsteinh | 2020-07-29 | bare bones report |
html | 99d68f7 | igoldsteinh | 2020-07-29 | bare bones report |
Rmd | 792b89a | vnminin | 2020-07-27 | Start workflowr project. |
The goal of this report is to inform interested parties about dynamics of SARS-CoV-2 spread in Orange County, CA and to predict (if feasible) the outbreak epidemic trajectory. Our approach is based on fitting a mechanistic model of SARS-CoV-2 spread to multiple sources of surveillance data. More specifically, we use daily numbers of new cases and deaths, while taking into account changes in the total number of tests reported on each day.
Since we rely on a mechanistic model, it is important to acknowledge limitations of this model. We will try to be transparent about our assumptions in the hope to receive feedback about their realism. So if something does not look right to you, please get in touch with us to help us improve our model.
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.
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.
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:
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.
We report estimated trajectories of latent cumulative deaths, incidence (i.e., total infections and deaths that have occurred by some prespecified time point), and prevalence . These trajectories represent our estimation of accumulation of unobserved/hidden number of infections and deaths in the Orange County population. We also project these three trajectories 4 weeks into the future.
Next we report prior and posterior distributions of key model parameters. Prior distributions represent our beliefs about these parameters before seeing/analyzing data. Posterior distributions encode our updated beliefs after seeing/analyzing data.
We report predictive distribution of observed deaths and positive test rate during the observation interval (blue shaded area with black dots in the plot below). In addition, we show a four week ahead forecast for both quantities. Our forecast assumes that interventions (physical distancing orders, mask recommendations, etc.) stay at the status quo, and that there are 2100 tests in each three day interval in the future. We plan to archive our forecasts and retrospectively measure their predictive ability/skill.
We examine how sensitive our conclusions about \(R_0\) to our prior assumptions by repeating estimation of all model parameters under different priors for this parameter. The priors are listed in the titles of the figures. Although the prior distribution of \(R_0\) does have some effect on its posterior (as it should), the our results and conclusions are not too sensitive to a particular specification of this prior.
We examine how sensitive our conclusions about \(R_0\) to our prior assumptions by repeating estimation of all model parameters under different priors for the parameter controlling how many people are not susceptible initially. This prior changes depending on the time period, so we adjust by changing the prior mean to be twice as large or one half as large as the default prior. As we would expect, changing this prior changes the number of people we estimate will become infected or are currently infectious. However, it seems to have little impact on the posterior of \(R_0\).
R version 4.0.2 (2020-06-22)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 18362)
Matrix products: default
locale:
[1] LC_COLLATE=English_United States.1252
[2] LC_CTYPE=English_United States.1252
[3] LC_MONETARY=English_United States.1252
[4] LC_NUMERIC=C
[5] LC_TIME=English_United States.1252
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] patchwork_1.0.1 scales_1.1.1 tidybayes_2.1.1 forcats_0.5.0
[5] stringr_1.4.0 dplyr_1.0.0 purrr_0.3.4 readr_1.3.1
[9] tidyr_1.1.0 tibble_3.0.3 ggplot2_3.3.2 tidyverse_1.3.0
[13] here_0.1 lubridate_1.7.9 workflowr_1.6.2
loaded via a namespace (and not attached):
[1] matrixStats_0.56.0 fs_1.4.2 RColorBrewer_1.1-2
[4] httr_1.4.1 rprojroot_1.3-2 rstan_2.21.2
[7] tools_4.0.2 backports_1.1.8 utf8_1.1.4
[10] R6_2.4.1 DBI_1.1.0 colorspace_1.4-1
[13] ggdist_2.2.0 withr_2.2.0 gridExtra_2.3
[16] tidyselect_1.1.0 prettyunits_1.1.1 processx_3.4.3
[19] curl_4.3 compiler_4.0.2 git2r_0.27.1
[22] cli_2.0.2 rvest_0.3.5 arrayhelpers_1.1-0
[25] xml2_1.3.2 labeling_0.3 callr_3.4.3
[28] digest_0.6.25 StanHeaders_2.21.0-5 rmarkdown_2.3
[31] pkgconfig_2.0.3 htmltools_0.5.0 dbplyr_1.4.4
[34] rlang_0.4.7 readxl_1.3.1 rstudioapi_0.11
[37] farver_2.0.3 generics_0.0.2 svUnit_1.0.3
[40] jsonlite_1.7.0 distributional_0.1.0 inline_0.3.15
[43] magrittr_1.5 loo_2.3.1 Rcpp_1.0.5
[46] munsell_0.5.0 fansi_0.4.1 lifecycle_0.2.0
[49] stringi_1.4.6 whisker_0.4 yaml_2.2.1
[52] pkgbuild_1.1.0 plyr_1.8.6 grid_4.0.2
[55] blob_1.2.1 parallel_4.0.2 promises_1.1.1
[58] crayon_1.3.4 lattice_0.20-41 haven_2.3.1
[61] hms_0.5.3 knitr_1.29 ps_1.3.3
[64] pillar_1.4.6 codetools_0.2-16 stats4_4.0.2
[67] reprex_0.3.0 glue_1.4.1 evaluate_0.14
[70] V8_3.2.0 RcppParallel_5.0.2 modelr_0.1.8
[73] vctrs_0.3.2 httpuv_1.5.4 cellranger_1.1.0
[76] gtable_0.3.0 assertthat_0.2.1 xfun_0.15
[79] broom_0.7.0 coda_0.19-3 later_1.1.0.1
[82] ellipsis_0.3.1