Enhance clean-data.Rmd with discussion on R functions

[avallecam]

Added discussion section to explore alternative diagnostic and cleaning methods in R.

• Please check if the PR fulfills these requirements

• I have read the CONTRIBUTING guidelines
• I created a new feature branch
• I have opened and refer to an issue or I am referring to an existing issue
• Lesson builds locally
• Checks have been run on GitHub and pass
• No output errors in the Rendered Changes link generated by github-actions

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Update from last delivery

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

The following changes were observed in the rendered markdown documents:

 clean-data.md     |   18 +-
 config.yaml (new) |   82 +
 md5sum.txt        |    4 +-
 renv.lock (new)   | 6799 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 6899 insertions(+), 4 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 2026-09-28 10:36:35 +0000