Difference between revisions of "Documentation/Nightly/Developers/FAQ/MRML"
From Slicer Wiki
m |
|||
| Line 21: | Line 21: | ||
</pre> | </pre> | ||
| − | Make sure the <code> | + | Make sure the <code>colorNodeRef</code> attribute is set on each <code>VolumeDisplay</code> node. |
Revision as of 13:53, 30 October 2013
Home < Documentation < Nightly < Developers < FAQ < MRML
|
For the latest Slicer documentation, visit the read-the-docs. |
Contents
MRML
What to do if you get 'No LookupTable was set but number of components in input doesn't match OutputFormat' when loading a MRML scene ?
If you get the following error messages:
ERROR: In /path/to/VTK/Imaging/vtkImageMapToColors.cxx, line 153 vtkImageMapToColors (0x268f190): RequestInformation: No LookupTable was set but number of components in input doesn't match OutputFormat, therefore input can't be passed through! ERROR: In /path/to/VTK/Imaging/vtkImageExtractComponents.cxx, line 239 vtkImageExtractComponents (0x26947e0): Execute: Component 1 is not in input. ERROR: In /path/to/VTK/Imaging/vtkImageExtractComponents.cxx, line 239 vtkImageExtractComponents (0x26947e0): Execute: Component 1 is not in input. [...]
Make sure the colorNodeRef attribute is set on each VolumeDisplay node.
