Documentation/Nightly/Developers/FAQ/MRML
From Slicer Wiki
Revision as of 20:26, 29 October 2013 by JChris.FillionR (talk | contribs) (Created page with '='''Developer FAQ: {{{1}}}'''= </includeonly> == What to do if you get 'No LookupTable was set but number of components in input doesn't match OutputFormat' when loading a MRML …')
Home < Documentation < Nightly < Developers < FAQ < MRML
Developer FAQ: {{{1}}}
</includeonly>
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 colorNodeID attribute is set on each VolumeDisplay node.
