search

epiverse-trace / tutorials-middle

https://epiverse-trace.github.io/tutorials-middle/
Other
3 stars 1 forks source link

use multiple chain summary to count threshold #71

Closed avallecam closed 2 months ago

avallecam commented 2 months ago

FIx #70

github-actions[bot] commented 2 months 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-middle/compare/md-outputs..md-outputs-PR-71

The following changes were observed in the rendered markdown documents:

 ...eading-simulate-rendered-unnamed-chunk-19-1.png | Bin 39727 -> 4596 bytes
 ...-simulate-rendered-unnamed-chunk-20-1.png (new) | Bin 0 -> 39727 bytes
 ...-simulate-rendered-unnamed-chunk-22-1.png (new) | Bin 0 -> 11576 bytes
 ...eading-simulate-rendered-unnamed-chunk-25-1.png | Bin 8636 -> 4052 bytes
 ...-simulate-rendered-unnamed-chunk-26-1.png (new) | Bin 0 -> 8636 bytes
 md5sum.txt                                         |   2 +-
 superspreading-simulate.md                         |  48 ++++++++++++++++++---
 7 files changed, 44 insertions(+), 6 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-05-04 01:15:46 +0000