1 / 28

Internship Exit Presentation

Internship Exit Presentation. Pearl Christie ER4 Branch Fall 2011. Presentation Overview. Short Biography Internship Project Skills Gained Internship Highlights Future Plans Acknowledgments. Short Biography. Born in Houston, TX Missouri City, Sugar Land, Richmond

frisco
Download Presentation

Internship Exit Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Internship Exit Presentation Pearl Christie ER4 Branch Fall 2011

  2. Presentation Overview • Short Biography • Internship Project • Skills Gained • Internship Highlights • Future Plans • Acknowledgments

  3. Short Biography • Born in Houston, TX Missouri City, Sugar Land, Richmond • University of Houston-Victoria - Senior, CIS, CS minor • Hobbies: Tennis, Country Music • Pet: Joey

  4. Re-Designing 7 of PIGI’s InterfacesPIGI • PIGI stands for Predictive Interactive Graphical Interface • It is a tool that consists of 10 interfaces that enables an operator to remotely control a robot through variable time delays. • Some of the robots that can be remotely controlled through PIGI include Centaur 2 and the Space Exploration Vehicle (SEV).

  5. Re-designing 7 of PIGI’s User Interfaces • Goal: Re- design user interfaces (UI) for its NEW operators • Design Approach: - Understand each UI’s Function - Re-design the UI’s by aiming to enhance the user experience

  6. Major Design Modifications • Visual Appeal: Adding a background theme to all UIs. Design Factors Considered: • (1) Enhance understanding: Grouping buttons, re-naming labels, adding tooltips & icon representations • (2) Providing Convenience: Writing JAVA code to create widgets & add them to UI’s - A widget is any item within UI that has functionality • (3) Providing Customization: Creating new UI’s and personalizing UI’s

  7. UI #1:Joystick Drive View • Function: Enables an operator to remotely drive a robot with a joystick

  8. Joystick Drive View Before After 1 4 3 2

  9. UI #2:Text Driving View • Function: Enables an operator to remotely drive a robot through his/her numerical data inputs & through text driving control button selections Before After 4 3 1 2

  10. UI #3:Robot Status View • Function: Displays data specific to the robot that the operator is remotely controlling Before After 1 2 3 4

  11. SEV Status View(Added Robot Values: Gear(Low or Hi), L or R Canbus Communication Dropout) Used As Model Customized 1 2 3

  12. Centaur II Status View(Added Robot Values: TTL Dist Left, TTL Distance Driven) Used As Model Customized 1 2 3 4

  13. UI #4:Common Controls View 2 Functions, Overcrowded – Split It! Enables an operator to choose an available subsystem (robot) to remotely control & select the desired command for the robot to execute It also enables efficient operators’ switching of control of the same robot at different times.

  14. Re-designed Common Controls & Created Access Control View Common Controls View Access Control View 2 1

  15. UI #5 & 6:Queue Management & Waypoint Queue View Waypoint Queue Displays waypoints that have been selected in the Common Controls view but have not been sent as commands for the robot to execute. Queue Management View Displays the commands’ status of the command selected for the robot as it progresses through sent, pending, active, and completed queues.

  16. Re-designed Queue Management & Waypoint Queue View Queue Management View Waypoint Queue View 1 2

  17. UI #7:Command Dialog • Function: This GUI prompts the operator to enter in or select values in order for the robot command selected in the Common Controls View to be executed Before • Inconvenient to view all 16 drop down boxes of which not all will be needed to execute a selected robot command • Solution: • Customized the GUI’s display by only showing the # of fields needed to be filled out in order for the selected robot command to execute

  18. Re-designed & Modified Command Dialog • Examples of some robot commands selected & how the values required for them are displayed in Command Dialog… Modified display for SEVB robot’s initializeRobot Command Modified display for SEVB robot’s simpleMoveCommand

  19. Initial Joystick Driving View With Views

  20. Joystick Drive View With Newly Designed Views

  21. Initial Text Driving View With Views

  22. Text Driving View With Newly Designed Views

  23. Skills Gained • Learned how to design GUI views for PIGI’s human robotic interfaces • Learned how to use Windows Builder Pro UI design tool to design GUIs • Practiced JAVA programming skills

  24. Internship Highlights • Shaking hands with Robonaut 2 • Seeing the Centaur 2, SEV, and Spidernaut robots • Being able to ride in the SEV out on the field • Meeting Gene Kranz at Apollo 13 movie night in MOD • Participating in R2’s Halloween Competition Contest

  25. Future Plans • Graduate from UHV with Bachelors degree in CIS/CS in May 2012 • Work full-time and concurrently pursue graduate studies in Human-Computer Interactions

  26. Acknowledgments • Dr. Hambuchen • Thanks to all my fellow co-workers: Jodi Graf, Steve Goza, Ron Allison, Shonn Everett • Entire ER-4 Branch • Diego and Dr. Adams

  27. Questions ?

  28. Internship Exit Presentation Pearl Christie ER4 Branch Fall 2011

More Related