Maverick: Difference between revisions
(13 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<h1><center><b>Maverick</b></center></h1> | <h1><center><b>Maverick (MavTK)</b></center></h1> | ||
= PUBLIC RELEASE = | |||
<b>Maverick</b> has been incorporated into the <b>Common Toolkit</b> (CTK, http://commontk.org) and <b>3D Slicer</b> (http://www.slicer.org). Maverick no longer exists as a stand-alone package. | |||
<b>CommonTK</b> contains the majority of the GUI elements that Maverick used to create its workflow-based applications. | |||
<b>3D Slicer</b> contains select algorithms for Maverick, and the community is adopting Slicer's MRML scene graph instead of the custom scene graph that had been developed within Maverick. Using this community standard allows the impact and contributions of Maverick to be more effective. | |||
Slicer now also contains the registration and interactive segmentation tools that were developed for Maverick. These tools are very powerful and practical. | |||
Additionally, many of the segmentation algorithms of Maverick are being divided into algorithm-specific libraries. In particular, select organ and vessel segmentation methods are now available in <b>TubeTK</b> (http://public.kitware.com/Wiki/TubeTK), and interfaces for running them within Slicer are under development. | |||
= Overview = | = Overview = | ||
Maverick | Maverick was an extensive collection of C++ classes, parameter files, specifications, and documentation for the following: | ||
# Building applications that vary in specificity from workflow-based applications to general-purpose applications. | # Building applications that vary in specificity from workflow-based applications to general-purpose applications. | ||
## Workflow-based applications allow a user to rapidly apply a sequence of filters in a prescribed manner in order to solve specific problems with minimal interaction. | ## Workflow-based applications allow a user to rapidly apply a sequence of filters in a prescribed manner in order to solve specific problems with minimal interaction. | ||
Line 12: | Line 24: | ||
## QT-based rendering widgets can display objects or entire scenes using any combination of themes and formats (e.g., using volume rendering, surface rendering, and overlays in 3D views, slice-based views, lighbox views, and more). | ## QT-based rendering widgets can display objects or entire scenes using any combination of themes and formats (e.g., using volume rendering, surface rendering, and overlays in 3D views, slice-based views, lighbox views, and more). | ||
# Applying advanced ITK and VTK frameworks as Maverick Modules that were built by image analysis experts and that hide the complexities of ITK and VTK. | # Applying advanced ITK and VTK frameworks as Maverick Modules that were built by image analysis experts and that hide the complexities of ITK and VTK. | ||
<em>The development of Maverick was funded, in part, by the Air Force Research Laboratories under Phases I and II of the SBIR contract | <em>The development of Maverick was funded, in part, by the Air Force Research Laboratories under Phases I and II of the SBIR contract | ||
"Generating Labeled Voxelization for Numerical Simulation," Topic: AF06-034, Contract #: FA8650-07-C-6756 </em> | "Generating Labeled Voxelization for Numerical Simulation," Topic: AF06-034, Contract #: FA8650-07-C-6756 </em> | ||
= Contact = | = Contact = |
Latest revision as of 13:53, 21 March 2012
Maverick (MavTK)
PUBLIC RELEASE
Maverick has been incorporated into the Common Toolkit (CTK, http://commontk.org) and 3D Slicer (http://www.slicer.org). Maverick no longer exists as a stand-alone package.
CommonTK contains the majority of the GUI elements that Maverick used to create its workflow-based applications.
3D Slicer contains select algorithms for Maverick, and the community is adopting Slicer's MRML scene graph instead of the custom scene graph that had been developed within Maverick. Using this community standard allows the impact and contributions of Maverick to be more effective.
Slicer now also contains the registration and interactive segmentation tools that were developed for Maverick. These tools are very powerful and practical.
Additionally, many of the segmentation algorithms of Maverick are being divided into algorithm-specific libraries. In particular, select organ and vessel segmentation methods are now available in TubeTK (http://public.kitware.com/Wiki/TubeTK), and interfaces for running them within Slicer are under development.
Overview
Maverick was an extensive collection of C++ classes, parameter files, specifications, and documentation for the following:
- Building applications that vary in specificity from workflow-based applications to general-purpose applications.
- Workflow-based applications allow a user to rapidly apply a sequence of filters in a prescribed manner in order to solve specific problems with minimal interaction.
- General-purpose applications offer a user a multitude of filtering options at any point in time, so that the user can investigate a wide range of problems and solutions from within the same application.
- Using an intuitive scene-based data structure to manage the objects to be viewed and processed by an application
- Hierarchies of images, segmentation results, landmarks, and more can be created and manipulated as members of a scene
- Physical and visual properties can be associated with each of those objects
- QT-based rendering widgets can display objects or entire scenes using any combination of themes and formats (e.g., using volume rendering, surface rendering, and overlays in 3D views, slice-based views, lighbox views, and more).
- Applying advanced ITK and VTK frameworks as Maverick Modules that were built by image analysis experts and that hide the complexities of ITK and VTK.
The development of Maverick was funded, in part, by the Air Force Research Laboratories under Phases I and II of the SBIR contract "Generating Labeled Voxelization for Numerical Simulation," Topic: AF06-034, Contract #: FA8650-07-C-6756
Contact
Project Lead
- Stephen R. Aylward, Ph.D.
- Director of Medical Imaging
- stephen.aylward@kitware.com
- 919-969-6990 (Ext 300)
Developers
- Julien Finet
- julien.finet@kitware.com
- Patrick Reynolds
- patrick.reynolds@kitware.com
- Julien Jomier
- julien.jomier@kitware.com