Sunilk: /* Projects */

Back to [[Project Events]], [[Events]]
Back to [[Project Events]], [[AHM_2013]], [[Events]]

__NOTOC__
[[image:PW-SLC2013.png|300px]]

Project Week is a hands on activity -- programming using the open source [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the NA-MIC, NCIGT, and NAC calendars. It is held in the summer at MIT, typically the last week of June, and a shorter version is held in Salt Lake City in the winter, typically the second week of January.

Active preparation begins 6-8 weeks prior to the meeting, when a kick-off teleconference is hosted by the NA-MIC Engineering, Dissemination, and Leadership teams, the primary hosts of this event. Invitations to this call are sent to all na-mic members, past attendees of the event, as well as any parties who have expressed an interest in working with NA-MIC. The main goal of the kick-off call is to get an idea of which groups/projects will be active at the upcoming event, and to ensure that there is sufficient NA-MIC coverage for all. Subsequent teleconferences allow the hosts to finalize the project teams, consolidate any common components, and identify topics that should be discussed in breakout sessions. In the final days leading upto the meeting, all project teams are asked to fill in a template page on this wiki that describes the objectives and plan of their projects.

The event itself starts off with a short presentation by each project team, driven using their previously created description, and allows all participants to be acquainted with others who are doing similar work. In the rest of the week, about half the time is spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half is spent in project teams, doing hands-on programming, algorithm design, or clinical application of NA-MIC kit tools. The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical. To facilitate this work, a large room is setup with several tables, with internet and power access, and each team gathers on a table with their individual laptops, connects to the internet to download their software and data, and is able to work on their projects. On the last day of the event, a closing presentation session is held in which each project team presents a summary of what they accomplished during the week.

A summary of all past NA-MIC Project Events is available [[Project_Events#Past|here]].
= Dates.Venue.Registration =

Please [[AHM_2013#Dates_Venue_Registration|click here for Dates, Venue, and Registration]] for this event.

= [[AHM_2013#Agenda|'''AGENDA''']] and Project List=

Please:
* [[AHM_2013#Agenda|'''Click here for the agenda for AHM 2013 and Project Week''']].
* [[#Projects|'''Click here to jump to Project list''']]

=Background and Preparation=

A summary of all past NA-MIC Project Events is available [[Project_Events#Past|here]].

Please make sure that you are on the [http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week na-mic-project-week mailing list]

=Projects=
* [[2013_Project_Week_Template | Template for project pages]]

==TBI==
* [[4D DTI tractography in Slicer for TBI | Coregistration of structural and diffusion MRI towards 4D modeling of TBI]] (Bo Wang, Andrei Irimia, Micah Chambers, Jack Van Horn, Marcel Prastawa, Guido Gerig)
* [[Clinically oriented TBI connectivity analysis in Slicer]] (Andrei Irimia, Bo Wang, Micah Chambers, Jack Van Horn, Marcel Prastawa, Guido Gerig)
* [[Geometric metamorphosis for TBI]] (Danielle Pace, Stephen Aylward, Andrei Irimia, Micah Chambers)
* [[UKF Tractography in Slicer 4]] (Ryan Eckbo, Yogesh Rathi, Demian Wassermann, C.F Westin, Ron Kikinis)
* [[4D DTI analysis via longitudinal modeling of tract diffusivities]] (Anuja Sharma, Bo Wang, Andrei Irimia, Micah Chambers, Jack Van Horn, Marcel Prastawa, Guido Gerig)

==Atrial Fibrillation==
* [[2013_Project_Week:CARMA_Scar_Segmentation|Scar Identification (LiangJia Zhu, Yi Gao, Josh Cates, Rob MacLeod, Allen Tannenbaum)]]
* [[2013_Project_Week:CARMA_PV_Antrum_Cut|SLICER MODULE: PV Antrum Cut Filter (Salma Bengali, Alan Morris, Josh Cates, Rob MacLeod)]]
* [[2013_Project_Week:CARMA_LA_Seg_Gopal|SLICER MODULE: Automated LA Segmentation by Gopal (Gopal Veni, Salma Bengali, Greg Gardner, Alan Morris, Josh Cates, Rob MacLeod)]]
* [[2013_Project_Week:CARMA_2D_Dilate|SLICER MODULE: 2D Dilate Filter (Salma Bengali, Greg Gardner, Alan Morris, Josh Cates, Rob MacLeod)]]
* [[2013_Project_Week:CARMA_PractialLASeg|SLICER WORKFLOW: Practical Manual LA Segmentation in Slicer (Salma Bengali, Greg Gardner, Alan Morris, Josh Cates, Rob MacLeod)]]
* [[2013_Project_Week:CARMA_RT_MRI|PROJECT PLANNING: Real Time MRI in Slicer with OpenIGT (Alan Morris, Ashvin George, Josh Cates, Rob MacLeod)]]

==Slicer4 Extensions==
* [[2013_Project_Week:DTIExtension|Diffusion Tensor Images processing tools as Slicer4 extensions (Francois Budin, Adrien Kaiser, Martin Styner)]]

==Huntington's Disease==
* [[2013_Project_Week:QualityAssuranceModule|Quality assurance module enhancements]] (Dave Welch, Hans Johnson)
* [[2013_Project_Week:PythonModules|Slicer interface to add Python modules to Slicer environment]] (Dave Welch)
* [[2013_Project_Week:FastFiducialRegistrationModule|Fast fiducial registration module]] (Dave Welch, Nicole Aucoin)
* [[2013_Project_Week:4DShapeAnalysis | 4D shape analysis: application to HD]] (James Fishbaugh, Marcel Prastawa, Hans Johnson, Guido Gerig)

==Head and Neck Cancer==
* [[2013_Winter_Project_Week:MABS|Multi atlas-based segmentation]] (Sharp, Shusharina, Golland)
* [[2013_Winter_Project_Week:Hybrid_registration|Hybrid interactive-automatic registration]] (Shusharina, Sharp, Pieper)
* [[2013_Winter_Project_Week:PointSetRegistration|Constrained Point Set Registration]] (Kolesov, Karasev, Sharp, Tannenbaum)

==Stroke==
* [[2013_Project_Week:WMH_Segmentation_for_Stroke|White Matter Hyperintensity Segmentation in Stroke (Adrian Dalca, Ramesh Sridharan, Polina Golland)]]
* [[2013_Project_Week:Imaging_Genetic_for_Stroke|Imaging Genetics for Stroke (Adrian Dalca, Kayhan Batmanghelich, Polina Golland)]]

==Prostate Interventions==
* [[2013_Project_Week:BRAINSFit_new_features|BRAINSFit in ITK4: extra functionality and testing for prostate MR registration (Andrey, Hans)]]
* [[2013_Project_Week:PkModeling_for_prostate_DCE_MRI|PkModeling for prostate DCE MRI (Jim, Andrey)]]

==Abdominal Interventions==
* [[2013_Project_Week:AbdominalNavigationModule|Abdominal navigation module (Junichi Tokuda, Atsushi Yamada)]]

==Medical Robotics==
* [[Configurable fiducial-based device to image registration]] (Junichi Tokuda)
* Reviving ultrasound integration for visual servoing (Laurent Chauvin, Noby Hata)
* [[2013_Project_Week:AgileMedicalRobot | Agile medical robotics development with Slicer: Case study with MRI compatible robot(Taka Kato, Atsushi Yamada, Noby Hata, Kazuhumi Onuma)]]
* [[2013_Project_Week:InvestigatingRoleOfOpenSourceInTranslationalResearch | Investigating role of open source in translational research (Miki Kumekawa)]]

==General Image Guided Therapy==
* [[2013_Project_Week:UnitedSlicerIGTExtension|United SlicerIGT extension, repository, website]] (Tamas Ungi, Junichi Tokuda, Adam Rankin)
* [[2013_Project_Week:MobileImageOverlay|Mobile image overlay augmented reality needle guidance]] (Adam Rankin, Tamas Ungi)
* [[2013_Project_Week:TemperatureMonitoring|Temperature Monitoring for Laser Ablation intervention]] (Laurent Chauvin, Noby Hata)

==Radiation Therapy==
* [[2013_Project_Week:DicomRtExport|SlicerRT: DICOM RT export]] (Kevin Wang, Greg Sharp, Csaba Pinter)
* [[2013_Project_Week:RtBeamGeometry|SlicerRT: Beam geometry widgets]] (Csaba Pinter, Greg Sharp)
* [[2013_Project_Week:MRIAblation|Thermal monitoring tools for MRI-guided laser ablation therapy of brain tumor]] (Laurent Chauvin)

==NA-MIC Kit Internals==
*[[2013_Project_Week:WebbasedAnatomicalTeachingFramework|Web-based anatomical teaching framework for mi2b2]] (Daniel Haehn, Steve Pieper, Sonia Pujol, Randy Gollub, Rudolph Pienaar, Ellen Grant)
*[[2013_Project_Week:ITKv4Default|ITKv4 Default in Superbuild]] - [http://www.na-mic.org/Bug/search.php?project_id=3&sticky_issues=on&sortby=last_updated&dir=DESC&hide_status_id=80&tag_string=ITKv4 Issues] (Matt McCormick, Luis Ibanez, Hans Johnson, Jc?, Bill Lorensen,Bradley Lowekamp)
*[[2013_Project_Week:MarkupsModule|Slicer4 Markups Module]] (Nicole Aucoin)
*[[2013_Project_Week:ColorHierarchies|Slicer4 Color Hierarchies]] (Nicole Aucoin)
*[[2013_Project_Week:PatientHierarchy|Slicer4 Patient Hierarchy]] (Csaba Pinter, Andrey Fedorov?, Nicole Aucoin, Steve Pieper)
*[[2013_Project_Week:ScalarBar|Slicer4 Scalar bar improvements]] (Kevin Wang, Nicole Aucoin Csaba Pinter)
*[[2013_Project_Week:CliMatlabInterface|Slicer4 CLI Matlab interface]] (Kevin Wang, Steve Pieper, Csaba Pinter)
*[[2013_Project_Week:PETStandardUptakeValueComputation| PET/CT SUV Module for Clinicians]] (Sonia Pujol, Markus Van Tol, Nicole Aucoin)
*[[2013_Project_Week:SelfTests|Slicer4 Self Test and Sample Data Refactor]] (Steve Pieper, Jim Miller, Jc, Sankhesh Jhaveri)
*[[2013_Project_Week:SimplifyMRMLReference|Simplify MRML References]] - Issue [http://www.na-mic.org/Bug/view.php?id=2727 #2727] (Alex Yarmarkovich, Andras Lasso?, Steve Pieper, Julien Finet ?, Sankhesh Jhaveri ?, Jc ?)
*[[2013_Project_Week:SlicerIPythonIntegration|Integration of IPython]] (Jc, Hans Johnson, Dave Welch, Steve Pieper, Matt McCormick)
*[[2013_Project_Week:SlicerDebianPackage|Slicer Debian package]] (Jc, Dominique Belhachemi ?, Greg Sharp)
*[[2013_Project_Week:SimplifyRendererMouseInteraction|Simplify renderer window mouse interaction]] - Mailing list [http://slicer-devel.65872.n3.nabble.com/Left-mouse-button-changes-window-level-Is-it-good-tt4026815.html thread] (Csaba ?, Greg?, Andriy?, Steve, Jc)
*[[2013_Project_Week:PotentialSolutionForDefiningRoleAttributesForVolumes|Potential solutions for defining roles and/or attributes for volumes that are preserved when the volume is processed.]] - Mailing list [http://slicer-devel.65872.n3.nabble.com/Volume-node-subclass-tt4026807.html thread] (Andras?, Greg?, Andriy?, Steve, Jc)
*[[2013_Project_Week:SteeredRegistration|Interactive Registration for Image Guided Therapy]] (Dirk Padfield, Jim Miller, Steve Pieper, Kunlin Cao)
*[[2013_Project_Week:Threaded SimpleITK Modules|Threaded SimpleITK Modules]] (Brad Lowekamp, Steve Pieper)

==Infrastructure==
*[[2013_Project_Week:XNATSlicer|XNATSlicer]] (Sunil Kumar, Dan Marcus, Steve Pieper, etc.)

2013 Winter Project Week

2013-01-06T02:43:15Z

Sunilk: /* Projects */

2012-06-18T15:39:28Z

Sunilk:

__NOTOC__
<gallery>
Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]]
Image:XNATSlicer_SC_07_08_12.png|Module Screenshot 1 - June 2012
Image:XNATSlicerSC23--6-12.PNG|Module Screenshot 2 - June 2012
Image:XNATSlicerSC2--6-12.PNG|Module Screenshot 3 - June 2012
</gallery>

==Key Investigators==
* Washington University in St. Louis: Daniel Marcus, Sunil Kumar
* Isomics: Steve Pieper

<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Objective</h3>
Allow data exchange between XNAT and Slicer. A detailed objective list can be found [http://www.na-mic.org/Wiki/index.php/Talk:2012_Summer_Project_Week:XNATSlicerIntegration here].

</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Approach, Plan</h3>

Phase 1: Develop a beta module that fulfills the outlined objectives.<br>
Phase 2: Solidify UI and functionality though user testing.<br>
Phase 3: Port the REST API-based UI into a web-based UI.<br>

</div>

<div style="width: 40%; float: left;">

<h3>Progress</h3>
As of June 2012, a beta version of this widget is being tested.

</div>
</div>

==Known Issues==
<h3>Increased Crash Frequency in "Update Scene" Workflow, Save Scene Workflow </h3>
The module tends to crash more frequently during the "Update Scene" workflow. <br> Next step: define a set replicatable tests.

<h3>DICOM Details Popup </h3>
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.<br>

<i>1 - Refreshing DICOM Details Popup:</i><br>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. <br> 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.<br>

<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: </h3>
(Refers to command "slicer.app().applicationLogic().SaveSceneToSlicerDataBundleDirectory()")<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").<br>
<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.

<h3>MRML Adjusting: </h3>
<i>1- Altering directory references and volumes:</i><br>
Parsing the MRML and changing URLs from local references to remote references has some consequences in terms of how volumes are built. It appears that volume names are stored deeper than the MRML file itself. Therefore, changing filenames and filepaths could lead to Slicer not being able to find the volumes. This is evidenced in testing conducted with a potential user -- renamed filenames in the MRML apparently reference volume names not apparent in the MRML itself (likely embedded in the referenced files). Consequently, changing the filenames in the MRML is only one step of many that need to occur in changing the filenames.

<h3>XNAT Install Check: </h3>
<i>Check for relevant files:</i><br>
Right now the module checks for the XNAT install folder, but does not check for the relevant files. Needs to be a check in place to make sure they exist.

<h3>Check for Updated Nodes </h3>
<i>Lag times:</i><br>
About 60% of the lag time in the "Update Scene" workflow comes from resending unmodified data sets back to XNAT. Need to determine the simplest way to get Slicer to check if a node has been modified.

<h3>Empty or Unmodified Scene </h3>
Determine the best way to check for an empty or unmodified scene.

<h3>Firewall issues for some users</h3>
Acquire thoughts on ways to circumvent firewall issues -- sample data, access to XNAT server and extensions behind a firewall.

==References==

File:XNATSlicerSC2--6-12.PNG

2012-06-18T15:39:03Z

Sunilk:

2012 Summer Project Week:XNATSlicerIntegration

2012-06-18T15:38:29Z

Sunilk:

__NOTOC__
<gallery>
Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]]
Image:XNATSlicer_SC_07_08_12.png|Module Screenshot 1 - June 2012
Image:XNATSlicerSC23--6-12.PNG|Module Screenshot 2 - June 2012
</gallery>

==Key Investigators==
* Washington University in St. Louis: Daniel Marcus, Sunil Kumar
* Isomics: Steve Pieper

<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Objective</h3>
Allow data exchange between XNAT and Slicer. A detailed objective list can be found [http://www.na-mic.org/Wiki/index.php/Talk:2012_Summer_Project_Week:XNATSlicerIntegration here].

</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Approach, Plan</h3>

Phase 1: Develop a beta module that fulfills the outlined objectives.<br>
Phase 2: Solidify UI and functionality though user testing.<br>
Phase 3: Port the REST API-based UI into a web-based UI.<br>

</div>

<div style="width: 40%; float: left;">

<h3>Progress</h3>
As of June 2012, a beta version of this widget is being tested.

</div>
</div>

==Known Issues==
<h3>Increased Crash Frequency in "Update Scene" Workflow, Save Scene Workflow </h3>
The module tends to crash more frequently during the "Update Scene" workflow. <br> Next step: define a set replicatable tests.

<h3>DICOM Details Popup </h3>
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.<br>

<i>1 - Refreshing DICOM Details Popup:</i><br>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. <br> 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.<br>

<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: </h3>
(Refers to command "slicer.app().applicationLogic().SaveSceneToSlicerDataBundleDirectory()")<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").<br>
<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.

<h3>MRML Adjusting: </h3>
<i>1- Altering directory references and volumes:</i><br>
Parsing the MRML and changing URLs from local references to remote references has some consequences in terms of how volumes are built. It appears that volume names are stored deeper than the MRML file itself. Therefore, changing filenames and filepaths could lead to Slicer not being able to find the volumes. This is evidenced in testing conducted with a potential user -- renamed filenames in the MRML apparently reference volume names not apparent in the MRML itself (likely embedded in the referenced files). Consequently, changing the filenames in the MRML is only one step of many that need to occur in changing the filenames.

<h3>XNAT Install Check: </h3>
<i>Check for relevant files:</i><br>
Right now the module checks for the XNAT install folder, but does not check for the relevant files. Needs to be a check in place to make sure they exist.

<h3>Check for Updated Nodes </h3>
<i>Lag times:</i><br>
About 60% of the lag time in the "Update Scene" workflow comes from resending unmodified data sets back to XNAT. Need to determine the simplest way to get Slicer to check if a node has been modified.

<h3>Empty or Unmodified Scene </h3>
Determine the best way to check for an empty or unmodified scene.

<h3>Firewall issues for some users</h3>
Acquire thoughts on ways to circumvent firewall issues -- sample data, access to XNAT server and extensions behind a firewall.

==References==

2012-06-18T15:36:13Z

Sunilk:

__NOTOC__
<gallery>
Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]]
Image:XNATSlicer_SC_07_08_12.png|Module Screenshot 1 - June 2012
Image:XNATSlicerSC2--6-12.jpeg|Module Screenshot 2 - June 2012
Image:XNATSlicerSC3--6-12.jpeg|Module Screenshot 3 - June 2012
</gallery>

==Key Investigators==
* Washington University in St. Louis: Daniel Marcus, Sunil Kumar
* Isomics: Steve Pieper

<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Objective</h3>
Allow data exchange between XNAT and Slicer. A detailed objective list can be found [http://www.na-mic.org/Wiki/index.php/Talk:2012_Summer_Project_Week:XNATSlicerIntegration here].

</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Approach, Plan</h3>

Phase 1: Develop a beta module that fulfills the outlined objectives.<br>
Phase 2: Solidify UI and functionality though user testing.<br>
Phase 3: Port the REST API-based UI into a web-based UI.<br>

</div>

<div style="width: 40%; float: left;">

<h3>Progress</h3>
As of June 2012, a beta version of this widget is being tested.

</div>
</div>

==Known Issues==
<h3>Increased Crash Frequency in "Update Scene" Workflow, Save Scene Workflow </h3>
The module tends to crash more frequently during the "Update Scene" workflow. <br> Next step: define a set replicatable tests.

<h3>DICOM Details Popup </h3>
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.<br>

<i>1 - Refreshing DICOM Details Popup:</i><br>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. <br> 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.<br>

<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: </h3>
(Refers to command "slicer.app().applicationLogic().SaveSceneToSlicerDataBundleDirectory()")<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").<br>
<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.

<h3>MRML Adjusting: </h3>
<i>1- Altering directory references and volumes:</i><br>
Parsing the MRML and changing URLs from local references to remote references has some consequences in terms of how volumes are built. It appears that volume names are stored deeper than the MRML file itself. Therefore, changing filenames and filepaths could lead to Slicer not being able to find the volumes. This is evidenced in testing conducted with a potential user -- renamed filenames in the MRML apparently reference volume names not apparent in the MRML itself (likely embedded in the referenced files). Consequently, changing the filenames in the MRML is only one step of many that need to occur in changing the filenames.

<h3>XNAT Install Check: </h3>
<i>Check for relevant files:</i><br>
Right now the module checks for the XNAT install folder, but does not check for the relevant files. Needs to be a check in place to make sure they exist.

<h3>Check for Updated Nodes </h3>
<i>Lag times:</i><br>
About 60% of the lag time in the "Update Scene" workflow comes from resending unmodified data sets back to XNAT. Need to determine the simplest way to get Slicer to check if a node has been modified.

<h3>Empty or Unmodified Scene </h3>
Determine the best way to check for an empty or unmodified scene.

<h3>Firewall issues for some users</h3>
Acquire thoughts on ways to circumvent firewall issues -- sample data, access to XNAT server and extensions behind a firewall.

==References==