Difference between revisions of "2016 Winter Project Week/Breakout Session/What's Planned for Slicer Core"

From NAMIC Wiki
Jump to: navigation, search
Line 21: Line 21:
 
*Andras Lasso: Sequences,  
 
*Andras Lasso: Sequences,  
 
*Mike Halle: Slicer webinfrastructure and github
 
*Mike Halle: Slicer webinfrastructure and github
*Andrey Fedorov: DICOM
+
*Andrey Fedorov: DICOM objects for interoperability
 +
** focus areas: segmentations, enhanced multiframe (single-file MR series, parametric maps), volumetric measurement structured reports
 +
** approach
 +
*** developer API in DCMTK
 +
*** reusable command-line converters for extension developers
 +
*** user-level domain-specific applications
 +
** open question for discussion: should this functionality be in the core or extension

Revision as of 21:16, 13 December 2015

Home < 2016 Winter Project Week < Breakout Session < What's Planned for Slicer Core

Introduction

Maintenance needed for core libraries

  • VTK7 (rapid changes coming to VTK due to maintenance grant)
  • Python: conda (and?)or cmake/wheels?
  • Qt5: improvements, plus 4.8 may eventually stop supporting new systems

Organization

  • Moving diffusion to extension (other things to extensions?)

Key requests from the community

Roadmaps

  • Steve Pieper: Chronicle, ctkjs, CommonGL
  • JC Fillion-Robin: Girder, Anaconda, Factory machines
  • Andras Lasso: Sequences,
  • Mike Halle: Slicer webinfrastructure and github
  • Andrey Fedorov: DICOM objects for interoperability
    • focus areas: segmentations, enhanced multiframe (single-file MR series, parametric maps), volumetric measurement structured reports
    • approach
      • developer API in DCMTK
      • reusable command-line converters for extension developers
      • user-level domain-specific applications
    • open question for discussion: should this functionality be in the core or extension