incorporate feedback pretrial

[avallecam]

Collects pending feedback in #19

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

The following changes were observed in the rendered markdown documents:

 config.yaml                                        |   2 +-
 delays-reuse.md                                    |  50 +++----
 fig/pkgs-hexlogos-2.png (new)                      | Bin 0 -> 622072 bytes
 ...ransmissibility-rendered-unnamed-chunk-17-1.png | Bin 31751 -> 31461 bytes
 ...ransmissibility-rendered-unnamed-chunk-18-1.png | Bin 30204 -> 30693 bytes
 ...ransmissibility-rendered-unnamed-chunk-21-1.png | Bin 85099 -> 84337 bytes
 md5sum.txt                                         |   8 +-
 quantify-transmissibility.md                       | 153 +++++++++++----------
 setup.md                                           |   4 +-
 9 files changed, 112 insertions(+), 105 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-08 16:56:40 +0000