-
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
Using Poisson glm to estimate growth rate #74
Comments
Thanks for this @ffinger really good point. I have addressed (by a straight conversion to the suggested Poisson) in 4303daa - does everything there look okay to you? Outside of this fn bootstrapping assuming normality so maybe need to change that as well? What do you think about the justification for using Poisson over QuasiPoisson or Negative binomial here? Thanks again - Sam |
Looks good to me, yes.
Agreed that overdispersion is likely, so certainly a good point. I don't know enough to be able to tell the advantage of each, other than that @thibautjombart, any specific reason you choose quasipoisson over NegBin for your application? |
Switched to Quasipoisson as I think no reason not to use it. |
Thanks for all the amazing work you are doing!
I just wanted to make you aware of a discussion regarding the estimation of growth rate and doubling time we had with @patrickbarks.
The way it is estimated here currently (and the way I have used for previous projects) is to use a log-linear model (linear model similar to
lm(log(incidence) ~ date)
. For the log to work you need to remove the 0s or replace them with a small positive value.A better way to estimate the growth rate would be to use a Poisson glm of the incident cases (
glm(incidence ~ date, family = poisson())
or similar). In addition to the more appropriate error model for count data this can handle 0s in the data natively.Here are some references:
https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-12-147#additional-information
https://besjournals.onlinelibrary.wiley.com/doi/10.1111/j.2041-210X.2010.00021.x
And here is how this is done in the R0 package (https://github.com/cran/R0/blob/master/R/est.R0.EG.R):
The text was updated successfully, but these errors were encountered: