Cfr explained

[Degoot-AM]

This PR adds explanation for the math behind CFR adjustment.

[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-middle/compare/md-outputs..md-outputs-PR-235

The following changes were observed in the rendered markdown documents:

 config.yaml (gone)                                 |   86 -
 create-forecast.md                                 |   46 +-
 data-covid-filter.R                                |    5 +-
 data-severity-static.R                             |    1 -
 data-severity-stratified.R                         |    2 +-
 delays-functions.md                                |   28 +-
 ...create-forecast-rendered-unnamed-chunk-10-1.png |  Bin 9592 -> 9562 bytes
 ...create-forecast-rendered-unnamed-chunk-12-1.png |  Bin 8571 -> 8358 bytes
 fig/create-forecast-rendered-unnamed-chunk-4-1.png |  Bin 46451 -> 44704 bytes
 ...unctions-rendered-unnamed-chunk-13-1.png (gone) |  Bin 5088 -> 0 bytes
 ...unctions-rendered-unnamed-chunk-16-1.png (gone) |  Bin 50215 -> 0 bytes
 ...elays-functions-rendered-unnamed-chunk-19-1.png |  Bin 51649 -> 49851 bytes
 ...unctions-rendered-unnamed-chunk-20-1.png (gone) |  Bin 30533 -> 0 bytes
 ...unctions-rendered-unnamed-chunk-21-1.png (gone) |  Bin 30140 -> 0 bytes
 ...elays-functions-rendered-unnamed-chunk-22-1.png |  Bin 52084 -> 51964 bytes
 ...elays-functions-rendered-unnamed-chunk-23-1.png |  Bin 30731 -> 30473 bytes
 ...ust-delays-rendered-unnamed-chunk-2-1.png (new) |  Bin 0 -> 5897 bytes
 ...ust-delays-rendered-unnamed-chunk-3-1.png (new) |  Bin 0 -> 17420 bytes
 ...ust-delays-rendered-unnamed-chunk-4-1.png (new) |  Bin 0 -> 5658 bytes
 ...ust-delays-rendered-unnamed-chunk-5-1.png (new) |  Bin 0 -> 15681 bytes
 ...ust-delays-rendered-unnamed-chunk-6-1.png (new) |  Bin 0 -> 19654 bytes
 ...ransmissibility-rendered-unnamed-chunk-10-1.png |  Bin 62183 -> 58635 bytes
 ...sibility-rendered-unnamed-chunk-17-1.png (gone) |  Bin 28343 -> 0 bytes
 ...sibility-rendered-unnamed-chunk-18-1.png (gone) |  Bin 32514 -> 0 bytes
 ...ransmissibility-rendered-unnamed-chunk-19-1.png |  Bin 28828 -> 28929 bytes
 ...ransmissibility-rendered-unnamed-chunk-20-1.png |  Bin 32358 -> 31655 bytes
 ...ssibility-rendered-unnamed-chunk-9-1.png (gone) |  Bin 9543 -> 0 bytes
 ...y-static-rendered-unnamed-chunk-10-1.png (gone) |  Bin 9896 -> 0 bytes
 ...everity-static-rendered-unnamed-chunk-18-1.png} |  Bin
 ...ty-static-rendered-unnamed-chunk-2-1.png (gone) |  Bin 6577 -> 0 bytes
 ...y-static-rendered-unnamed-chunk-21-1.png (gone) |  Bin 24151 -> 0 bytes
 ...y-static-rendered-unnamed-chunk-22-1.png (gone) |  Bin 24151 -> 0 bytes
 ...reading-estimate-rendered-unnamed-chunk-4-1.png |  Bin 5012331 -> 6571356 bytes
 intro-cfr-adjust-delays.md (new)                   |  721 +++
 md5sum.txt                                         |   37 +-
 network.html                                       |    6 +-
 quantify-transmissibility.md                       |   88 +-
 renv.lock (gone)                                   | 6172 --------------------
 severity-static.md                                 |   89 +-
 webshot.png                                        |  Bin 5012331 -> 6571356 bytes
 40 files changed, 863 insertions(+), 6418 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 2025-10-17 15:38:50 +0000

[avallecam]

Hi @Degoot-AM thanks for this contribution. I only complemented with formatting edits like making equations long instead of wide, one line about understimation factor on each time, showing a table on incident events.

this is ready to merge 🚀