2009 Summer Project Week

Back to Project Events, Events

• Dates: June 22-26, 2009
• Location: MIT. Grier Rooms A & B: 34-401A & 34-401B.

Introduction to the FIRST Joint NA-MIC, NCIGT and NAC Project Week

This is the first JOINT PROJECT WEEK of hands on activity -- programming for Image-Guided Therapy and Neuroscience applications using the open source software NA-MIC Kit, algorithm design, medical imaging sequence development, and clinical application -- between three NIH sponsored grants: NA-MIC, NCIGT, and NAC. It is an expansion of the NA-MIC Summer Project Week that has been held annually since 2005. This event will continue to be held in the summer at MIT, typically the last full week of June, and a shorter version will be held in Salt Lake City in the winter, typically the second week of January.

The main goal of these events if to move forward the deliverables of NA-MIC, NCIGT, and NAC. NA-MIC, NCIGT, and NAC participants, as well as active and potential collaborators are typical attendees at these events. These events are setup to maximize informal interaction between participants.

Active preparation begins 6-8 weeks prior to the meeting, when a kick-off teleconference is hosted by the NA-MIC, NCIGT, and NAC Engineering, Dissemination, and Leadership teams. Invitations to this call are sent to all NA-MIC, NCIGT, and NAC members, 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 NA-MIC, NCIGT, and NAC 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 project work. The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in software, algorithms, and clinical applications. 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 here.

 Back to Project Events

Please read an introduction about these events here.

Agenda

• Monday
  • 1pm: start
• Tuesday
• Wednesday
• Thursday
• Friday
  • 1pm adjourn

Projects

Other Projects

1. Propagating Event Broker through Slicer code base (Jim, Steve)

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. Stay tuned for details of teleconferences that will take place starting April 2009 to plan for this meeting.
3. June 18 TCON at 3pm ET to tie loose ends. Anyone with un-addressed questions should call.
4. By 3pm ET on June 11, 2009: 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 18, 2009: 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. 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.)
   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...

Attendee List

If you plan to attend, please add your name here.

Logistics

• Dates: June 22-26, 2009
• Location: MIT. Grier Rooms A & B: 34-401A & 34-401B.
• Registration Fee: TBD (covers the cost of breakfast, lunch and coffee breaks for the week). Due by Friday, June 12th, 2009. Please make checks out to "Massachusetts Institute of Technology" and mail to: Donna Kaufman, MIT, 77 Massachusetts Ave., 38-409a, Cambridge, MA 02139. Receipts will be provided by email as checks are received. Please send questions to dkauf at mit.edu. If this is your first event and you are attending for only one day, the registration fee is waived.
• Registration Method Add your name to the Attendee List section of this page
• Hotel: We have a group rate of XXX/night (plus tax) for a room with either 1 king or 2 queen beds at the Hotel at MIT (now called Le Meridien). Please click here to reserve. This rate is good only through June 1.
• Here is some information about several other Boston area hotels that are convenient to NA-MIC events: Boston_Hotels. Summer is tourist season in Boston, so please book your rooms early.
• 2008 Summer Project Week Template
• Last Year's Projects as a reference
• For hosting projects, we are planning to make use of the NITRC resources. See Information about NITRC Collaboration