fix delays error from epiparameter epinow2 conflict

[avallecam]

No description provided.

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

The following changes were observed in the rendered markdown documents:

 config.yaml (new)                                  |   86 +
 delays-reuse.md => delays-access.md                |    2 +-
 delays-functions.md                                |  106 +-
 ... delays-access-rendered-unnamed-chunk-15-1.png} |  Bin
 ...elays-functions-rendered-unnamed-chunk-16-1.png |  Bin 50497 -> 50991 bytes
 ...functions-rendered-unnamed-chunk-17-1.png (new) |  Bin 0 -> 52773 bytes
 ...functions-rendered-unnamed-chunk-20-1.png (new) |  Bin 0 -> 51082 bytes
 ...elays-functions-rendered-unnamed-chunk-21-1.png |  Bin 30718 -> 30827 bytes
 md5sum.txt                                         |    6 +-
 renv.lock (new)                                    | 2711 ++++++++++++++++++++
 10 files changed, 2833 insertions(+), 78 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-06-18 16:31:06 +0000