Skip to content

Episode 6, Exercise 1 proposal: instance segmentation, semantic segmentation or object detection?#40

Open
marcodallavecchia wants to merge 4 commits into
carpentries-incubator:mainfrom
marcodallavecchia:mdv/ep06ex01-proposal
Open

Episode 6, Exercise 1 proposal: instance segmentation, semantic segmentation or object detection?#40
marcodallavecchia wants to merge 4 commits into
carpentries-incubator:mainfrom
marcodallavecchia:mdv/ep06ex01-proposal

Conversation

@marcodallavecchia
Copy link
Copy Markdown
Collaborator

This PR implements the exercise proposed in #15.

Briefly, I introduced 5 different scenarios that deal with images and some objects for a variety of goals. The students can individually or in small groups discuss and choose which approach between instance segmentation, semantic segmentation or object detection would be the best fit for the described scenario.

Remarks

  • I tried to keep it general and not bio-image specific as I thought it might be easier to develop an understanding with examples closer to a day-to-day experience.
  • I first tried to go through the image already present in the episodes/fig folder to keep the amount of new images to the minimum, but I still chose to introduce a couple of new ones with CC0 license.
  • I places this challenge at the top of the corresponding episode for now as all the main text already present introduces and focuses only on segmentation (via threshold etc..). I assume it could be moved where more appropriate later on if needed.
  • To keep consistency with the upstream original image-processing curriculum, I also integrated the small definition of segmentation introduced recently in this PR

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 29, 2026

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/bioimage-analysis-python/compare/md-outputs..md-outputs-PR-40

The following changes were observed in the rendered markdown documents:

 06-processing-segmentation.md | 77 ++++++++++++++++++++++++++++++++++++++++++-
 md5sum.txt                    |  2 +-
 2 files changed, 77 insertions(+), 2 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-05-29 12:09:40 +0000

@marcodallavecchia marcodallavecchia added the exercise-proposal Proposed exercises for the new curriculum label May 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

exercise-proposal Proposed exercises for the new curriculum

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant