Save & load (scalar opacity | Scalar color | gradient opacity) mapping settings from volume rendering?

hherhold · August 19, 2021, 12:55pm

Hey all,

Is there a way (python or otherwise) to save and load the “transfer curves”, meaning the scalar opacity mapping, scalar color mapping, and gradient opacity mapping settings to a file for reloading later? I do not use any of the presets, and it would be nice to be able to save mappings for later.

Totally fine if this is only doable from python with telling a node (or nodes) to write/read to/from disk.

Thanks!

-Hollister

pieper · August 19, 2021, 2:35pm

These links should help:

github.com

SlicerMorph/Spr_2021/blob/cbd6e1d269fdb256d2ab0f42933a1422c8c8fff6/Day_2/VolumeRendering/VolumeRendering.md#saving-your-transfer-functions

## Visualization: Volume Rendering
The `Volume Rendering` module provides interactive visualization of 3D image data. For [**official documentation of the panel and functions, see here**](https://slicer.readthedocs.io/en/latest/user_guide/modules/volumerendering.html).

* Only scalar volumes can be used for volume rendering. Vector volumes (eg jpg, png, bmp, or other classic 2D formats) can be converted to scalar volumes using the [VectorToScalarVolume module](https://www.slicer.org/wiki/Documentation/Nightly/Modules/VectorToScalarVolume). If you used SlicerMorph's `ImageStacks` module to import your data, vector to scalar conversion was done already at the time of import the data.

One quick way to render your volume is using the drag and drop function. In the `Data` module you can drag the mouse skull volume from the image stacks example directly into the 3D widow and Slicer will guess at the settings to render the volume. 

<img src="./DragDropVR.png">

While this may be a good starting point, there are a lot of settings you can modify to improve the rendering of your volume in the `Volume Rendering` module. 

* 3D Slicer uses volume ray casting to computes 2D images from 3D volumetric data sets. Unlike surface reconstruction, there is no estimation of object surfaces or segmentation.
* The values displayed are calculated using a transfer function that incorporates voxel intensities, material properties, and illumination.
* The opacity and color of the image can be adjusted by modifying their transfer functions in the `Volume Rendering` module.

 <img src="./volumeRenderTF.png">
 
* Slicer supports both CPU and GPU volume rendering. CPU based will always work, whether you are on a computer without a dedicated graphics card, or on a remote connection (which may not support hardware accelerated graphics), but it can be slow (unless you have dozens of cores in your cpu). GPU requires you have a dedicated graphics card with 1GB or more videoRAM and it is much faster, but it has its own limitations (see below).  
* If you have a dedicated graphics card, you may want to set the default visualization method to GPU rendering using the menu option in: Edit->Preferences 
* Always set the rendering quality to normal (this is enabled by defalt, if you opt-in for the SlicerMorph Preferences).

This file has been truncated. show original

hherhold · August 19, 2021, 2:42pm

Most excellent! Thanks much.

-Hollister

muratmaga · August 19, 2021, 6:57pm

Here is an example from SlicerMorph. A mrml file that defines the presets, and a short resource script that loads it into the scene (you only care the top couple lines, the rest are other SlicerMorph preferences).

Topic		Replies	Views
Sync “Volumes” color look-up table with “Volume Rendering” Support	3	1116	January 8, 2018
Slicer 4.10.2 vs Slicer 4.11.2 volumes rendering Support volume-rendering	2	575	November 29, 2020
Apply transfer function to 2D slices Support	1	272	March 4, 2023
Contents of .VP File Development volume-rendering	1	452	March 23, 2020
Set Volume Rendering Options with PYTHON Support	1	582	July 19, 2021

Save & load (scalar opacity | Scalar color | gradient opacity) mapping settings from volume rendering?

Related topics