Comments (6)
Sorry yes, I missed that before. Done
from epinow2.
I have only put the timeout in the regional_epinow function which always returns a result set from the epinow call - this might mean we can sidestep the re-loading from disk issue.
from epinow2.
To give visibility of processes being killed this needs a mechanism to return the identity of any failures
from epinow2.
good news! Rstan does indeed seem to be killed and die.
bad news - funnily enough the summary processing doesn't handle missing data very well!
@seabbs do you have any feeling about how we should represent No Data Available / timeout in the estimate summary? I think the regional epinow route is using the out
object to hold the data so it doesn't re-load from disk, and it also has the full list of locations in the region.
from epinow2.
That is great news and yes I can imagine.
So at the moment, the expectation is that when read in from the out object subregions that have failed will have NULL
. These then get thrown away in regional_summary
and everything continues as normal. When using regional_summary
and reading in from disk I think it may be less fault-tolerant (with this bit of code:
Line 54 in fafb618
Line 113 in fafb618
NULL
in the output indicates any failure.
Could continue this for subregions that have been timed out with an informative log entry or add a message to the out object/into the results folder but this would then add a bit of a headache for results processing.
When saving it would make sense to save a killed due to time-out flag definitely.
When outputting results (we stick with this duality, by the way, to stay being CRAN compliant + acting like a normal package whilst also supporting saving to folders in order to make producing regional results more independent) we could add another list entry on the top level to the out
object. At the moment it has $regional
and $summary
. Could also add $timeout
and list subregions that have been timed out (could do the same thing for regions that have errored). If going with this approach I guess it would make sense to save this information into the summary folder (though that adds complexity in passing objects into regional_summary
whilst trying to maintain interoperability between reading in from disk and passing in objects).
Sorry - a bit of ramble - happy to clarify any of the above that is unclear.
from epinow2.
@seabbs Please could you add @JAllen42 so he can put a bit of work in on this? Thanks
from epinow2.
Related Issues (20)
- allcontributors still runs into errors, presumably too many requests when checking URLs
- add check for a finite maximum `max` to the new distribution inferface functions HOT 1
- Update `stan_sampling_opts()` documentation of `...`
- error with fixed delays in `estimate_secondary()` + `forecast_secondary()` workflow
- error in `plot.estimate_secondary()` to plot the output from `forecast_secondary()`
- out of range doubling/halving central estimate from confidence intervals reported with default but not "vb" method HOT 3
- Add forecasting and nowcasting courses to README HOT 1
- set seed in vignettes HOT 3
- Suggest installing `cmdstanr` HOT 2
- Update `touchstone` workflows HOT 1
- non-continuity between the estimated and forecast growth rate credible intervals HOT 6
- rename `tolerance`
- rename `fix_dist`
- `forecast_infections()` errors with `estimates` from `epinow()` run HOT 1
- Vignette on `estimate_infections()` examples has errors in code chunks HOT 2
- Test coverage action is very slow
- `bootstrapped_dist_fit` example produces warnings about too many samples
- Considerations for the responsible use of GitHub Actions HOT 10
- Overflow issues with `neg_binomial_2_rng` in variational bayes method HOT 1
- `pathfinder` fails for large case reports
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 epinow2.