Difference between revisions of "AlgorithmRetreat2010"

From NAMIC Wiki
Jump to: navigation, search
Line 13: Line 13:
 
== Agenda==
 
== Agenda==
  
* 8:30 meet in  
+
* 8:30 meet in Chair's conference room, Brooks Building, coffee
* DBP updates, each 15 minutes
+
* 9-10 DBP updates, each 15 minutes
* short and long term plans for each core 1 site
+
* 10-11 Overview of Core 1 site short and long term plans (each 10 min)
 
+
* 11-12 Slicer update by run, demo
* Ron Slicer update, demo
+
** Gao and Tannenbaum demo
* Gao and Tannenbaum demo
+
* noon lunch
 
+
* 1-2 Discussion on handshaking of Core1 developments and the Slicer development
 +
* 2-3:30 Discussion on registration topics, meshing
 +
* 3:30-5 Discussion on
  
 
==Topics ==
 
==Topics ==

Revision as of 19:56, 26 October 2010

Home < AlgorithmRetreat2010
Back to brainstorming page
Back to events page

Nov 5-6, Chapel Hill, NC

Introduction

  • The NA-MIC algorithm core holds an annual retreat
  • The 2010 event will begin on 8:30 am on Friday the 5th of Nov and finish at approximately 2pm on Saturday the 6th.
  • Meeting location: SittersonHall/Brooks Building, chair's conference room, FB120 (first floor)

Map

Agenda

  • 8:30 meet in Chair's conference room, Brooks Building, coffee
  • 9-10 DBP updates, each 15 minutes
  • 10-11 Overview of Core 1 site short and long term plans (each 10 min)
  • 11-12 Slicer update by run, demo
    • Gao and Tannenbaum demo
  • noon lunch
  • 1-2 Discussion on handshaking of Core1 developments and the Slicer development
  • 2-3:30 Discussion on registration topics, meshing
  • 3:30-5 Discussion on

Topics

  • Plans, Needs, Expectations of and Interactions with DBPs (Core-1 contacts, all)
    • Actions items for the AHM
    • Plans for the next 12 months
  • Segmentation
  • Registration
  • Other algorithm classes
    • Shape
    • Interactive algorithms
  • Interaction with the Engineering Core
    • See whitepaper about the interactions between Cores 1a, 1b, and 2.
  • Slicer
  1. If your algorithm can be delivered as a CLI, then develop and deploy it now as an extension for 3.6 and the nightly builds. This will transition smoothly to slicer4.
  2. If your algorithm requires interactivity then
    1. If you want to deploy it within the next 6 months, then consider a python or tcl scripted wizard interface to CLI code, knowing that there will be some porting required.
    2. if a wizard isn't interactive enough, consider a custom kwwidgets interface, knowing that this will be difficult to port to slicer4
  3. if your deployment target is 6 or more months out, you should begin working with the slicer4 Qt developer build starting in January.

Suggested Hotels

Nice for walking to campus & Franklin Street, but rather expensive (ask for the University/Computer Science rate of 159 USD per night):

Best suggestions (need taxi or rental car to campus & Franklin Street):

Attendees

  • Ross Whitaker
  • Guido Gerig
  • Polina Golland
  • Allen Tannenbaum
  • Martin Styner
  • Ron Kikinis (Saturday only)
  • Michal Depa, MIT
  • Archana Venkataraman, MIT
  • Sam Gerber, Utah
  • Marcel Prastawa
  • Yi Gao, Georgia Tech
  • Romeil Sandhu, Georgia Tech