Documentation/Nightly/Extensions/BlendVectorVolumes

For the latest Slicer documentation, visit the read-the-docs.

Introduction and Acknowledgements

Extension: OpenCVExample Acknowledgments: This work was supported by a supplement to the Quantitative Image Informatics project via the NIH-National Cancer Institute Grant U24 CA180918-03 as well as U24 CA180924 Tools to Analyze Morphology and Spatially Mapped Molecular Data with Stony Brook University. Author: Nicole Aucoin (SPL) Contact: Nicole Aucoin, <email>nicole@bwh.harvard.edu</email>

Quantitative Image Informatics for Cancer Research   Surgical Planning Laboratory (SPL)

Module Description

This is a CLI module that depends on the SlicerOpenCV extension, providing a way to blend two vector volumes together.

Use Cases

When loading in RGB files, they are loaded as vector volumes in Slicer. Use this module to blend them together.

Panels and their use

Blend Vector Volumes GUI

IO: Alpha: A double value between 0.0 and 1.0 that gives the weight of the first input image in the resulting blend. Gamma: A double value that is added to the weighted blend, used to increase or decrease intensity. First Input Volume: First input vector volume Second Input Volume: Second input vector volume Output Volume: Output vector volume, holding the blending of the two input volumes, Can be a newly created vector volume.

Similar Modules

• The Slicer Pathology extension also uses the SlicerOpenCV extension

References

• Quantitative Image Informatics for Cancer Research (QIICR) http://qiicr.org
• Open Source Computer Vision http://opencv.org

Information for Developers

To depend on the OpenCV provided by SlicerOpenCV, in the CLI's CMakeLists.txt file define OpenCV_DIR by finding the package that SlicerOpenCV provided:

 find_package(OpenCV 3.1 REQUIRED)

• The header include path is defined as:

 get_filename_component(OpenCV_INCLUDE_DIR ${OpenCV_DIR}/../../include ABSOLUTE)

• Add ${OpenCV_INCLUDE_DIR} to the MODULE_INCLUDE_DIRECTORIES list
• Link against the OpenCV libraries by adding ${OpenCV_LIBS} to the MODULE_TARGET_LIBRARIES

OpenCVExample provides some more information about writing an extension that includes modules that depend on OpenCV