Difference between revisions of "Explore integration of Web-based imaging workflows with Slicer"
From NAMIC Wiki
(2 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
<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: | + | 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 29: | Line 31: | ||
* Hosted Slicer locally and was able to reach the REST API, extracting | * 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 | * Retrieved a 2D Slice from Slicer and automatically ran it through a small workflow | ||
− | * Next | + | * 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 | ||
|} | |} | ||
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