[AWSIM + automatic goal panel] /planning/scenario_planning/trajectory topic is timeout

[bl-24]

Checklist

• [X] I've read the contribution guidelines.
• [X] I've searched other issues and no duplicate issues were found.
• [X] I'm convinced that this is not my fault but a bug.

Description

I am testing the Autoware with automatic goal panel. it has good function but I face some bugs in long run mode. example: when I choose 5 goals and try to loop them. after some diverse loops (sometimes 4 sometime 8 loops or more!!) the vehicle does not move anymore. the bash massage in this state is like: [topic_state_monitor_node-15] [WARN] [1725012554.120036877] [system.topic_state_monitor_scenario_planning_trajectory]: /planning/scenario_planning/trajectory topic is timeout. Set ERROR in diagnostics. [component_container_mt-78] [INFO] [1725012554.162544451] [control.vehicle_cmd_gate]: The operation mode is changed, but the TurnIndicatorsCommand is not received yet:

Expected behavior

it should run like previous loops reach at goal and go to the next goal

Actual behavior

[topic_state_monitor_node-15] [WARN] [1725012554.120036877] [system.topic_state_monitor_scenario_planning_trajectory]: /planning/scenario_planning/trajectory topic is timeout. Set ERROR in diagnostics. [component_container_mt-78] [INFO] [1725012554.162544451] [control.vehicle_cmd_gate]: The operation mode is changed, but the TurnIndicatorsCommand is not received yet:

Steps to reproduce

1. add AutowareAutomaticGoalPanel
2. select some goals like 5 goals
3. choose loop list
4. select send goal automaticly
5. wait to vehicle face the blocking bug after some loops (in some cases it may take time more than 18 loops!)

Versions

No response

Possible causes

No response

Additional context

can you guide me what can be the reason of this bug and how we can fix it?

[maxime-clem]

[system.topic_state_monitor_scenario_planning_trajectory]: /planning/scenario_planning/trajectory topic is timeout. Set ERROR in diagnostics.

The above issue is what is probably preventing the vehicle from moving. The message means that the trajectory is no longer being published, which could be caused by a crash or a bug in some planning node.

If possible please share the full log which can be found in $HOME/.ros/log/{DATE}-{USER}-{...}/. Otherwise I can try reproducing the issue next week. Please also indicate which version of Autoware you are using.

[bl-24]

component_container_mt_156383_1725011121629.log you can find the last run log in attachment. about version I'm not sure how can I find correctly the version. I just know that it is last released of previous week.

[maxime-clem]

component_container_mt_156383_1725011121629.log you can find the last run log in attachment.

Thank you but this is only the log for a single component. Please share the launch.log found in a folder with the format {DATE}-{USER} (e.g., $HOME/.ros/log/2024-08-30-20-32-39-537351-mclement-10969).

I just know that it is last released of previous week.

This should be enough thank you. I will know to use a recent version to try to reproduce the issue.

[bl-24]

launch.log sorry for miss understanding. this one is the launch.log when error happened.

[maxime-clem]

Thank you but this is the log from a run where you did not set any goal. Please share a log which contains the error you reported.

[system.topic_state_monitor_scenario_planning_trajectory]: /planning/scenario_planning/trajectory topic is timeout. Set ERROR in diagnostics.

[bl-24]

launch.log let me make it clear again. I run it again and this error happened again (this time at first loop!) this error does not happen in any specific area of the map It happened to me in different situations.

[maxime-clem]

The log file is still not good. It only contains messages from control.vehicle_cmd_gate which are not helpful. I renamed the issue to make it more clear what is the problem and hopefully someone else with the same issue can share some more information.