copy full review upcoming for preliminary merge

[avallecam]

copy of #19 to redirect commits to main and wait for any complementary commits in that branch

review in https://github.com/epiverse-trace/tutorials-early/tree/md-outputs-PR-43

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

The following changes were observed in the rendered markdown documents:

 delays-functions.md                                | 452 +++++++++++----------
 delays-reuse.md                                    | 229 ++++++-----
 ...functions-rendered-unnamed-chunk-16-1.png (new) | Bin 0 -> 50976 bytes
 ...functions-rendered-unnamed-chunk-17-1.png (new) | Bin 0 -> 52139 bytes
 ...elays-functions-rendered-unnamed-chunk-20-1.png | Bin 52059 -> 51341 bytes
 ...functions-rendered-unnamed-chunk-21-1.png (new) | Bin 0 -> 32834 bytes
 ...ays-reuse-rendered-unnamed-chunk-15-1.png (new) | Bin 0 -> 11595 bytes
 md5sum.txt                                         |   4 +-
 8 files changed, 370 insertions(+), 315 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-04-02 20:53:56 +0000