Difference between revisions of "Explore integration of Web-based imaging workflows with Slicer"
From NAMIC Wiki
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | + | ||
<gallery> | <gallery> | ||
Image:PW-Winter2017.png|link=2017_Winter_Project_Week#Projects|[[2017_Winter_Project_Week#Projects|Projects List]] | Image:PW-Winter2017.png|link=2017_Winter_Project_Week#Projects|[[2017_Winter_Project_Week#Projects|Projects List]] | ||
+ | Image:Slicer connected workflow.png | Workflow to read from SlicerWeb with downstream processing | ||
+ | Image:Outimage.png|Image as received from SlicerWeb | ||
+ | Image:Rotated and blurred.png | Result after running workflow | ||
<!-- Use the "Upload file" link on the left and then add a line to this list like "File:MyAlgorithmScreenshot.png" --> | <!-- Use the "Upload file" link on the left and then add a line to this list like "File:MyAlgorithmScreenshot.png" --> | ||
</gallery> | </gallery> | ||
Line 16: | Line 19: | ||
| | | | ||
<!-- Objective bullet points --> | <!-- Objective bullet points --> | ||
− | * Explore how Slicer can interact with an existing web-based, open-source workflow system ( | + | * 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 --> | <!-- Approach and Plan bullet points --> | ||
− | * | + | * Load a MRML scene into Slicer and read images into Flow by accessing through Slicer's RestAPI |
− | * Connect with Girder-breakout team to discuss data sharing between systems | + | * 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. | ||
| | | | ||
<!-- Progress and Next steps bullet points (fill out at the end of project week) --> | <!-- 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 |
+ | * 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 | ||
|} | |} | ||
==Background and References== | ==Background and References== | ||
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data --> | <!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data --> | ||
+ | The Flow source code is available here: https://github.com/Kitware/flow |
Latest revision as of 13:23, 13 January 2017
Home < Explore integration of Web-based imaging workflows with SlicerKey Investigators
- Curt Lisle, KnowledgeVis, LLC
Project Description
Objective | Approach and Plan | Progress and Next Steps |
---|---|---|
|
|
|
Background and References
The Flow source code is available here: https://github.com/Kitware/flow