Difference between revisions of "CISC367 S2023"
(→Schedule) |
(→Schedule) |
||
| Line 375: | Line 375: | ||
|Off-the-shelf object detectors | |Off-the-shelf object detectors | ||
|[https://github.com/Ar-Ray-code/YOLOv5-ROS ROS2 wrapper around YOLOv5] (not tested)<!--[https://navigation.ros.org/ nav2], [https://navigation.ros.org/tutorials/docs/navigation2_on_real_turtlebot3.html Turtlebot3 navigation tutorial]--> | |[https://github.com/Ar-Ray-code/YOLOv5-ROS ROS2 wrapper around YOLOv5] (not tested)<!--[https://navigation.ros.org/ nav2], [https://navigation.ros.org/tutorials/docs/navigation2_on_real_turtlebot3.html Turtlebot3 navigation tutorial]--> | ||
| − | |HW #6 | + | |[https://docs.google.com/document/d/1c8_zHq2k7myrNJDrRX763M46lIiy27zwKTNoUf8qpfk/edit?usp=sharing HW #6] |
|- | |- | ||
|23 | |23 | ||
Revision as of 07:36, 3 May 2023
Course information
| Title | CISC367-012 Introduction to Mobile Robot Programming |
| Description | A hands-on approach to implementing mobile robot algorithms on a small wheeled platform, both in simulation and reality. We will review the fundamentals of kinematics, planning, sensing, and control, as well as getting acquainted with higher-level concepts related to navigation, tracking, mapping, and learning. |
| When | Wednesdays and Fridays, 8:40-9:55 am. When there is a homework due, no more than the first 30 minutes of each class will be in lecture format. The rest of the class period (and optionally the subsequent office hours) will be spent working on the robots. |
| Where | Feb. 8: Willard 215 Feb. 10 and beyond: Smith 211 |
| Instructor | Christopher Rasmussen, 446 Smith Hall, cer@cis.udel.edu |
| Office hours | Mondays, 9-10:30 am and Wednesdays and Fridays, 9:55-11 am in Smith 211 (starting Feb. 10) |
| Grading |
Programming assignments will be graded on how many of the subtasks you complete or demonstrate successfully. For the overall course grade, a preliminary absolute mark will be assigned to each student based on the percentage of the total possible points they earn according to the standard formula: A = 90-100, B = 80-90, C = 70-80, etc., with +'s and -'s given for the upper and lower third of each range, respectively. Based on the distribution of preliminary grades for all students (i.e., "the curve"), the instructor may increase these grades monotonically to calculate final grades. This means that your final grade can't be lower than your preliminary grade, and your final grade won't be higher than that of anyone who had a higher preliminary grade. I will try to keep you informed about your standing throughout the semester. If you have any questions about grading or expectations at any time, please feel free to ask me. |
| Academic policies | Programming projects should be demo'd in class on the deadline day and uploaded to Canvas by midnight of that day (with a grace period of a few hours afterward...after sunrise is definitely late). A late homework is a 0 without a valid prior excuse. To give you a little flexibility, you have 3 "late days" to use on homeworks to extend the deadline to the next class period without penalty. No more than one late day may be used per assignment. Late days will automatically be subtracted, but as a courtesy please notify the instructor in an e-mail of your intention to use late days before the deadline.
Assignment submissions should consist of a directory containing all code (your .cpp/.py files, etc.), any output data generated (e.g., images, movies, etc.), and an explanation of your approach, what worked and didn't work, etc. contained in a separate text or HTML file. Do not submit executables or .o files, please! The directory you submit for each assignment should be packaged by tar'ing and gzip'ing it or just zip'ing it. Students can discuss problems with one another in general terms, but must work independently or within their teams as specified for each assignment. This also applies to online and printed resources: you may consult them as references (as long as you cite them), but the words and source code you turn in must be yours alone. The University's policies on academic dishonesty are set forth in the student code of conduct here. |
Instructions/Resources
| Robot |
Yes, our robot platform is a Roomba. Except it can't clean.
|
| Operating system |
Working backwards from the ROS requirements there are 3 options for your laptop...
|
| ROS2 |
We are using ROS2, to be exact, and the Humble Hawksbill version. My laptop and the Raspberry Pi's on the robots are running Ubuntu, so you will have your best support for this option. I have personally tried installing ROS2 Humble on Windows and it seems to be fine, so I at least have the ability to test things in this environment. I have no access to a Mac and therefore no experience and no ability to help troubleshoot issues there. A lot of public sample code and tutorials are available in both C++ and Python, but expect mostly C++ examples from me. I am agnostic about which of these two languages you use for homeworks and projects, but you will get your best support from me in C++.
|
| Readings |
|
| Gazebo |
This is a 3-D robot simulator |
Schedule
Note: The blue squares in the "#" column below indicate Wednesdays.
| # | Date | Topic | Notes | Readings/links | Assignments/slides |
|---|---|---|---|---|---|
| 1 | Feb. 8 | Introduction | Background, course information | slides | |
| 2 | Feb. 10 | hello robot, hello ROS | ROS basics, Create ROS interface | Creating & building ROS2 packages, ROS2 nodes, ROS2 topics, Create 3 topics |
slides HW #1 |
| 3 | Feb. 15 | Kinematics/Dynamics | Degrees of freedom, configuration space; wheeled systems (unicycle/car vs. differential drive) | MR Chap. 2, PA Chap. 13.1.2 | |
| 4 | Feb. 17 | Kinematics/Dynamics | URDFs, ROS rviz2 and tf2, odometry | rviz2 user manual (Turtlebot3), Introduction to tf2, MR Chap. 13.4 | slides HW #1 due |
| 5 | Feb. 22 | More ROS + Controllers | ROS 2 workspaces and packages, subscribing and publishing, and timer callbacks; basic feedback controller concepts | FS Chap. 1 | slides HW #2 |
| 6 | Feb. 24 | Controllers | Waypoint following, line following, trajectory and wall following (pure pursuit) | RVC Chap. 4-4.1.2 | slides |
| 7 | Mar. 1 | HW #2 | Coding time | Starter code for Python wanderer | |
| 8 | Mar. 3 | Costmaps and discrete motion planning | Connecting to the lidar sensor; representing the environment as a map and basic planning | rplidar_ros; MR Chap. 10.4, Abbeel slides (skip SLAM, reflection maps) |
slides |
| 9 | Mar. 8 | Estimation | Least-squares line-fitting and outlier rejection with RANSAC for lidar scans |
Scikit-learn ordinary least-squares and RANSAC | slides HW #2 due |
| 10 | Mar. 10 | Localization | Particle filters, MCL | Thrun particle filtering slides | slides HW #3 |
| 11 | Mar. 15 | HW #3 | Coding time | ||
| 12 | Mar. 17 | HW #3 | Quiz then coding time | Quiz #1 | |
| 13 | Mar. 22 | SLAM | ROS slam_toolbox package | slam_toolbox Github, Thrun FastSLAM slides | slides |
| 14 | Mar. 24 | HW #3 | HW #3 due | ||
| Mar. 29 | NO CLASS Spring break |
||||
| Mar. 31 | NO CLASS Spring break |
||||
| Apr. 5 | NO CLASS Instructor away |
||||
| 15 | Apr. 7 | Computer vision | Connecting to the RGB-D camera | realsense-ros Github, basic OpenCV color processing | HW #4 / #5 |
| 16 | Apr. 12 | Computer vision | Line finding | Hough lines | slides |
| 17 | Apr. 14 | Computer vision | Tags/fiducials | AprilTag Github, apriltag_ros | slides |
| 18 | Apr. 19 | HW #4 | |||
| 19 | Apr. 21 | HW #4 | HW #4 due | ||
| 20 | Apr. 26 | HW #5 | |||
| 21 | Apr. 28 | 3-D point cloud processing | Obstacles as fitted ground plane outliers; ROS perception_pcl package | perception_pcl | slides HW #5 due |
| 22 | May 3 | Computer vision | Off-the-shelf object detectors | ROS2 wrapper around YOLOv5 (not tested) | HW #6 |
| 23 | May 5 | Computer vision | Training your own object detector | Training YOLOv5 on custom data | |
| 24 | May 10 | Learning | Dynamical tasks, reinforcement learning | Gymnasium Github | Quiz #2 |
| 25 | May 12 | FULL PERIOD FOR DEMOS/COMPETITION | HW #6 due | ||
| NO FINAL EXAM |
