Stable release | 5.2.0
/ January 28, 2021 |
---|---|
Written in | C++ (Qt), OpenGL, GLSL, OpenCL. Python |
Operating system | Cross-platform |
Type | Volume rendering, Interactive visualization |
License | GNU General Public License Version 2 |
Website |
voreen |
Voreen (volume rendering engine) is an open-source volume visualization library and development platform. Through the use of GPU-based volume rendering techniques it allows high frame rates on standard graphics hardware to support interactive volume exploration.
Voreen was initiated at the Department of Computer Science at the University of Münster, Germany in 2004 and was first released on 11 April 2008 under the GNU general public license (GPL). Voreen is written in C++ utilizing the Qt framework and using the OpenGL rendering acceleration API, and is able to achieve high interactive frame rates on consumer graphics hardware. [1] It is platform independent and compiles on Windows and Linux. The source code and documentation, and also pre-compiled binaries for Windows and Linux, are available from its website. Although it is intended and mostly used for medical applications, [2] any other kind of volume data can be handled, e.g., microscopy, flow data or other simulations. [3] [4]
The visualization environment VoreenVE based on that engine is designed for authoring and performing interactive visualizations of volumetric data. Different visualizations can be assembled in form of so-called networks via rapid prototyping, with each network consisting of several processors. [5] Processors perform more or less specialized tasks for the entire rendering process, ranging from supplying data over raycasting, geometry creation and rendering to image processing. Within the limits of their respective purposes, the processors can be combined freely with each other, and thereby granting a great amount of flexibility and providing a uniform way of handling volume rendering. Authors who need to implement a certain rendering technique can confine their work basically on the development of new processors, whereas users who only want to access a certain visualization simply need to employ the appropriate processors or networks and do not need to care about technical details.
Visualization
Volume Processing
Interaction
Data I/O
Stable release | 5.2.0
/ January 28, 2021 |
---|---|
Written in | C++ (Qt), OpenGL, GLSL, OpenCL. Python |
Operating system | Cross-platform |
Type | Volume rendering, Interactive visualization |
License | GNU General Public License Version 2 |
Website |
voreen |
Voreen (volume rendering engine) is an open-source volume visualization library and development platform. Through the use of GPU-based volume rendering techniques it allows high frame rates on standard graphics hardware to support interactive volume exploration.
Voreen was initiated at the Department of Computer Science at the University of Münster, Germany in 2004 and was first released on 11 April 2008 under the GNU general public license (GPL). Voreen is written in C++ utilizing the Qt framework and using the OpenGL rendering acceleration API, and is able to achieve high interactive frame rates on consumer graphics hardware. [1] It is platform independent and compiles on Windows and Linux. The source code and documentation, and also pre-compiled binaries for Windows and Linux, are available from its website. Although it is intended and mostly used for medical applications, [2] any other kind of volume data can be handled, e.g., microscopy, flow data or other simulations. [3] [4]
The visualization environment VoreenVE based on that engine is designed for authoring and performing interactive visualizations of volumetric data. Different visualizations can be assembled in form of so-called networks via rapid prototyping, with each network consisting of several processors. [5] Processors perform more or less specialized tasks for the entire rendering process, ranging from supplying data over raycasting, geometry creation and rendering to image processing. Within the limits of their respective purposes, the processors can be combined freely with each other, and thereby granting a great amount of flexibility and providing a uniform way of handling volume rendering. Authors who need to implement a certain rendering technique can confine their work basically on the development of new processors, whereas users who only want to access a certain visualization simply need to employ the appropriate processors or networks and do not need to care about technical details.
Visualization
Volume Processing
Interaction
Data I/O