Difference between revisions of "2016 Summer Project Week/medical imaging webapp"

From NAMIC Wiki
Jump to: navigation, search
Line 48: Line 48:
 
* Identified [http://www.zerorpc.io zerorpc] as a powerful solution for distributed MIC apps (based on [http://zeromq.org ØMQ] and [http://msgpack.org MessagePack]).
 
* Identified [http://www.zerorpc.io zerorpc] as a powerful solution for distributed MIC apps (based on [http://zeromq.org ØMQ] and [http://msgpack.org MessagePack]).
 
** Use [https://pypi.python.org/pypi/msgpack-numpy msgpack-numpy] to support ndarrays in zerorpc (implemented via monkey-patching).
 
** Use [https://pypi.python.org/pypi/msgpack-numpy msgpack-numpy] to support ndarrays in zerorpc (implemented via monkey-patching).
* The JS-C++ interaction lives now on an experimental branch in commontk/CTK
+
* The JS-C++ interaction lives now on an [https://github.com/nolden/CTK/tree/wip-dicom-web experimental branch in CTK] (will move to the commontk organization soon)
 
** various mechanisms for development, debug and deployment can be tested,  
 
** various mechanisms for development, debug and deployment can be tested,  
 
*** Qt resource compiler
 
*** Qt resource compiler

Revision as of 08:52, 25 June 2016

Home < 2016 Summer Project Week < medical imaging webapp

Key Investigators

  • Steve Pieper (Isomics)
  • Hans Meine (Uni Bremen, MEVIS)
  • Marco Nolden (DKFZ)

(other interested parties are welcome!)

Project Description

Ctk-web.jpg

Objective

  • Review the state of the art in medical imaging web apps
  • Consider various use cases:
    • Pure web browser application
    • Web browser + remote compute or rendering services
    • Web App widgets used in desktop application (e.g. via QtWebKit/QtWebEngine in Slicer/MITK/MeVis)
  • Topics
    • Native JavaScript code for DICOM IO, Rendering, Processing
    • Organization of toolkits and libraries
    • Interacting with the community of like-minded developers

Approach, Plan

  • Discuss recent developments cited in the Objective section
  • Identify more valuable development priorities
    • provide useful functionality (e.g. improved DICOM patient/study/series/search browser)
    • probe any outstanding issues (e.g. test scalability or performance questions)
    • establish paradigms for ongoing development
  • Finalize a prototype showing JS-C++ interaction replacing the CTK DICOM Browser Widget with a web-technology based implementation

Progress