Skip to content
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

Support user specified/learnt from data CrIs #42

Open
seabbs opened this issue Oct 15, 2020 · 5 comments
Open

Support user specified/learnt from data CrIs #42

seabbs opened this issue Oct 15, 2020 · 5 comments

Comments

@seabbs
Copy link
Collaborator

seabbs commented Oct 15, 2020

In a recent update to EpiNow2 we have added user options around the credible intervals returned (epiforecasts/EpiNow2#105) this means that any number and range of credible intervals can now be returned (in the format lower_90, lower_50, lower_20, upper_20, upper_50, upper_90) with the default being the 20%, 50% and 90% CrI.

It would be good to support this feature in RtD3 as this is also a major blocker for other groups estimating Rt from adopting this package (as they are likely outputing (or want to visualise) different credible intervals)

@hamishgibbs
Copy link
Contributor

Agreed that this will improve the usability of the package for others not using the same CIs.

I will think how to best do this for an arbitrary number of CIs at arbitrary intervals. Will probably be some lookup for colours at x interval for the 3 time periods - We could select the colour for each time interval from a single CI to make the time series legend.

If the lower_ upper_ pattern is sure to be the same it will make things easier - could pass a color reference like {'ci':57, 'estimated':'green', 'estimated_b':'blue', 'forecast':'red'} then append the civalue to lower_ and upper_ pattern and visualise those values.

@hamishgibbs
Copy link
Contributor

@seabbs is the lower_ upper_ pattern sure to be the same?

@hamishgibbs
Copy link
Contributor

Probably best to do this - then release to CRAN - #17? Rather than releasing and then immediately releasing again.

@seabbs
Copy link
Collaborator Author

seabbs commented Oct 16, 2020

Yes from EpiNow2 it will be the same and obviously can make this a package requirement.

There is a helper function in (EpiNow2::extract_CrI) that pulls out the CrIs present which might be helpful or could provide some level of template for the R code.

@seabbs
Copy link
Collaborator Author

seabbs commented Oct 16, 2020

In terms of CRAN I think it is valid doing either. When first on CRAN can make frequent updates with no issue. Perhaps would be good to get it up and then deal with this for the next release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants