Open SijmenHuizenga opened 4 years ago
Observations:
Did not investigate the nature of the problem further than to check that lidar messages come at a good rate and seem to be different, judging by the number of points in every message. When I find some time for it after exams and stuff (certainly not within the next 40 days) and we set up a simulator again, I might try to look into it further.
BTW nice to see activity here even after the event :)
This issue may improve its performance: https://github.com/microsoft/AirSim/pull/4505
Looks great, currently it's not in an official version of Airsim yet, let's wait until it is merged and an official version is released. Changing the airsim version however is not easy, as it has been heavily cut down and modified from the original repo, but I will open a draft PR as soon as it is merged so I can start to work on getting this improvement into the sim.
There was also an issue for the camera performance microsoft/airsim#4101, this one has not progressed as much though.
The PR microsoft/Airsim#4505 has been merged in the Colosseum fork. I'll try and start a draft pull request to update the simulator to the newest version of Airsim (aka Colosseum).
Apparently raycasting simulations can do 600,000 points per second. This simulator can only do 100,000 points per second. Does anyone have an idea on how we can improve lidar performance?
Currently lidar is using unreal's LineTraceSingleByChannel. Here is the code for the lidar sensor in unreal.