2011 Winter Project Week

Back to Project Events, Events
Back to Project Events, AHM_2011, Events

Dates.Venue.Registration

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

Agenda

Please click here for the agenda for AHM 2011 and Project Week.

Background

From January 10-14, 2011, the twelfth project week for hands-on research and development activity in Image-Guided Therapy and Neuroscience 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.

A summary of all past NA-MIC Project Events is available here.

Projects

Segmentation

• Extension of ABC (Atlas-Based Classification) to detect pathology categories, with tests on TBI images (Bo Wang, Marcel Prastawa, Guido Gerig).
• Segmentation of the left atrial wall for atrial fibrillation ablation therapy (Behnood Gholami, Yi Gao, and Allen Tannenbaum)
• The Vascular Modeling Toolkit in 3D Slicer (Daniel Haehn)
• A stenosis detector in Slicer4 using VMTK (Suares Tamekue, Daniel Haehn)

Registration

• The 3DSlicer Registration Case Library (Dominik Meier)
• Voxel Anisotropy and Bias Field Effects on Slicer Image Registration (Dominik Meier) (tentative)
• Efficient co-registration of multiple MR modalities using the ABC (atlas-based classification) framework, joint visualization of multiple co-registered modalities (Bo Wang, Guido Gerig)
• DTI-MRI registration: Evaluation of large deformation diffeomorphic mapping (LDDMM) with other nonlinear registration schemes (Anuja Sharma, Guido Gerig)
• Registration of CT and MRI volumes for Adaptive Radiotherapy (Ivan Kolesov, Gregory Sharp, and Allen Tannenbaum)
• Atlas Registration in Slicer3 (Daniel Haehn, Dominik Meier, Kilian Pohl)

IGT

• Open IGT Link 2.0 (Junichi Tokuda, Nobuhiko Hata)
• Osteormak, navigation tool for Osteotomy (Laurent Chauvin, Nobuhiko Hata)
• Detection and compensation for prostate motion during transperineal MR-guided prostate biopsy (A.Fedorov)

Radiotherapy

• User controlled segmentation of head and neck structures for Adaptive Radiotherapy (Ivan Kolesov, Gregory Sharp, and Allen Tannenbaum)

Analysis

• GAMBIT - Cortical thickness analysis (Clement Vachet, Martin Styner)
• Particle shape analysis incorporating surface normals (Beatriz Paniagua, Martin Styner)

Informatics

• Share all UIowa Traveling Human Phantom DTI data with NAMIC - Mark Scully, Hans Johnson
• Ontology-augmented MRI brain atlas - Michael Halle, Jim Miller, Samira Farough
• Functional brain atlas (version 2) - Michael Halle, Jim Miller
• Annotation module in Slicer4: Display widget intersections (Daniel Haehn, ..)

Diffusion

• Testing suite for DicomToNrrdConverter - Mark Scully, Hans Johnson
• Documentation and 1st Draft Tutorial for DTIPrep - Mark Scully, Hans Johnson, Clement Vachet
• Voxelwise fiber distribution from tractography - Yinpeng Li, Martin Styner

NA-MIC Kit Internals

• Command line module logic redesign (passing paramenters, tie into workflows) - Jim, Steve
• CDash at Home / testing on demand of git topic branches - Steve

Execution Model

• Extract SlicerExecutionModel (SEM) into separate entity. SEM is the only component needed to build modules compatible with Slicer3D, so it should be easy incorporate into external applications without all of Slicer3D. Jim, Hans
• Extend SEM xml to include sections for explicit grant acknowledgements, and pointers to documentation, and pointers to examples. Hans, Andriy
• Make an formal schema for the SEM xml so that eternal tools (i.e. nipype) can validate the xml. Hans Johnson, Jim Miller, Tim Olsen
• Improve documentation extractor script that converts XML to MediaWiki format so that it can directly push this information into the Slicer3D MediaWiki. (Wiki Systems Admin), Hans Johnson
• Improve merging strategies between BRAINS3Tools that are part of BRAINS3 and BRAINS3Tools that are part of Slicer. - Mark Scully, Hans Johnson

Workflows and Integration

• Workflows and Service Oriented Architecture Solutions for Slicer3 Modules. - Alexander Zaitsev, Wendy Plesniak, Charles Guttmann, Ron Kikinis

Preparation

1. Please make sure that you are on the na-mic-project-week mailing list
2. Starting Thursday, October 28th, 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 28: Engineering Infrastructure Projects
   • November 4: Engineering Infrastructure Projects
   • November 11: DPB Projects: Iowa, Outcomes from Alg Core Retreat
   • November 18: DPB Projects: MGH
   • November 25: DBP Projects, Funded External Collaborations
   • December 2: Funded External Collaborations
   • December 9: Other External Collaborations
   • December 16:Finalize Engineering Projects
   • January 6: Loose Ends
3. By December 16, 2010: 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 16, 2010: 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. the BIRN). 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...