Difference between revisions of "Projects:RegistrationDocumentation"

From NAMIC Wiki
Jump to: navigation, search
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/")
 
(116 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:Registration]]
 +
[[Projects:ARRASuplements|Back to ARRA main page]]
 
==Use Case Library==
 
==Use Case Library==
*this will contain a list of the most common scenarios encountered for Slicer Registration. Each case will contain a dataset, a parameter set, a guided tutorial with example result. The hierarchy will be represented graphically as a tree and as a list with links to the abovementioned data. The library will be as exhaustive as possible, containin brain and non-brain, different modalities (MRI, CT, PET/SPECT).
+
*'''[[Projects:RegistrationDocumentation:UseCaseInventory| Registration Case Library ]]'''
*considered is also a list of troubleshooting cases, i.e. a list of the most common sources of registration failure, again complete with dataset, tutorial and remedy.
+
*'''[[Projects:RegistrationDocumentation:UseCaseAdvertisement|Use Case Sharing Advertisment Page]]'''
==Reference Manual==
+
*[[Projects:RegistrationDocumentation:UseCaseInventoryNotes|Notes & concepts about the Registration Case Library]]
*This will contain detailed descriptions of each parameter and each control element within the slicer registration module. The description should help the user understand what exactly that function/parameter does and if/how useful it will be for their specific registration problem
 
*Preferred formats: Slicer Wiki, maybe PDF
 
==User Manuals==
 
*this documentation will discussing the main registration module functionality as a whole, focusing not on the individual controls but the main workflow.
 
formats: Slicer Wiki, PowerPoint.
 
*Also included in this category are Background Tutorials, explaining the basics of registration, formats: PowerPoint. Minimal understanding of the inner workings of a registration optimization algorithm is essential to understand and judge the results obtained and obtainable.
 
==Training Video Tutorials==
 
  
[[Image:TrainingMovieThumbnail.jpg|thumb|frame| [[Media:VideoTutorialDemo_v1_0.mov|Training Movie Demo (1min)]]]]
+
== Development Efforts ==
*These movies contain step by step instructions, running through each of the use-cases described above.
+
*Slicer4: '''[[Projects:RegistrationDocumentation:Developer4|Notes & feedbacl for GUI and algorithm implementation. Testing Summaries]]'''
*An example of the features/character of a video tutorial is here: [[Media:VideoTutorialDemo_v1_0.mov]]
+
*Slicer3: [[Projects:RegistrationDocumentation:Developer|Notes & ideas for GUI and algorithm implementation. Discussion platform with the developer group]]
*video tutorials have become a popular and widespread form to document GUI interactions, particularly tutorials
+
*[[Projects:RegistrationDocumentation:RegEval_Anisotropy|'''Effects of Voxel Anisotropy and Intensity-Inhomogeneity on Image-Based 3D Registration''' ]]
* they can have almost  the quality of direct tutoring
+
*[[Projects:RegistrationDocumentation:Benchmarking|'''Benchmarking''']]
*they are compact in length and filesize (because the changes are local and small over time, MPEG compression is very effective with little quality loss), which makes them ideal for online distribution
+
*[[Projects:RegistrationDocumentation:ParameterTesting|Parameter Exploration]]
*movie viewing capability is mainstream, i.e. all OS will have this capability, viewers can be downloaded for free
+
*[[Projects:RegistrationDocumentation:Evaluation|Result Evaluation & Visualization]]
*the audio track can provide main instructions, motivation, commentary and an abundance of detail information at the right juncture, something very difficult to provide in other formats without overloading a tutorial
+
*[[Projects:RegistrationImprovement|Kitware Wiki on developer efforts]]
*the step by step interaction is captured unambiguously. We do not spend a lot of time and space in showing slides with screen captures.
 
*since they are easy to make and great software is inexpensive, potential use even for developer communication can be considered, e.g. to document complex bugs
 
*they have a low usage threshold, i.e. users are more inclined to watch a video than to dig through a power point presentation
 
*they are not all that useful for reference or main documentation material, e.g. a tutorial on main registration concepts is probably still better in PPT.
 
*formats: video files (quicktime, WMV, mp4 , Flash), optimized for streaming or download
 
  
== Ideas for Developers ==
+
==Reference Manual==
This will contain lists of ideas for GUI and function addition/improvements.
+
*The reference manual will be organized by submodules and contain detailed descriptions of each parameter and each control element within the slicer registration module. The description should help the user understand what exactly that function/parameter does and if/how useful it will be for their specific registration problem.  
*Both multi-resolution and the sequence of calls with increasing DOF could be implemented as a single recursive scheme. The caller provides an array of DOF and a matching array of resolution levels, which is processed by recursive calls with the first/last element taken from the list. A simulation Matlab program and example is  here: [[Projects:RegistrationImprovement:RecursiveScheme]]
+
* Each entry will have one short description (that could also serve as tooltip) and one longer, more technical explanation.
**The GUI can list the many combination as a single list of checkboxes for increasing DOF. The full list would be 3,6,7,9,12,b . The checked boxes provide the input string for the recursive call. [[Media:DOFHierarchy_GUI.jpg‎ ]]
+
* links to journal articles for in depth algorithm info
*direct links to Reference Manual from Widget tooltips? Can the static text or widget itself launch a link to the Reference manual entry on the Documentation Wiki? That would enable a one-click answer to "What does this button do?"
+
*Preferred formats:  Slicer Wiki, maybe PDF, cross-linking required
*decomposition of affine into the 4 3DOF components: translation, rotation, scaling, shearing. Can an SVD do this for 12DOF vs. 3 DOF? Having values that relate directly to geometry can help greatly in evaluating and adjusting results. E.g. user can tell visually which of the 3 rotations is most out of alignment. Checking the result rotation angles already provides a quick check and valuable info about where things went awry if solution is suboptimal. Also enables to decouple individual elements, i.e. extract the shear component etc. The current "Transforms" module already does this for translation & rotation, but the scale and shear portions are missing.
+
*'''[[Projects:RegistrationDocumentation:ReferenceManual|Draft Registration Reference Manual]]'''
  
 +
