Difference between revisions of "2010-09-Leadership-Brainstorming"

From NAMIC Wiki
Jump to: navigation, search
Line 37: Line 37:
 
***Thumbnails everywhere: mrml files, scene snapshots,
 
***Thumbnails everywhere: mrml files, scene snapshots,
 
***Scene snapshot module: reorder, rename
 
***Scene snapshot module: reorder, rename
***unified load: harmonize loading of different types of data, from local and remote data sources. Logic components, local database & UI design
+
***unified load: harmonize loading of different types of data, from local and remote data sources. Make plans for logic components, local database & UI design
 +
***extended save: save to local and remote destinations. Make plans for logic components, DB transaction, and UI design.
 
***organizing multiple data sets from one subject: time series, image fusion etc.
 
***organizing multiple data sets from one subject: time series, image fusion etc.
  

Revision as of 18:35, 30 September 2010

Home < 2010-09-Leadership-Brainstorming
 Back to Leadership Main

Everybody

  • Please check to see that you have enough money budgeted for all necessary travel expenses: Project Weeks, All-Hands Meeting (AHM), core retreats, working meetings, participation in outreach activities.

DBP

Although the full NA-MIC team is engaged in supporting the DBPs, each DBP has been assigned specific algorithm and engineering partners from the Computer Science Cores 1A and 1B who are responsible either for providing technical support to the DBP directly, or for connecting them to the relevant NA-MIC resources. Partners have been allocated a separate line item in the budget that is distinctly allocated to support their time and travel to the DBP site.
DBP teams


Computer Science

  • Algorithm retreat before the end of the year
  • Engineering
    • TCON participation is mandatory for each site. Each engineering group has to be represented at all engineering TCON's.
    • Wishlist for Engineering core:
      • Finish Slicer4 (Qt port) ASAP
      • Review Slicer3 bug tracker for issues and feature requests - in particular widgets, command line modules, improved transforms/registration...
      • Interact with ITKv4, CTK, NiPy, and other like-minded projects.
      • VTK 3D Widgets plans
      • Make plans for a new and improved Editor for slicer4
        • Graph Cuts, RSS and fast Marching with volume cropping and volume rendering
        • Gestures in 2d and 3d
      • Thumbnails everywhere: mrml files, scene snapshots,
      • Scene snapshot module: reorder, rename
      • unified load: harmonize loading of different types of data, from local and remote data sources. Make plans for logic components, local database & UI design
      • extended save: save to local and remote destinations. Make plans for logic components, DB transaction, and UI design.
      • organizing multiple data sets from one subject: time series, image fusion etc.

Outreach

  • Update the website after NOGA is issued
  • Plan Slicer training on the west coast
  • Consider a NAMIC training activity at University of Utah to be done in conjunction with January 2011 AHM.

Service

  • factory.slicer.org : Have the new setup ready for the AHM
    • superbuild
    • nightlies
    • extensions
    • dashboards for trunk, extensions, selected
    • updating website to reflect those changes
  • support migration of Na-mic and Slicer websites

Leadership