Keeping low intensity pixels

[JeremyPike]

I've made a few changes to this exercise to either make it easier for participants to follow or to correct some minor mistakes.
Instructions

1. Tell participants to load as grayscale rather than as a hint.
2. Hint now to look at cmap, vmin and vmax arguments for matplotlib.pyplot.imshow as these are needed and vmin and vmax havn't been introduced yet.

Solution

1. There are a few discrepancies/mistakes between the text and the code. Specifically the code dosn't load in grayscale, uses a different threshold value and incorrect vmin and vmax.
2. When copying the image array I assign to a new variable and display both original and modified images at the end. I think this is nice but not essential.

[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/image-processing/compare/md-outputs..md-outputs-PR-310

The following changes were observed in the rendered markdown documents:

 03-skimage-images.md | 25 ++++++++++++++++---------
 md5sum.txt           |  2 +-
 2 files changed, 17 insertions(+), 10 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 2023-12-11 11:16:47 +0000

[mkcor]

Thank you, @JeremyPike! I remember there were issues with this exercise and I guess its fixing was never completed... I like your changes and additions.

[JeremyPike]

Thank you, @JeremyPike! I remember there were issues with this exercises and I guess its fixing was never completed... I like your changes and additions.

Thank you @mkcor for the review and nice changes!

[mkcor]

Wonderful, @JeremyPike! Thanks again. In case you may not be aware of it, you can apply several suggestions at once, as a batch: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request#applying-suggested-changes