Projects:RegistrationDocumentation:UseCaseInventoryNotes

From NAMIC
Jump to: navigation, search
Home < Projects:RegistrationDocumentation:UseCaseInventoryNotes

back to Use Case Library
back to Registration Main Page

Categories & Formatting

  • June 2010: rename pages, download files and images to a consistent scheme that allows pages to be created & edited in a more automated fashion. Thus far, to better support searching, part of the case title was included in the filenames. The new scheme will have numbers only and the details stored in a separate database
 main page:	Projects:RegistrationLibrary_C%02d
 
 Thumbnails:   
   fixed:	RegLib_C%02d_thumb_f%02d.png
   moving:	RegLib_C%02d_thumb_m%02d.png
   tags:	RegLib_C%02d_thumb_t%02d.png
   masks:	RegLib_C%02d_thumb_k%02d.png
   
 Results:	RegLib_C%02d_res01.gif, 
                RegLib_C%02d_res02.gif
                ...
 Download:
   RegLib_C%02d_DATA.zip
   RegLib_C%02d_Tutorial.zip
   RegLib_C%02d_Presets.mrml
   RegLib_C%02d_Full.zip
  • Jan 2010: add all cases as is to get an overview of content, add registration solutions later
  • Ideally we seek 2 sets for each use case to define a range of settings, i.e. one case that is average and works reasonably well, and one case that is more challenging. Both cases together then define a range. The two cases would be posted together, provided the difficult case can be solved with different settings and does not require a different approach. The latter case would then be better listed in a Troubleshooting category.
  • We seek to strike a balance between a research tool of best possible flexibility and a "clinician research tool" of limited complexity that places performance robustness and ease of use before feature richness. For the registration module this is most evidently expressed in 1) the parameter settings made available and controlled by presets and 2) the concatenation of single registration steps into a pipeline for a concatenation of transforms.
  • We seek to have all datasets in a single-volume file format. Our first choice is .nrrd' and second is .nii. This will greatly facilitate file management and case documentation and will also guarantee full anonymization. The NRRD format is defined here and the NIFTI format is defined here. If possible we will offer both formats in the library.
  • Anonymization: Anonymized data is imperative. In a first pass posting single volume files only that do not contain subject-specific meta data is the safest. Relying on the provider/user to properly anonymize is likely insufficient. It's easy to overlook single DICOM fields. Defacing algorithms are avail. thru MBIRN but will affect the result and require the mask to be avail. to the registration.
  • Once formatting, anonymization and description are complete, listing here will be replaced with a download link. Temporarily listed are links to source databases, where avail.
  • Speed: include speed measurement with each case. Include note in tutorial that speed concerns are built into the default settings, i.e. if results do not look right on first run, there's many options to fine tune, hence the library concept

Hierarchy / Organization

108 Level Tree
360 Level Tree
  • The registration case library will contain 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).
  • 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.
  • the organization of a use case hierarchy can be accomplished in several ways. The main categories are listed below. Not all combinations exist or are equally common occurrences. For example, a different-timepoint/contrast distinction is not necessary for inter-subject registration.
    • ORGAN: Brain, Head&Neck, Thorax, Abdomen&Pelvis, Limbs, WholeBody
    • SUBJECT: intra-subject, inter-subject
    • MODALITY: intra-modality, inter-modality
    • CONTRAST: same_Contrast, different_Contrast
      • MR, CT, PET+SPECT, US
      • T1, T2, PD, T2s, DTI, MRPerfusion
    • CONTENT: same_TimeOrContent, different_TimeOrContent
    • VIEW: same_View, different_View
  • Depending on grouping this leads to trees with 80-1080 entries. Two example hierarchies (directory trees) are here: 108 Level Tree , 360 Level Tree
  • the VIEW distinction arises from commonly occurring problems of co-registering sets acquired with different slice orientation. The basics of dealing with axis orientation is already integrated into the algorithm, but further details remain: basically different_view implies a possibly high voxel size ratio (i.e. different voxel sizes if one image acquired axial the other coronal). Actions/Parameter settings are with multi-resolution settings, blurring and special checking of the axis orientation (vox2ras) meta-data. If, for example,voxel size ratio is close to [1 1 1] we need not do anything different other than resample based on vox2ras.
  • No separate distinction for Atlas Registration, i.e. the case where the volume of interest is not the one used for calculating the transform.
  • User-populated content The exploding # of combinations makes a successful top-down approach difficult. More effective to organize bottom-up, i.e. have user invited content, which we organize into a growing tree. We can make a call to the user community for submitting datasets and registration problems. This call should be in the "Register Images" Documentation as well as the "Help&Acknowledgement" tab of the "Register Images" module. e.g. Post a link on the documentation pages and module info tabs: Having trouble with registration? Try our service. We will consider all cases, provided that you have already tried what we do offer on the library and that did not work. If it didn't then that speaks for having your case added.

NAMIC AHM 10 notes

  • Martin Styner (UNC): validation workshop (MICCAI)-> Mehul
  • MICCAI 2010 workshop: lung CT registration
  • Slicer Regional Cortical Thickness Module: mature & avail.
  • developer effort priorities: + reference manual for multires and fiducial and register images
  • HAMMER : will ev. incl. WM segmentation algorithm
  • Skull Stripping SPECTRE (JHU, J.Prince): looking for validation sets. Also avail. as JAVA (within JIST-> works with MIPAV)
  • Wendy: PET-CT module: example datasets