-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add R21 PEV profiles #333
Add R21 PEV profiles #333
Conversation
Cherry-pick fixes for latest dqrng release.
The workflow runs on-demand by commenting `/benchmark` on any pull request. It runs a few iterations of both the base branch and the PR and posts the results back to the pull request as a comment. Additionally, detailed plots are available as images in the workflow artifacts. Unfortunately GitHub doesn't have a way for actions to upload images in comments. At the moment the workflow runs two benchmarks, one at a 10k population size and 10k time steps, and second one at 1M population size and 1k time steps. The workflow currently takes on the order of 1 hour to run. We can easily tweak the set of benchmarks in the future if we want to run more scenarios, or conversly if we want to reduce the total time. There is no long-term tracking of benchmark results yet. Doing so is tricky as the performance of the underlying CI is unlikely to be stable long-term.
It was merged into touchstone upstream.
I'm getting issues with 24.04 where pak installs some system packages with apt-get, some system services are upgraded and restarted and the CI runner is canceled. Not sure what the reason is, but 22.04 doesn't have this problem.
Add GitHub workflow for continuous benchmarking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! If you could run devtools::document()
and then add and commit the updated documentation, then it'll be ready.
Hi Giovanni, when I try to document it errors out-- maybe not worth investigating if anyone else can document and push that version successfully? Here's my traceback:
|
I've re-doc'd @lmhaile |
Very bizarre error message!.. |
Hi everyone,
Just pushing the R21 vaccine profiles to the dev branch, which @NoSchID has checked over. If there are any downstream changes needed also happy to make them.
Thanks!