Slicer Wiki - User contributions [en]

Documentation/Nightly/Extensions/GyroGuide

2014-01-27T01:48:14Z

Lpfang: Redirected page to Documentation/Nightly/Modules/GyroGuide

#REDIRECT [[Documentation/Nightly/Modules/GyroGuide]]

Documentation/Nightly/Modules/GyroGuide

2014-01-27T01:32:53Z

Lpfang:

<noinclude>{{documentation/versioncheck}}</noinclude>

{{documentation/{{documentation/version}}/module-header}}



{{documentation/{{documentation/version}}/module-section|Introduction and Acknowledgements}}
{{documentation/{{documentation/version}}/module-introduction-start|{{documentation/modulename}}}}
{{documentation/{{documentation/version}}/module-introduction-row}}
Extension: [[Documentation/{{documentation/version}}/Extensions/GyroGuide|GyroGuide]] 
[[File:GyroGuide.png|150px]] 
Acknowledgments:
This work is supported by International Scientific and Technical Cooperation Project of Zhejiang Province (Grant 2012C34G2020027) 
Author: Ruifeng Chen, Luping Fang, Qing Pan (College of Information Engineering, Zhejiang University of Technology, Hangzhou, China),Xiaolei Chen, Jiashu Zhang (Department of Neurosurgery, PLA General Hospital, Beijing, China) 
Contact: Luping Fang <email>flp@zjut.edu.cn</email> 
{{documentation/{{documentation/version}}/module-introduction-row}}

{{documentation/{{documentation/version}}/module-introduction-end}}


{{documentation/{{documentation/version}}/module-section|Module Description}}
{|
*The module should be used in cooperation with “Markups” module. First, it is required to choose five fiducial points to define two mutually-perpendicular planes as the Registration Markers. Second, set a target point and an entry point. Third, click the “Calculate” button to obtain the puncture path information, including the puncture depth and the angles between the puncture path and the reference planes. Finally, these results are displayed on a monitor or transmitted to the gyroscope-based device to assist the surgical operation.
|}

{{documentation/{{documentation/version}}/module-section|Use Cases}}
{|
*Puncture surgery (e.g. endoscopic insertion) is a typical example to show the use of this module. This module calculates the distance of the puncture path and the angle between the probe and the reference planes. The module can also transmit the calculation results to the gyroscope-based device to facilitate the surgical operation.
|}


{{documentation/{{documentation/version}}/module-section|Tutorials}}
*1 Load MRI/CT images of brain [[File:GyroGuide-Step-1.png|200px]] 
*2 Define “Markers”, “Target Point” and “Entry Point” using the Markups module. [[File:GyroGuide-Step-2.png|400px]] 
*3 Load the defined fiducial lists [[File:GyroGuide-Step-3.png]] 
:Select GyroGuide module
: 1 Select the fiducial list - Markers as the markers which define the reference planes.
: 2 Select the fiducial list – Target as the target point
: 3 Select the fiducial list – Entry as the entry point
*4 Calculate puncture path information 
:Click the “Calculate” button. The puncture path information will be displayed in the “Results” section. [[File:GyroGuide-Step-4.png|500px]] 
*5 Export the results 
:Input IP address and port of the puncture instrument in the “Exporter” panel. Click “Send”. The calculated puncture path information could be transmitted to the gyroscope-based device to facilitate the surgical operation.


{{documentation/{{documentation/version}}/module-section|Panels and their use}}

