Add challenges and explanations on classes and modes for #55

[JasonJWilliamsNY]

Added explanation and new challenges to explain modes and classes.

[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/datacarpentry/genomics-r-intro/compare/md-outputs..md-outputs-PR-273

The following changes were observed in the rendered markdown documents:

 01-r-basics.md                                     | 111 +++++++++++++++++++--
 03-basics-factors-dataframes.md                    |  55 +++++++++-
 ...ataframes-rendered-unnamed-chunk-12-1.png (new) | Bin 0 -> 362 bytes
 ...tors-dataframes-rendered-unnamed-chunk-16-1.png | Bin 3688 -> 3685 bytes
 ...ataframes-rendered-unnamed-chunk-18-1.png (new) | Bin 0 -> 3688 bytes
 md5sum.txt                                         |   4 +-
 6 files changed, 157 insertions(+), 13 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-04-10 16:38:21 +0000

[naupaka]

Added some minor typos fixes and wording clarification. Thanks @JasonJWilliamsNY