Open maierl opened 7 years ago
Now I have a shorter workflow now that 100% reproduces that bug. At does behave quite strange, though. If I delete the nodes parallel with the Image Calculator, the error is gone. Are you still interested?
Here's a workflow with a already broken table. https://powerfolder.dkfz.de/dl/fiXKUhttBDXNJPfeYxeGBv7r/img_calc_fail_test.tar.gz
I'm also preparing a workflow that reproduces the process of breaking itself.
There it is. Both workflows just need to be executed to fail. You just need to adjust the image paths for the "splitter test fail" workflow, which fails only in batch mode.
I called it splitter fail because when the batch mode saves the results after execution and I load that, it fails to continue in the GUI. But when I've reset the Splitter, it executed successfully.
https://powerfolder.dkfz.de/dl/fiKRKwY5fSzNzvaH28Te3uzw/splitter_fail_test.tar.gz https://powerfolder.dkfz.de/dl/fiVefEYTMuxTsWJAMmt8f7gV/splitter_fail_test_images.tar.gz
Puh, this seems to be a tricky one - I'll take a look as soon as possible. Thanks for reporting
My workflow runs fine in the GUI, but in batch mode the Image Calculator fails. I'll try to extract an example workflow if necessary. Has anyone already seen that behavior?