update local renv and packages: EpiNow2, cfr, epichains

[avallecam]

Fix #74
Fix #73
Fix #49
Fix #44
Fix #43
Fix #27
Fix #13
Fix #12

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 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:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

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

The following changes were observed in the rendered markdown documents:

 config.yaml (gone)                                 |   84 -
 create-forecast.md                                 |  337 ++-
 delays-access.md (new)                             |  970 ++++++++
 delays-functions.md (new)                          |  957 ++++++++
 ...create-forecast-rendered-unnamed-chunk-10-1.png |  Bin 10186 -> 9864 bytes
 ...forecast-rendered-unnamed-chunk-12-1.png (gone) |  Bin 8139 -> 0 bytes
 fig/create-forecast-rendered-unnamed-chunk-4-1.png |  Bin 50598 -> 48998 bytes
 ...ys-access-rendered-unnamed-chunk-15-1.png (new) |  Bin 0 -> 9568 bytes
 ...functions-rendered-unnamed-chunk-13-1.png (new) |  Bin 0 -> 5088 bytes
 ...functions-rendered-unnamed-chunk-16-1.png (new) |  Bin 0 -> 50708 bytes
 ...functions-rendered-unnamed-chunk-17-1.png (new) |  Bin 0 -> 52546 bytes
 ...functions-rendered-unnamed-chunk-20-1.png (new) |  Bin 0 -> 50381 bytes
 ...functions-rendered-unnamed-chunk-21-1.png (new) |  Bin 0 -> 31020 bytes
 ...ssibility-rendered-unnamed-chunk-11-1.png (new) |  Bin 0 -> 7102 bytes
 ...ssibility-rendered-unnamed-chunk-19-1.png (new) |  Bin 0 -> 29684 bytes
 ...ssibility-rendered-unnamed-chunk-20-1.png (new) |  Bin 0 -> 31050 bytes
 ...ssibility-rendered-unnamed-chunk-24-1.png (new) |  Bin 0 -> 72977 bytes
 ...issibility-rendered-unnamed-chunk-5-1.png (new) |  Bin 0 -> 5925 bytes
 ...issibility-rendered-unnamed-chunk-9-1.png (new) |  Bin 0 -> 9810 bytes
 ...severity-static-rendered-unnamed-chunk-19-1.png |  Bin 27448 -> 29023 bytes
 fig/severity-static-rendered-unnamed-chunk-9-1.png |  Bin 10346 -> 9896 bytes
 ...reading-estimate-rendered-unnamed-chunk-4-1.png |  Bin 7452292 -> 5876609 bytes
 ...reading-simulate-rendered-unnamed-chunk-1-1.png |  Bin 39727 -> 39692 bytes
 ...eading-simulate-rendered-unnamed-chunk-15-1.png |  Bin 37532 -> 37532 bytes
 ...eading-simulate-rendered-unnamed-chunk-20-1.png |  Bin 39727 -> 39692 bytes
 ...eading-simulate-rendered-unnamed-chunk-22-1.png |  Bin 11576 -> 10095 bytes
 ...reading-simulate-rendered-unnamed-chunk-4-1.png |  Bin 10931 -> 9197 bytes
 md5sum.txt                                         |   31 +-
 network.html                                       |    6 +-
 quantify-transmissibility.md (new)                 |  751 ++++++
 renv.lock (gone)                                   | 2386 --------------------
 setup.md                                           |   50 +-
 severity-static.md                                 |  229 +-
 superspreading-estimate.md                         |  109 +-
 superspreading-simulate.md                         |  380 ++--
 webshot.png                                        |  Bin 7452292 -> 5876609 bytes
 36 files changed, 3352 insertions(+), 2938 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.

⏱️ Updated at 2024-06-19 01:46:33 +0000