update episode content

[avallecam]

• use discrete distributions
• separate multiple from iterations
• fix and hide solutions

[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-206

The following changes were observed in the rendered markdown documents:

 ...reading-simulate-rendered-unnamed-chunk-1-1.png | Bin 39692 -> 46988 bytes
 ...eading-simulate-rendered-unnamed-chunk-19-1.png | Bin 4596 -> 22495 bytes
 ...-simulate-rendered-unnamed-chunk-23-1.png (new) | Bin 0 -> 4596 bytes
 ...-simulate-rendered-unnamed-chunk-24-1.png (new) | Bin 0 -> 46988 bytes
 ...eading-simulate-rendered-unnamed-chunk-26-1.png | Bin 8636 -> 11011 bytes
 ...-simulate-rendered-unnamed-chunk-29-1.png (new) | Bin 0 -> 4052 bytes
 ...-simulate-rendered-unnamed-chunk-30-1.png (new) | Bin 0 -> 10703 bytes
 md5sum.txt                                         |   2 +-
 superspreading-simulate.md                         | 388 ++++++++++++---------
 9 files changed, 220 insertions(+), 170 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-07-15 19:06:13 +0000