start path lesson

[drcandacemakedamoore]

Seperate pathology episode

[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/carpentries-incubator/medical-image-processing/compare/md-outputs..md-outputs-PR-71

The following changes were observed in the rendered markdown documents:

 config.yaml                     |   1 +
 environment_pathology.yml (new) |  19 ++++
 fig/path_metastasis.jpg (new)   | Bin 0 -> 73551 bytes
 fig/pyramid1.png (new)          | Bin 0 -> 762934 bytes
 fig/pyramid2.png (new)          | Bin 0 -> 845024 bytes
 fig/slideshow1.png (new)        | Bin 0 -> 1006157 bytes
 md5sum.txt                      |   5 +-
 pathology.md (new)              | 200 ++++++++++++++++++++++++++++++++++++++++
 setup.md                        |  33 ++++++-
 9 files changed, 255 insertions(+), 3 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-01-05 11:59:59 +0000

[drcandacemakedamoore]

This is also undergoing a content sanity check by a digital pathology expert (Moshe), who already pointed out we needed to mention Bioformats as it is very standard, open source, and has Python bindings.