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

OpenSCENARIO: order of entities causes scenario_runner to crash #1126

Open
vollkornholztuer opened this issue Nov 5, 2024 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@vollkornholztuer
Copy link

vollkornholztuer commented Nov 5, 2024

Describe the bug
This a situation, where i found two bugs, which correlate for some unknown reason. Please let me know, if i have to create seperate issues for these bugs with cross references. Although the one that crashes the simulation is more severe.

About the bugs: Depending on the order of the declared cars in OpenSCENARIO, when executing the file with Scenario-Runner, may crash or not.

To be exact:

On one hand, if i declare new_car first inside of <Entities> (see .xosc-file inside of [...]_broken1.zip), the simulation runs but with the side effect, where the properties of Ego and new_car are mixed up. This means, both cars have the color of new_car and when despawning new_car, it instead despawns Ego. I can't explain that behaviour.

On the other hand, if i declare new_car anywhere else but as the first car, the simulation tries to run as intended (which can be seen from the Ego vehicle color), but crashes instantly after spawning the cars Ego and Target. See the screenshots for the error message inside of the terminal.

The interesting part is, that the .xosc-files are identical, except for the declaration order of the entities.

To Reproduce
Execute both attached .xosc-files inside of the zip-folders, which can be found under "Additional context".

Expected behavior
Both simulations should be able to run independently, either without mixing up the properties of the car, or without crashing the simulation.

Screenshots
The terminal output of [...]_broken1.xosc (broken car properties):
Terminal Output spawnDespawn_test_broken1 (copy)

The terminal output of [...]_broken2.xosc (simulation crashes):
Terminal Output spawnDespawn_test_broken2 (copy)

Desktop (please complete the following information):

  • OS: Ubuntu 22.04 LTS
  • CARLA Version: CARLA 0.9.15
  • Python version: 3.10
  • Version: 0.9.15

Additional context
File which doesn't crash the simulation: spawnDespawn_test_broken1.zip
Video of the execution: Screencast spawnDespawn_test_broken1.webm

File which crashes the simulation: spawnDespawn_test_broken2.zip
Video of the execution: Screencast spawnDespawn_test_broken2.webm

@vollkornholztuer vollkornholztuer added the bug Something isn't working label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants