@Florian Wuennemann On the topic of the cellpose 4 module update: It was noted in that PR that the container does not include the model weights. I've found this to be a big hassle in the past for cellpose (and mesmer)! It adds extra time to EVERY cellpose run for every sample in every pipeline run as the model weights aren't cached. People with network-restricted clusters will also be impacted as their compute nodes can't reach out to download the weights. Dynamic weights fetching also adds an extra point of failure, and this one has broken our GitHub Actions test runners multiple times when huggingface responds with a server error. When I created the separate mccellpose module (memory-efficient tile-by-tile processing) I built a container that does include the weights. I think cellpose 4 only has the one model now so one doesn't need to worry about different models as before, so the only concern is that the weights may be updated if the authors re-train.