There will be additional laboratory time in Week 6 on Thursday 23.10.2025 for both labs.
We plan to have the following arrangement:
I will send an email to each group with more details.
The report submission is now enabled.
You can submit via WebCMS (go to the submission tab for Assignments / Project (Stage 1)) or you can use the give command in VLAB:
give cs3431 Report1 <your file>.pdf
Good luck!
We will be enabling the report submission later today. We'll send out another announcement.
Officially, the reports are due 11:59pm Friday, but we won't start marking until next week, so we won't impose any late penalties until next week.
To give you more time, for the week 5 demonstration, we will mainly be marking the wall follower. If you can't get the marker recognition working by then, don't worry, you can try again in week 7.
Please note that you will have to run cartographer with the wall follower since we want to see how good your map is and how smooth is your path. Sometimes jerky movements can tear the map.
It's important that your wall follower does not hit the coloured markers, so even if you aren't doing the marker recognition yet, we will still have the markers in the maze. So try not to hit them.
Next week (week 4) we'll miss the Monday lecture and lab. The lecture slides will be put up on WebCMS anyway and I'll cover them in week 5, but you should look at them before then as they will help with knowing how to place the markers in the map correctly.
For the lab, we'll have extra time in the Design Studio on Tuesday 2pm, we'll see how many students can make it then.
There's a new version of see_marker.py here .
This adds another another way of finding the distance to the marker, assuming you know the focal length of the camera.
In today's lecture I incorrectly said that the arguments to update_cmd_vel were the speeds of the left and right motors. The argument names in the code are correct, they are the linear and angular speeds. e.g.
update_cmd_vel(0.2, 1.5) means drive with a linear speed of 0.2 and turn left (rotate with an angular rate 1.5 anti-clockwise)
update_cmd_vel(0.3, -1.5) means drive with a linear speed of 0.3 and turn right (rotate with an angular rate 1.5 clockwise)
update_cmd_vel(-0.2, 0.0) means drive backwards with a linear speed of 0.2.
To do the course assignments, you will have to connect your laptop to the TurtleBot3 that we assign to your group. This year we will be using UNSW's new IoT WiFi VLAN. This is a subnet especially for our class. We will need the MAC address of your laptop to register and authorise you to access the network. Please fill in this form as soon as you can. We will go through this in the lab session too.
Zijie made a few tweaks in the UTM image to better align with the name conventions in the course slides and materials, also with the intel image. You can find it
here.
We will update WebCMS soon.
If you decide to use the one earlier, make sure you uncomment the line after to ensure the path for pkgs such as turtlebot3_nav, turtlebot3_cartagrapher being added properly.
In the new UTM image, the code you need for your assessment 1 is in ~/turtlebot3_ws. You shouldn't need to change the code in ~/turtlebot3_source_ws, as they are just the public TurtleBot3 pkgs which you can "call" but do not need to modify. You may need to refer to some files in it during your "research" phase later on for assessment2.
Here are the configs for UTM (do not use 10GB of memory if you only have 8).
In this link,
https://github.com/utmapp/UTM/issues/2682#issuecomment-1064827650
. there are debug tips&hacks to deal with the UTM VM stucks at bootup. You may find that your VM hangs less frequently if the laptop is plugged into the power source.