: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:
The following changes were observed in the rendered markdown documents:
create-forecast.md | 106 +++------
data/covid_360days.rds (new) | Bin 0 -> 12023 bytes
delays-access.md | 198 +++++++++-------
delays-functions.md | 87 +++----
...create-forecast-rendered-unnamed-chunk-10-1.png | Bin 9606 -> 9588 bytes
...create-forecast-rendered-unnamed-chunk-12-1.png | Bin 5674 -> 8635 bytes
...forecast-rendered-unnamed-chunk-13-1.png (gone) | Bin 8760 -> 0 bytes
fig/create-forecast-rendered-unnamed-chunk-4-1.png | Bin 48953 -> 49159 bytes
...elays-functions-rendered-unnamed-chunk-16-1.png | Bin 50811 -> 50806 bytes
...elays-functions-rendered-unnamed-chunk-17-1.png | Bin 52553 -> 52047 bytes
...elays-functions-rendered-unnamed-chunk-20-1.png | Bin 49547 -> 50466 bytes
...elays-functions-rendered-unnamed-chunk-21-1.png | Bin 30714 -> 33460 bytes
....png => quantify-transmissibility-regional.png} | Bin
...ssibility-rendered-unnamed-chunk-10-1.png (new) | Bin 0 -> 69250 bytes
...sibility-rendered-unnamed-chunk-11-1.png (gone) | Bin 7102 -> 0 bytes
...ssibility-rendered-unnamed-chunk-18-1.png (new) | Bin 0 -> 29998 bytes
...ransmissibility-rendered-unnamed-chunk-19-1.png | Bin 30454 -> 30371 bytes
...sibility-rendered-unnamed-chunk-20-1.png (gone) | Bin 30622 -> 0 bytes
...transmissibility-rendered-unnamed-chunk-9-1.png | Bin 9810 -> 9543 bytes
...y-static-rendered-unnamed-chunk-19-1.png (gone) | Bin 29023 -> 0 bytes
...ty-static-rendered-unnamed-chunk-20-1.png (new) | Bin 0 -> 24187 bytes
...reading-estimate-rendered-unnamed-chunk-4-1.png | Bin 6139555 -> 6447234 bytes
md5sum.txt | 34 +--
network.html | 6 +-
quantify-transmissibility.md | 245 +++++++-------------
severity-static.md | 251 +++++++++------------
superspreading-estimate.md | 16 +-
superspreading-simulate.md | 58 ++---
webshot.png | Bin 6139555 -> 6447234 bytes
29 files changed, 442 insertions(+), 559 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.
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-middle/compare/md-outputs..md-outputs-PR-141
The following changes were observed in the rendered markdown documents:
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-11-21 16:30:16 +0000