search

epiverse-trace / tutorials-late

https://epiverse-trace.github.io/tutorials-late/
Other
2 stars 0 forks source link

incorporate full review post-trial 03 and tutorials-late #42

Closed avallecam closed 3 weeks ago

avallecam commented 3 weeks ago

This PR aims to merge the full-repo review from #34

github-actions[bot] commented 3 weeks ago

Thank you!

Thank you for your pull request :smiley:

:robot: 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:

Rendered Changes

:mag: Inspect the changes: https://github.com/epiverse-trace/tutorials-late/compare/md-outputs..md-outputs-PR-42

The following changes were observed in the rendered markdown documents:

 fig/model-choices-rendered-unnamed-chunk-3-1.png | Bin 11510 -> 14677 bytes
 fig/model-choices-rendered-unnamed-chunk-4-1.png | Bin 9024 -> 9148 bytes
 md5sum.txt                                       |   6 +++---
 model-choices.md                                 |   2 +-
 modelling-interventions.md                       |   2 +-
 simulating-transmission.md                       |  26 ++++++++++++++---------
 6 files changed, 21 insertions(+), 15 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.

:stopwatch: Updated at 2024-06-11 19:03:32 +0000