1. Project Paper Presentation Hanlin Wan March 15, 2011

2. iPad Mobile Surgical Console Goal: Create iPad application to allow remote configuration of surgical robot components Progress: Necessary libraries and tools compiled and working Future Steps: Design GUI, implement controls

3. Paper Selection Surgical Assistant Workstation (SAW) Communication Interfaces for Teleoperation M.Y. Jung, G. Sevinc, A. Deguet, R. Kumar, R. Taylor, P. Kazanzides From cisst workshop ICRA 2010.

4. Purpose of SAW Software development framework for interfacing with hardware and software modules Hardware – robotic devices, imagers, sensors Software – video processing, 3D user interfaces, robot motion control

5. SAW in Action From: Surgical Workstation Wiki, https://www.cisst.org/saw/Main_Page

6. Advantages Flexibility –Inter-thread communication – tasks running within a single process –Inter-process communication – tasks being distributed across networks Convenience –Can pass any data types supported by cisst –Runs on Windows, Linux, Mac, hopefully iOS High network performance

7. Framework cisst libraries – core framework Internet Communication Engine (ICE) – network layer

8. Proxy Pattern Design Replaces local connection with conceptual local connection over network From Jung Paper

9. cisstMultiTask library Provided interfaces – server task Required interfaces – client task From Jung Paper

10. Proxy Pattern in cisstMultiTask Proxy objects hidden from application level ICE makes proxy connections transparent From Jung Paper

11. Coding of Proxy Design Set up task manager Register tasks Connect tasks From Jung Paper

12. Network Performance Worst case: 5ms latencies From Jung Paper

13. Teleoperation Test Sensible Phantom Omni – position sensing and force feedback device From Jung Paper

14. Teleoperation Test Slight delay From Jung Paper

15. Conclusion Acceptable for haptic feedback and teleoperation Need optimal network topology for closed loop control

16. Good Aspects of Paper Framework explained very clearly Many figures Experiments demonstrate good performance Very flexible and reusable code Simple API

17. Weaknesses of Paper Mentioned other tools but didn’t compare Tested with predictable paths No real user data

18. Further Studies Latencies with many modules occurring simultaneously Look at how delays affect usability

19. Applications to Our Project Framework compiled Next step – program interfaces between modules

20. Thank you. Any questions?