Comparing lossless versus lossy compression for Windows users

[JeremyPike]

The Comparing lossless versus lossy compression exercise does not work for Windows users who do not have a bash terminal with zip installed (I tried Git for Windows but zip not included). Here I've added a potential command line solution using Windows PowerShell.

[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-307

The following changes were observed in the rendered markdown documents:

 02-image-basics.md   | 10 ++++++----
 03-skimage-images.md |  6 +++---
 md5sum.txt           |  6 +++---
 setup.md             |  4 ++++
 4 files changed, 16 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-19 06:44:12 +0000

[tobyhodges]

Thanks for catching this, @JeremyPike. I like your proposed solution except that we do not list PowerShell in the setup instructions for the lesson.
If it would be needed only for this one, optional exercise, I suggest to add a note to the beginning of the exercise, stating that Windows users will need PowerShell installed to complete that exercise and linking to installation instructions.
If it is required for any other exercises/examples in the lesson, PowerShell should instead be added to the setup instructions.

[JeremyPike]

Thanks @tobyhodges, I'll leave this for now and come back to it once Ive gone through the rest of the course to see if Powershell would be useful elsewhere. I think modern versions of Windows (10 and newer) come shipped with some version of Powershell so in most cases no install would be required (but a link just in case wouldn't hurt).

[JeremyPike]

@tobyhodges so I only found one other terminal command in the course which I've added the Powershell equivalent command for. I've also added a note in the setup instructions but I would be surprised if anyone didn't have it installed by default. Note in JupterLab Windows users get Powershell if they open a terminal so that works nicely too :)

[mkcor]

Fine by me, @tobyhodges! I caught a few details which this PR only brought to my attention now.

[JeremyPike]

Fine by me, @tobyhodges! I caught a few details which this PR only brought to my attention now.

Thanks, all suggestions made :)