View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002830||Slicer4||Core: MRML||public||2012-12-17 03:38||2017-06-14 13:09|
|Status||resolved||Resolution||unable to reproduce|
|Product Version||Slicer 4.2.0|
|Target Version||Fixed in Version|
|Summary||0002830: Error reading NRRD files|
The ERROR during loading nrrd data files. I loaded Slicer4 tutorial files MR-head.nrrd from the 3DVisualizationData dataset succesfully but I can`t load another files. For example, grayscale.nrrd from the tumorbase dataset. Only one difference between these files is endiannes.
OS Ubuntu 12.04 LTS.
ERROR: In /home/bks/Slicer/Libs/MRML/Core/vtkMRMLVolumeArchetypeStorageNode.cxx, line 317
ERROR: In /home/bks/Slicer/Libs/MRML/Core/vtkMRMLVolumeArchetypeStorageNode.cxx, line 367
|Tags||No tags attached.|
For the files that don't load: could you attach them to this bug report, and could you provide the steps you used to create them?
Sorry, its my mistake, the file size is 6Mb (a slightly bigger of limit).
I was able to read greyscale.nrrd on Windows fine.
I was just looking at this too - I was able to load all the files that I tried on a mac using slicer 4.2.2.
bks_2005: can you give us any more clues on how to reproduce the issue?
I use Ubuntu 12.04 LTS with latest update. This error appears only in the Ubuntu in different computers and Ubuntu configurations.
Steve, could you take a look or reassign to somebody with an access to Ubuntu
I tried loading nrrd volumes from the tumorbase data on a ubuntu 12.04 machine and had no problems.
Are you sure there's not something else going on? Do you get any diagnostic information in the error log window?
Since this tested okay on my Ubuntu (12.04) installation there must be something else going on. Do you have an ITK_AUTOLOAD_PATH or something similar set in your environment?
Ok, I am grateful to collegues! The ITK_AUTOLOAD_PATH variable is not defined in my enviroment. I think it must be path to ITK shared libraries location.
Yes, it may be something else in your path. If you run the following in the slicer python console it will show the environment and maybe we can debug with that:
import os; print(os.environ)
Most of the values are set by the slicer launcher.
Here's what I get on my Ubuntu 12.04 machine:
Had the same Problem with the stable Version. The nightly build works for me.
Reporter confirmed that it was fixed in a nightly version.
|2012-12-17 03:38||bks_2005||New Issue|
|2012-12-17 03:38||bks_2005||Status||new => assigned|
|2012-12-17 03:38||bks_2005||Assigned To||=> alexy|
|2012-12-18 02:56||pieper||Note Added: 0007516|
|2012-12-18 08:12||bks_2005||Note Added: 0007527|
|2012-12-18 09:14||alexy||Note Added: 0007531|
|2012-12-18 09:14||alexy||Assigned To||alexy => pieper|
|2012-12-18 09:16||pieper||Note Added: 0007532|
|2012-12-18 09:17||pieper||Assigned To||pieper => alexy|
|2012-12-18 18:34||bks_2005||Note Added: 0007553|
|2012-12-21 06:18||alexy||Note Added: 0007565|
|2012-12-21 06:18||alexy||Assigned To||alexy => pieper|
|2012-12-21 07:16||pieper||Note Added: 0007567|
|2012-12-27 05:34||pieper||Note Added: 0007588|
|2012-12-27 05:34||pieper||Status||assigned => feedback|
|2012-12-28 00:58||bks_2005||Note Added: 0007589|
|2012-12-28 03:51||pieper||Note Added: 0007590|
|2013-07-17 03:26||ango||Note Added: 0009094|
|2017-06-14 13:09||lassoan||Status||feedback => resolved|
|2017-06-14 13:09||lassoan||Resolution||open => unable to reproduce|
|2017-06-14 13:09||lassoan||Note Added: 0014838|