search

epiverse-trace / tutorials-middle

https://epiverse-trace.github.io/tutorials-middle/
Other
3 stars 1 forks source link

fix `EpiNow2::forecast_secondary()` and `EpiNow2::plot.estimate_secondary()` #93

Closed avallecam closed 1 month ago

avallecam commented 1 month ago

fix #91

github-actions[bot] commented 1 month ago

Thank you!

Thank you for your pull request :smiley:

:robot: This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

Rendered Changes

:mag: Inspect the changes: https://github.com/epiverse-trace/tutorials-middle/compare/md-outputs..md-outputs-PR-93

The following changes were observed in the rendered markdown documents:

 config.yaml (new)                                  |   86 +
 create-forecast.md                                 |  112 +-
 ...create-forecast-rendered-unnamed-chunk-10-1.png |  Bin 9884 -> 9603 bytes
 ...-forecast-rendered-unnamed-chunk-12-1.png (new) |  Bin 0 -> 5674 bytes
 ...-forecast-rendered-unnamed-chunk-13-1.png (new) |  Bin 0 -> 8671 bytes
 fig/create-forecast-rendered-unnamed-chunk-4-1.png |  Bin 49107 -> 49329 bytes
 md5sum.txt                                         |    2 +-
 renv.lock (new)                                    | 2419 ++++++++++++++++++++
 8 files changed, 2564 insertions(+), 55 deletions(-)
What does this mean? If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

:stopwatch: Updated at 2024-06-19 13:32:23 +0000