2011 Summer Project Week

 Back to Events

• Dates: June 20-24, 2011
• Location: MIT

Agenda

Time	Monday, June 20	Tuesday, June 21	Wednesday, June 22	Thursday, June 23	Friday, June 24
	Project Presentations	NA-MIC Update Day		IGT Day	Reporting Day
8:30am		Breakfast	Breakfast	Breakfast	Breakfast
9am-12pm		Slicer 4 Core Modules Usability Review Star Room ---------------------------------------- 10:15am: Break ---------------------------------------- Slicer 4 Core Modules Usability Review Star Room	9am-12pm: Breakout Session: ITK (Luis Ibanez) Star Room	9am-5pm: Breakout Session: OpenIGTLink Grier Rooms	10am-12pm: Project Progress Updates Grier Rooms
12pm-1pm	Lunch	Lunch	Lunch	Lunch	Lunch boxes; Adjourn by 1:30pm
1pm-5:30pm	1-1:05pm: Ron Kikinis: Welcome Grier Rooms ---------------------------------------- 1:05-3:30pm: Project Introductions (all Project Leads) Grier Rooms ---------------------------------------- 3:30-5:00pm: NA-MIC Kit Update (Aylward, Miller, Pieper) Grier Rooms	1-3pm: Breakout Session: Slicer4 MultiVolume Containers Star Room ---------------------------------------- 3-4pm: Tutorial Contest Presentations Grier Rooms ---------------------------------------- 4-5pm: Breakout Session: Breakout Session TBD Star Room	12:45-1pm: Tutorial Contest Winner Announcement Grier Rooms ---------------------------------------- 1-3pm: Breakout Session: Microscopy Image Analysis TO BE CONFIRMED (Sean Megason) Kiva Room ---------------------------------------- 3-4pm: Breakout Session: Inter-subject Registration for EM segmenter Star Room ---------------------------------------- 5pm: Reception R&D Pub	1-2pm: Breakout Session: TBD ---------------------------------------- 2-3pm:Breakout Session:TBD ---------------------------------------- 3-4pm: Breakout Session: TBD
5:30pm	Adjourn for the day	Adjourn for the day	Adjourn for the day	Adjourn for the day

Projects

• Evaluate the applicability of DICOM RT I/O facility in Slicer (via Plastimatch Extension) for Brachytherapy Planning (Tina Kapur, Greg Sharp, Robert Cormack?)
• Visualization of b-spline and vector fields (Steve, Danielle, Dominik)
• Annotation Module in Slicer4 (Nicole Aucoin, Daniel Haehn)
• Slicer4 Multivolume Containers (Ron Kikinis, Nicole Aucoin, Steve Pieper, ... )
  • RECIST Slicer4 module (Nicole Aucoin)
• DicomToNrrdConverter refactoring ( Xiaodong Tao, Mark Scully)
• UNC Antialiasing Software as a Slicer extension or ITK module (Steve Pizer, Brad Davis, Petter Risholm, Andriy Fedorov)
• Normal consistency in particle correspondence computation using great circles in principal spheres (Beatriz Paniagua, Martin Styner, Sungkyu Jung)
• Group-wise Automatic Mesh-Based analysis of CortIcal Thickness - GAMBIT (Clement Vachet, Martin Styner)
• DTIProcessing within Predict HD (Clement Vachet, Martin Styner)

Background

We are pleased to announce the 13th PROJECT WEEK of hands-on research and development activity for applications in Image-Guided Therapy, Neuroscience, and several additional areas of biomedical research that enable personalized medicine. Participants will engage in open source programming using the NA-MIC Kit, algorithm design, medical imaging sequence development, tracking experiments, and clinical application. The main goal of this event is to move forward the translational research deliverables of the sponsoring centers and their collaborators. Active and potential collaborators are encouraged and welcome to attend this event. This event will be set up to maximize informal interaction between participants. If you would like to learn more about this event, please click here to join our mailing list.

Active preparation begins on Thursday, April 28th at 3pm ET, with a kick-off teleconference. Invitations to this call will be sent to members of the sponsoring communities, their collaborators, past attendees of the event, as well as any parties who have expressed an interest in working with these centers. 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 coverage for all. Subsequent teleconferences will allow for more focused discussions on individual projects and 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 will be asked to fill in a template page on this wiki that describes the objectives and plan of their projects.

The event itself will start off with a short presentation by each project team, driven using their previously created description, and will help all participants get acquainted with others who are doing similar work. In the rest of the week, about half the time will be spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half will be spent in project teams, doing hands-on project work. The hands-on activities will be done in 40-50 small teams of size 2-4, each with a mix of multi-disciplinary expertise. To facilitate this work, a large room at MIT will be setup with several tables, with internet and power access, and each computer software development based team will gather on a table with their individual laptops, connect to the internet to download their software and data, and be able to work on their projects. Teams working on projects that require the use of medical devices will proceed to Brigham and Women's Hospital and carry out their experiments there. On the last day of the event, a closing presentation session will be held in which each project team will present a summary of what they accomplished during the week.

This event is part of the translational research efforts of NA-MIC, NCIGT, NAC, Harvard Catalyst, and CIMIT. It is an expansion of the NA-MIC Summer Project Week that has been held annually since 2005. It will be held every summer at MIT and Brigham and Womens Hospital in Boston, typically during the last full week of June, and in Salt Lake City in the winter, typically during the second week of January.

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

Logistics

• Dates: June 20-24, 2011
• Location: MIT. Grier Rooms A & B: 34-401A & 34-401B.
• REGISTRATION: Please register here. Payment must be made by credit card.
• Registration Fee: $260 (covers the cost of breakfast, lunch and coffee breaks for the week).
• Hotel: Boston Marriott Cambridge, Two Cambridge Center, 50 Broadway, Cambridge, MA 02142. Group rate is $199/night plus tax. Book here or call 1-617-494-6600 and mention that you are booking in the MIT Room Block. All reservations must be made by May 29, 2011 to receive the discounted rate.

Preparation

1. Please make sure that you are on the http://public.kitware.com/cgi-bin/mailman/listinfo/na-mic-project-week mailing list
2. The NA-MIC engineering team will be discussing infrastructure projects in a kickoff TCON on April 28, 3pm ET. In the weeks following, new and old participants from the above mailing list will be invited to join to discuss their projects, so please make sure you are on it!
3. By 3pm ET on Thursday May 12, all participants to add a one line title of their project to #Projects
4. By 3pm ET on Thursday June 9, all project leads to complete 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.
5. By 3pm on June 16: Create a directory for each project on the NAMIC Sandbox (Zack)
   1. 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)
   2. Gather test images in any of the Data sharing resources we have (e.g. XNAT/MIDAS). 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.)
   3. 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)
6. 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...
7. People doing Slicer related projects should come to project week with slicer built on your laptop.
   1. Projects to develop extension modules should work with the Slicer-3-6 branch (new code should not be checked into the branch).
   2. Projects to modify core behavior of slicer should be done on the trunk.