Fix issue 123

[Degoot-AM]

This PR addresses issue #123.

Fix #123
Fix #104

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

The following changes were observed in the rendered markdown documents:

 describe-cases.md                                  | 488 ++++++++++-----------
 ...ibe-cases-rendered-unnamed-chunk-10-1.png (new) | Bin 0 -> 6655 bytes
 ...be-cases-rendered-unnamed-chunk-11-1.png (gone) | Bin 13312 -> 0 bytes
 fig/describe-cases-rendered-unnamed-chunk-12-1.png | Bin 7643 -> 27793 bytes
 ...ibe-cases-rendered-unnamed-chunk-13-1.png (new) | Bin 0 -> 23159 bytes
 fig/describe-cases-rendered-unnamed-chunk-7-1.png  | Bin 5791 -> 6821 bytes
 fig/describe-cases-rendered-unnamed-chunk-8-1.png  | Bin 9477 -> 8971 bytes
 fig/describe-cases-rendered-unnamed-chunk-9-1.png  | Bin 6284 -> 8236 bytes
 md5sum.txt                                         |   4 +-
 9 files changed, 245 insertions(+), 247 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-10-01 02:10:07 +0000

[avallecam]

Thanks for the edits and working in to this! I'll do the merge 🚀