scenario_simulator_v2: The position of kinematic_state topic is not updated
Describe the bug When I run the scenario simulator, the position of the ego stays in the initial position:
https://github.com/tier4/scenario_simulator_v2/assets/45468306/31b1f26f-2248-4840-ae32-a03680ba65a3
As you can see in the video, although the velocity is increasing, the ego stays in the same position.
When I checked the /localization/kinematic_state, the velocity message was changing but the position info stayed the same value.
I also run Autoware without scenario_simulator, I didn’t see this problem.
To Reproduce Steps to reproduce the behavior:
- Run scenario simulator
Expected behavior The position of the ego should be updated.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- Ubuntu Version: 22.04
- ROS 2 version: Humble
- DDS: cyclonedds
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 24 (9 by maintainers)
@kyoichi-sugahara @MertClk I was having similar issues, and confirmed that with Mert’s solution,the problem is solved.
I have tested it for now using multiple scenarios and I can confirm that the mentioned problem is no longer occurring after applying the proposed change.
FYI, I am using latest autoware repos and added this change on top of scenario simulator branch
RJD-736/autoware_msgs_supportThanks a lot @MertClk 👏
@brkay54 @ahmeddesokyebrahim @beyzanurkaya I created an issue to fix the bug. I’ll create the PR soon.
https://github.com/tier4/scenario_simulator_v2/issues/1312
@brkay54
So sorry I mised your mention 🙇 I will try to reproduce the issue tomorrow. cc: @ahmeddesokyebrahim
I faced the same problem and solved in the PR and this is caused by the change which is merged last Friday. So my pr is not the solution for this kinemtic_state issue I guess.
Sorry for waiting long time. This problem was fixed in master branch.
Thank you very much.
@kyoichi-sugahara I had this issue on my local as well and debugged it. I realized that accessing the elements of the matrix was problematic. They were 0 when you try to reach 1-by-1 however it was correct when you try to print the object. After this step, I started to review Eigen documentation and saw the warning related to the usage of “auto”. Considering that, I changed the type of the variable.
I apologize for not being able to assist with analyzing the cause 🙇 @MertClk For future troubleshooting and development reference, I’d like to know: How did you notice this error? I want to know how to identify the cause when I suspect something might be the reason.
@ahmeddesokyebrahim
I’m following source installtion step 🤔
I can’t debug this because I can’t reproduce the problem sorry for this 🙏 But you guys are having same issue, it’s strange… From my side, I will wait for other people’s report to this issue…