fix install chunk

[avallecam]

• Please check if the PR fulfills these requirements

• I have read the CONTRIBUTING guidelines
• Checks have been run locally and pass

[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-fr/compare/md-outputs..md-outputs-PR-21

The following changes were observed in the rendered markdown documents:

 create-forecast.md                                 |  37 ++++----
 delays-functions.md                                |  18 +++-
 ...create-forecast-rendered-unnamed-chunk-10-1.png | Bin 9601 -> 9582 bytes
 ...create-forecast-rendered-unnamed-chunk-12-1.png | Bin 8476 -> 8499 bytes
 fig/create-forecast-rendered-unnamed-chunk-4-1.png | Bin 46716 -> 46422 bytes
 ...elays-functions-rendered-unnamed-chunk-16-1.png | Bin 49378 -> 48704 bytes
 ...elays-functions-rendered-unnamed-chunk-17-1.png | Bin 50320 -> 50223 bytes
 ...elays-functions-rendered-unnamed-chunk-20-1.png | Bin 51965 -> 51133 bytes
 ...elays-functions-rendered-unnamed-chunk-21-1.png | Bin 30337 -> 30857 bytes
 ...ransmissibility-rendered-unnamed-chunk-10-1.png | Bin 56795 -> 61323 bytes
 ...ransmissibility-rendered-unnamed-chunk-19-1.png | Bin 29047 -> 28961 bytes
 ...ransmissibility-rendered-unnamed-chunk-20-1.png | Bin 32350 -> 31969 bytes
 ...everity-static-rendered-unnamed-chunk-10-1.png} | Bin
 ...everity-static-rendered-unnamed-chunk-17-1.png} | Bin
 ...severity-static-rendered-unnamed-chunk-2-1.png} | Bin
 ...everity-static-rendered-unnamed-chunk-26-1.png} | Bin
 ...eading-estimate-rendered-unnamed-chunk-10-1.png | Bin 15447 -> 4821 bytes
 ...estimate-rendered-unnamed-chunk-11-1.png (gone) | Bin 4821 -> 0 bytes
 ...ading-estimate-rendered-unnamed-chunk-13-1.png} | Bin
 ...g-estimate-rendered-unnamed-chunk-4-1.png (new) | Bin 0 -> 6206227 bytes
 ...-estimate-rendered-unnamed-chunk-5-1.png (gone) | Bin 7428224 -> 0 bytes
 ...g-estimate-rendered-unnamed-chunk-8-1.png (new) | Bin 0 -> 4745 bytes
 ...reading-estimate-rendered-unnamed-chunk-9-1.png | Bin 4745 -> 15447 bytes
 md5sum.txt                                         |  34 ++++----
 network.html                                       |   6 +-
 quantify-transmissibility.md                       |  97 +++++++++++----------
 severity-static.md                                 |  18 ++--
 superspreading-estimate.md                         |  21 ++---
 webshot.png                                        | Bin 7428224 -> 6206227 bytes
 29 files changed, 118 insertions(+), 113 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 2025-11-14 16:02:31 +0000