Difference between revisions of "Explore integration of Web-based imaging workflows with Slicer"

Revision as of 07:26, 13 January 2017

Home < Explore integration of Web-based imaging workflows with Slicer

Objective	Approach and Plan	Progress and Next Steps
Explore how Slicer can interact with an existing web-based, open-source workflow system (Flow, developed by Kitware and KnowledgeVis, LLC) Exchange data between 3D Slicer and the Flow workflow system	Load a MRML scene into Slicer and read images into Flow by accessing through Slicer's RestAPI Use Steve's (work in progress) SlicerWeb Extension to respond to REST requests from Flow Connect with Girder-breakout team to discuss data sharing between systems (Slicer, Girder, Flow, etc.) (after project week), expand to work for whole NRRD image that comes from the REST API.	Hosted Slicer locally and was able to reach the REST API, extracting

The Flow source code is available here: https://github.com/Kitware/flow

@@ Line 18: / Line 18: @@
 <!-- Objective bullet points -->
 * Explore how Slicer can interact with an existing web-based, open-source workflow system (Flow, developed by Kitware and KnowledgeVis, LLC)
+* Exchange data between 3D Slicer and the Flow workflow system
 |
 <!-- Approach and Plan bullet points -->
 * Load a MRML scene into Slicer and read images into Flow by accessing through Slicer's RestAPI
-* Prototype a Slicer scripted module that loads images using Flow's RestAPI.  Flow is a Girder-based app.
+* Use Steve's (work in progress) SlicerWeb Extension to respond to REST requests from Flow
-* Evaluate SimpleITK vs. scikit-image as imaging toolkit for the workflow system.
 * Connect with Girder-breakout team to discuss data sharing between systems (Slicer, Girder, Flow, etc.)
+* (after project week), expand to work for whole NRRD image that comes from the REST API.
 |
 <!-- Progress and Next steps bullet points (fill out at the end of project week) -->
-*
+* Hosted Slicer locally and was able to reach the REST API, extracting
 |}