Difference between revisions of "2012 Winter Project Week"

From NAMIC Wiki
Jump to: navigation, search
 
(20 intermediate revisions by 8 users not shown)
Line 1: Line 1:
Back to [[Project Events]], [[Events]]
 
Back to [[Project Events]], [[AHM_2012]], [[Events]]
 
 
 
__NOTOC__
 
__NOTOC__
[[image:PW-SLC2012.png|300px]]
+
Back to [[Events]]
 
 
== Dates.Venue.Registration ==
 
 
 
Please [[AHM_2012#Dates_Venue_Registration|click here for Dates, Venue, and Registration]] for this event.
 
 
 
== [[AHM_2012#Agenda|'''AGENDA''']] and Project List==
 
 
 
Please:
 
*  [[AHM_2012#Agenda|'''Click here for the agenda for AHM 2012 and Project Week''']].
 
*  [[#Projects|'''Click here to jump to Project list''']]
 
 
 
==Background==
 
 
 
From January 9-13, 2012, the 14th project week for hands-on research and development activity in Neuroscience and Image-Guided Therapy applications will be hosted in Salt Lake City, Utah. Participant engage in open source programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithms, medical imaging sequence development, tracking experiments, and clinical applications. The main goal of this event is to further the translational research deliverables of the sponsoring centers ([http://www.na-mic.org NA-MIC], [http://www.ncigt.org NCIGT], [http://nac.spl.harvard.edu NAC], [http://catalyst.harvard.edu/home.html Harvard Catalyst], and [http://www.cimit.org CIMIT]) and their collaborators by identifying and solving programming problems during planned and ad hoc break-out sessions. 
 
 
 
Active preparation for this conference begins with a kick-off teleconference. Invitations to this call are sent to members of the sponsoring communities, their collaborators, past attendees of the event, as well as any parties expressing an interest in working with these centers. The main goal of the initial teleconference is to gather information about which groups/projects would be active at the upcoming event to ensure that there were sufficient resources available to meet everyone's needs. Focused discussions about individual projects are conducted during several subsequent teleconferences and permits the hosts to finalize the project teams, consolidate any common components, and identify topics that should be discussed in break-out sessions. In the final days leading up to the meeting, all project teams are asked to complete a template page on the wiki describing the objectives and research plan for each project. 
 
 
 
On the first day of the conference, each project team leader delivers a short presentation to introduce their topic and individual members of their team. These brief presentations serve to both familiarize other teams doing similar work about common problems or practical solutions, and to identify potential subsets of individuals who might benefit from collaborative work.  For the remainder of the conference, about 50% time is devoted to break-out discussions on topics of common interest to particular subsets and 50% to hands-on project work.  For hands-on project work, attendees are organized into 30-50 small teams comprised of 2-4 individuals with a mix of multi-disciplinary expertise.  To facilitate this work, a large room is setup with ample work tables, internet connection, and power access. This enables each computer software development-based team to gather on a table with their individual laptops, connect to the internet, download their software and data, and work on specific projects.  On the final day of the event, each project team summarizes their accomplishments in a closing presentation.
 
 
 
A summary of all past NA-MIC Project Events is available [[Project_Events#Past|here]].
 
  
 +
To [[AHM_2012| AHM 2012]]
  
 +
[[image:PW-SLC2012.png|300px]]
  
 +
=Welcome to the web page for the 14th Project Week!=
 +
==Summary==
 +
The 14th PROJECT EVENT was held on January 9-13, 2012 in Salt Lake City, UT. It recorded 104 registered attendees, who worked on 57 projects. These attendees represented 19 academic sites (Brigham and Women's Hospital, Mayo Clinic, UPenn, University of Utah, UNC Chapel Hill, UCLA, University of Virginia, Old Dominion, MIT, MD Anderson, Arizona State University, Georgia Tech, Boston University, University of Iowa, Queen's University, Massachusetts General Hospital,  UCSD,  WUSTL, Robarts)  and  6 companies (Kitware, Isomics, GE Research, Radnostisc, Cosmo, AZE). T
  
 +
A [[Project_Events#Past_Project_Weeks|summary]] of all past Project Events.
  
 
==Projects==
 
==Projects==
Line 70: Line 53:
 
*[[2012_Winter_Project_Week:LiveUltrasound|Live ultrasound in Slicer4 using Plus and OpenIGTLink]] (Tamas Ungi, Elvis Chen, Junichi Tokuda)
 
*[[2012_Winter_Project_Week:LiveUltrasound|Live ultrasound in Slicer4 using Plus and OpenIGTLink]] (Tamas Ungi, Elvis Chen, Junichi Tokuda)
 
*[[2012_Winter_Project_Week:4DUltrasound|4D Ultrasound Storage and Volume Rendering on Slicer 3.6]] (Laurent, Noby)
 
*[[2012_Winter_Project_Week:4DUltrasound|4D Ultrasound Storage and Volume Rendering on Slicer 3.6]] (Laurent, Noby)
*[[2012_Winter_Project_Week:BKPLUSSlicer|Integration of BK Ultrasound into PLUS and Slicer]] (Isaiah Norton, Mehdi Moradi, Tamas Ungi)
+
*[[2012_Winter_Project_Week:BKPLUSSlicer|Integration of BK Ultrasound into PLUS and Slicer]] (Isaiah Norton, Mehdi Moradi, Matthew Toews, Tamas Ungi)
 
*[[2012_Winter_Project_Week:LaserAblationAndGuidance|Slicer-BrainLab integration for laser ablation]] (Erol Yeniaras, Isaiah Norton, Pratik Patel)
 
*[[2012_Winter_Project_Week:LaserAblationAndGuidance|Slicer-BrainLab integration for laser ablation]] (Erol Yeniaras, Isaiah Norton, Pratik Patel)
 
*[[2012_Winter_Project_Week:PelvicRegistration|Deformable prostate registration: 3D ultrasound to MRI]] (Mehdi Moradi, Jan Egger, Andrey Fedorov)
 
*[[2012_Winter_Project_Week:PelvicRegistration|Deformable prostate registration: 3D ultrasound to MRI]] (Mehdi Moradi, Jan Egger, Andrey Fedorov)
Line 96: Line 79:
  
 
===NA-MIC Kit Internals===
 
===NA-MIC Kit Internals===
*Slicer4 release (Jean-Christophe Fillion-Robin (JC), and Julien Finet (J2))
+
*[[2012_Project_Week:AfibDataOnMidas| Afib Data on MIDAS]] (Josh Cates, Patrick Reynolds)
*Slicer4 extensions (JC)
 
*Slicer4 documentation (JC)
 
*Slicer4 GUI Testing (Benjamin Long, JC, J2)
 
*Slicer4 data on MIDAS (Josh Cates, Patrick Reynolds)
 
 
*[[2012_Project_Week:SceneViews|Slicer4 Scene Views Module]] (Nicole Aucoin, Ron Kikinis, Julien Finet)
 
*[[2012_Project_Week:SceneViews|Slicer4 Scene Views Module]] (Nicole Aucoin, Ron Kikinis, Julien Finet)
 
*[[2012_Project_Week:AnnotationsFileFormatRefactor|Annotations Module File Format Refactor]] (Nicole Aucoin)
 
*[[2012_Project_Week:AnnotationsFileFormatRefactor|Annotations Module File Format Refactor]] (Nicole Aucoin)
Line 106: Line 85:
 
*[[2012_Project_Week:DICOM|DICOM Networking, Database, and Slicer Integration]] (Steve, Andrey, Andras)
 
*[[2012_Project_Week:DICOM|DICOM Networking, Database, and Slicer Integration]] (Steve, Andrey, Andras)
 
*[[2012_Project_Week:EditorExtensions|Editor Extension Examples and Debugging]] (Steve, Andrey, Jc, Hans, Satra)
 
*[[2012_Project_Week:EditorExtensions|Editor Extension Examples and Debugging]] (Steve, Andrey, Jc, Hans, Satra)
*[[2012_Project_Week:GeneralGUI|General minor GUI redesign]] (Wendy Plesniak, Julien Finet, Ron Kikinis)
 
 
*[[2012_Project_Week:ViewerControls|Redesign of the slice viewer control panels]] (Julien Finet, Ron Kikinis, Hans Johnson, Greg Sharp)
 
*[[2012_Project_Week:ViewerControls|Redesign of the slice viewer control panels]] (Julien Finet, Ron Kikinis, Hans Johnson, Greg Sharp)
*[[2012_Project_Week:AutomatedTesting |Automated Testing (Sonia Pujol, Steve Pieper, Jc, Benjamin)]]
 
*[[2012_Project_Week:RemoveSlicerLegacyCode|Remove legacy code from slicer4 (itk, modules, build scripts) (Hans, Jim, Steve, J2, JC)]]
 
 
*[[2012_Project_Week:BatchProcessing|Batch Processing with Slicer Modules]] (Steve, Andrey, JC, Hans, Satra, Dave Welch)
 
*[[2012_Project_Week:BatchProcessing|Batch Processing with Slicer Modules]] (Steve, Andrey, JC, Hans, Satra, Dave Welch)
 
*[[2012_Project_Week:4DImageSlicer4|Support for 4D Images in Slicer4]] (Andrey, Steve, Junichi, Alex)
 
*[[2012_Project_Week:4DImageSlicer4|Support for 4D Images in Slicer4]] (Andrey, Steve, Junichi, Alex)
 
*[[2012_Project_Week:QIN-SAM|QIN Slicer Annotation Module: AIM, DICOM SR and Slicer annotations]] (Andrey, Steve, Nicole, Jayashree)
 
*[[2012_Project_Week:QIN-SAM|QIN Slicer Annotation Module: AIM, DICOM SR and Slicer annotations]] (Andrey, Steve, Nicole, Jayashree)
*[[2012_Project_Week:ScriptView|Consistent, scripted setup of Slicer view for multiple subjects]] (Albert, Steve)
+
*[[2012_Winter_Project_Week:ScriptView|Consistent, scripted setup of Slicer view for multiple subjects]] (Albert, Steve)
 +
*[[2012_Winter_Project_Week:Charts|Chart views that can be packed in Slicer layouts]] (Jim, Kedar, Steve)
 +
 
 +
== Dates.Venue.Registration ==
 +
 
 +
Please [[AHM_2012#Dates_Venue_Registration|click here for Dates, Venue, and Registration]] for this event.
 +
 
 +
== [[AHM_2012#Agenda|'''AGENDA''']] and Project List==
 +
 
 +
Please:
 +
*  [[AHM_2012#Agenda|'''Click here for the agenda for AHM 2012 and Project Week''']].
 +
*  [[#Projects|'''Click here to jump to Project list''']]
 +
 
 +
==Background==
 +
 
 +
From January 9-13, 2012, the 14th project week for hands-on research and development activity in Neuroscience and Image-Guided Therapy applications will be hosted in Salt Lake City, Utah. Participant engage in open source programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithms, medical imaging sequence development, tracking experiments, and clinical applications. The main goal of this event is to further the translational research deliverables of the sponsoring centers ([http://www.na-mic.org NA-MIC], [http://www.ncigt.org NCIGT], [http://nac.spl.harvard.edu NAC], [http://catalyst.harvard.edu/home.html Harvard Catalyst], and [http://www.cimit.org CIMIT]) and their collaborators by identifying and solving programming problems during planned and ad hoc break-out sessions. 
 +
 
 +
Active preparation for this conference begins with a kick-off teleconference. Invitations to this call are sent to members of the sponsoring communities, their collaborators, past attendees of the event, as well as any parties expressing an interest in working with these centers. The main goal of the initial teleconference is to gather information about which groups/projects would be active at the upcoming event to ensure that there were sufficient resources available to meet everyone's needs. Focused discussions about individual projects are conducted during several subsequent teleconferences and permits the hosts to finalize the project teams, consolidate any common components, and identify topics that should be discussed in break-out sessions. In the final days leading up to the meeting, all project teams are asked to complete a template page on the wiki describing the objectives and research plan for each project. 
 +
 
 +
On the first day of the conference, each project team leader delivers a short presentation to introduce their topic and individual members of their team. These brief presentations serve to both familiarize other teams doing similar work about common problems or practical solutions, and to identify potential subsets of individuals who might benefit from collaborative work.  For the remainder of the conference, about 50% time is devoted to break-out discussions on topics of common interest to particular subsets and 50% to hands-on project work.  For hands-on project work, attendees are organized into 30-50 small teams comprised of 2-4 individuals with a mix of multi-disciplinary expertise.  To facilitate this work, a large room is setup with ample work tables, internet connection, and power access. This enables each computer software development-based team to gather on a table with their individual laptops, connect to the internet, download their software and data, and work on specific projects.  On the final day of the event, each project team summarizes their accomplishments in a closing presentation.
  
 
=== Preparation ===
 
=== Preparation ===
 
+
#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]
#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]  
 
 
#Starting Thursday, October 27th, part of the weekly Thursday 3pm NA-MIC Engineering TCON will be used to prepare for this meeting.  The schedule for these preparatory calls is as follows:
 
#Starting Thursday, October 27th, part of the weekly Thursday 3pm NA-MIC Engineering TCON will be used to prepare for this meeting.  The schedule for these preparatory calls is as follows:
 
#*October 27: MGH DBP
 
#*October 27: MGH DBP

Latest revision as of 15:51, 30 March 2017

Home < 2012 Winter Project Week

Back to Events

To AHM 2012

PW-SLC2012.png

Welcome to the web page for the 14th Project Week!

Summary

The 14th PROJECT EVENT was held on January 9-13, 2012 in Salt Lake City, UT. It recorded 104 registered attendees, who worked on 57 projects. These attendees represented 19 academic sites (Brigham and Women's Hospital, Mayo Clinic, UPenn, University of Utah, UNC Chapel Hill, UCLA, University of Virginia, Old Dominion, MIT, MD Anderson, Arizona State University, Georgia Tech, Boston University, University of Iowa, Queen's University, Massachusetts General Hospital, UCSD, WUSTL, Robarts) and 6 companies (Kitware, Isomics, GE Research, Radnostisc, Cosmo, AZE). T

A summary of all past Project Events.

Projects

Traumatic Brain Injury

Predict Huntington's Disease

Atrial fibrillation

Head and Neck Cancer

IGT for Surgery and Radiation Treatments

Musculoskeletal System

Registration

Shape Analysis

NA-MIC Kit Internals

Dates.Venue.Registration

Please click here for Dates, Venue, and Registration for this event.

AGENDA and Project List

Please:

Background

From January 9-13, 2012, the 14th project week for hands-on research and development activity in Neuroscience and Image-Guided Therapy applications will be hosted in Salt Lake City, Utah. Participant engage in open source programming using the NA-MIC Kit, algorithms, medical imaging sequence development, tracking experiments, and clinical applications. The main goal of this event is to further the translational research deliverables of the sponsoring centers (NA-MIC, NCIGT, NAC, Harvard Catalyst, and CIMIT) and their collaborators by identifying and solving programming problems during planned and ad hoc break-out sessions.

Active preparation for this conference begins with a kick-off teleconference. Invitations to this call are sent to members of the sponsoring communities, their collaborators, past attendees of the event, as well as any parties expressing an interest in working with these centers. The main goal of the initial teleconference is to gather information about which groups/projects would be active at the upcoming event to ensure that there were sufficient resources available to meet everyone's needs. Focused discussions about individual projects are conducted during several subsequent teleconferences and permits the hosts to finalize the project teams, consolidate any common components, and identify topics that should be discussed in break-out sessions. In the final days leading up to the meeting, all project teams are asked to complete a template page on the wiki describing the objectives and research plan for each project.

On the first day of the conference, each project team leader delivers a short presentation to introduce their topic and individual members of their team. These brief presentations serve to both familiarize other teams doing similar work about common problems or practical solutions, and to identify potential subsets of individuals who might benefit from collaborative work. For the remainder of the conference, about 50% time is devoted to break-out discussions on topics of common interest to particular subsets and 50% to hands-on project work. For hands-on project work, attendees are organized into 30-50 small teams comprised of 2-4 individuals with a mix of multi-disciplinary expertise. To facilitate this work, a large room is setup with ample work tables, internet connection, and power access. This enables each computer software development-based team to gather on a table with their individual laptops, connect to the internet, download their software and data, and work on specific projects. On the final day of the event, each project team summarizes their accomplishments in a closing presentation.

Preparation

  1. Please make sure that you are on the NA-MIC Project Week mailing list
  2. Starting Thursday, October 27th, part of the weekly Thursday 3pm NA-MIC Engineering TCON will be used to prepare for this meeting. The schedule for these preparatory calls is as follows:
    • October 27: MGH DBP
    • November 3: Iowa DBP Huntingtons, Engineering Infrastructure Topics
    • November 10: Utah Atrial Fibrillation DBP
    • November 17: UCLA TBI DBP
    • November 24: No call. thanksgiving.
    • December 1:
    • December 8:
    • December 15:Finalize Projects
    • January 5: Loose Ends
  3. By December 15: Complete a templated wiki page for your project. Please do not edit the template page itself, but create a new page for your project and cut-and-paste the text from this template page. If you have questions, please send an email to tkapur at bwh.harvard.edu.
  4. By December 15: Create a directory for each project on the NAMIC Sandbox (Zack)
    1. Ask Zack for a Sandbox account
    2. Commit on each sandbox directory the code examples/snippets that represent our first guesses of appropriate methods. (Luis and Steve will help with this, as needed)
    3. Gather test images in any of the Data sharing resources we have (e.g. MIDAS, xNAT). These ones don't have to be many. At least three different cases, so we can get an idea of the modality-specific characteristics of these images. Put the IDs of these data sets on the wiki page. (the participants must do this.)
    4. Setup nightly tests on a separate Dashboard, where we will run the methods that we are experimenting with. The test should post result images and computation time. (Zack)
  5. Please note that by the time we get to the project event, we should be trying to close off a project milestone rather than starting to work on one...