From 12f641dbd704dafd476b7ad27ec998c9fad9ba72 Mon Sep 17 00:00:00 2001 From: Ahmed Ebrahim Date: Tue, 12 Mar 2024 14:32:08 +0200 Subject: [PATCH] docs(log-messages): fixing review comments Signed-off-by: Ahmed Ebrahim --- .../ad-hoc-simulation/rosbag-replay-simulation.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/tutorials/ad-hoc-simulation/rosbag-replay-simulation.md b/docs/tutorials/ad-hoc-simulation/rosbag-replay-simulation.md index 33d2c675a8d..399ff87afdb 100644 --- a/docs/tutorials/ad-hoc-simulation/rosbag-replay-simulation.md +++ b/docs/tutorials/ad-hoc-simulation/rosbag-replay-simulation.md @@ -62,7 +62,9 @@ ![after-autoware-launch](images/rosbag-replay/after-autoware-launch.png) - > ⚠️ It might happen that you see in the terminal some error and warning messages before playing the rosbag (next step) unit you play the rosbag and proper initialization occurs +!!! warning + + You might encounter error and warning messages in the terminal before playing the `rosbag`. This is normal behavior. These should cease once the `rosbag` is played and proper initialization takes place 2. Play the sample rosbag file. @@ -71,7 +73,9 @@ ros2 bag play ~/autoware_map/sample-rosbag/sample.db3 -r 0.2 -s sqlite3 ``` - > ⚠️ As the timestamp in the rosbag is different than the current timestamp in your system , Autoware will output in to the terminal some warning messages due to this timestamp mismatch +!!! warning + + Due to the discrepancy between the timestamp in the `rosbag` and the current system timestamp, Autoware may generate warning messages in the terminal alerting to this mismatch. This is normal behavior. ![after-rosbag-play](images/rosbag-replay/after-rosbag-play.png)