Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure of recording a scenario simulation #1179

Closed
lethal233 opened this issue Jan 26, 2024 · 3 comments
Closed

Failure of recording a scenario simulation #1179

lethal233 opened this issue Jan 26, 2024 · 3 comments
Assignees

Comments

@lethal233
Copy link

Describe the bug
A clear and concise description of what the bug is.

The scenario simulator cannot perform normally when I set the record to true, which means:

  1. it cannot do the scenario test simulation
  2. it cannot record the simulation.

To Reproduce
Steps to reproduce the behavior:

  1. Run the scenario test simulation with the command ros2 launch scenario_test_runner scenario_test_runner.launch.py architecture_type:=awf/universe record:=false scenario:='t4v2.yml' sensor_model:=sample_sensor_kit vehicle_model:=sample_vehicle
  2. The scenario is simulated and played on the rviz.
  3. Run the scenario test simulation again with the command ros2 launch scenario_test_runner scenario_test_runner.launch.py architecture_type:=awf/universe record:=true scenario:='t4v2.yml' sensor_model:=sample_sensor_kit vehicle_model:=sample_vehicle
  4. Rviz is successfully started, but the scenario is not simulated, along with console error output.

Expected behavior

The scenario test simulator should run the scenario normally and record the whole simulation messages.

Screenshots

image

Desktop (please complete the following information):

  • OS: Ubuntu 22.04
  • ROS 2 version: humble

The file is attached here: https://drive.google.com/file/d/1LDSyvA9PUEf58OzcS4sJ-3XLTVgAnOPJ/view?usp=drive_link

@hakuturu583
Copy link
Collaborator

As we infer from the error text, it is probably an error in the DDS communication process.
It may be cured by reviewing the DDS communication settings, etc.

@hakuturu583 hakuturu583 self-assigned this Jan 30, 2024
@lethal233
Copy link
Author

Got it, I will try to inspect the DDS settings first.

@lethal233
Copy link
Author

lethal233 commented Jan 30, 2024

@hakuturu583 Thanks, I think I have resolved this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants