Difference between revisions of "2016 Winter Project Week/Projects/SlicerROSIntegration"
From NAMIC Wiki
| Line 14: | Line 14: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
| − | * | + | * Define requirements and system architecture for medical robotics software system based on 3D Slicer and Robot Operating System (ROS) |
| + | |||
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | * | + | * Needs for 3D Slicer / ROS integration in ongoing research projects (presentations by participants) |
| + | ** Axel (Suturing robot) | ||
| + | ** Simon (dVRK?) | ||
| + | ** Junichi (OpenIGTLink and medical robotics research) | ||
| + | ** Tobias (OCT robot / Integration of KUKA robot and 3D Slicer | ||
| + | * Brainstorming 1: Requirements | ||
| + | ** Applications (e.g. endoscopic surgery, percutaneous interventions, catheterization, etc.) | ||
| + | ** Roles for 3D Slicer -- visualization, image processing, etc. | ||
| + | ** Roles for ROS -- vision, sensors, devices, etc. | ||
| + | * Brainstorming 2: Architecture for 3D Slicer-ROS integration | ||
| + | ** Types of data exchanged between ROS and 3D Slicer | ||
| + | ** Communication scheme between ROS and 3D Slicer | ||
| + | ** Software package to provide | ||
| + | *** Independent middleware? | ||
| + | *** 3D Slicer plug-in modules | ||
| + | *** ROS modules | ||
| + | * Brainstorming 3: Collaborative tools / teams | ||
| + | *** Repository | ||
| + | |||
| + | |||
| + | |||
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
Revision as of 13:25, 23 November 2015
Home < 2016 Winter Project Week < Projects < SlicerROSIntegration
Key Investigators
- Junichi Tokuda (Brigham and Women's Hospital)
- Axel Krieger (Children's National Medical Center)
- Simon Leonard (Johns Hopkins University)
Project Description
Objective
- Define requirements and system architecture for medical robotics software system based on 3D Slicer and Robot Operating System (ROS)
Approach, Plan
- Needs for 3D Slicer / ROS integration in ongoing research projects (presentations by participants)
- Axel (Suturing robot)
- Simon (dVRK?)
- Junichi (OpenIGTLink and medical robotics research)
- Tobias (OCT robot / Integration of KUKA robot and 3D Slicer
- Brainstorming 1: Requirements
- Applications (e.g. endoscopic surgery, percutaneous interventions, catheterization, etc.)
- Roles for 3D Slicer -- visualization, image processing, etc.
- Roles for ROS -- vision, sensors, devices, etc.
- Brainstorming 2: Architecture for 3D Slicer-ROS integration
- Types of data exchanged between ROS and 3D Slicer
- Communication scheme between ROS and 3D Slicer
- Software package to provide
- Independent middleware?
- 3D Slicer plug-in modules
- ROS modules
- Brainstorming 3: Collaborative tools / teams
- Repository
