latest version of lesson using "import imageio.v3 as iio" causes error about image-processing HOT 4 CLOSED

@uschille , a couple notes:

1. I went to try to make a fix here, but I couldn't find any examples where we weren't handling the error. Am I missing it somewhere?
2. The behavior/bug that leads to read-only images is changed in imageio as of v2.28.1 imageio/imageio#976. The latest is v2.31.1, so if the learner creates an environment themselves, they will likely get a version of imageio that doesn't have the bug.
3. The version of imageio that ships with the base Anaconda distribution is different for Windows and MacOS 😱. https://docs.anaconda.com/free/anaconda/reference/packages/pkg-docs/. Anaconda on Windows still has imageio v2.26.0 (weird read behavior), but Mac and Linux users get imageio v2.31.1 (consistent read behavior).

I suppose, in light of point 3, we need to keep the np.array(img) work-around for now, but I put in a request to have Anaconda bump the version for Windows to match Mac+Linux (ContinuumIO/anaconda-issues#13242). I have no idea what the constraints might be to doing that, so we shall see.

from image-processing.

Thanks for pointing this out @shaw2thefloor! The error can be avoided by adding maize = np.array(maize) after the line with iio.imread. It seems that I missed a few instances when implementing #247 - I will fix it as soon as I can. If you could point me to any other instances you found that would be a great help. Thank you!

from image-processing.

@deppen8 thanks for taking care of this!

@shaw2thefloor the latest version of the lesson reads:
"""

# read input image
maize_roots = iio.imread(uri="data/maize-root-cluster.jpg")
maize_roots = np.array(maize_roots)

# display original image
fig, ax = plt.subplots()
plt.imshow(maize_roots)

Now we can threshold the image and display the result.
PYTHON

# keep only high-intensity pixels
maize_roots[maize_roots < 128] = 0

"""
Does it run properly for you?

from image-processing.

I am going to close this since we believe the issue had been resolved now. @shaw2thefloor please post back here if you think there is still an issue here, and we'll be happy to re-open.

from image-processing.