I am a new user and I apologize for my English, I am trying to do my best to explain.
When I save my work, all files that get created after segmentation, export it, etc. Then I can’t open them and appear the following error message:
Slicer has caught an internal error.
You may be able to continue from this point, but results are undefined.
Suggested action is to save your work and restart.
If you have a repeatable sequence of steps that causes this message, please report the issue following instructions available at http://slicer.org
The message detail is:
Exception thrown in event: D:\D\blablabla:
itk::ERROR: NrrdImageIO(000001E7F3BD21E0): ReadImageInformation: Error reading C:/blabla/Segmentation.seg.nrrd:
[nrrd] nrrdLoad: trouble reading "C:/blabla/Segmentation.seg.nrrd"
[nrrd] nrrdRead: trouble
[nrrd] _nrrdRead: trouble reading NRRD file
[nrrd] _nrrdFormatNRRD_read: trouble parsing space directions info |(-0,70703125,-0,0) (-0,-0,70703125,-0) (0,0,5)|
[nrrd] _nrrdReadNrrdParse_space_directions: trouble getting space vector 1 of 3
[nrrd] _nrrdSpaceVectorParse: space dimension is 3, but seem to have 4 coefficients
What I am doing wrong? Is there any way to open or load them?
Thanks you very much in advance!
It seems that your locale is set so that comma (
,) character is used as decimal mark and for some reason the NRRD file writer uses this locale-specific mark, instead of the standard dot (
Can you upload the Segmentation.seg.nrrd file that you are trying to read?
What operating system do you use? What language/regional setting is selected in the operating system?
Does it work correctly if you use latest nightly version of Slicer (4.9.x version)?
I am using latest nightly version for Windows 10. But it is already resolved.
What I have done is to change the format of these files .nrrd for .vkt which is compatible. Then, when I load the folder on Slicer, I dont check files .png, .py nor the scene created by the programme. Immediatly, I load the DICOM and import the segmentation which I want to edit, within the module Segmentations. It is already to work!
I have the same problem, but the above solution by @Laura_CM does not work for me. Could you kindly suggest what could be done here?
I’m running Slicer 4.11.0 2020-05-30 pre-release on a Windows 10 machine.
Thank you in advance.
I decided to do the segmenting again from scratch. Luckily, I had only few segmentations affected by this issue.
So for me it is solved.