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

Latest revision as of 13:23, 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 Retrieved a 2D Slice from Slicer and automatically ran it through a small workflow Next step would be to retrieve named volumes as 3D NRRD format from the SlicerWeb Productive discussions were conducted with the NiPype team regarding how to utilize the Flow engine as an interface for NiPype-executed computation

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

@@ Line 31: / Line 31: @@
 * Hosted Slicer locally and was able to reach the REST API, extracting
 * Retrieved a 2D Slice from Slicer and automatically ran it through a small workflow
-* Next is to retrieve named volumes as 3D NRRD format volume
+* Next step would be to retrieve named volumes as 3D NRRD format from the SlicerWeb
+* Productive discussions were conducted with the NiPype team regarding how to utilize the Flow engine as an interface for NiPype-executed computation
 |}