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

feat(diagnostic_aggregator): add localization_tf_status to /autoware/localization/node_alive_monitoring/tf_status #544

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,12 @@
contains: [": localization_topic_status"]
timeout: 1.0

tf_status:
type: diagnostic_aggregator/GenericAnalyzer
path: tf_status
contains: [": localization_tf_status"]
timeout: 1.0

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I've removed this since we don't use this anymore. There is the pose(vehicle_kinematic_state) topic instead.
What is your motivation for adding it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is your motivation for adding it?

Now, ad_service_state_monitor publishes it, so I'm sure it is used in autoware.

There is the pose(vehicle_kinematic_state) topic instead.

Could you tell me where it is written?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here.

/localization/pose_twist_fusion_filter/pose:
module: "localization"
timeout: 1.0
warn_rate: 5.0
type: "geometry_msgs/msg/PoseStamped"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your information. I confirmed it.
So, as next action, two choices are suggested.

  • delete tf diag since this is not used.
  • merge this PR to check tf. Because tf and topic are different.

Do you have any ideas?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can delete this diag, but before that, I think we should discuss the use case and consider what to check.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got it. I'll make issue to discuss it. I'll change to draft.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

performance_monitoring:
type: diagnostic_aggregator/AnalyzerGroup
path: performance_monitoring
Expand Down