{|
|[[File:GyroGuide-Panel.png|400px]] 
*GyroGuide 
Markers 
It’s a fiducial list which consists of five fiducial points. Three points define the “Red Plane”. The other two points define the “Green Plane” which is perpendicular to the “Red Plane”. The “Blue Plane” is the one perpendicular to both the “Red Plane” and the “Green Plane”. Before measuring angles, the reference planes of the gyroscope have to be registered to the planes defined by the markers. 

Target Point 
The fiducial point which represents the target of the puncture. 

Entry Point 
The fiducial point which represents the entry of the puncture. 

Calculate Button 
Click the button to calculate the puncture path information. 
Angles between Puncture Path and Red Plane/Green Plane/Blue Plane 
The included angle between the puncture path and the red plane, green plane and blue plane, respectively. 
Distance between Target and Entry Point 
The length of the recommended puncture path. 
Exporter 
Hostname IP address of the puncture device. Default: localhost 
Port Port of the puncture device. Default: 18944 
Send Button Send the calculated results to the designated puncture device, which supports OpenIGTLink protocol. 


{{documentation/{{documentation/version}}/module-section|Similar Modules}}
*N/A

{{documentation/{{documentation/version}}/module-section|References}}
* N/A


{{documentation/{{documentation/version}}/module-section|Information for Developers}}
{{documentation/{{documentation/version}}/module-developerinfo}}


{{documentation/{{documentation/version}}/module-footer}}
[[Category:Documentation/{{documentation/version}}/Modules/Segmentation]]

File:GyroGuide.png

2014-01-27T01:29:04Z

Lpfang:

Documentation/Nightly/Extensions

2014-01-22T08:02:45Z

Lpfang:

<noinclude>{{documentation/versioncheck}}</noinclude>
<noinclude>
__TOC__
</noinclude>= Extensions by Category =

==Cat 1==

==Cat 2==
* [[Documentation/{{documentation/version}}/Extensions/SkullStripper|SkullStripper]] (Xiaodong Tao)
* [[Documentation/{{documentation/version}}/Extensions/MABMIS|MABMIS]] (Xiaofeng Liu)
* [[Documentation/{{documentation/version}}/Extensions/SwissSkullStripper|SwissSkullStripper]] (Bill Lorensen)
* [[Documentation/{{documentation/version}}/Extensions/CARMA|Cardiac MRI Toolkit]] (Alan Morris, Salma Bengali)[[image:UnderConstruction.png|tumb|10px]]
* [[Documentation/{{documentation/version}}/Extensions/PkModeling|PkModeling]] (Emma Zhu, Jim Miller)
* [[Documentation/{{documentation/version}}/Extensions/FacetedVisualizer|FacetedVisualizer]] (Harini Veeraraghavan, Jim Miller)
* [[Documentation/{{documentation/version}}/Extensions/Reporting|Reporting]] (Andrey Fedorov, Nicole Aucoin, Steve Pieper) (work in progress)
* [[Documentation/{{documentation/version}}/Extensions/SlicerRT|SlicerRT]] (Csaba Pinter, Andras Lasso, Kevin Wang, Greg Sharp, Steve Pieper)
** [[Documentation/{{documentation/version}}/Modules/DicomRtImport|DICOM-RT import]]
** [[Documentation/{{documentation/version}}/Modules/DicomRtExport|DICOM-RT export]]
** [[Documentation/{{documentation/version}}/Modules/Contours|Contours]]
** [[Documentation/{{documentation/version}}/Modules/DoseVolumeHistogram|Dose volume histogram]]
** [[Documentation/{{documentation/version}}/Modules/DoseAccumulation|Dose accumulation]]
** [[Documentation/{{documentation/version}}/Modules/DoseComparison|Dose comparison]]
** [[Documentation/{{documentation/version}}/Modules/Isodose|Isodose line and surface display]]
** [[Documentation/{{documentation/version}}/Modules/ContourComparison|Contour comparison]]
** [[Documentation/{{documentation/version}}/Modules/ContourMorphology|Contour morphology]]
** [[Documentation/{{documentation/version}}/Modules/PatientHierarchy|Patient hierarchy]]
** Modules from [[Documentation/{{documentation/version}}/Extensions/Plastimatch|Plastimatch]] (Greg Sharp)
*** [[Documentation/{{documentation/version}}/Modules/PlmBSplineDeformableRegistration|Plastimatch Automatic deformable image registration]]
*** [[Documentation/{{documentation/version}}/Modules/PlmLANDWARP|Plastimatch LANDWARP Landmark]]
*** [[Documentation/{{documentation/version}}/Modules/PlmXFORMWARP|Plastimatch XFORMWARP]] [[image:UnderConstruction.png|tumb|10px]]
* [[Documentation/{{documentation/version}}/Extensions/SlicerIGT|SlicerIGT]] (Tamas Ungi, Adam Rankin, Andras Lasso, Junichi Tokuda, Laurent Chauvin)
** [[Documentation/{{documentation/version}}/Modules/CollectFiducials|CollectFiducials]] (Tamas Ungi)
** [[Documentation/{{documentation/version}}/Modules/CreateModels|CreateModels]] (Tamas Ungi, Matthew Holden)
** [[Documentation/{{documentation/version}}/Modules/OpenIGTLinkRemote|OpenIGTLinkRemote]] (Tamas Ungi, Andras Lasso)
** [[Documentation/{{documentation/version}}/Modules/UltrasoundSnapshots|UltrasoundSnapshots]] (Tamas Ungi, Franklin King)
** [[Documentation/{{documentation/version}}/Extensions/VolumeResliceDriver|VolumeResliceDriver]] (Junichi Tokuda, Tamas Ungi, Laurent Chauvin)
* [[Documentation/{{documentation/version}}/Extensions/MatlabBridge|Matlab Bridge]] (Andras Lasso, Jean-Christophe Fillion-Robin, Kevin Wang)
* [[Documentation/{{documentation/version}}/Extensions/iGyne|iGyne]] (Xiaojun Chen and iGyne Team)
* [[Documentation/{{documentation/version}}/Extensions/LongitudinalPETCT|LongitudinalPETCT]] (Paul Mercea, Andrey Fedorov)
* [[Documentation/{{documentation/version}}/Extensions/DTIProcess|DTIProcess]] (Francois Budin)
* [[Documentation/{{documentation/version}}/Extensions/DTIAtlasFiberAnalyzer|DTIAtlasFiberAnalyzer]] (Francois Budin)
* [[Documentation/{{documentation/version}}/Extensions/FiberViewerLight|FiberViewerLight]] (Francois Budin)
* [[Documentation/{{documentation/version}}/Extensions/DTIPrep|DTIPrep]] (Francois Budin)
* [[Documentation/{{documentation/version}}/Extensions/DTIAtlasBuilder|DTIAtlasBuilder]] (Adrien Kaiser)
* [[Documentation/{{documentation/version}}/Extensions/ShapePopulationViewer|ShapePopulationViewer]] (Alexis Girault)
* [[Documentation/{{documentation/version}}/Extensions/TubeTK|TubeTK]] (Stephen Aylward, Jean-Christophe Fillion-Robin, Christopher Mullins, Michael Jeulin-L, Matthew McCormick)
* [[Documentation/{{documentation/version}}/Extensions/UKFTractography|UKFTractography]] (Ryan Eckbo, Yogesh Rathi)
* [[Documentation/{{documentation/version}}/Extensions/TrackerStabilizer|TrackerStabilizer]] (Laurent Chauvin, Jayender Jagadeesan)
* [[Documentation/{{documentation/version}}/Extensions/ChangeTracker|ChangeTracker]] (Andrey Fedorov)
* [[Documentation/{{documentation/version}}/Extensions/SobolevSegmenter|SobolevSegmenter]] (Arie Nakhmani)
* [[Documentation/{{documentation/version}}/Extensions/QuickTools|QuickTools]] (Julien Finet)
** [[Documentation/{{documentation/version}}/Modules/ImageMaker|Image Maker]]
* [[Documentation/{{documentation/version}}/Extensions/XNATSlicer|XNATSlicer]]
* [[Documentation/{{documentation/version}}/Extensions/ErodeDilateLabel|ErodeDilateLabel]] (Junichi)
* [[Documentation/{{documentation/version}}/Extensions/ThingiverseBrowser|ThingiverseBrowser]] (Nigel Goh)
* [[Documentation/{{documentation/version}}/Extensions/VirtualFractureReconstruction|Virtual Fracture Reconstruction]] (Karl Fritscher, Peter Karasev)
* [[Documentation/{{documentation/version}}/Extensions/AirwaySegmentation|AirwaySegmentation]] (Pietro Nardelli)
* [[Documentation/{{documentation/version}}/Extensions/ModelClip|ModelClip]] (Jun Lin, Xiaojun Chen)
* [[Documentation/{{documentation/version}}/Extensions/SurfaceMirror|SurfaceMirror]] (Jiaxi Luo, Ruqing Ye, Xiaojun Chen)
* [[Documentation/{{documentation/version}}/Extensions/Scoliosis|Scoliosis]] (Franklin King, Tamas Ungi)
**[[Documentation/{{documentation/version}}/Modules/SpinalCurvatureMeasurement|Spinal Curvature Measurement]] (Franklin King, Tamas Ungi)
* [[Documentation/{{documentation/version}}/Extensions/PortPlacement|Port Placement]] (Andinet Enquobahrie, Luis G. Torres)
* [[Documentation/{{documentation/version}}/Extensions/PlusRemote|Plus Remote]] (Franklin King, Tamas Ungi)
* [[Documentation/{{documentation/version}}/Extensions/TransformVisualizer|Transform Visualizer]] (Franklin King, Andras Lasso, Csaba Pinter)
* [[Documentation/{{documentation/version}}/Extensions/WindowLevelEffect|WindowLevelEffect]] (Andrey Fedorov, Steve Pieper)
* [[Documentation/{{documentation/version}}/Extensions/PerkTutor|PerkTutor]] (Tamas Ungi, Matthew Holden)
** [[Documentation/{{documentation/version}}/Modules/PerkEvaluator|PerkEvaluator]]
** [[Documentation/{{documentation/version}}/Modules/TransformRecorder|TransformRecorder]]
** [[Documentation/{{documentation/version}}/Modules/WorkflowSegmentation|WorkflowSegmentation]]
* [[Documentation/{{documentation/version}}/Modules/SlicerToKiwiExporter|SlicerToKiwiExporter]] (Jean-Christophe Fillion-Robin)
* [[Documentation/{{documentation/version}}/Modules/GelDosimetry|GelDosimetry]] (Csaba Pinter)
* [[Documentation/{{documentation/version}}/Extensions/MultidimData|Multidimensional data]] (Andras Lasso, Matthew Holden, Kevin Wang)
* [[Documentation/{{documentation/version}}/Extensions/GyroGuide|GyroGuide]] (Ruifeng Chen,Luping Fang, Qing Pan, Xiaolei Chen, Jiashu Zhang)

==Cat 3==
* [[Documentation/{{documentation/version}}/Extensions/LesionSegmentation|LesionSegmentation]] (Mark Scully)
**[[Documentation/{{documentation/version}}/Modules/TrainModel|LesionSegmentation->TrainModel]] (Mark Scully)
**[[Documentation/{{documentation/version}}/Modules/PredictLesions|LesionSegmentation->PredictLesions]] (Mark Scully)
* [[Documentation/{{documentation/version}}/Extensions/IASEM|IASEM]] (Bradley Lowekamp)
<noinclude>
{{:Documentation/{{documentation/version}}/FAQ/Extensions|Extensions}}
</noinclude>

Documentation/Nightly/Modules/GyroGuide

2014-01-22T07:46:44Z

Lpfang:

<noinclude>{{documentation/versioncheck}}</noinclude>

{{documentation/{{documentation/version}}/module-header}}



{{documentation/{{documentation/version}}/module-section|Introduction and Acknowledgements}}
{{documentation/{{documentation/version}}/module-introduction-start|{{documentation/modulename}}}}
{{documentation/{{documentation/version}}/module-introduction-row}}
Extension: [[Documentation/{{documentation/version}}/Extensions/GyroGuide|GyroGuide]] 
Acknowledgments:
This work is supported by International Scientific and Technical Cooperation Project of Zhejiang Province (Grant 2012C34G2020027) 
Author: Ruifeng Chen, Luping Fang, Qing Pan (College of Information Engineering, Zhejiang University of Technology, Hangzhou, China),Xiaolei Chen, Jiashu Zhang (Department of Neurosurgery, PLA General Hospital, Beijing, China) 
Contact: Luping Fang <email>flp@zjut.edu.cn</email> 
{{documentation/{{documentation/version}}/module-introduction-row}}

{{documentation/{{documentation/version}}/module-introduction-end}}


{{documentation/{{documentation/version}}/module-section|Module Description}}
{|
*The module should be used in cooperation with “Markups” module. First, it is required to choose five fiducial points to define two mutually-perpendicular planes as the Registration Markers. Second, set a target point and an entry point. Third, click the “Calculate” button to obtain the puncture path information, including the puncture depth and the angles between the puncture path and the reference planes. Finally, these results are displayed on a monitor or transmitted to the gyroscope-based device to assist the surgical operation.
|}

{{documentation/{{documentation/version}}/module-section|Use Cases}}
{|
*Puncture surgery (e.g. endoscopic insertion) is a typical example to show the use of this module. This module calculates the distance of the puncture path and the angle between the probe and the reference planes. The module can also transmit the calculation results to the gyroscope-based device to facilitate the surgical operation.
|}


{{documentation/{{documentation/version}}/module-section|Tutorials}}
*1 Load MRI/CT images of brain [[File:GyroGuide-Step-1.png|200px]] 
*2 Define “Markers”, “Target Point” and “Entry Point” using the Markups module. [[File:GyroGuide-Step-2.png|400px]] 
*3 Load the defined fiducial lists [[File:GyroGuide-Step-3.png]] 
:Select GyroGuide module
: 1 Select the fiducial list - Markers as the markers which define the reference planes.
: 2 Select the fiducial list – Target as the target point
: 3 Select the fiducial list – Entry as the entry point
*4 Calculate puncture path information 
:Click the “Calculate” button. The puncture path information will be displayed in the “Results” section. [[File:GyroGuide-Step-4.png|500px]] 
*5 Export the results 
:Input IP address and port of the puncture instrument in the “Exporter” panel. Click “Send”. The calculated puncture path information could be transmitted to the gyroscope-based device to facilitate the surgical operation.


{{documentation/{{documentation/version}}/module-section|Panels and their use}}

{|
|[[File:GyroGuide-Panel.png|400px]] 
*GyroGuide 
Markers 
It’s a fiducial list which consists of five fiducial points. Three points define the “Red Plane”. The other two points define the “Green Plane” which is perpendicular to the “Red Plane”. The “Blue Plane” is the one perpendicular to both the “Red Plane” and the “Green Plane”. Before measuring angles, the reference planes of the gyroscope have to be registered to the planes defined by the markers. 

Target Point 
The fiducial point which represents the target of the puncture. 

Entry Point 
The fiducial point which represents the entry of the puncture. 

Calculate Button 
Click the button to calculate the puncture path information. 
Angles between Puncture Path and Red Plane/Green Plane/Blue Plane 
The included angle between the puncture path and the red plane, green plane and blue plane, respectively. 
Distance between Target and Entry Point 
The length of the recommended puncture path. 
Exporter 
Hostname IP address of the puncture device. Default: localhost 
Port Port of the puncture device. Default: 18944 
Send Button Send the calculated results to the designated puncture device, which supports OpenIGTLink protocol. 


{{documentation/{{documentation/version}}/module-section|Similar Modules}}
*N/A

{{documentation/{{documentation/version}}/module-section|References}}
* N/A


{{documentation/{{documentation/version}}/module-section|Information for Developers}}
{{documentation/{{documentation/version}}/module-developerinfo}}


{{documentation/{{documentation/version}}/module-footer}}
[[Category:Documentation/{{documentation/version}}/Modules/Segmentation]]

Documentation/Nightly/Modules/GyroGuide

2014-01-22T07:41:54Z

Lpfang:

<noinclude>{{documentation/versioncheck}}</noinclude>

{{documentation/{{documentation/version}}/module-header}}



{{documentation/{{documentation/version}}/module-section|Introduction and Acknowledgements}}
{{documentation/{{documentation/version}}/module-introduction-start|{{documentation/modulename}}}}
{{documentation/{{documentation/version}}/module-introduction-row}}
Extension: [[Documentation/{{documentation/version}}/Extensions/GyroGuide|GyroGuide]] 
Acknowledgments:
This work is supported by International Scientific and Technical Cooperation Project of Zhejiang Province (Grant 2012C34G2020027) 
Author: Ruifeng Chen, Luping Fang, Qing Pan (College of Information Engineering, Zhejiang University of Technology, Hangzhou, China),Xiaolei Chen, Jiashu Zhang (Department of Neurosurgery, PLA General Hospital, Beijing, China) 
Contact: Luping Fang <email>flp@zjut.edu.cn</email> 
{{documentation/{{documentation/version}}/module-introduction-row}}

{{documentation/{{documentation/version}}/module-introduction-end}}


{{documentation/{{documentation/version}}/module-section|Module Description}}
{|
*The module should be used in cooperation with “Markups” module. First, it is required to choose five fiducial points to define two mutually-perpendicular planes as the Registration Markers. Second, set a target point and an entry point. Third, click the “Calculate” button to obtain the puncture path information, including the puncture depth and the angles between the puncture path and the reference planes. Finally, these results are displayed on a monitor or transmitted to the gyroscope-based device to assist the surgical operation.

|
|}


{{documentation/{{documentation/version}}/module-section|Use Cases}}
{|
Puncture surgery (e.g. endoscopic insertion) is a typical example to show the use of this module. This module calculates the distance of the puncture path and the angle between the probe and the reference planes. The module can also transmit the calculation results to the gyroscope-based device to facilitate the surgical operation.
|}


{{documentation/{{documentation/version}}/module-section|Tutorials}}
*1 Load MRI/CT images of brain [[File:GyroGuide-Step-1.png|200px]]
*2 Define “Markers”, “Target Point” and “Entry Point” using the Markups module. [[File:GyroGuide-Step-2.png|400px]]
*3 Load the defined fiducial lists [[File:GyroGuide-Step-3.png]]
:Select GyroGuide module
: 1 Select the fiducial list - Markers as the markers which define the reference planes.
: 2 Select the fiducial list – Target as the target point
: 3 Select the fiducial list – Entry as the entry point
*4 Calculate puncture path information 
:Click the “Calculate” button. The puncture path information will be displayed in the “Results” section. [[File:GyroGuide-Step-4.png|500px]]
*5 Export the results 
:Input IP address and port of the puncture instrument in the “Exporter” panel. Click “Send”. The calculated puncture path information could be transmitted to the gyroscope-based device to facilitate the surgical operation.


{{documentation/{{documentation/version}}/module-section|Panels and their use}}

{|
|[[File:GyroGuide-Panel.png|400px]]
*GyroGuide 
Markers 
It’s a fiducial list which consists of five fiducial points. Three points define the “Red Plane”. The other two points define the “Green Plane” which is perpendicular to the “Red Plane”. The “Blue Plane” is the one perpendicular to both the “Red Plane” and the “Green Plane”. Before measuring angles, the reference planes of the gyroscope have to be registered to the planes defined by the markers. 

Target Point 
The fiducial point which represents the target of the puncture. 

Entry Point 
The fiducial point which represents the entry of the puncture. 

Calculate Button 
Click the button to calculate the puncture path information. 
Angles between Puncture Path and Red Plane/Green Plane/Blue Plane 
The included angle between the puncture path and the red plane, green plane and blue plane, respectively. 
Distance between Target and Entry Point 
The length of the recommended puncture path. 
Exporter 
Hostname IP address of the puncture device. Default: localhost 
Port Port of the puncture device. Default: 18944 
Send Button Send the calculated results to the designated puncture device, which supports OpenIGTLink protocol. 
}


{{documentation/{{documentation/version}}/module-section|Similar Modules}}
*N/A

{{documentation/{{documentation/version}}/module-section|References}}
* N/A


{{documentation/{{documentation/version}}/module-section|Information for Developers}}
{{documentation/{{documentation/version}}/module-developerinfo}}


{{documentation/{{documentation/version}}/module-footer}}
[[Category:Documentation/{{documentation/version}}/Modules/Segmentation]]

Documentation/Nightly/Modules/GyroGuide

2014-01-22T07:34:32Z

Lpfang: Created page with '<noinclude>{{documentation/versioncheck}}</noinclude>  {{documentation/{{documentation/version}}/module-header}} <!-- -----------------------…'

<noinclude>{{documentation/versioncheck}}</noinclude>

{{documentation/{{documentation/version}}/module-header}}



{{documentation/{{documentation/version}}/module-section|Introduction and Acknowledgements}}
{{documentation/{{documentation/version}}/module-introduction-start|{{documentation/modulename}}}}
{{documentation/{{documentation/version}}/module-introduction-row}}
Extension: [[Documentation/{{documentation/version}}/Extensions/GyroGuide|GyroGuide]] 
Acknowledgments:
This work is supported by International Scientific and Technical Cooperation Project of Zhejiang Province (Grant 2012C34G2020027) 
Author: Ruifeng Chen, Luping Fang, Qing Pan (College of Information Engineering, Zhejiang University of Technology, Hangzhou, China),Xiaolei Chen, Jiashu Zhang (Department of Neurosurgery, PLA General Hospital, Beijing, China) 
Contact: Luping Fang <email>flp@zjut.edu.cn</email> 
{{documentation/{{documentation/version}}/module-introduction-row}}

{{documentation/{{documentation/version}}/module-introduction-end}}


{{documentation/{{documentation/version}}/module-section|Module Description}}
{|
*The module should be used in cooperation with “Markups” module. First, it is required to choose five fiducial points to define two mutually-perpendicular planes as the Registration Markers. Second, set a target point and an entry point. Third, click the “Calculate” button to obtain the puncture path information, including the puncture depth and the angles between the puncture path and the reference planes. Finally, these results are displayed on a monitor or transmitted to the gyroscope-based device to assist the surgical operation.

|
|}


{{documentation/{{documentation/version}}/module-section|Use Cases}}
{|
Puncture surgery (e.g. endoscopic insertion) is a typical example to show the use of this module. This module calculates the distance of the puncture path and the angle between the probe and the reference planes. The module can also transmit the calculation results to the gyroscope-based device to facilitate the surgical operation.
|}


{{documentation/{{documentation/version}}/module-section|Tutorials}}
*1 Load MRI/CT images of brain [[File:GyroGuide-Step-1.png]]
*2 Define “Markers”, “Target Point” and “Entry Point” using the Markups module. [[File:GyroGuide-Step-2.png]]
*3 Load the defined fiducial lists [[File:GyroGuide-Step-3.png]]
:Select GyroGuide module
: 1 Select the fiducial list - Markers as the markers which define the reference planes.
: 2 Select the fiducial list – Target as the target point
: 3 Select the fiducial list – Entry as the entry point
*4 Calculate puncture path information 
:Click the “Calculate” button. The puncture path information will be displayed in the “Results” section. [[File:GyroGuide-Step-4.png]]
*5 Export the results 
:Input IP address and port of the puncture instrument in the “Exporter” panel. Click “Send”. The calculated puncture path information could be transmitted to the gyroscope-based device to facilitate the surgical operation.


{{documentation/{{documentation/version}}/module-section|Panels and their use}}

{|
|[[File:GyroGuide-Panel.png]]
*GyroGuide 
Markers 
It’s a fiducial list which consists of five fiducial points. Three points define the “Red Plane”. The other two points define the “Green Plane” which is perpendicular to the “Red Plane”. The “Blue Plane” is the one perpendicular to both the “Red Plane” and the “Green Plane”. Before measuring angles, the reference planes of the gyroscope have to be registered to the planes defined by the markers. 

Target Point 
The fiducial point which represents the target of the puncture. 

Entry Point 
The fiducial point which represents the entry of the puncture. 

Calculate Button 
Click the button to calculate the puncture path information. 
Angles between Puncture Path and Red Plane/Green Plane/Blue Plane 
The included angle between the puncture path and the red plane, green plane and blue plane, respectively. 
Distance between Target and Entry Point 
The length of the recommended puncture path. 
Exporter 
Hostname IP address of the puncture device. Default: localhost 
Port Port of the puncture device. Default: 18944 
Send Button Send the calculated results to the designated puncture device, which supports OpenIGTLink protocol. 
}


{{documentation/{{documentation/version}}/module-section|Similar Modules}}
*N/A

{{documentation/{{documentation/version}}/module-section|References}}
* N/A


{{documentation/{{documentation/version}}/module-section|Information for Developers}}
{{documentation/{{documentation/version}}/module-developerinfo}}


{{documentation/{{documentation/version}}/module-footer}}
[[Category:Documentation/{{documentation/version}}/Modules/Segmentation]]

File:GyroGuide-Panel.png

2014-01-22T07:24:20Z

Lpfang:

File:GyroGuide-Step-4.png

2014-01-22T07:23:55Z

Lpfang:

File:GyroGuide-Step-3.png

2014-01-22T07:23:24Z

Lpfang:

File:GyroGuide-Step-2.png

2014-01-22T07:22:46Z

Lpfang:

File:GyroGuide-Step-1.png

2014-01-22T07:19:33Z

Lpfang:

File:EndoscopyGUI.png

2011-08-10T18:01:58Z

Lpfang:

Slicer4:Internationalization of Slicer

2011-08-10T17:57:59Z

Lpfang: /* Scripted Module */

[[Slicer4:Developers| Back to Slicer 4 Developers]]

=Introduction=

This pages contains notes on source code additions and modifications of different modules within Slicer for the internationalization purpose.
=QT-based Internationalization=
Internationalization is well supported in QT. A lot of modules of Slicer are developed on QT. This has set a good ground for the internationalization of Slicer.
*basic idea
In Qt, tr() is one of the static public members of QObject class, which returns a translated version of input sourceText.
QString QObject::tr ( const char * sourceText, const char * disambiguation = 0, int n = -1 ) [static]
tr() will search the translation in a so-called translation file. If nothing is found, then the sourceText instead of the translated version will be displayed directly. For example,
label->setText(tr("Measurement"));
*translation file template
The following is an example of the translation file, from English to Chinese.
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE TS>
<TS version="2.0" language="zh_CN">
<context>
<name>qSlicerMainWindow</name>
<message>
<source>&File</source>
<translation>文件</translation>
</message>
<message>
<source>&Edit</source>
<translation>编辑</translation>
</message>
<message>
<source>Feedback</source>
<translation>反馈</translation>
</message>
<message>
<source>Import Scene</source>
<translation>导入场景</translation>
</message>
<message>
<source>Add Data</source>
<translation>添加数据</translation>
</message>
</context>
</TS>
In the above example, all the texts are within the scope of qSlicerMainWindow class. So, 'qSlicerMainWindo' occurs in section 'name'.

*Prepare translation file
The translation file can be prepared manually based on the above template and file name extension should be like .ts, for example, lang_hz.ts, lang_de.hz, etc.
Translation file can also be created conviently by a tool called lupdate. lupdate is a command line tool that finds the translatable strings (tr())in the specified source, header and Qt Designer interface files, and produces or updates .ts translation files. TS files are text files, which can be viewed or edited by any text editor tools. The following command searchs the folder and subfolders for tr() occurences in files (.ui, .h, .cxx) and create translation file test.ts.
Usage: lupdate c:\myproject\slicer4\ -ts test.ts

lrelease is a command line tool that produces QM files out of TS files. The QM file format is a compact binary format that is used by the localized application. It provides extremely fast lookups for translations.
Usage: lrelease test.ts

*Modifications to the source codes:

In file \Slicer4\Base\QTCore\qSlicerCoreApplication.h, add the following line:
#include <QTranslator>
In file \Slicer4\Applications\SlicerQT\main.cxx (around line#230), add the following lines:
static QTranslator* translator;
if (translator != NULL)
{
qApp->removeTranslator(translator);
delete translator;
translator = NULL;
}
QString langCode= argv[1];
translator = new QTranslator;
QString qmFilename = "lang_" + langCode;
if (translator->load(qmFilename))
{
qApp->installTranslator(translator);
}

If slicer4 launches with the first argument being 'zh', lang_zh.qm will be installed. The extension .qm doesn't need to be specified, for installTranslator only loads QM file.

*To be continued

=Scripted Module=
Some modules are implemented in Python. Endoscopy is one of the typical examples. In endoscopy.py, if we change the code in line#10
parent.titel = “Endoscopy”
to
parent.title = slicer.app.translate(self.__class__.__name__, "Endoscopy")
then "Endoscopy" can be shown in other languages.Similarily, other displayable strings can be handled in the same way.
In endoscopy.py, classes 'Endoscopy' and 'EndoscopyWidget' are defined. String "Endoscopy" is used in Class 'Endoscopy'. Strings like 'Path' ,'Input Fiducial' and 'camera' are used in 'EndoscopyWidget'. The following lines should be appended in the TS file:

<context>
<name>Endoscopy</name>
<message>
<source>Endoscopy</source>
<translation>内窥镜</translation>
</message>
</context>
<context>
<name>EndoscopyWidget</name>
<message>
<source>Path</source>
<translation>路径</translation>
</message>
<message>
<source>Camera</source>
<translation>相机(Camera)</translation>
</message>
<message>
<source>Input Fiducials</source>
<translation>输入参考点(Input Fiducials)</translation>
</message>
</context>
[[image:EndoscopyGUI.png|left|thumb|400px|Screenshot of the Chinese version of the GUI for Endoscopy module]]

=To be continued=

Slicer4:Internationalization of Slicer

2011-08-10T17:49:09Z

Lpfang: /* Scripted Module */

Slicer4:Internationalization of Slicer

2011-08-09T14:00:53Z

Lpfang: /* Scripted Module */

[[Slicer4:Developers| Back to Slicer 4 Developers]]

=Introduction=

This pages contains notes on source code additions and modifications of different modules within Slicer for the internationalization purpose.
=QT-based Internationalization=
Internationalization is well supported in QT. A lot of modules of Slicer are developed on QT. This has set a good ground for the internationalization of Slicer.
*basic idea
In Qt, tr() is one of the static public members of QObject class, which returns a translated version of input sourceText.
QString QObject::tr ( const char * sourceText, const char * disambiguation = 0, int n = -1 ) [static]
tr() will search the translation in a so-called translation file. If nothing is found, then the sourceText instead of the translated version will be displayed directly. For example,
label->setText(tr("Measurement"));
*translation file template
The following is an example of the translation file, from English to Chinese.
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE TS>
<TS version="2.0" language="zh_CN">
<context>
<name>qSlicerMainWindow</name>
<message>
<source>&File</source>
<translation>文件</translation>
</message>
<message>
<source>&Edit</source>
<translation>编辑</translation>
</message>
<message>
<source>Feedback</source>
<translation>反馈</translation>
</message>
<message>
<source>Import Scene</source>
<translation>导入场景</translation>
</message>
<message>
<source>Add Data</source>
<translation>添加数据</translation>
</message>
</context>
</TS>
In the above example, all the texts are within the scope of qSlicerMainWindow class. So, 'qSlicerMainWindo' occurs in section 'name'.

*Prepare translation file
The translation file can be prepared manually based on the above template and file name extension should be like .ts, for example, lang_hz.ts, lang_de.hz, etc.
Translation file can also be created conviently by a tool called lupdate. lupdate is a command line tool that finds the translatable strings (tr())in the specified source, header and Qt Designer interface files, and produces or updates .ts translation files. TS files are text files, which can be viewed or edited by any text editor tools. The following command searchs the folder and subfolders for tr() occurences in files (.ui, .h, .cxx) and create translation file test.ts.
Usage: lupdate c:\myproject\slicer4\ -ts test.ts

lrelease is a command line tool that produces QM files out of TS files. The QM file format is a compact binary format that is used by the localized application. It provides extremely fast lookups for translations.
Usage: lrelease test.ts

*Modifications to the source codes:

In file \Slicer4\Base\QTCore\qSlicerCoreApplication.h, add the following line:
#include <QTranslator>
In file \Slicer4\Applications\SlicerQT\main.cxx (around line#230), add the following lines:
static QTranslator* translator;
if (translator != NULL)
{
qApp->removeTranslator(translator);
delete translator;
translator = NULL;
}
QString langCode= argv[1];
translator = new QTranslator;
QString qmFilename = "lang_" + langCode;
if (translator->load(qmFilename))
{
qApp->installTranslator(translator);
}

If slicer4 launches with the first argument being 'zh', lang_zh.qm will be installed. The extension .qm doesn't need to be specified, for installTranslator only loads QM file.

*To be continued

=Scripted Module=
Some modules are implemented in Python. Endoscopy is one of the typical examples. In endoscopy.py, if we change the code in line#10
parent.titel = “Endoscopy”
to
parent.title = slicer.app.translate(self.__class__.__name__, "Endoscopy")
then "Endoscopy" can be shown in other languages.Similarily, other displayable strings can be handled in the same way.
In endoscopy.py, classes 'Endoscopy' and 'EndoscopyWidget' are defined. String "Endoscopy" is used in Class 'Endoscopy'. String 'Path' is used in 'EndoscopyWidget'. The following lines should be appended in the TS file:

<context>
<name>Endoscopy</name>
<message>
<source>Endoscopy</source>
<translation>内窥镜</translation>
</message>
</context>
<context>
<name>EndoscopyWidget</name>
<message>
<source>Path</source>
<translation>路径</translation>
</message>
</context>

=To be continued=

Slicer4:Internationalization of Slicer

2011-08-09T13:53:53Z

Lpfang: /* Scripted Module */

[[Slicer4:Developers| Back to Slicer 4 Developers]]

=Introduction=

This pages contains notes on source code additions and modifications of different modules within Slicer for the internationalization purpose.
=QT-based Internationalization=
Internationalization is well supported in QT. A lot of modules of Slicer are developed on QT. This has set a good ground for the internationalization of Slicer.
*basic idea
In Qt, tr() is one of the static public members of QObject class, which returns a translated version of input sourceText.
QString QObject::tr ( const char * sourceText, const char * disambiguation = 0, int n = -1 ) [static]
tr() will search the translation in a so-called translation file. If nothing is found, then the sourceText instead of the translated version will be displayed directly. For example,
label->setText(tr("Measurement"));
*translation file template
The following is an example of the translation file, from English to Chinese.
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE TS>
<TS version="2.0" language="zh_CN">
<context>
<name>qSlicerMainWindow</name>
<message>
<source>&File</source>
<translation>文件</translation>
</message>
<message>
<source>&Edit</source>
<translation>编辑</translation>
</message>
<message>
<source>Feedback</source>
<translation>反馈</translation>
</message>
<message>
<source>Import Scene</source>
<translation>导入场景</translation>
</message>
<message>
<source>Add Data</source>
<translation>添加数据</translation>
</message>
</context>
</TS>
In the above example, all the texts are within the scope of qSlicerMainWindow class. So, 'qSlicerMainWindo' occurs in section 'name'.

*Prepare translation file
The translation file can be prepared manually based on the above template and file name extension should be like .ts, for example, lang_hz.ts, lang_de.hz, etc.
Translation file can also be created conviently by a tool called lupdate. lupdate is a command line tool that finds the translatable strings (tr())in the specified source, header and Qt Designer interface files, and produces or updates .ts translation files. TS files are text files, which can be viewed or edited by any text editor tools. The following command searchs the folder and subfolders for tr() occurences in files (.ui, .h, .cxx) and create translation file test.ts.
Usage: lupdate c:\myproject\slicer4\ -ts test.ts

lrelease is a command line tool that produces QM files out of TS files. The QM file format is a compact binary format that is used by the localized application. It provides extremely fast lookups for translations.
Usage: lrelease test.ts

*Modifications to the source codes:

In file \Slicer4\Base\QTCore\qSlicerCoreApplication.h, add the following line:
#include <QTranslator>
In file \Slicer4\Applications\SlicerQT\main.cxx (around line#230), add the following lines:
static QTranslator* translator;
if (translator != NULL)
{
qApp->removeTranslator(translator);
delete translator;
translator = NULL;
}
QString langCode= argv[1];
translator = new QTranslator;
QString qmFilename = "lang_" + langCode;
if (translator->load(qmFilename))
{
qApp->installTranslator(translator);
}

If slicer4 launches with the first argument being 'zh', lang_zh.qm will be installed. The extension .qm doesn't need to be specified, for installTranslator only loads QM file.

*To be continued

=Scripted Module=
Some modules are implemented in Python. Endoscopy is one of the typical examples. In endoscopy.py, if we change the code in line#10
parent.titel = “Endoscopy”
to
parent.title = slicer.app.translate(self.__class__.__name__, "Endoscopy")
then "Endoscopy" can be shown in other languages.Similarily, other displayable strings can be handled in the same way.
Browse file endoscopy.py, it is found that string "Endoscopy" is within Class 'Endoscopy'. Therefore, the following lines should be appended in the TS file:

=To be continued=

Slicer4:Internationalization of Slicer

2011-08-09T13:35:39Z

Lpfang: /* QT-based Internationalization */

Slicer4:Internationalization of Slicer

2011-08-09T13:34:42Z

Lpfang: /* QT-based Internationalization */

[[Slicer4:Developers| Back to Slicer 4 Developers]]

=Introduction=

This pages contains notes on source code additions and modifications of different modules within Slicer for the internationalization purpose.
=QT-based Internationalization=
Internationalization is well supported in QT. A lot of modules of Slicer are developed on QT. This has set a good ground for the internationalization of Slicer.
*basic idea
In Qt, tr() is one of the static public members of QObject class, which returns a translated version of input sourceText.
QString QObject::tr ( const char * sourceText, const char * disambiguation = 0, int n = -1 ) [static]
tr() will search the translation in a so-called translation file. If nothing is found, then the sourceText instead of the translated version will be displayed directly. For example,
label->setText(tr("Measurement"));
*translation file template
The following is an example of the translation file, from English to Chinese.
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE TS>
<TS version="2.0" language="zh_CN">
<context>
<name>qSlicerMainWindow</name>
<message>
<source>&File</source>
<translation>文件</translation>
</message>
<message>
<source>&Edit</source>
<translation>编辑</translation>
</message>
<message>
<source>Feedback</source>
<translation>反馈</translation>
</message>
<message>
<source>Import Scene</source>
<translation>导入场景</translation>
</message>
<message>
<source>Add Data</source>
<translation>添加数据</translation>
</message>
</context>
</TS>
In the above example, all the texts are within the scope of qSlicerMainWindow class. So, 'qSlicerMainWindo' occurs in section 'name'.

*Prepare translation file
The translation file can be prepared manually based on the above template and file name extension should be like .ts, for example, lang_hz.ts, lang_de.hz, etc.
Translation file can also be created conviently by a tool called lupdate. lupdate is a command line tool that finds the translatable strings (tr())in the specified source, header and Qt Designer interface files, and produces or updates .ts translation files. TS files are text files, which can be viewed or edited by any text editor tools. The following command searchs the folder and subfolders for tr() occurences in files (.ui,.h,.cxx) and create translation file test.ts.
Usage: lupdate c:\myproject\slicer4\ -ts test.ts

lrelease is a command line tool that produces QM files out of TS files. The QM file format is a compact binary format that is used by the localized application. It provides extremely fast lookups for translations.
Usage: lrelease test.ts

*Modifications to the source codes:

In file \Slicer4\Base\QTCore\qSlicerCoreApplication.h, add the following line:
#include <QTranslator>
In file \Slicer4\Applications\SlicerQT\main.cxx (around line#230), add the following lines:
static QTranslator* translator;
if (translator != NULL)
{
qApp->removeTranslator(translator);
delete translator;
translator = NULL;
}
QString langCode= argv[1];
translator = new QTranslator;
QString qmFilename = "lang_" + langCode;
if (translator->load(qmFilename))
{
qApp->installTranslator(translator);
}

If slicer4 launches with the first argument being 'zh', lang_zh.qm will be installed. The extension .qm doesn't need to be specified, for installTranslator only loads QM file.

*To be continued

=Scripted Module=
Some modules are implemented in Python. Endoscopy is one of the typical examples. In endoscopy.py, if we change the code in line#10
parent.titel = “Endoscopy”
to
parent.title = slicer.app.translate(self.__class__.__name__, "Endoscopy")
then "Endoscopy" can be shown in other languages.Similarily, other displayable strings can be handled in the same way.

=To be continued=

Slicer4:Internationalization of Slicer

2011-08-08T16:50:28Z

Lpfang: /* QT-based Internationalization */

[[Slicer4:Developers| Back to Slicer 4 Developers]]

=Introduction=

This pages contains notes on source code additions and modifications of different modules within Slicer for the internationalization purpose.
=QT-based Internationalization=
Internationalization is well supported in QT. A lot of modules of Slicer are developed on QT. This has set a good ground for the internationalization of Slicer.
*basic idea
In Qt, tr() is one of the static public members of QObject class, which returns a translated version of input sourceText.
QString QObject::tr ( const char * sourceText, const char * disambiguation = 0, int n = -1 ) [static]
tr() will search the translation in a so-called translation file. If nothing is found, then the sourceText instead of the translated version will be displayed directly. For example,
label->setText(tr("Measurement"));
*translation file template
The following is an example of the translation file, from English to Chinese.
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE TS>
<TS version="2.0" language="zh_CN">
<context>
<name>qSlicerMainWindow</name>
<message>
<source>&File</source>
<translation>文件</translation>
</message>
<message>
<source>&Edit</source>
<translation>编辑</translation>
</message>
<message>
<source>Feedback</source>
<translation>反馈</translation>
</message>
<message>
<source>Import Scene</source>
<translation>导入场景</translation>
</message>
<message>
<source>Add Data</source>
<translation>添加数据</translation>
</message>
</context>
</TS>
In the above example, all the texts are within the scope of qSlicerMainWindow class. So, 'qSlicerMainWindo' occurs in section 'name'.

*The following modifications are are needed:

In file \Slicer4\Base\QTCore\qSlicerCoreApplication.h, add the following line:
#include <QTranslator>
In file \Slicer4\Applications\SlicerQT\main.cxx (around line#230), add the following lines:
static QTranslator* translator;
if (translator != NULL)
{
qApp->removeTranslator(translator);
delete translator;
translator = NULL;
}
QString langCode= argv[1];
translator = new QTranslator;
QString qmFilename = "lang_" + langCode;
if (translator->load(qmFilename))
{
qApp->installTranslator(translator);
}
*Prepare translation file
The translation file can be prepared manually based on the above template and file name extension should be like .ts, for example, lang_hz.ts, lang_de.hz, etc.
Translation file can also be created conviently by a tool called lupdate. lupdate is a command line tool that finds the translatable strings (tr())in the specified source, header and Qt Designer interface files, and produces or updates .ts translation files. The following command will search the folder and subfolders for tr() occurences in files (.ui,.h,.cxx) and create translation file test.tr.
Usage: Lupdate c:\myproject\slicer4\ -ts test.ts

*To be continued

=Scripted Module=
Some modules are implemented in Python. Endoscopy is one of the typical examples. In endoscopy.py, if we change the code in line#10
parent.titel = “Endoscopy”
to
parent.title = slicer.app.translate(self.__class__.__name__, "Endoscopy")
then "Endoscopy" can be shown in other languages.Similarily, other displayable strings can be handled in the same way.

=To be continued=

Slicer4:Internationalization of Slicer

2011-08-08T16:29:33Z

Lpfang:

Slicer4:Internationalization of Slicer

2011-08-08T16:28:53Z

Lpfang: /* QT-based Internationalization */

Slicer4:Internationalization of Slicer

2011-08-08T16:28:01Z

Lpfang: /* QT-based Internationalization */

Slicer4:Internationalization of Slicer

2011-08-08T15:36:47Z

Lpfang:

Slicer4:Internationalization of Slicer

2011-08-08T15:24:52Z

Lpfang:

Slicer4:Internationalization of Slicer

2011-08-08T15:20:13Z

Lpfang:

Slicer4:Internationalization of Slicer

2011-08-08T14:59:22Z

Lpfang:

Slicer4:Internationalization of Slicer

2011-08-08T14:56:02Z

Lpfang: Created page with '=Introduction= This pages contains notes on source code additions and modifications of different modules within Slicer for the internationalization purpose.'

=Introduction=
This pages contains notes on source code additions and modifications of different modules within Slicer for the internationalization purpose.

Slicer4:Developers

2011-08-08T14:44:47Z

Lpfang: /* Projects */

''Slicer 4 is now at the stage where developers can begin to port their modules from Slicer3 to Slicer4. If you are working on extensions, you should continue to use Slicer 3 as your target platform. If you are not sure, ask us.''

For now, refer to [http://www.na-mic.org/Wiki/images/5/51/2010_Project_Week_Slicer.ppt the 3D Slicer Status Presentation from the June 2010 Project Week] for planning and transition information.

Work on 3D Slicer version 4 has begun in June of 2010. It is expected that Slicer4 will be released in 2011. Please see the [[Slicer4|Slicer4 Description Page]] for detailed information on the current plans.

*For information about older versions of Slicer, see [[Developers|here]].

=Introduction=
*This page of for scientist who write source code, if you want to use a pre-compiled version of Slicer, please go to the [http://www.slicer.org/pages/Special:SlicerDownloads download page].
*Slicer 4 will include a number of fundamental changes to the infrastructure:
**Qt widgets will replace KWW widgets
**CMAKE superbuild will replace getbuildtest

=Developers Documentation=

*[[Slicer4:QtPort/Tutorials|Tutorial on how to write code with Slicer 4 Qt on your computer]] ('''Julien Finet''', Jean-Christophe Fillion-Robin)

=Projects=
(please add your new project to the top of the table)

 
{|width="800px" border="1"
|-
|style="background:#ddf" width="60%"|'''Slicer4 Projects'''
|bgcolor="#ddf" valign="top"|'''Key People''' Bold names are responsible for an aspect of the project.
|-
|[[Slicer4:Internationalization_of_Slicer|Internationalization of Slicer]]
||'''Luping Fang''', Steve Pieper, Julien Finet, Jean-Christophe Fillion-Robin
|-
|[[Slicer4:ArchitectureDesign|Architecture design (CTK,MRML,Logic,Qt)]]
||'''Steve Pieper''', Julien Finet, Jean-Christophe Fillion-Robin
|-
|[[Slicer4:Build_Instructions|Slicer4 build instructions]]
||'''Jean-Christophe Fillion-Robin''', Julien Finet
|-
|[[Slicer4:MultiVolumeContainer|MultiVolumeContainers: Infrastructure for RGB, RT labelmaps, DCE, Recist, "What changed"]]
||'''Ron Kikinis'''
|-
|[[Slicer4:VectorImageVisualization|Infrastructure for multi-volumes]]
||'''Demian Wassermann''', Lauren Odonnell, CF Westin
|-
|[[Slicer4:WikipediaNotes|Updating the Wikipedia pages for Slicer]]
||'''Ann Adams''', Ron Kikinis, Steve Pieper
|-
|[[Slicer4:Diffusion|Porting Diffusion from Slicer 3 to 4]]
||'''Demian Wassermann''', Alex Yarmanovich, Steve Pieper
|-
||[[Slicer4:DownloadPackage|Slicer 4 download package]]
||'''Jean-Christophe Fillion-Robin''', Stephen Aylward, Steve Pieper
|-
||[[Slicer4:VolumeRenderingPorting|Porting Volume Rendering from Slicer 3 to 4]]
||'''Julien Finet''', Alex Yarmanovich, Curtis Lisle
|-
||[[Slicer4:CMAKESuperbuild|CMAKE superbuild]]
||'''Jean-Christophe Fillion-Robin''', Stephen Aylward
|-
||[[Slicer4:Download Data|Download Data Appearance]]
||'''Ron Kikinis''', Zach Mullen, Julien Jomier
|-
||[[Slicer4:DisplayModule|Slicer 4 Display Module]]
||'''Wendy Plesniak''', Ron Kikinis
|-
||[[Slicer4:VTKWidgets|Slicer 4 VTK Widgets tuning]]
||'''Will Schroeder''', Jean-Christophe Fillion-Robin
|-
||[[Slicer4:ViewerDesign| Slicer 4 Viewer Presentation Layer Design & Guidelines ]]
||'''Wendy Plesniak''', Ron Kikinis, Julien Jomier, Jim Miller, Stephen Aylward
|-
||[[Slicer4:UIDesign|Slicer 4 UI design]]
||'''Wendy Plesniak''',
|-
||[[Slicer4:SceneViewsModule|Slicer 4 SceneViews Module]]
||'''Nicole Aucoin'''
|-
||[[Slicer4:EMSegment|EM Segmenter]]
||'''Kilian Pohl''', Daniel Haehn, Dominique Belhachemi
|-
||[[Slicer4:Annotation|Annotation]]
||'''Nicole Aucoin''', Daniel Haehn, Kilian Pohl
|-
||[[Slicer4:QtPort|Porting Slicer from kww to Qt]]
||'''Julien Finet''', Jean-Christophe Fillion-Robin, Steve Pieper, Stephen Aylward
|}

=Extensions=

 
{|width="800px" border="1"
|-
|style="background:#ddf" width="60%"|'''Slicer4 Extensions'''
|bgcolor="#ddf" valign="top"|'''Key People''' Bold names are responsible for an aspect of the project.
|-
||[[Slicer4:VMTK|VMTK]]
||'''Daniel Haehn'''
|-
||[[Slicer4:DTI-EM-Clustering|DTI EM Clustering]]
||'''Mahnaz Maddah''', Jim Miller
|}

= Quick Links for Developers =
This section centrally locates many existing (and developing) wiki pages useful to Slicer4 developers.

== Slicer 4 Quick links to the Source code ==
The Slicer4 git repository:

*'''Put link here'''

{|width="800px" border="1"
|-
|style="background:#ddf" width="60%"|'''General Slicer4 Quick Links'''
|style="background:#ddf" width="40%"|'''Debugging Slicer4 Quick Links'''
|-
||[[Slicer4:Build_Instructions|Slicer4 build instructions]]
||[http://www.cdash.org/CDash/index.php?project=Slicer4 Slicer4 Dashboard]
|-
||Use [http://viewvc.slicer.org ViewVC to browse the repository]
||[http://na-mic.org/Mantis/main_page.php Slicer Bug Tracker]
|-
||[http://www.na-mic.org/Wiki/index.php/Engineering:SandBox Instructions for NA-MIC svn]
||
|-
||[http://slicer.org/doc/html/ Doxygen documentation for Slicer4].
||
|-
||The [[Slicer4:VisualBlog|Slicer4 VisualBlog]] shows screenshots of slicer developments.
||
|-
||Developers should follow the [[Slicer4:Style|Slicer 4 Coding Style]].
|
|-
||[[Slicer4:QtPort/Tutorials|QtPort Tutorials]]
|
|}

==Developers' Mailing List ==
Discussion of Slicer 3 and Slicer 4 takes place on the slicer-devel at massmail.spl.harvard.edu list. To join developer's mailing list, send a request to: slicer-devel-request at massmail.spl.harvard.edu with the keyword '''''subscribe''''' as the subject. Or access the [http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel slicer-devel archives and web administration interface].