From 895fd96d1eb0ce7e83fcae9e3ba604322827ee4f Mon Sep 17 00:00:00 2001 From: Ahmed Ebrahim Date: Fri, 22 Dec 2023 18:28:38 +0200 Subject: [PATCH] fix(log-messages): proposing solution for waning message "diagnostic_updater: No HW_ID was set..." Signed-off-by: AhmedEbrahim --- .../control/control_validator/control_validator.param.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/autoware_launch/config/control/control_validator/control_validator.param.yaml b/autoware_launch/config/control/control_validator/control_validator.param.yaml index c51cbafba2..ffd259e5e5 100644 --- a/autoware_launch/config/control/control_validator/control_validator.param.yaml +++ b/autoware_launch/config/control/control_validator/control_validator.param.yaml @@ -1,8 +1,6 @@ /**: ros__parameters: - publish_diag: false # if true, diagnostic msg is published - # If the number of consecutive invalid predicted_path exceeds this threshold, the Diag will be set to ERROR. # (For example, threshold = 1 means, even if the predicted_path is invalid, Diag will not be ERROR if # the next predicted_path is valid.)