Closed imagejan closed 7 years ago
Is there anything more I should try to get at the cause of this issue? It is blocking one of our groups here at FMI who want to read and annotate large datasets (a few GB each single volume image) and keep only the processed regions, so we're using the Don't Save nodes to avoid saving the original image data with every saved version of the workflow. Unfortunately, this is incompatible with the use of the Segment Cropper.
Hi @imagejan, I am looking at this bug today ~and hope I can fix it quickly.~ I fixed the bug sucessfully, the next nightly build should contain a fixed version of the Segment Cropper.
When using the Segment Cropper node inside a Don't Save Start/End loop, the workflow cannot be saved in an executed state. When you try to save the executed workflow, the following exceptions get thrown:
and
When trying to re-open the workflow, it is broken, i.e. the Segment Cropper is missing and the subsequent nodes are orphaned and therefore don't contain any data.
Here is an example workflow that reproduces the issue:
DontSave Bug SegmentCropper.zip
The result of re-saving the workflow in an executed state is this:
DontSave Bug SegmentCropper Executed.zip