2013 Summer Project Week

Back to Events

Dates: June 17-21, 2013.

Location: MIT, Cambridge, MA.

Agenda

The Project Week events will start at noon on Monday June 17, 2013 and run through to noon on Friday June 21, 2013.

Projects

Please use this template to create wiki pages for your project. Then link the page here with a list of key personnel.

General Registration

• Landmark Registration (Steve, Nadya, Greg, Paolo, Erol)

Informatics

• 3D Slicer based Biomedical image computing teaching modules (A.Vilchis, J-C. Avila-Vilchis, S.Pujol)
• Robot Control (A.Vilchis, J-C. Avila-Vilchis, S.Pujol)

Infrastructure

• Annotations rewrite (Nicole Aucoin)
• Brain atlas optimisations demo (Marianna)
• Provenance
• Patient hierarchies (Csaba Pinter)
• Sample data (Steve Pieper, Jim Miller)
  • content addressable data, in external data processing in Slicer, cmake file for external data, when write test can decorate the data file name with macro keywords saying it's external
• Plastimatch in NiPype (Paolo, Dave, Hans)
• Quality Assurance Module (Dave)
  • look for commonalities/reuse of CompareVolumes
• iPython in Slicer (Hans, Jc, Dave)
• Optimizing start time of slicer (Jc)

Background

We are pleased to announce the 17th PROJECT WEEK of hands-on research and development activity for applications in Neuroscience, Image-Guided Therapy 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 25th 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, CIMIT, and OCAIRO. 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 17-21, 2013.
• Location: MIT.
• REGISTRATION:
• Registration Fee:
• Hotel:

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 projects in a their weekly teleconferences. 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 8, all participants to add a one line title of their project to #Projects
4. By 3pm ET on Thursday June 6, 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 13: Create a directory for each project on the NAMIC Sandbox (Matt)
   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. Where possible, 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. (Matt)
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. See the Developer Section of slicer.org for information.
   2. Projects to develop extension modules should be built against the latest Slicer4 trunk.