Difference between revisions of "Special topic breakout: IGT for Prostate"
From NAMIC Wiki
| Line 49: | Line 49: | ||
==System diagram== | ==System diagram== | ||
===Proposals=== | ===Proposals=== | ||
| − | |||
*[http://www.cisst.org/wiki/MRI_Robot:System_design System design draft proposed by Csaba (JHU)] | *[http://www.cisst.org/wiki/MRI_Robot:System_design System design draft proposed by Csaba (JHU)] | ||
| Line 61: | Line 60: | ||
*Recovering packet loss (especially for command events). | *Recovering packet loss (especially for command events). | ||
**Each subsystem keeps sending status information every several seconds / or ACK message when command received | **Each subsystem keeps sending status information every several seconds / or ACK message when command received | ||
| − | |||
| − | |||
=System Design (Draft)= | =System Design (Draft)= | ||
See [[U41:Prostate:BRP:SystemDesign_Jun2007]]. | See [[U41:Prostate:BRP:SystemDesign_Jun2007]]. | ||
Revision as of 18:04, 27 June 2007
Home < Special topic breakout: IGT for Prostate
Return to Project Week Main Page
Prostate IGT Breakout Session
June 26th, 11am-noon
Location: Grier Rooms A & B: 34-401A & 34-401B
Contents
Invited Attendees
- Clare Tempany, BWH
- Clif Burdette, Acousticmed
- Jack Blevins, Acousticmed
- Greg Fischer, JHU
- Gabor Fichtinger, Queens
- Csaba Csoma, JHU
- David Gobbi, Queens
- Purang Abolmaesumi, Queens
- Robert Cormack, BWH
- Junichi Tokuda, BWH
- Haiying Liu, BWH
Agenda
Technical updates
2-3 slides from each site.
BWH
- Scanner control interface (NaviTrack)
- Real-time image transfer interface (NaviTrack)
- Z-frame tracking for manipulator calibration
- 3D Slicer 3.0 prostate module
JHU
- Movie: CAD simulation of the robot
- Q&A about the robot and the controller interface
Acoustic Med
Clinical workflow
Proposal
U41:Prostate:BRP:Tasks:Biopsy_Workflow_Design
Issues
- State (mode) transition
System diagram
Proposals
Issues
Minor change from BWH:
- Port numbers are changed (to avoid conflicts while testing multiple subsystems in one host)
Suggested by Csaba:
- Connection between RT Scanner IO and Robot Controller.
- The robot controller should get z-frame postion data from the navigation software
- Recovering packet loss (especially for command events).
- Each subsystem keeps sending status information every several seconds / or ACK message when command received
