Comments (2)
I agree that measures of uncertainty would be important to add. Would your idea be to 1) store the raw data and construct summary statistics and CIs, or 2) to take them directly from the cited sources? For option (1) I think at the least we'd need to store the sample size alongside the estimates.
from epiparameter.
For now we only have the parameters or summary statistics reported in the papers and do not have any raw data to infer the parameters or CIs ourselves. Usually papers report the sample size which is indeed needed for bootstrapping the CIs.
I've added a basic function that calculates the confidence intervals of a summary statistic (https://github.com/epiverse-trace/epiparameter/blob/feature/ci/R/calc_ci.R). However, there is a new issue (I can open a new issue if that helps organise things).
The distribution assumed in the function is either a gamma, lognormal or weibull. However, in many studies reporting summary statistics or distribution parameters the distribution is right-truncated. This paper give a clear example of the differences between the standard distribution and the truncated form. Using the bootstrapping function to calculate the CIs for these values will be biased as it lacks the right truncation. Any ideas on how to solve this issue?
from epiparameter.
Related Issues (20)
- Plot PDF/CDF have misleading x-axis label for offspring distribution HOT 1
- Easily attach estimated distribution to epidist object HOT 3
- Epidists[[26]] - the parameter is termed as "generation time" but actually it is still serial interval HOT 1
- Function list_distributions() and convert_params_to_summary_stats() HOT 2
- Function plot() HOT 1
- Potential naming conflict HOT 5
- `as_epidist()` fails for infectious period from {epireview} HOT 5
- Allow `<epidist>` object to contain exponential distribution
- `as_epidist()` not showing up in website function reference HOT 2
- Release epiparameter 0.2.0 HOT 2
- Remove `<vb_epidist>` class and methods HOT 1
- Add units to parameter entries in the database and to `<epidist>` object
- Consistent use of `.` prefix for internal functions
- mpox incubation period discrepancy HOT 2
- Include author list in parameter database HOT 2
- Subsetting multiple entries in as_epidist
- Automatically adding author information to epidists from {epireview}
- `c.epidist()` method for `<epidist>`?
- Extraction of {epireview} parameters to provide consensus distribution
- Change from `validate_*()` to `assert_*()` HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from epiparameter.