Projects:ARRA:SlicerWF:MigrationJavaClients2QT
From NAMIC Wiki
Home < Projects:ARRA:SlicerWF:MigrationJavaClients2QT
Integration of Workflow Clients with Slicer4
Front-End GUI (NEW):
Development Toolkit / Language: QT/C++
*Two tier GUI integration:
1. QT Widget Palette for listing available Workflow Applications Callable from Development Tools Menu
2. QT Pop-up Windows for controlling Workflow Application.
Callable from dispatching palette 1) as QT child dialog widget. The pop-up approach is proposed for ease navigation between WF GUI and Slicer4 GUI (volume edit window, cropping, etc)Major functionality:
- project/data organizing
- workflow pipelines invocation
- loading Slicer scenes into parent Slicer4 instance
Workflow and Web Services invocation:
- Java stubs (implemented)
- File Binding (implemented)
- RESTFul web service calls (if needed. Note: non-commercial QT does not support SOAP protocol)
Workflow and Web Services deployment:
- BPEL Modules on Application Server for workflow pipelines (implemented)
- SOAP Web services for CLI with Slicer modules
- RESTFul web services as stubs between Slicer QT Modules and web services (if needed – most probably, file binding and Java stubs will suffice)
Case Studies / Scenarios
- Basic EM Segmentation. Target completion date - end of AHM-2011 (initial project with minimal features but with full integration with Slicer. Migrate scenarios from Aging and HIV studies )
- PET/CT registration and SUV computation (Migrate Currently Developed WF Fron-end)
- Universal registration suite (NEW: longitudinal studies with multimodal images)
- More complex EM Segmentation scenarios (with SPECTRE module, Lesion and WM hyper-intensity segmentation...)