ilastik 1.4.2b5 is out, and I'm really excited about this one.

The release highlights (www.ilastik.org/download#beta) should hopefully read as huge as this update already is in its very first beta release. Physical pixel size metadata, label explorer, up to 10x raw data viewing speedups 😱❤️‍🔥

Lol that soon™️ turned unto 6 months 😶 oh well, onwards! To Zurich!

Day 2 of #Zidas2025 is happening!

After a lecture from @ahklemm.bsky.social, it's now time for hands on with @ilastik-team.bsky.social by @benediktbest.bsky.social from Anna Kreshuk's lab and some tracking in the afternoon with #Trackmate from @jytinevez.bsky.social !

Protip for Python on Windows:

"Copy as path" from Windows Explorer has the issue that it copies "C:\Users\me\path" with single backslashes, which you cannot directly paste as a string in Python.

Unless you make it a raw string:

path = r"C:\Users\me\example.png" # yay, copy-paste works

Oh boy, big feature finally finished from my side (ok well e2e test still tbd but eh...). Time for review & release soon™️, I guesstimate another month. New beta already after stable 1.4.1 only just went out 🤣

If you have talented students in your team looking for a coding-heavy summer project, let them know that ilastik is participating in Google Summer of Code 2025! We are a sub-org under the Python Software Foundation. Come code with us as a (paid!) open source internship: github.com/btbest/gsoc-...

Miniforge giving me so much pain these last few days... And it seems all because I insisted that "conda now uses the mamba solver, so there's no reason to use mamba anymore".

I don't know why, but `conda install plotly` in my env consistently failed to solve, while `mamba` worked first try.

When an entire new feature just needs a few changes in one function