Dissemination:Events Planning

From NAMIC Wiki
Revision as of 13:31, 18 December 2006 by Andy (talk | contribs) (Update from Wiki)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Home < Dissemination:Events Planning

DISCLAIMER: This page is currently just a set of thoughts I have on planning dissemination events. You are welcome to browse it but I expect it to change quite a bit over the next few days. Tkapur


Core Members

  1. Core 1 (Algorithms)
    1. MIT (Eric Grimson, Polina Golland)
    2. MGH (David Kennedy, Dave Tuch)
    3. U Utah (Ross Whitaker, Tom Fletcher)
    4. UNC (Guido Gerig, Martin Styner)
    5. GATech (Allen Tannenbaum)
  2. Core 2 (Engineering)
    1. GE (Bill Lorensen)
    2. UCLA (Art Toga, TBD)
    3. UCSD (Mark Ellisman, Jeff Grethe)
    4. Kitware (Will Schroeder)
    5. Isomics (Steve Pieper)
  3. Core 3 (DBP)
    1. Harvard (Martha Shenton, Sylvain Bouix)
    2. UCI (Steve Potkin, Yi Jin)
    3. Dartmouth (Andrew Saykin)
    4. U Toronto (James Kennedy, Fabio Macciardi)
  4. Core 4 Service Core PI: William Schroeder, PhD - Kitware, Inc.
  5. Core 5 Training Core PI: Randy Gollub, MD, PhD - MGH
  6. Core 6 Dissemination Core PI: Steven Pieper, PhD - Isomics, Inc.
  7. Core 7 Management Core PI: Stephen Wong, PhD - BWH

Order of Events =

Target: complete core 1 & 2 events by end of Jan, and all by end of Feb.

  1. ITK training session(Dec)
  2. Slicer training session (Dec/Jan?)
  3. LONI Pipeline training session (Jan?)
  1. GE, Kitware(Dec/Jan)
  2. UNC, GATech, Utah (Jan)
  3. UCLA, UCSD (need LONI pipeline documents, talk to Art about inclusion in V0 or V1)
  4. Dartmouth, Harvard, UCI

Goal of Event

  1. Meet with the NA-MIC team at each site in-person
  2. Discuss the concept of the NA-MIC kit: the value proposition(software infrastructure/maintenance,painless access to other people's cutting edge results) the components of the current version kit, and a roadmap for the kit over the next 4 years. Use example to illustrate how to plug in .. (Raul's work?)
  3. Ensure that the software developer(s) at each site have the resources needed to install the kit, and start developing applications in the NA-MIC environment
  4. Reiterate the key concepts that are part of the "core" of NA-MIC
    1. an open source platform for medical image analysis
    2. a community of expert clinicians, scientists, and engineers available as a resource to all members
    3. strong commitment to communication between the clinical, algorithms, and engineering cores
  5. Set up Matrix of options for "menu" at event: ITK (intro, advanced), Slicer (user, programmer,..) etc.


At All-hands Meeting

  1. schedule a 2-3 hour follow up session with NAMIC developers at all-hands meeting