==User Manuals & Tutorials==
 +
*[https://www.slicer.org/wiki/Slicer3:Registration#Registration_in_3D_Slicer|'''Main Registration Portal Page''']
 +
*[[Media:NCIGT2010_RegistrBreakout_Slides_v3_1.ppt|'''Registration Basics, Registration Tools & User Support in Slicer''' (Powerpoint, 14MB)]]
 +
*[https://www.slicer.org/wiki/Slicer-3-6-FAQ '''FAQ & Cookbooks''']
 +
*The user manual will contain a systematic overview of registration functionality within 3DSlicer. formats: Slicer Wiki, PowerPoint.
 +
**[[Projects:RegistrationDocumentation:UserManual|Draft Registration User Manual]]
 +
**[[Projects:RegistrationDocumentation:DocumentationResources|notes and documentation resources]]
 +
*Tutorials will be case oriented and always demonstrate a particular task or feature
 +
**[[Projects:RegistrationDocumentation:VideoTutorials|Video Tutorials: showcase of specific workflow]]
 +
**Background Tutorials, explaining the basics of registration, formats: PowerPoint. Minimal understanding of the inner workings of a registration optimization algorithm is essential to understand and judge the results obtained and obtainable.
  
 +
== Contact ==
 +
*if there is anything you think would be of help to the 3DSlicer registration user, be that documentation, examples or features, we'd love to hear about it:
 +
**any questions/concerns are welcome on the slicer user mailing list: mailto:slicer-users@bwh.harvard.edu
 +
**particular questions/concerns re. these pages or Registration Documentation drop a line to  mailto:meier@bwh.harvard.edu
 +
----
  
 +
== Links ==
 +
*[[Downloads|Data links]]
 +
*[https://www.predict-hd.net huntington data]
  
----
+
*[[ITK_Registration_Optimization|Register Images Reference Material]]
  
== Links ==
+
*[[Events:Registration_Summit_August_2009|Registration Summit Aug'09]]
*Developer efforts (Kitware): [[Projects:RegistrationImprovement]]
+
*[[2009_Summer_Project_Week_Slicer3_registration]]
*Slicer Wiki: [http://www.slicer.org/slicerWiki/index.php/Documentation-3.5]
+
*[https://www.slicer.org/wiki/Documentation-3.5 Slicer Documentation 3.5]
*Slicer Bug Tracker: [http://na-mic.org/Mantis/my_view_page.php]
+
*[http://na-mic.org/Mantis/my_view_page.php|Slicer Bug Tracker]
 +
*[[AHM_2010]]
 +
*[[2010_Winter_Project_Week_RegistrationCaseLibrary|AHM 2010 Project Week: Registration Case Library Project Page]]
 +
*[https://www.slicer.org/wiki/Slicer3:Slicer3Brand#3D_Slicer_Visual_Communication_Guide Slicer Logo & Communication Guide]
 
*NAMIC registration:
 
*NAMIC registration:
*Contact: Dominik Meier : meier@bwh.harvard.edu
+
*Contact: Dominik Meier : mailto:meier@bwh.harvard.edu
 +
 
 +
=== Bundled Registration and Tests ===
 +
* http://www.na-mic.org/Wiki/index.php/Projects:DBP2:Harvard:Registration_Documentation
 +
* http://www.na-mic.org/Wiki/index.php/MeningiomaMRIRegistrationStudy#Limitations_of_the_Slicer_registration_tools
 +
* [http://www.na-mic.org/Wiki/index.php/Vervet_MRI_registration Vervet head MRI atlas-to-subject registration]
 +
* [http://www.na-mic.org/Wiki/index.php/MeningiomaMRIRegistrationStudy Head MRI registration between different timepoints (human subjects, changing pathology present)]
 +
* [https://www.slicer.org/wiki/Slicer3:Registration Side by side comparisons in slicer2 and slicer3 with data and images]
 +
* http://mindboggle.info/papers/index.php
 +
*testing on the Vanderbuild database: [http://www.insight-journal.org/RIRE/ RIRE]
 +
* [[ITK_Registration_Optimization#Algorithmic_Requirements_and_Use_Cases|ITK Registration Optimization Sets]]
 +
*[[DTI-non-rigid]]
 +
*[[Projects:DBP2:Harvard:Registration_Documentation:Compare#Case_to_case_registration]]

Latest revision as of 17:41, 10 July 2017

Home < Projects:RegistrationDocumentation

Back to ARRA main page

Use Case Library

Development Efforts

Reference Manual

  • The reference manual will be organized by submodules and contain detailed descriptions of each parameter and each control element within the slicer registration module. The description should help the user understand what exactly that function/parameter does and if/how useful it will be for their specific registration problem.
  • Each entry will have one short description (that could also serve as tooltip) and one longer, more technical explanation.
  • links to journal articles for in depth algorithm info
  • Preferred formats: Slicer Wiki, maybe PDF, cross-linking required
  • Draft Registration Reference Manual

User Manuals & Tutorials

Contact

  • if there is anything you think would be of help to the 3DSlicer registration user, be that documentation, examples or features, we'd love to hear about it:

Links

Bundled Registration and Tests