Difference between revisions of "Project Events"

From NAMIC Wiki
Jump to: navigation, search
Line 1: Line 1:
 
[[Image:EMSegment31Structures.png|thumb|350px|Brain segmentation using EMSegment and ModelMaker in Slicer3.]]
 
[[Image:EMSegment31Structures.png|thumb|350px|Brain segmentation using EMSegment and ModelMaker in Slicer3.]]
  
 +
==Introduction==
  
 
NA-MIC Project Week is a hands on activity -- programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the NA-MIC calendar. It is held in the summer at MIT, typically the last week of June, and a shorter version is held in Salt Lake City in the winter, typically the second week of January.   
 
NA-MIC Project Week is a hands on activity -- programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the NA-MIC calendar. It is held in the summer at MIT, typically the last week of June, and a shorter version is held in Salt Lake City in the winter, typically the second week of January.   
Line 9: Line 10:
 
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 programming, algorithm design, or clinical application of NA-MIC kit tools.  The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical.  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.
 
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 programming, algorithm design, or clinical application of NA-MIC kit tools.  The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical.  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.
  
 
+
==Listing of all Project Events==
  
 
#[[2008_Project_Half_Week|2008 January: Project/Programming Event #6]]
 
#[[2008_Project_Half_Week|2008 January: Project/Programming Event #6]]

Revision as of 19:43, 28 November 2007

Home < Project Events
Brain segmentation using EMSegment and ModelMaker in Slicer3.

Introduction

NA-MIC Project Week is a hands on activity -- programming using the NA-MIC Kit, algorithm design, and clinical application -- that has become one of the major events in the NA-MIC calendar. It is held in the summer at MIT, typically the last week of June, and a shorter version is 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. NA-MIC 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 Engineering, Dissemination, and Leadership teams, the primary hosts of this event. Invitations to this call are sent to all na-mic members, past attendees of the event, as well as any parties who have expressed an interest in working with NA-MIC. 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 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 templated 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 programming, algorithm design, or clinical application of NA-MIC kit tools. The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical. 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.

Listing of all Project Events

  1. 2008 January: Project/Programming Event #6
  2. 2007 June: Project/Programming Event #5
  3. 2007 January: Project/Programming Event #4
  4. 2006 June: Project/Programming Event #3
  5. 2006 January: Programming Event #2
  6. 2005 June: Programming Event #1