add install box

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

The following changes were observed in the rendered markdown documents:

 ...eading-estimate-rendered-unnamed-chunk-10-1.png | Bin 4821 -> 15447 bytes
 ...-estimate-rendered-unnamed-chunk-11-1.png (new) | Bin 0 -> 4821 bytes
 ...-estimate-rendered-unnamed-chunk-14-1.png (new) | Bin 0 -> 16689 bytes
 ...g-estimate-rendered-unnamed-chunk-5-1.png (new) | Bin 0 -> 6101090 bytes
 ...reading-estimate-rendered-unnamed-chunk-9-1.png | Bin 15447 -> 4745 bytes
 md5sum.txt                                         |   2 +-
 network.html                                       |   6 ++--
 superspreading-estimate.md                         |  33 ++++++++++++++++-----
 webshot.png                                        | Bin 6719631 -> 6101090 bytes
 9 files changed, 30 insertions(+), 11 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-10-24 13:25:59 +0000