Hello Teams,
we’ve done a lot of admin tasks during the time since the ROS Test. This topic is a summary of all the updates.
First of all, results of the ROS test: erc2025/phase_2/ros_test_results.md at main · husarion/erc2025 · GitHub - congrats! This test was meant to be difficult and you’ve aced it!
Secondly, we’ve updated the Social Excellence points on the repository. There were first points in the sub-category other than “Community Forum” so we’ve added a column there.
Current statistics:
| Team | Qualification | Connectivity Test | ROS Test | Jury | Social Excelence | Total |
|---|---|---|---|---|---|---|
| IITB Mars Rover Team | 38 | 20 | 32 | 5 | 33 | 128 |
| Sapienza Technology Team | 41 | 20 | 39 | 4 | 20 | 124 |
| CRISS Robotics | 37 | 20 | 29 | 15 | 20 | 121 |
| SHUNYA | 39 | 20 | 45 | 7 | 10 | 121 |
| NSpace | 31 | 20 | 27 | 5 | 3 | 86 |
| TerraBots | 32 | 20 | 23 | 10 | 0 | 85 |
| Mind Cloud | 32 | 16 | 4 | 0 | 20 | 72 |
| Team Interplanetar - BUET Mars Rover Team | 25 | 20 | 19 | 5 | 0 | 69 |
| Team Robocon IITR | 31 | 20 | 13 | 3 | 0 | 67 |
| DJS Antariksh | 31 | 20 | 9 | 5 | 0 | 65 |
| PSG Team Aurora | 32 | 18 | 3 | 8 | 0 | 61 |
| Makercie | 33 | 20 | 0 | 3 | 0 | 56 |
| RIVAL | 19 | 20 | 10 | 5 | 0 | 54 |
| ARES | 29 | 20 | 0 | 5 | 0 | 54 |
| PUTLunarTeam | 23 | 20 | 0 | 3 | 5 | 51 |
| Amogh | 28 | 20 | 0 | 2 | 0 | 50 |
| Team Inferno DTU | 37 | 8 | 3 | 2 | 0 | 50 |
| ProjectRed | 20 | 20 | 0 | 5 | 0 | 45 |
| Team Horizon | 23 | 4 | 9 | 2 | 0 | 38 |
| CSA ROBOTICS | 31 | 0 | 0 | 0 | 0 | 31 |
Next, Payload Test Announcement is here: erc2025/phase_3/payload_test_announcement.md at main · husarion/erc2025 · GitHub. Have in mind that this time only 10 Teams are invited for a Test Drive. Also, have in mind that we do consider all points for the qualifications - so things like Social Excellence and others do matter. Please re-check the timezone calculations.
When it comes to the Payload Test, a couple of remarks/suggestions based on the experience from the previous Tests:
- have in mind that at the beginning of your Time Slot we’re enabling additional network connection - this usually requires you to restart DDS (
ros2 daemon stop,ros2 daemon start) in order to pick up changes - for the Panther-VM communication you need to use Cyclone DDS. All other steps of the communication are up to you
- if you need changes to the VMs that you don’t have permissions to - please open a Pull Request in this repository - see
ansibledirectory - we’ve started a pattern where if there’s a config that you may need for reference (i.e. in case you do some changes to the actual file) - you’ll find it with a
.referenceextension - we will be updating RAM allocation for your machines soon - there may be a hard reboot required
- when it comes to the remote desktop solutions - you’ll need to test them, and adjust them to your particular networking conditions - some will work better with higher latency connections and some will work better with low bandwidth connections. X11 forwarding is enabled on all machines. We suggest trying (random order): VNC, nomachine, Moonlight, ones from here Images by Category - LinuxServer.io, etc. Feel free to post your experiences on the Forum
Ros2router image - the version available during the ROS Test was incompatible with Husarnet nightly installed on VMs. This was an issue we’ve not anticipated somehow (stable versions did work together but Husarnet was newer than the ros2router image, which didn’t have any nightly branch at all). We’ve updated the latest version of ros2router to support both nightly and stable Husarnet versions at the same time.
One extra activity that we have not initially planned, but will do is… remote access to Panther in between Tests. This access won’t be realized on a Competition-grade connection and it’s meant mostly to resolve config issues but judging from the ROS test - should be helpful either way. You can reserve your time slots here: https://calendar.app.google/gmk7YWA7Bz1TqYBH6 Have in mind though, that the access is given and taken manually and on a “best effort” QoS - so do expect some delays and so on. All points from the previous paragraph still stand - like restarting the DDS at the begining of the slot and so on. Please have in mind, that the camera config will most likely change in a couple of days - we’ve faced some technical issues with these (this was the reason for the delay during the ROS test) and will be replacing them - along with TF and calibration data. Have also in mind that during the weekends there most likely won’t be any movement on lidar. Also - please be mindful of other Teams and try to have at most 1 future slot reserved at any given time.
Finally, we’d like to ask you a question. We have an option for making the Payload Test either indoors (like the last time) or outdoor. The outdoor environment won’t be comparable with the Marsyard but there will be a better chance of getting bumps in the terrain, testing the flip-over prevention and so on. Please let us know if those are things that you’d benefit from - as it’d require more effort from us to organize access to such environment.
–
Thank you all for the engagement
Paweł on behalf of Husarion Team