Constantin Pape

I guess this is related to #1852, but for me ilastik is just killed and doesn't even throw a `MemoryError`.

Ok, so Ilastik doesn't get killed if I set the number of threads to 4, but then I run into a `MemoryError`. A different one than #1852 though (just copying...

Hmm, I tried reproducing it, but it also works for me now. Not sure what combination of layers I had activated where it didin't work. I also realized that I...

Following up here, I would have a bit more radical proposal: remove "Live Predict" completely and just have an update button that repredicts the edges and updates the multicut. I...

> sorry you ran into this. No worries, it's called `from experimental ...` after all ;). > also available as `ilastik-core` on ilastik-forge for experimental use) I have tried to...

> current vigra build (on conda-forge) is not compatible with numpy>1.19... I am not so sure about this, writing some comments about it in the other PR right now ;)

Ok, I figured out what's causing this: I have moved the project and so it couldn't find the path to the probabilities any more. This seems to cause this cascade...

Usiing a custom sigma also does not allow you to specify an anisotropic one: https://user-images.githubusercontent.com/4263537/153220159-f67874bf-e490-45c9-a58b-ff0b1f0e566b.mp4

Another example project for this issue is here: `/g/kreshuk/pape/MyProject3D.ilp`.

> This one is close to my heart - I'd say that the feature selection in multicut is my least favorite dialog and I'd really like to improve it: I...