Difference between revisions of "2012 Summer Project Week:XNATSlicerIntegration"
Line 47: | Line 47: | ||
<i>2 - Customization of DICOM Details Popup:</i><br>If a user downloads a DICOM folder off of XNAT, it would be nice to have the ability to load a customized "DICOM Details" popup where the only DICOM set presented is the one the user just downloaded. Right now, the popup lists all DICOM sets downloaded by the user.<br> Next Step: inquire what the effort would be to create such a customized popup. | <i>2 - Customization of DICOM Details Popup:</i><br>If a user downloads a DICOM folder off of XNAT, it would be nice to have the ability to load a customized "DICOM Details" popup where the only DICOM set presented is the one the user just downloaded. Right now, the popup lists all DICOM sets downloaded by the user.<br> Next Step: inquire what the effort would be to create such a customized popup. | ||
− | <h3>Scene Packaging: slicer.app().applicationLogic().SaveSceneToSlicerDataBundleDirectory ( | + | <h3>Scene Packaging: (LOW)</h3> |
+ | (Refers to command "slicer.app().applicationLogic().SaveSceneToSlicerDataBundleDirectory()") | ||
<i>1 - Spaces in file names:</i><br> | <i>1 - Spaces in file names:</i><br> | ||
− | + | Investigate the possibility of eliminating the use of spaces in the packaged filenames. (Ex. "Master Scene View.png" should become "MasterSceneView.png"). | |
+ | <i>2 - More Control Over How Scenes Are Packaged:</i><br> | ||
+ | Assess to what control is given over how scenes are packaged: compression of DICOMS, file localization (paths), etc. | ||
+ | |||
<br> | <br> | ||
<br> | <br> |
Revision as of 14:19, 13 June 2012
Home < 2012 Summer Project Week:XNATSlicerIntegrationKey Investigators
- Washington University in St. Louis: Daniel Marcus, Sunil Kumar
- Isomics: Steve Pieper
Objective
Allow data exchange between XNAT and Slicer. A detailed objective list can be found here.
Approach, Plan
Phase 1: Develop a beta module that fulfills the outlined objectives.
Phase 2: Solidify UI and functionality though user testing.
Phase 3: Port the REST API-based UI into a web-based UI.
Progress
As of June 2012, a beta version of this widget is being tested.
Known Issues
Increased Crash Frequency in "Update Scene" Workflow (MEDIUM)
The module tends to crash more frequently during the "Update Scene" workflow.
Next step: define a replicatable test.
DICOM Details Popup (LOW)
The XNAT-Slicer module utilizes the DICOM Details Popup (from the DICOM module) after a user loads a scan folder of DICOM images from the XNAT. While this communication is incredibly useful, we believe a few adjustments to the DICOM module would streamline the workflow of XNAT-Slicer.
1 - Refreshing DICOM Details Popup:
After downloading a scan in the XNAT-Slicer module, the "DICOM Details" popup lists the downloaded DICOMs only when the popup hasn't yet been used in the current Slicer session. If the popup has already been used/opened, the "DICOM Details" popup does not list the new set. This is in spite of the downloaded files being successfully inserted in Slicer's SQL DICOM database. In this scenario, when the user restarts Slicer and opens the DICOM module, they will find that the "DICOM Details" popup contains the newly downloaded set. This is likely the result of a highly controlled "refresh" condition in reading the updated database. This may be by design, and consequently a "fix" by be out of reach.
Next step: Inquire if the popup can be refreshed or a one-off "Details Popup" window can be developed that will allow the developer to control its behavior.
2 - Customization of DICOM Details Popup:
If a user downloads a DICOM folder off of XNAT, it would be nice to have the ability to load a customized "DICOM Details" popup where the only DICOM set presented is the one the user just downloaded. Right now, the popup lists all DICOM sets downloaded by the user.
Next Step: inquire what the effort would be to create such a customized popup.
Scene Packaging: (LOW)
(Refers to command "slicer.app().applicationLogic().SaveSceneToSlicerDataBundleDirectory()")
1 - Spaces in file names:
Investigate the possibility of eliminating the use of spaces in the packaged filenames. (Ex. "Master Scene View.png" should become "MasterSceneView.png").
2 - More Control Over How Scenes Are Packaged:
Assess to what control is given over how scenes are packaged: compression of DICOMS, file localization (paths), etc.
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a (please select the appropriate options by noting YES against them below)
- Slicer Module - YES