remove use of deprecated binary_erosion#123
Conversation
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:
Rendered Changes🔍 Inspect the changes: https://github.com/HealthBioscienceIDEAS/microscopy-novice/compare/md-outputs..md-outputs-PR-123 The following changes were observed in the rendered markdown documents: 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-06-04 14:26:21 +0000 |
|
Thanks @thompson318 - I'll go ahead and merge this. @stellaprins - just tagging you here so you are aware of this change (as it affects the segmentation episodes you'll be teaching next week) - this is a simple replacement of |
Auto-generated via `{sandpaper}`
Source : 621e5ef
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2026-06-05 12:55:05 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : 87f4e36
Branch : main
Author : Kimberly Meechan <24316371+K-Meech@users.noreply.github.com>
Time : 2026-06-05 12:52:57 +0000
Message : Merge pull request #123 from HealthBioscienceIDEAS/km/remove-binary-erosion
remove use of deprecated binary_erosion
Closes #121
binary_erosionhas been deprecated in the last skimage release. To avoid deprecation warnings (see issue), this PR removesbinary_erosionin favour oferosion. I checked and all segmentation results look the same.