You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occurs when saving an image as .mhd (therefore probably when using the ITK bindings) at a location where an image of the same name already exists. Correct behaviour would be the error message, that the target image already exists.
Does not appear when the -f flag is set.
Using nibabel as third party lib, the error did not occur.
Observed while calling: medpy_intensity_range_standardization.py adc.mhd --load-model model.pkl --save-images=tmp/ -vd
Issue could be repeated with medpy_convert.py, but this, as most scripts, does a previous internal check whether the target image exists and is therefore usually not affected by the bug (except in race conditions).
The text was updated successfully, but these errors were encountered:
Took a look at it and observed some strange behaviour. The error occurs in medpy.io.save module in the save(...) function at line 151 when calling: raise ImageSavingError('The target file {} already exists.'.format(filename))
I can not really see, why there should occur a core dump (which most likely is caused by itk) should be triggered here. Raising another type of exception lead to exactly the same problem.
Occurs when saving an image as .mhd (therefore probably when using the ITK bindings) at a location where an image of the same name already exists. Correct behaviour would be the error message, that the target image already exists.
Does not appear when the
-f
flag is set.Using nibabel as third party lib, the error did not occur.
Observed while calling:
medpy_intensity_range_standardization.py adc.mhd --load-model model.pkl --save-images=tmp/ -vd
Issue could be repeated with
medpy_convert.py
, but this, as most scripts, does a previous internal check whether the target image exists and is therefore usually not affected by the bug (except in race conditions).The text was updated successfully, but these errors were encountered: