Tl;dr: *Please visit our new forum* at https://discuss.scientific-python.org/c/contributor/skimage and *click on the bell icon* to set your notification settings.
Dear scikit-image community,
This mailing list has been going for more than a decade, and we've had lots of good conversations here. It all started with the announcement of a new scikit <https://firstname.lastname@example.org/thread/3SQ4UO…> after the SciPy2009 sprints. It's been a fun journey!
But, times are changing and it's not clear that email lists are still the best place for discussion: newcomers to a thread cannot see its history and it is harder to share images, highlight markup, and browse long-running conversations. Besides, the new generation of contributors prefer more modern ways of communicating.
It is important that we have vibrant spaces where we can discuss (and enjoy discussing!) the project and its future. Thus, the core team has decided to switch from this mailing list to Discourse. Our communication channels will now be:
- User Q&A (how to use skimage): https://forum.image.sc/tag/scikit-image
*- Contribution / development discussion (previously this list!): **https://discuss.scientific-python.org/c/contributor/skimage*
- Chat: https://skimage.zulipchat.com/
Egor will keep monitoring this list, and will redirect requests as necessary.
Thank you for making this journey with us, and I hope to see y'all over at discuss.scientific-python.org!
Next up... skimage2! Stay tuned.
I would like to thank Marianne for updating our documentation to reflect best commit message practices. Please familiarize yourself with those changes:
Special kudos this month to Pradyumna Rahul and Fred Bunt for their stellar commit messages, even before the guidelines were published!
After a joint application by several projects (including scikit-image) NumFOCUS has made a grant which will fund Damián Avila to improve the PyData Sphinx theme. Proposed changes include a version switcher, better screen reader compatibility, dark mode, improved mobile support, and customized color schemes.
If you have any suggestions for improvements, you can file an issue here:
thank you for the great scikit-image library. I have encountered an error
when using the function skimage.filters.threshold_local:
threshold = skimage.filters.threshold_local(data, 7, method='gaussian',
line 209, in threshold_local
line 320, in check_nD
raise ValueError(msg_incorrect_dim % (arg_name, '-or-'.join([str(n) for
n in ndim])))
ValueError: The parameter `image` must be a 2-dimensional array
For my understanding, the 'image' can be N-dimensional, but why does it
give me the error? Do I misunderstand something? In my case, the 'data' is
a 3D image with dtype of 'float32', and the element values range from
'-2000' to '+2000'. Thank you in advance.
I notice that we've become a bit lax at writing proper commit messages. Especially with squash merges, it is now common to see in the long list of items like "polish things up a bit" and "more verbose".
What do you think is the best way of handling this?
Perhaps we should copy the PR description into the commit message, instead of having a list of random gibberish? Or maybe the first commit should have a detailed description, and then we simply cut the rest of the items from that list?
We are aiming to release scikit-image 1.0 near the end of the year. We are, however, planning to make a number of breaking changes in the API that will affect downstream libraries. We have published a proposal for how we plan to do this at https://bit.ly/skip-3. The gist of it is:
- we'll release 0.19 in the coming weeks.
- we'll release 0.20 immediately after, which will be exactly the same but with a warning to pin scikit-image to `<0.20` (for those that want to stay in 0.x land indefinitely) or `!=0.20.*` (for those that want to be "on the ball" when 1.0 is released and update their code as soon as possible).
- we'll publish a transition guide along with 1.0rc0, and maintain 0.19.x with bug fixes for another year to give users time to transition.
The document describes alternative approaches ("change the wheels on the bus while still driving it" or "make a new bus with a new name") and why the core team ultimately chose to promote the current approach. Nonetheless, scikit-image is committed to being a community-led project, so we are still gathering feedback and can make substantive modifications to the plan going forward. Please don't hesitate to voice your concerns so we can make the best choice for our entire community going forward!
I'm interested in contributing to scikit-image but I am new to scientific
programming. I studied physics in undergrad and have a minor in
bioinformatics. As a result, I'm familiar with oop, data structures, and
algorithms. I'd like some mentorship to get started on actually developing
/ contributing code. I'm interested in image processing for structural
biology applications, and sometimes in my spare time I write scripts for my
current company. However, it is not production-grade, and it is quite
hacky. I'm hoping that through contributing to scikit-image, in whatever
way possible, I can gain some skills and give back in parallel.
According to the scikit-image website, mentoring is available and it seems
like contributing to open source is encouraged. Would anyone be interested
in mentoring me?
Thank you for your time,