search

datacarpentry / image-processing

Image Processing with Python
https://datacarpentry.org/image-processing
Other
99 stars 122 forks source link

More library name formatting #302

Closed tobyhodges closed 1 year ago

tobyhodges commented 1 year ago

Please briefly summarise the changes made in the pull request, and the reason(s) for making these changes.

This adjusts references to imageio in the lesson to fit the formatting convention we chose for other libraries in #288, based on how imageio is mentioned in the project's own documentation. It also fixes one reference to scikit-image that I missed in my first pass.

If any relevant discussions have taken place elsewhere, please provide links to these.

See https://github.com/datacarpentry/image-processing/pull/288#issuecomment-1721043612 for @mkcor's original comment that raised this.

github-actions[bot] commented 1 year ago

Thank you!

Thank you for your pull request :smiley:

:robot: 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

:mag: Inspect the changes: https://github.com/datacarpentry/image-processing/compare/md-outputs..md-outputs-PR-302

The following changes were observed in the rendered markdown documents:

 02-image-basics.md   | 10 +++++-----
 03-skimage-images.md |  8 ++++----
 md5sum.txt           |  4 ++--
 3 files changed, 11 insertions(+), 11 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.

:stopwatch: Updated at 2023-09-18 09:05:33 +0000