Class SoDataSet
- All Implemented Interfaces:
SafeDisposable
- Direct Known Subclasses:
SoVolumeData
SoVolumeData, SoHeightFieldGeometry, SoHeightFieldProperty, etc. Those nodes provide the data for VolumeViz rendering nodes: SoVolumeRender, SoOrthoSlice, SoObliqueSlice, etc. See SoVolumeData for more details about loading and managing volume data.
The data set can be specified by:
- Setting the
fileNamefield
This implies that the data set is stored on disk, in one of the file formats for which LDM has a built-in reader. LDM will automatically select a reader based on the file extension, for example ".am" for the AmiraMesh file format. - Calling the
setReader()method
This is the most general method because an application can specify one of the standard LDM readers or implement a customized subclass ofSoVolumeReader. LDM will get the data set properties (dimensions, size, data type, etc) and access the data through the specified reader object. This allows the application to completely control how, and from where, the data is loaded.
SoDataSetId, SoDataCompositor, SoVolumeData, SoMeshGeometry, SoMeshProperty
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic enumSupported data type.classDeprecated.static enumSpecifies an image type: segmented or not segmented.Nested classes/interfaces inherited from class com.openinventor.inventor.nodes.SoNode
SoNode.RenderModesNested classes/interfaces inherited from class com.openinventor.inventor.Inventor
Inventor.ConstructorCommand -
Field Summary
FieldsModifier and TypeFieldDescriptionfinal SoSFBoolIndicates if resource allocation is done only on first render traversal or as soon as the node is created.final SoSFInt32final SoSFLDMDataTransformIf set to an appropriateSoLDMDataTransformobject, the object's transformFunction method is called after each tile is loaded, but before it is stored in main memory.final SoSFBox3fThe real size (extent) of the volume in modeling coordinates.final SoSFFilePathStringIndicates the file location containing the data set.Contains anSoLDMResourceParametersobject which allows you to set LDM resource parameters.final SoSFUShortFor scalar (non-RGBA) data, specifies the size of voxel values on the GPU in bits.final SoSFDoubleSpecifies the data value that should be considered undefined and therefore not rendered.final SoSFBoolControls use of OpenGL lossy texture compression for RGBA data (if available).Specifies if this dataset corresponds or does not correspond to a segmented image.Fields inherited from class com.openinventor.inventor.Inventor
VERBOSE_LEVEL, ZeroHandle -
Method Summary
Modifier and TypeMethodDescriptionvoidcallback(SoCallbackAction action) static intdataSize(SoDataSet.DataTypes dataType) Returns the number of bytes per voxel of the specified data type.voidinteditBoxes(Collection<SbVec3i32> boxCenters, int boxSize, double newValue) Replace all voxels in the region defined by a list of boxes with the specified value.inteditSolidShape(SoNode solidShape, double value) Replaces all voxels intersecting the given shape with the specified value.inteditSubVolume(SbBox3i32 subVolume, double value) Replaces the contents of a subvolume with the specified value.inteditSubVolume(SbBox3i32 subVolume, SoBufferObject userData) Replaces the contents of a subvolume with the given data.inteditSurfaceShape(SoNode surfaceShape, float thickness, double value) Replaces all voxels intersecting the polygons or lines defined by the surfaceShape and given thickness with the specified value.inteditTile(SoLDMTileID tileId, double value) Replaces the contents of a tile with the specified value.inteditTile(SoLDMTileID tileId, SoBufferObject userData) Replaces the contents of a tile with the given data.booleanfinishEditing(int transactionId) Terminates an editing transaction.voidgetBoundingBox(SoGetBoundingBoxAction action) intReturns the number of bytes per voxel in VolumeViz.Returns the data type.intReturns the number of bytes per voxel.Returns the data set dimension.double[]Returns min and max values of the data set.Returns a reference to theSoLDMDataAccessobject.Returns a pointer to the current data set reader object.Returns the LDMTopoOctree used by thisSoDataSet.static intReturns the maximum number of data sets that can be render composited on the current hardware (essentially the number of texture units - 1).long[]Returns min and max values of the data set data.intDeprecated.As of Open Inventor 9.0.0.0.Returns the current data set reader object.Returns the tile dimension.voidGLRender(SoGLRenderAction action) voidhandleEvent(SoHandleEventAction action) booleanReturns true if DataSet has edited tiles.static booleanisDataFloat(SoDataSet.DataTypes dataType) Returns true if the given data type is a float data type.booleanisDataInMemory(SoLDMTileID tileID) Indicates whether the data attached to a tile is in main memory.static booleanisDataSigned(SoDataSet.DataTypes dataType) Returns true if the given data type is a signed integer data type.booleanisInMemory(SoLDMTileID tileID) Indicates whether a tile is in main memory.intReturns the number of significant bits.voidpick(SoPickAction action) voidreadTile(SoLDMTileID tileID, SoBufferObject buffer, boolean transform) Copies the specified tile into the provided buffer.booleanredoEditing(int transactionId) Redo all modifications associated with the specified transaction id.voidResets previously set custom reader setup by setReader call.booleanCommit all transactions.voidsetLDMDataModifier(SoDataSet.LDMDataModifier transformer) Deprecated.As of Open Inventor 9.9, should usedataTransformfield instead.voidsetLDMReader(SoLDMReader reader) Sets the LDM volume reader object to use.voidsetReader(SoVolumeReader reader) Calls setReader(reader, false).voidsetReader(SoVolumeReader reader, boolean takeOwnership) This method allows the data to be read directly from the disk using the specified subclass ofSoVolumeReader.intInitiate an editing transaction.booleanundoEditing(int transactionId) Undo all modifications associated with the specified transaction id.voiduseFakeData(SoLDMTileID name_10609, SoBufferObject name_10610) Creates fake data in buffer.voxelToXYZ(SbBox3f box) Converts the specified box in voxel coordinates (I,J,K) to geometric coordinates (X,Y,Z).voxelToXYZ(SbVec3f dataPosition) Converts the specified point in voxel coordinates (I,J,K) to geometric coordinates (X,Y,Z).voidwrite(SoWriteAction action) voidwriteTile(SoLDMTileID tileID, SoBufferObject buffer, SoVolumeWriter writer) Write the specified tile using the specified writer.XYZToVoxel(SbBox3f xyzBox) Converts the specified box in geometric coordinates to voxel coordinates.XYZToVoxel(SbVec3f dataPosition) Converts the specified point in geometric coordinates (X,Y,Z) to voxel coordinates (I,J,K).Methods inherited from class com.openinventor.inventor.nodes.SoNode
affectsState, copy, copy, distribute, getAlternateRep, getByName, getMatrix, getPrimitiveCount, getRenderEngineMode, getRenderUnitID, GLRenderBelowPath, GLRenderInPath, GLRenderOffPath, grabEventsCleanup, grabEventsSetup, isBoundingBoxIgnoring, isOverride, rayPick, search, setOverride, touchMethods inherited from class com.openinventor.inventor.fields.SoFieldContainer
copyFieldValues, copyFieldValues, enableNotify, fieldsAreEqual, get, getAllFields, getEventIn, getEventOut, getField, getFieldName, hasDefaultValues, isNotifyEnabled, set, setToDefaultsMethods inherited from class com.openinventor.inventor.misc.SoBase
dispose, getName, isDisposable, isSynchronizable, setName, setSynchronizableMethods inherited from class com.openinventor.inventor.Inventor
getNativeResourceHandle
-
Field Details
-
dataSetId
When using multipleSoDataSetnodes, thedataSetIdfield uniquely identifies each data set used in the compositing. It also specifies the OpenGL texture unit in which the textures for this data set will be stored when doing render compositing. It is 1 by default (texture unit 0 is reserved for the color lookup table by default). The number of available texture units depends on your hardware. You can query this number usinggetMaxNumDataSets.Note: The
SoDataSetIdnode can also be used to define dataSetId. If anSoDataSetIdnode is traversed before theSoDataSetnode, the id from theSoDataSetIdnode is used and this field is ignored.- Since:
- Open Inventor 6.0
-
fileName
Indicates the file location containing the data set. Default is an empty string. Depending on the file type, the correspondingSoVolumeReader(if it exists) is used.File Extension Loader Class Description .am SoVRAmFileReaderAmira Mesh file format .dc3, .dic, .dicom SoVRDicomFileReaderDicom file format .fld SoVRAvsFileReaderAVS field file format .lda or .ldm SoVRLdmFileReaderLarge Data Management file format .sgy or .segy SoVRSegyFileReaderSEG Y revision 1 file format .vol SoVRVolFileReaderVol file format .vox SoVRVoxFileReaderVox file format .lst SoVRRasterStackReaderLst file format The filename extension is not case sensitive.
Note:
SoDataSetand its derived classes (SoVolumeData, etc) do not search theSoInputdirectory list to find files specified in this field. To check file existence and other properties theSbFileHelperclass may be useful. -
useCompressedTexture
Controls use of OpenGL lossy texture compression for RGBA data (if available). Default is true.A significant advantage of compressed textures is that they conserve texture memory space. At the moment, the extension works on RGBA textures only, not on paletted textures. The compression factor is about 5.
A potential drawback of compressed textures is that lossy compression can result in values on the GPU that are slightly different from the actual value in the volume. For example "gray scale" colors could have a slight color in some cases. You should always set this option to false when using "RGBA" data to store 32-bit "id" values.
-
texturePrecision
For scalar (non-RGBA) data, specifies the size of voxel values on the GPU in bits. The valid values are: 0 (default), 8 and 16.
When set to 0, LDM chooses the best precision based on the size of the data type (or if specified, the number of significant bits) - meaning that LDM will store 8-bit values on the GPU for 8-bit data and store 16-bit values for all other data types.There are several trade-offs influenced by this value, including:
- 8 bit values use less memory on the GPU than 16-bit values, allowing more data to be stored on the GPU. 8-bit values are adequate for many visualization tasks. But...
- If the specified (or chosen) precision is smaller than the data type, then LDM must
scale down the data values before sending them to the GPU.
- Limitation: This is currently unavoidable for 32-bit data.
- Down scaling adds some time whenever a tile of data must be sent to the GPU.
- In particular, all tiles currently stored on the GPU must be
rescaled if the application changes the data range (
SoDataRangenode).
Note: As a result, changing the data range may be slow for large volumes. - Down scaling also means "aliasing" data values, i.e. multiple data values may scale to the same value on the GPU.
- Since:
- Open Inventor 6.0
-
-
extent
The real size (extent) of the volume in modeling coordinates. Default is -1,-1,-1 to 1,1,1.Note this can be used to define a volume with non-uniform voxel spacing. For example, if the volume dimensions (voxels) are 64x64x64, but the voxel spacing in Z is twice the X and Y spacing, then you might specify the volume size as -1 to 1 for X and Y but -2 to 2 for Z.
-
dataTransform
If set to an appropriateSoLDMDataTransformobject, the object's transformFunction method is called after each tile is loaded, but before it is stored in main memory. This allows you to modify the original data (for example, scaling or filtering) before it is displayed. Default is no transform.Note: Before Open Inventor 8.0, the data transformFunction was set using the setLDMDataModifier method. That method is now deprecated.
- Since:
- Open Inventor 8.0
-
allocateResourceOnRender
Indicates if resource allocation is done only on first render traversal or as soon as the node is created. Default is true. It must be set to false if the dataset is not inserted in a scene graph but will be used for data access for example. Otherwise, memory resources will still remain on default value. -
undefinedValue
Specifies the data value that should be considered undefined and therefore not rendered.
By default, this field is set to NaN (Not a Number), meaning that no specific value is excluded.
Otherwise, the value must match the data type.
Limitations: There are several limitations in order for the undefined value to work:
- The texturePrecision must be at least equal to the number of significant bits of the data type.
- The data type must be BYTE, SHORT (either SIGNED or UNSIGNED) or FLOAT
- The field is ignored in the following classes :
SoHeightFieldProperty,SoHeightFieldPropertyMaskandSoVolumeMask. Setting this field has no effect in these cases.
Note: If the application uses custom shaders, particularly when overriding the VVizComputeFragmentColor() function:
- Undefined values are handled in the GLSL function VVizTransferFunction().
- If the voxel value is undefined, VVizTransferFunction() returns the RGBA value 0,0,0,0. You may return this value for your undefined value.
- If the application's shader does not call VVizTransferFunction() (e.g. voxel color is computed without using a colormap), the application's shader must explicity check for undefined values. This can be done using the function VVizIsUndefined()
- Since:
- Open Inventor 10.11
valueInterpretation
This field is only useful if the SoVolumeShape.interpolation type used by the rendering is either LINEAR or CUBIC. For other types of interpolation, this field is ignored and the data set is always considered as continuous. This field is also ignored for RGBA datasets (see SoVolumeData.dataRGBA).
. Default is CONTINUOUS.
- Since:
- Open Inventor 2024.2
ldmResourceParameters
SoLDMResourceParameters object which allows you to set LDM resource parameters.Method Details
-
setLDMDataModifier
Deprecated.As of Open Inventor 9.9, should usedataTransformfield instead.This method allows you to modify the original data (for example, attribute calculation) before it's displayed. The modifyData method of the given LDMDataModifier is called after each tile is loaded.- Since:
- 6.0
-
setReader
Calls setReader(reader, false). -
isDataInMemory
Indicates whether the data attached to a tile is in main memory. Called when the node front manager evaluates the texture front.This allows to manage data that implements SoBufferAsyncInterface. If the specified tile does not implement SoBufferAsyncInterface then this method always returns true. So effectively it always returns true for non-LDM volumes.
-
hasEditedTile
public boolean hasEditedTile()Returns true if DataSet has edited tiles. -
isInMemory
Indicates whether a tile is in main memory. Called when the node front manager evaluates the texture front. -
voxelToXYZ
Converts the specified point in voxel coordinates (I,J,K) to geometric coordinates (X,Y,Z). The geometric coordinates are expressed in "extent" space, where voxel coordinates are mapped to the box defined by the volume extent.The left bottom coordinate of the voxel is returned. Correctly converts coordinates that are outside the volume dimensions, but the resulting geometric coordinate is outside the volume extent.
- See Also:
-
writeTile
Write the specified tile using the specified writer. No operations are done on buffer (dataTransform or edition), the buffer is written as is. The writer must be initialized and handles must be properly set (seeSoVolumeReader.closeAllHandlesandSoVolumeWriter.restoreAllHandles), ie. the current reader's handles must be closed, and the specified writer's handles must be opened. -
readTile
Copies the specified tile into the provided buffer.
Applies the data transformation (set in dataTransform field) if transform is true. -
dataSize
Returns the number of bytes per voxel of the specified data type. -
isDataSigned
Returns true if the given data type is a signed integer data type. -
isDataFloat
Returns true if the given data type is a float data type. -
getLDMTopoOctree
Returns the LDMTopoOctree used by thisSoDataSet. The LDMTopoOctree is initialized at the initialization of the reader. -
resetReader
public void resetReader()Resets previously set custom reader setup by setReader call. -
getOverlapping
Deprecated.As of Open Inventor 9.0.0.0. No longer used.Returns the tile border (overlap) in voxels. Since OIV 9.0 always returns 0.Warning Deprecated since Open Inventor 9000. No longer used.
-
getMaxNumDataSets
public static int getMaxNumDataSets()Returns the maximum number of data sets that can be render composited on the current hardware (essentially the number of texture units - 1). -
getTileDimension
Returns the tile dimension. -
getDatumSize
public int getDatumSize()Returns the number of bytes per voxel. -
voxelToXYZ
Converts the specified box in voxel coordinates (I,J,K) to geometric coordinates (X,Y,Z). The geometric coordinates are expressed in "extent" space, where voxel coordinates are mapped to the box defined by the volume extent.Correctly converts coordinates that are outside the volume dimensions, but the resulting geometric coordinate is outside the volume extent.
- See Also:
-
XYZToVoxel
Converts the specified box in geometric coordinates to voxel coordinates. The geometric coordinates are expressed in "extent" space, where voxel coordinates are mapped to the box defined by the volume extent.Correctly converts coordinates that are outside the volume extent, but the resulting voxel coordinate is outside the volume dimensions.
- See Also:
-
XYZToVoxel
Converts the specified point in geometric coordinates (X,Y,Z) to voxel coordinates (I,J,K). The geometric coordinates are expressed in "extent" space, where voxel coordinates are mapped to the box defined by the volume extent.Correctly converts coordinates that are outside the volume extent, but the resulting voxel coordinate is outside the volume dimensions.
- See Also:
-
getDimension
Returns the data set dimension. -
setLDMReader
Sets the LDM volume reader object to use.
This method allows the data to be read directly from the disk using the specified subclass ofSoVolumeReader. -
handleEvent
- Overrides:
handleEventin classSoNode
-
getReader
Returns the current data set reader object.
The actual type will be a subclass ofSoVolumeReader, either one of the predefined subclasses or an application-defined subclass. Returns null if no reader is currently set. Applications should always verify the class type before using the returned object as a specific sub-class ofSoVolumeReader. -
pick
-
setReader
This method allows the data to be read directly from the disk using the specified subclass ofSoVolumeReader. If the takeOwnership parameter is false (default), LDM will not delete the specified instance. Otherwise, LDM will automatically delete the specified instance, for example, when theSoDataSetnode is deleted. If filename is not set before setting the reader, LDM will display an error message just to warn that the reader has not opened any file yet. LDM continues to work as expected.Note: When using a custom reader, any reader method that changes the volume properties (dimension, size, data type, etc) should notify the
SoVolumeDatanode by calling the reader'stouch()method. If this notification is not done,SoDataSetfields, for exampleSoDataSet.extent, won't be updated correctly. -
write
-
getLDMReader
Returns a pointer to the current data set reader object.
The actual type will be a subclass ofSoVolumeReader, either one of the predefined subclasses or an application-defined subclass. Returns NULL if no reader is currently being used (for example if setVolumeData() was called). -
getBoundingBox
- Overrides:
getBoundingBoxin classSoNode
-
getMinMax
public long[] getMinMax()Returns min and max values of the data set data.
Returns nullif the requested data is not available (for example, if no data set exists).
NOTE: This method might force LDM to load the entire data set if the volume reader does not respond to the getMinMax query. Normally for an LDM format data set, the min and max values are stored in the LDM header. For a non-LDM data set, if a filename and/or reader have been specified and the data set has not yet been loaded, LDM will load the entire data set to compute the min and max values. For a large data set this may take a long time. -
getDoubleMinMax
public double[] getDoubleMinMax()Returns min and max values of the data set.
Returns nullif the requested data is not available (for example, if no data set exists).
NOTE: This method might force LDM to load the entire data set if the volume reader does not respond to the getMinMax query. Normally for an LDM format data set, the min and max values are stored in the LDM header. For a non-LDM data set, if a filename and/or reader have been specified and the data set has not yet been loaded, LDM will load the entire data set to compute the min and max values. For a large data set this may take a long time. -
getDataType
Returns the data type. -
callback
-
getDataSize
public int getDataSize()Returns the number of bytes per voxel in VolumeViz. -
GLRender
-
numSigBits
public int numSigBits()Returns the number of significant bits. -
editSubVolume
Replaces the contents of a subvolume with the given data.
The buffer size (in bytes) must match the subvolume size (in bytes) exactly. The subvolume is specified in voxel/cell coordinates. CallstartEditing()before calling this method. Returns 0 if successful.Warning The modification may be postponed until the tiles are really needed. Therefore the contents of the userData buffer must not be modified until after
saveEditing()is called. -
editTile
Replaces the contents of a tile with the specified value.
CallstartEditing()before calling this method. Returns 0 if successful. -
editSubVolume
Replaces the contents of a subvolume with the specified value.
The subvolume is specified in voxel/cell coordinates. CallstartEditing()before calling this method. Returns 0 if successful. -
editTile
Replaces the contents of a tile with the given data.
The buffer size (in bytes) must match the tile size (in bytes) exactly. CallstartEditing()before calling this method. Returns 0 if successful.Warning The modification may be postponed until the tile is really needed. Therefore the contents of the userData buffer must not be modified until after
saveEditing()is called. -
getLdmDataAccess
Returns a reference to theSoLDMDataAccessobject.
This object can be used to query data from the volume. -
startEditing
public int startEditing()Initiate an editing transaction.
Returns true if successful and also returns a unique transaction id. This value is required for finishing the edit transaction (seefinishEditing()) and for undo/redo (seeundoEditing()andredoEditing()). Multiple transactions may be active at the same time. -
finishEditing
public boolean finishEditing(int transactionId) Terminates an editing transaction.
Returns true if successful. May only be called with a valid transaction id returned by thestartEditing()method. On error does nothing. The finish method will schedule a redraw so the correct data is displayed. To commit the edits, in other words to save the edited data back to the data source, callsaveEditing(). -
editSurfaceShape
Replaces all voxels intersecting the polygons or lines defined by the surfaceShape and given thickness with the specified value. surfaceShape is defined in the same 3D space as the dataSet. thickness is defined in voxels. The surfaceShape can be deleted after calling this function.Call
startEditing()before calling this method. Returns 0 if successful.Warning The modification may be postponed until the tiles are really needed. Therefore the surfaceShape node (and children if any) must not be modified until after
saveEditing()is called. -
useFakeData
Creates fake data in buffer. -
saveEditing
public boolean saveEditing()Commit all transactions. All modified tiles are written back to the data source using the current reader format. May only be called when no threads are editing, i.e. after all threads that calledstartEditinghave calledfinishEditing.Returns true if successful. On error does nothing returns false. Returns false if:
- No edits have been done.
- Transaction(s) still in progress (finishEditing has not been called).
- Volume was not loaded using a volume reader (direct from memory doesn't work).
- No volume writer class exists for this volume reader.
Warning: Effectively, saveEditing currently only works for data loaded using an SoVRLDMFileReader (an LDM format tiled data set) or an
SoVRMemoryReader(data set completely in memory). -
doAction
-
redoEditing
public boolean redoEditing(int transactionId) Redo all modifications associated with the specified transaction id. Returns true if successful. On error does nothing. May only be called after the specified transaction has been terminated (seefinishEditing()method) and undone (seeundoEditing()method). Schedules a redraw so the correct data is displayed.Note: Redo is no longer available after transactions are saved. After calling
saveEditing(), the transaction ids are no longer valid and the modified data is the new reference. -
editSolidShape
Replaces all voxels intersecting the given shape with the specified value. The geometry defined under solidShape must represent a list of closed surfaces otherwise the result is unpredictable. solidShape must not contain any lines or open polyhedrons (polyhedron with shapes). The result is based on the odd-winding rule, so the result is not necessarily the union or the intersection of the closed surfaces. If you want to voxelize lines or single polygons, see also theeditSurfaceShapemethod.If the goal is to define a shape which is the result of the intersection/union of multiple closed surfaces, see the
SoCSGShapenode.solidShape is defined in the same 3D space as the dataSet. The solidShape can be deleted after calling this function.
Call
startEditing()before calling this method. Returns 0 if successful.Warning The modification may be postponed until the tiles are really needed. Therefore the surfaceShape node (and children if any) must not be modified until after
saveEditing()is called. -
editBoxes
Replace all voxels in the region defined by a list of boxes with the specified value. boxCenter and boxSize are defined in ijk (voxel) space.Call
startEditing()before calling this method. Returns 0 if successful. -
undoEditing
public boolean undoEditing(int transactionId) Undo all modifications associated with the specified transaction id. Returns true if successful. On error does nothing. May only be called after the specified transaction has been terminated (seefinishEditing()method). Schedules a redraw so the correct data is displayed.Note: Undo is no longer available after transactions are saved. After calling
saveEditing(), the transaction ids are no longer valid and the modified data is the new reference.
dataTransformfield instead ofsetLDMDataModifier(LDMDataModifier)method.