#include <vtkVolumeMapper.h>
Inheritance diagram for vtkVolumeMapper:
vtkVolumeMapper is the abstract definition of a volume mapper. Several basic types of volume mappers are supported. There are ray casters, which produce an image that must be merged with geometry, there are hardware methods that blend with geometry, and some combinations of these.
Definition at line 64 of file vtkVolumeMapper.h.
|
Reimplemented from vtkAbstractMapper3D. Reimplemented in vtkMesaVolumeRayCastMapper, vtkMesaVolumeTextureMapper2D, vtkOpenGLVolumeProVG500Mapper, vtkOpenGLVolumeProVP1000Mapper, vtkOpenGLVolumeRayCastMapper, vtkOpenGLVolumeTextureMapper2D, vtkVolumeProMapper, vtkVolumeProVG500Mapper, vtkVolumeProVP1000Mapper, vtkVolumeRayCastMapper, vtkVolumeTextureMapper, and vtkVolumeTextureMapper2D. Definition at line 67 of file vtkVolumeMapper.h. |
|
Definition at line 192 of file vtkVolumeMapper.h. |
|
|
|
|
|
|
Return 1 if this class type is the same type of (or a subclass of) the named class. Returns 0 otherwise. This method works in combination with vtkTypeRevisionMacro found in vtkSetGet.h. Reimplemented from vtkAbstractMapper3D. Reimplemented in vtkMesaVolumeRayCastMapper, vtkMesaVolumeTextureMapper2D, vtkOpenGLVolumeProVG500Mapper, vtkOpenGLVolumeProVP1000Mapper, vtkOpenGLVolumeRayCastMapper, vtkOpenGLVolumeTextureMapper2D, vtkVolumeProMapper, vtkVolumeProVG500Mapper, vtkVolumeProVP1000Mapper, vtkVolumeRayCastMapper, vtkVolumeTextureMapper, and vtkVolumeTextureMapper2D. |
|
Return 1 if this class is the same type of (or a subclass of) the named class. Returns 0 otherwise. This method works in combination with vtkTypeRevisionMacro found in vtkSetGet.h. Reimplemented from vtkAbstractMapper3D. Reimplemented in vtkMesaVolumeRayCastMapper, vtkMesaVolumeTextureMapper2D, vtkOpenGLVolumeProVG500Mapper, vtkOpenGLVolumeProVP1000Mapper, vtkOpenGLVolumeRayCastMapper, vtkOpenGLVolumeTextureMapper2D, vtkVolumeProMapper, vtkVolumeProVG500Mapper, vtkVolumeProVP1000Mapper, vtkVolumeRayCastMapper, vtkVolumeTextureMapper, and vtkVolumeTextureMapper2D. |
|
|
Methods invoked by print to print information about the object including superclasses. Typically not called by the user (use Print() instead) but used in the hierarchical print process to combine the output of several classes. Reimplemented from vtkAbstractMapper3D. Reimplemented in vtkMesaVolumeRayCastMapper, vtkMesaVolumeTextureMapper2D, vtkOpenGLVolumeProVG500Mapper, vtkOpenGLVolumeProVP1000Mapper, vtkOpenGLVolumeRayCastMapper, vtkOpenGLVolumeTextureMapper2D, vtkVolumeProMapper, vtkVolumeProVG500Mapper, vtkVolumeProVP1000Mapper, vtkVolumeRayCastMapper, vtkVolumeTextureMapper, and vtkVolumeTextureMapper2D. |
|
Update the volume rendering pipeline by updating the scalar input Implements vtkAbstractMapper3D. Reimplemented in vtkVolumeTextureMapper. |
|
Set/Get the input data |
|
Set/Get the input data |
|
Does the data have independent components, or do some define color only? If IndependentComponents is On (the default) then each component will be independently passed through a lookup table to determine RGBA, shaded, and then combined with the other components using the ComponentBlendMode. Some volume Mappers can handle 1 to 4 component unsigned char or unsigned short data (see each mapper header file to determine functionality). If IndependentComponents is Off, then you must have either 2 or 4 componenet data. For 2 component data, the first is passed through the first color tranfser function and the second component is passed through the first opacity transfer function. Normals will be generated off of the second component. For 4 component data, the first three will directly represent RGB (no lookup table). The fourth component will be passed through the first scalar opacity transfer function for opacity. Normals will be generated from the fourth component. |
|
Does the data have independent components, or do some define color only? If IndependentComponents is On (the default) then each component will be independently passed through a lookup table to determine RGBA, shaded, and then combined with the other components using the ComponentBlendMode. Some volume Mappers can handle 1 to 4 component unsigned char or unsigned short data (see each mapper header file to determine functionality). If IndependentComponents is Off, then you must have either 2 or 4 componenet data. For 2 component data, the first is passed through the first color tranfser function and the second component is passed through the first opacity transfer function. Normals will be generated off of the second component. For 4 component data, the first three will directly represent RGB (no lookup table). The fourth component will be passed through the first scalar opacity transfer function for opacity. Normals will be generated from the fourth component. |
|
Does the data have independent components, or do some define color only? If IndependentComponents is On (the default) then each component will be independently passed through a lookup table to determine RGBA, shaded, and then combined with the other components using the ComponentBlendMode. Some volume Mappers can handle 1 to 4 component unsigned char or unsigned short data (see each mapper header file to determine functionality). If IndependentComponents is Off, then you must have either 2 or 4 componenet data. For 2 component data, the first is passed through the first color tranfser function and the second component is passed through the first opacity transfer function. Normals will be generated off of the second component. For 4 component data, the first three will directly represent RGB (no lookup table). The fourth component will be passed through the first scalar opacity transfer function for opacity. Normals will be generated from the fourth component. |
|
Does the data have independent components, or do some define color only? If IndependentComponents is On (the default) then each component will be independently passed through a lookup table to determine RGBA, shaded, and then combined with the other components using the ComponentBlendMode. Some volume Mappers can handle 1 to 4 component unsigned char or unsigned short data (see each mapper header file to determine functionality). If IndependentComponents is Off, then you must have either 2 or 4 componenet data. For 2 component data, the first is passed through the first color tranfser function and the second component is passed through the first opacity transfer function. Normals will be generated off of the second component. For 4 component data, the first three will directly represent RGB (no lookup table). The fourth component will be passed through the first scalar opacity transfer function for opacity. Normals will be generated from the fourth component. |
|
If we have more than 1 independent components, how will the resulting RGBA values be combined? Add: R = R1 + R2, G = G1 + G2, B = B1 + B2, A = A1 + A2 MaxOpacity: A1 >= A2 then R = R1, G = G1, B = B1, A = A1 A2 > A1 then R = R2, G = G2, B = B2, A = A2 |
|
If we have more than 1 independent components, how will the resulting RGBA values be combined? Add: R = R1 + R2, G = G1 + G2, B = B1 + B2, A = A1 + A2 MaxOpacity: A1 >= A2 then R = R1, G = G1, B = B1, A = A1 A2 > A1 then R = R2, G = G2, B = B2, A = A2 |
|
If we have more than 1 independent components, how will the resulting RGBA values be combined? Add: R = R1 + R2, G = G1 + G2, B = B1 + B2, A = A1 + A2 MaxOpacity: A1 >= A2 then R = R1, G = G1, B = B1, A = A1 A2 > A1 then R = R2, G = G2, B = B2, A = A2 Definition at line 109 of file vtkVolumeMapper.h. References ComponentBlendAdd. |
|
If we have more than 1 independent components, how will the resulting RGBA values be combined? Add: R = R1 + R2, G = G1 + G2, B = B1 + B2, A = A1 + A2 MaxOpacity: A1 >= A2 then R = R1, G = G1, B = B1, A = A1 A2 > A1 then R = R2, G = G2, B = B2, A = A2 Definition at line 111 of file vtkVolumeMapper.h. References ComponentBlendMaxOpacity. |
|
Turn On/Off orthogonal cropping. (Clipping planes are perpendicular to the coordinate axes.) |
|
Turn On/Off orthogonal cropping. (Clipping planes are perpendicular to the coordinate axes.) |
|
Turn On/Off orthogonal cropping. (Clipping planes are perpendicular to the coordinate axes.) |
|
Turn On/Off orthogonal cropping. (Clipping planes are perpendicular to the coordinate axes.) |
|
Set/Get the Cropping Region Planes ( xmin, xmax, ymin, ymax, zmin, zmax ) These planes are defined in volume coordinates - spacing and origin are considered. |
|
Set/Get the Cropping Region Planes ( xmin, xmax, ymin, ymax, zmin, zmax ) These planes are defined in volume coordinates - spacing and origin are considered. |
|
Set/Get the Cropping Region Planes ( xmin, xmax, ymin, ymax, zmin, zmax ) These planes are defined in volume coordinates - spacing and origin are considered. |
|
Set/Get the Cropping Region Planes ( xmin, xmax, ymin, ymax, zmin, zmax ) These planes are defined in volume coordinates - spacing and origin are considered. |
|
Get the cropping region planes in voxels. Only valid during the rendering process |
|
Get the cropping region planes in voxels. Only valid during the rendering process |
|
Set the flags for the cropping regions. The clipping planes divide the volume into 27 regions - there is one bit for each region. The regions start from the one containing voxel (0,0,0), moving along the x axis fastest, the y axis next, and the z axis slowest. These are represented from the lowest bit to bit number 27 in the integer containing the flags. There are several convenience functions to set some common configurations - subvolume (the default), fence (between any of the clip plane pairs), inverted fence, cross (between any two of the clip plane pairs) and inverted cross. |
|
Set the flags for the cropping regions. The clipping planes divide the volume into 27 regions - there is one bit for each region. The regions start from the one containing voxel (0,0,0), moving along the x axis fastest, the y axis next, and the z axis slowest. These are represented from the lowest bit to bit number 27 in the integer containing the flags. There are several convenience functions to set some common configurations - subvolume (the default), fence (between any of the clip plane pairs), inverted fence, cross (between any two of the clip plane pairs) and inverted cross. |
|
Set the flags for the cropping regions. The clipping planes divide the volume into 27 regions - there is one bit for each region. The regions start from the one containing voxel (0,0,0), moving along the x axis fastest, the y axis next, and the z axis slowest. These are represented from the lowest bit to bit number 27 in the integer containing the flags. There are several convenience functions to set some common configurations - subvolume (the default), fence (between any of the clip plane pairs), inverted fence, cross (between any two of the clip plane pairs) and inverted cross. Definition at line 151 of file vtkVolumeMapper.h. References VTK_CROP_SUBVOLUME. |
|
Set the flags for the cropping regions. The clipping planes divide the volume into 27 regions - there is one bit for each region. The regions start from the one containing voxel (0,0,0), moving along the x axis fastest, the y axis next, and the z axis slowest. These are represented from the lowest bit to bit number 27 in the integer containing the flags. There are several convenience functions to set some common configurations - subvolume (the default), fence (between any of the clip plane pairs), inverted fence, cross (between any two of the clip plane pairs) and inverted cross. Definition at line 153 of file vtkVolumeMapper.h. References VTK_CROP_FENCE. |
|
Set the flags for the cropping regions. The clipping planes divide the volume into 27 regions - there is one bit for each region. The regions start from the one containing voxel (0,0,0), moving along the x axis fastest, the y axis next, and the z axis slowest. These are represented from the lowest bit to bit number 27 in the integer containing the flags. There are several convenience functions to set some common configurations - subvolume (the default), fence (between any of the clip plane pairs), inverted fence, cross (between any two of the clip plane pairs) and inverted cross. Definition at line 155 of file vtkVolumeMapper.h. References VTK_CROP_INVERTED_FENCE. |
|
Set the flags for the cropping regions. The clipping planes divide the volume into 27 regions - there is one bit for each region. The regions start from the one containing voxel (0,0,0), moving along the x axis fastest, the y axis next, and the z axis slowest. These are represented from the lowest bit to bit number 27 in the integer containing the flags. There are several convenience functions to set some common configurations - subvolume (the default), fence (between any of the clip plane pairs), inverted fence, cross (between any two of the clip plane pairs) and inverted cross. Definition at line 157 of file vtkVolumeMapper.h. References VTK_CROP_CROSS. |
|
Set the flags for the cropping regions. The clipping planes divide the volume into 27 regions - there is one bit for each region. The regions start from the one containing voxel (0,0,0), moving along the x axis fastest, the y axis next, and the z axis slowest. These are represented from the lowest bit to bit number 27 in the integer containing the flags. There are several convenience functions to set some common configurations - subvolume (the default), fence (between any of the clip plane pairs), inverted fence, cross (between any two of the clip plane pairs) and inverted cross. Definition at line 159 of file vtkVolumeMapper.h. References VTK_CROP_INVERTED_CROSS. |
|
Return bounding box (array of six floats) of data expressed as (xmin,xmax, ymin,ymax, zmin,zmax). Implements vtkAbstractMapper3D. |
|
Return bounding box (array of six floats) of data expressed as (xmin,xmax, ymin,ymax, zmin,zmax). Reimplemented from vtkAbstractMapper3D. Definition at line 167 of file vtkVolumeMapper.h. References vtkAbstractMapper3D::GetBounds(). |
|
WARNING: INTERNAL METHOD - NOT INTENDED FOR GENERAL USE Reimplemented in vtkVolumeRayCastMapper, and vtkVolumeTextureMapper. Definition at line 175 of file vtkVolumeMapper.h. Referenced by vtkVolumeTextureMapper::GetGradientMagnitudeScale(), and vtkVolumeRayCastMapper::GetGradientMagnitudeScale(). |
|
WARNING: INTERNAL METHOD - NOT INTENDED FOR GENERAL USE Reimplemented in vtkVolumeRayCastMapper, and vtkVolumeTextureMapper. Definition at line 176 of file vtkVolumeMapper.h. Referenced by vtkVolumeTextureMapper::GetGradientMagnitudeBias(), and vtkVolumeRayCastMapper::GetGradientMagnitudeBias(). |
|
WARNING: INTERNAL METHOD - NOT INTENDED FOR GENERAL USE Reimplemented in vtkVolumeRayCastMapper, and vtkVolumeTextureMapper. Definition at line 177 of file vtkVolumeMapper.h. |
|
WARNING: INTERNAL METHOD - NOT INTENDED FOR GENERAL USE Reimplemented in vtkVolumeRayCastMapper, and vtkVolumeTextureMapper. Definition at line 178 of file vtkVolumeMapper.h. |
|
WARNING: INTERNAL METHOD - NOT INTENDED FOR GENERAL USE DO NOT USE THIS METHOD OUTSIDE OF THE RENDERING PROCESS Render the volume Implemented in vtkMesaVolumeTextureMapper2D, vtkOpenGLVolumeTextureMapper2D, vtkVolumeProMapper, vtkVolumeProVG500Mapper, vtkVolumeProVP1000Mapper, vtkVolumeRayCastMapper, vtkVolumeTextureMapper, and vtkVolumeTextureMapper2D. |
|
WARNING: INTERNAL METHOD - NOT INTENDED FOR GENERAL USE Release any graphics resources that are being consumed by this mapper. The parameter window could be used to determine which graphic resources to release. Reimplemented from vtkAbstractMapper. Reimplemented in vtkVolumeRayCastMapper. Definition at line 190 of file vtkVolumeMapper.h. |
|
The default behaviour is to use a vtkImageClip on the input to ensure it is the right size. Allow the user to turn that behaviour off. |
|
The default behaviour is to use a vtkImageClip on the input to ensure it is the right size. Allow the user to turn that behaviour off. |
|
The default behaviour is to use a vtkImageClip on the input to ensure it is the right size. Allow the user to turn that behaviour off. |
|
The default behaviour is to use a vtkImageClip on the input to ensure it is the right size. Allow the user to turn that behaviour off. |
|
|
|
Definition at line 213 of file vtkVolumeMapper.h. |
|
Definition at line 214 of file vtkVolumeMapper.h. |
|
Definition at line 215 of file vtkVolumeMapper.h. |
|
Definition at line 216 of file vtkVolumeMapper.h. |
|
Definition at line 220 of file vtkVolumeMapper.h. |
|
Definition at line 223 of file vtkVolumeMapper.h. |
|
Definition at line 225 of file vtkVolumeMapper.h. |
|
Definition at line 228 of file vtkVolumeMapper.h. |
|
Definition at line 229 of file vtkVolumeMapper.h. |