1 / 17

Cornell Cup Mid-Review: Intel Autobot Project

Cornell Cup Mid-Review: Intel Autobot Project. Team: ASU TechPriests Members: Garret Walliman, Samantha Axtell, Riky Ringer, Hien Nguyen, Austin Noel Sponsor: Dr. Yinong Chen Arizona State University. Project Abstract.

kateb
Download Presentation

Cornell Cup Mid-Review: Intel Autobot Project

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. Cornell Cup Mid-Review:Intel Autobot Project Team: ASU TechPriestsMembers: Garret Walliman, Samantha Axtell, Riky Ringer, Hien Nguyen, Austin NoelSponsor: Dr. Yinong ChenArizona State University

  2. Project Abstract • Our goal is to improve the robot’s existing services and create new ones, to the end of connecting the robot’s services to the web and hooking them up to specially designed “algorithm-centric” user interfaces through which young students can easily program the robot.

  3. Challenge Definition • The Problem: • Today’s best tools for introducing students to programming are not good enough. • Too much conceptual / technical overhead. • Simple programming exercises are rarely interesting or enthralling. • First programming assignments focus on language and not algorithm.

  4. Challenge Definition • The Solution: • Create a new, simple UI used to program a robot, which: • Eliminates all technical / language overhead. • Focuses solely on the algorithm design! • Provides immediate, interesting feedback (by controlling a large robot).

  5. The Intel Autobot: Hardware

  6. The Intel Autobot: Software • The Autobot’s main functionality can be broken down into various services: • Motor / Motor Commands • Sonar • Directional Sensor • Kinect Depth Tracker (our service!) • These services will be made available on the web and accessed through a simulator and algorithm-centric UI.

  7. What is an Algorithm-Centric UI? • “An ‘algorithm-centric UI’ is a high-level programming environment where the act of programming is reduced to manipulating predefined conditions and outcomes to accomplish some simple – although non-obvious – task”. • This UI will allow students to remotely create an algorithm to control the robot. • It can be used as either a simulator or to control the actual robot, which gives it flexibility enough for classroom use. • http://venus.eas.asu.edu/WSRepository/RaaS/MazeNav/

  8. What Have We Done? • Robot code cleanup – documented API for robot’s current code. • Investigated and documented legacy code. • Improved needed legacy code, jettisoned unneeded. • Developed Kinect Depth Tracker Service. • Added Microsoft Kinect to robot. • Created depth tracking service to improve path finding ability. • Developed patrolling algorithm. • Simple wall-following maze algorithm utilizing Kinect and Sonar sensors. • Developed as proof-of-concept of Kinect.

  9. Kinect Depth Tracker Service • As our first service, we created this to: • Improve the Autobot’s capability. • Familiarize ourselves with the robot and with SOA programming overall. • How does it work? • Service splits Kinect field-of-view into N sections (configurable). • Each section’s depth values are consistently averaged. • Averages are rounded and returned multiple times per second.

  10. Kinect Depth Tracker: Far Right

  11. Kinect Depth Tracker: Middle

  12. Kinect Depth Tracker: Far Left

  13. Current Project Status • Team has thorough understanding of robot code / functionality, and a decent understanding of SOA architecture / SOC paradigm. • Robot functions mechanically well, services are running bug-free. • Simulator / UI code has been written. • Team is now ready to proceed with linking the robot with the UI.

  14. Project Timeline: January - February • January: • Convert current DSS services to web services. • Improve existing Motor / Motor Commands / DepthTrackerservices. • Set up Windows Server 2008 on web server. • We will use server to store simulator UI. • February • Document using server / SOAP. • Gather knowledge for linking up simulator with robot. • Cleanup/improve simulator code. • Gain fuller understanding of how simulator works. • Write and test controlling robot via web services.

  15. Project Timeline: March - April • March: • Connect web services to simulator and test. • Critical step! • Develop small website to wrap simulator in. • April: • Develop new simulators with new tasks. • Performance test simulator with students. • We hope to use the primary audience – elementary or middle school students for this, but if this is not possible we will use classmates.

  16. Conclusion • We hope to use our project to fill a void in CS education: • Simple introductory projects are not interesting. • Interesting projects are too hard. • Our robot will aim to be both simple to use and highly interesting to young students. • We have all but finished the hardware / service side of things. • We now need only to: • Link up the UI with the robot. • Create new simulators / algorithm UIs to use with the robot. • Test!

  17. Question and Answer

More Related