RSNA2012 Planning
From NAMIC Wiki
Home < RSNA2012 Planning
Contents
RSNA hands-on courses
Nb | Tutorial slides | Datasets | Tools | Slicer Modules | Developer/Tester | Clinical Expert |
---|---|---|---|---|---|---|
Classroom Course 1 - ICIA32, Nov.27, 12:30-2:00 pm | 3D Visualization of DICOM Data for Radiology Applications | I ICIA 32 dataset | Compare View, Clipping, Save, Restore, Scene Views, Dicom studies sorting, Dicom networking | Data, Volumes, Models, Scene Views + DICOM ( note: the DICOM part will be a new addition to the slides) | Steve | Sonia |
Classroom Course 2 - ICIA11, Nov.25, 11:00-12:30 pm | Quantitative Imaging Tutorial | ICIA 11 datasets: PETCTFusion and Change Tracker | Change Tracker, Compare Views, Volume Rendering, CropVolume, Crosshairs, BRAINSFit | Change Tracker, Volume Rendering, BRAINSFit, CropVolume} | Steve | Sonia |
Quantitative Imaging Reading Room
Tentative list of demonstrations for the RSNA 2012 Slicer booth. Needs further development and testing Note: RSNA demo machines will need nvidia graphics cards to get GPU Volume Rendering
Nb | DEMO | Datasets | Notes | Tools | Slicer Modules | Developer/Tester | Clinical Expert |
---|---|---|---|---|---|---|---|
0 | 3D Visualization of DICOM images for Radiology Applications | RSNA datasets | 3D Visualization for Radiology Applications | Compare View, Clipping, Save, Restore, Scene Views, Dicom studies sorting, Dicom networking | Data, Volumes, Models, Scene Views | Jim | Sonia |
1 | Data Loading and Visualization | Slicer3Visualization Data | Slicer4Visualization Tutorial | Compare View, Clipping, Save, Restore, Scene Views, DICOM studies sorting, DICOM networking (?) | Data, Volumes, Models, Scene Views | Jim | Sonia |
2 | MRI-based topographic parcellation of human brain | EM Segmenter Data | registration, segmentation EMSegmenter Tasks | EM Segmenter | EMSegmenter | Kilian | Ron |
3 | Volume Rendering #1 Head | Head CT Scan (Osirix Manix Dataset) | show cropping, transfer functions, GPU, slice composite view, Annotations | Volume Rendering and Annotations | Volume Rendering, Annotations, Scene Views | Julien | Ron |
4 | Volume Rendering #2 Abdomen | Abdominal CT scan with AAA (Osirix Panoramix Dataset) | show cropping, transfer functions, GPU, slice composite view, Annotations | Volume Rendering and Annotations | Volume Rendering, Annotations, Scene Views | Julien | Ron |
5 | Volume Rendering #3 Thorax | Thoracic CT scan | show cropping, transfer functions, GPU, slice composite view, Annotations | Volume Rendering and Annotations | Volume Rendering, Annotations, Scene Views | Julien | Ron |
6 | Traumatic Brain Injury Case Analysis | TBI Demo Data (UCLA) | TBI tutorial | ABC Segmentation, Model Maker, Editor, Annotations | Data, ABC Segmentation, Model Maker, Editor, Annotations, Scene Views | Alex | Jack Van Horn |
7 | Radiotherapy | Plastimatch Dose Warping Data (MGH) | Plastimatch Tutorial | Plastimatch, DVH extension (Csaba) | Data, Plastimatch Extension: DICOM/DICOM-RT Import, DICOM/DICOM-RT Export, B-Spine Deformable Registration,XFORMWARP Warping with transform Transforms, | Csaba | Andras |
8 | White matter exploration for neurosurgical planning | White Matter Exploration dataset | Neurosurgical planning Tutorial] | Diffusion ( Estimation, Tractography, Fiducial Seeding), Editor, Model Maker | Data, Volumes, Editor, Fiducials, Diffusion Tensor Estimation, Diffusion Tensor Scalar Measurements, Labelmap Seeding, Tractography Fiducial Seeding, Tractography Display | Demian | Ron |
9 | Longitudinal analysis of meningioma growth | Change Tracker Data are part of the tutorial | Quantitative Imaging Tutorial | Change Tracker, Compare Views, Volume Rendering, CropVolume, Crosshairs, BRAINSFit | Change Tracker, Volume Rendering, BRAINSFit, CropVolume | Jc | Andrey |
10 | Image-guided prostate interventions | Prostate Data updated for Slicer4, in progress Can load RSNA2010 demo scene, mostly working, see [1] | Pre-op/Intra-op registration; Use Case Demo Prostate Data | Linked Viewing | Annotations, Models, Crosshairs, CompareViews | Jim | Andrey |
11 | Brain Atlas | NAC Multi-modality MRI-based Atlas of the Brain | Work in progress - atlases are being updated | Linked Viewing | Data, Volumes, Models, Scene Views | Nicole | Marianna |
12 | Abdomen Atlas | Knee Atlas | Work in progress - atlases are being updated | Linked Viewing | Data, Volumes, Models, Scene Views | Nicole | Marianna |
13 | Knee Atlas Atlas | Abdominal Atlas | Work in progress - atlases are being updated | Linked Viewing | Data, Volumes, Models, Scene Views | Nicole | Marianna |
Process
We are following the release schedule documented during the 4.2 release planning session.
TODO: how to write a python test for a demo or tutorial
- Adopt-a-demo program
- For the demos and tutorials listed above, the roles of developer and clinical contact are:
- clinical expert who is responsible for the data and content of the tutorial and can answer questions about how the program is meant to work. This person should be providing the data and in some cases provides a step by step tutorial.
- developer / tester
- is the point of contact if anyone finds that the demo in question does not work correctly
- is responsible for testing that the functionality is working for the demo on all platforms (mac, windows, linux). If you do not have the platform available yourself, you will need to offer to trade some work with another person who has access to the platform. You cannot just ignore testing just because you don't have ready access to all the platforms!
- needs to get a working familiarity with the demo and investigate any incorrect or unworkable behavior
- needs to file bug reports and track down appropriate developer resources to get issues resolved (pester your fellow developers as needed so that issues are addressed).
- If there's a tutorial already existing, the developer should be able to go through the testing on all platforms and only contact the tutorial writer with feedback or questions. In the case of demos or atlas datasets, the developer should discuss with the clinical contact about what functionality should be supported and test that this is working as expected on all platforms.
- In all cases the developer should try to provide a test that loads and manipulates the data, using either a python script or Qt testing, to help automate the testing process for future releases.
- For the demos and tutorials listed above, the roles of developer and clinical contact are:
List of Slicer Modules involved in RSNA tutorials & demos
- Data
- Welcome to Slicer
- Volumes
- Models
- Scene Views
- Annotations
- Volume Rendering
- Editor
- Model Maker
- Diffusion Tensor Estimation
- Diffusion Tensor Scalar Measurements
- Tractography Labelmap Seeding
- Tractography Fiducial Seeding
- Tractography Display
- BRAINSTools
- Change Tracker
- CropVolume
- Extensions:
- ABC
- Plastimatch
- EMSegmenter
- Skull Stripper
- Reporting
- Documentation: We need all core modules reasonably well documented.