Conversation
harishkumarbalaji
commented
Apr 23, 2025
- Dockerize the GEMStack
- Add Gem Gazebo interface to connect to the Gazebo simulator
- Add passenger comfort metrics analysis script
- Add a parameter to launch the main.py with the vehicle model to run the corresponding vehicle
Fix setup issues and add support for CUDA 12 users
…ncies Update missing dependencies for GEMstack
Infra b - Fix setup machine script
krishauser
left a comment
There was a problem hiding this comment.
Please clean up contributions
There was a problem hiding this comment.
Should not include homework files
There was a problem hiding this comment.
We are using few of the homework files to test the simulation metrics and performance.
We will review and make the necessary changes.
There was a problem hiding this comment.
Move calibration transforms to separate files and !include them. Is it necessary to have separate calibration files for the simulation vehicles? Wouldn’t it be better for those to match the actual vehicles?
There was a problem hiding this comment.
We are working on closing the Sim to Real Gap.
Could you let us know if these needs to be fixed before the merge or keep it separate for now and then merge in next request?
The other teams can ignore the gazebo yaml files and make changes to the hardware related e2 and e4 vehicle yaml files, the simulation team will review the changes make integrate accordingly.
There was a problem hiding this comment.
By using the same calibration files there should be zero gap.
There was a problem hiding this comment.
This request has been completed and yaml files have been reverted.
There was a problem hiding this comment.
This is quite a kludge. It would be better to change main.py to accept a config file name.
There was a problem hiding this comment.
Just to be clear on this change.
You want us to get the file path of the yaml file from system arguments and pass it to
init.py from main.py ?
Moving forward with the above may involve tinkering with GEMstack/utils/settings.py and config.py.
Would changes made to those files acceptable or do you recommend just changing main.py and current.yaml ?
There was a problem hiding this comment.
You shouldn’t need to mess with config.py. Just letting settings.py override the defaults would be sufficient.
There was a problem hiding this comment.
This request is completed.
There was a problem hiding this comment.
Is this part of the simulation contribution? Suggest removing it
There was a problem hiding this comment.
This change will be reverted.
There was a problem hiding this comment.
This request has been completed and yaml files have been reverted.
There was a problem hiding this comment.
Again, is there any reason to have separate simulation vehicle configurations rather than just using the overall one?
There was a problem hiding this comment.
We are working on closing the Sim to Real Gap.
The controller performance in simulation is quite close to real now, after a bit more testing we will be converting it to a single yaml file.
We are still working on closing the gap on transformation matrix.
There was a problem hiding this comment.
This request has been completed and yaml files have been reverted.
There was a problem hiding this comment.
Is this file necessary? Is it wahat the perception team wants?
There was a problem hiding this comment.
This file will be used to showcase object detection using simulation with the base yolo model.
Could we rename the file to represent test code?
There was a problem hiding this comment.
Yes, please rename to be more specific.
There was a problem hiding this comment.
This request is completed.
There was a problem hiding this comment.
Is this compatible with what the SW infra team wants?
There was a problem hiding this comment.
This is also part of homework done by SW infra team. We have included this to test performance of agent state in simulation.
Please let us know if we could rename this to test code and merge to s2025 or remove it.
There was a problem hiding this comment.
This request is completed.
There was a problem hiding this comment.
This file is done as part of SW Infra Team Homework to plot more info on controller cross track error and vehicle's acceleration and the trajectory that the vehicle has taken. We can remove it if you think it is related to HW and dont need in S2025 branch.
There was a problem hiding this comment.
This request is completed.
launch/perception.yaml
Outdated
There was a problem hiding this comment.
This file will be removed
There was a problem hiding this comment.
This request is completed.
testing/test_comfort_metrics.py
Outdated
There was a problem hiding this comment.
This file is done as part of SW Infra Team Homework to plot more info on controller cross track error and vehicle's acceleration and the trajectory that the vehicle has taken. We can remove it if you think it is related to HW and dont need in S2025 branch.
There was a problem hiding this comment.
Suggest to remove it for now, let’s ask the control team to commit any comfort test scripts they are using
There was a problem hiding this comment.
This request is completed.
…mu condition in subscribe_sensor
S2025 -> Simulation
S2025 simulation
There was a problem hiding this comment.
This file has been added back
Revert yaml files
Subscribe to gnss topic from gazebo simulation
Removed yaml changes
|
|
LGTM |

