Data Module
Browse the image gallery

3D Slicer is a free open source extensible software application for medical image computing and visualization. Mainly written in C++ and based on the NA-MIC kit, 3D Slicer relies on a variety of libraries: VTK, ITK, CTK, CMake, Qt and Python.

To ensure the stability of the application, relying on a robust software process, the source code is compiled and tested on a daily basis on a variety of platform configurations. The testing results are summarized and reported using a web-based centralized CDash dashboard. Developers of 3D Slicer can also report issues on the open mailing list or using web-based bug tracking system.

3D Slicer consists of both a lean application core and modules offering specific functionality. The core implements the user interface, provides support for data input/output (IO) and visualization and also exposes developer interfaces that support extension of the application with new modules.

Three types of modules are supported: CLI, Loadable module and Scripted module. While the developer has to choose between one of the 3 types to implement its module, the end user won't notice the difference as they all share the same look & feel. The choice for a given type of module is usually based on the type of inputs/parameters for a given module.

These modules can be either built-in or installed on demand via the extensions manager.

Add or improve a functionality: Where to start ?

Developer references


Getting involved Developer meetings It is open to everyone, feel free to join. Developers mailing list / Browse archives Intended for discussion of programming related questions Resources CDash Quality Dashboard / Setup a dashboard Nightly, continuous and experimental dashboards. Bug tracker / Register / Report a bug Web-based bug tracking system Doxygen Source code API documentation. Slicer Style Guidelines Consistency and Readability for a manageable code base Git repository / ViewVC / last commit `git clone git://github.com/Slicer/Slicer.git` Developer Projects Pages for the developer projects. Change logs and release details Informations about Slicer releases		Step by step - Develop a module or an extension Where to start? Build Slicer application Create CLI module Loadable module [[Documentation/4.1/Developers/Modules#Scripted_Modules\|Scripted module] Editor effect Build, test, package and distribute extensions Build instructions Slicer application Compiling and installing Slicer from source. Slicer extensions Build, test, package and distribute extensions Design & Implementation Modules Comparison between the different supported module types Data Model - MRML Objects and their organization. MRML Library provides API for managing medical image data type Logics Details the role of MRML/Slicer/Application/Modules logics and Displayable managers Python scripting Presents the underlying infrastructure. Charts Description of the Charting architecture. Build system Details how Slicer is built and packaged.		How To Create a CLI module Create a Loadable module Create a Scripted module Create an Editor effect Document a module NEW Contribute a patch UPDATED Setup QtCreator to develop Slicer application or modules Setup a dashboard Use debugger with Slicer application Troubleshoot issues such as crash, or memory leaks Prevent memory leaks Write a widget for Slicer and Qt Designer Use custom widgets in Qt Designer Load UI file from python Pass data between Slicer and Matlab Experimental