During debugging or testing, lifecycle logs don't print human-readable transition ids.
Due to this, users of carma-platform don't have context of what stage the carma-platform is unless they are intimately familiar with the ids. For example, transition.id 1 below is hard to understand:
platform_ros2 | [guidance_controller-43] 1726033822.220037748 | INFO | guidance.guidance_controller | wait_on_change_state_future:363 | Transition 1 successfully triggered.
platform_ros2 | [carma_component_container_mt-11] 1726033822.220110111 | WARN | LifecyclePublisher | publish:104 | Trying to publish message on the topic '/localization/localization_status', but the publisher is not activated
platform_ros2 | [carma_component_container_mt-11] 1726033822.320015148 | WARN | LifecyclePublisher | publish:104 | Trying to publish message on the topic '/localization/localization_status', but the publisher is not activated
platform_ros2 | [lifecycle_component_wrapper_mt-7] 1726033822.360261833 | INFO | environment.lanelet2_map_visualization | CarmaLifecycleNode:54 | CarmaLifecycleNode node launched, waiting on state transition requests
platform_ros2 | [lifecycle_component_wrapper_mt-7] 1726033822.361215544 | INFO | environment.lanelet2_map_visualization_container | on_load_node:349 | A lifecycle component has been loaded by the LifecycleComponentWrapper. Attempting to move it to the ACTIVE state.
I added human-readable format so that it is easier for the users to understand what is happening:
PR Details
Description
During debugging or testing, lifecycle logs don't print human-readable transition ids. Due to this, users of carma-platform don't have context of what stage the carma-platform is unless they are intimately familiar with the ids. For example, transition.id 1 below is hard to understand:
I added human-readable format so that it is easier for the users to understand what is happening:
Related GitHub Issue
NA.
Related Jira Key
CAR-6076
Motivation and Context
As people other than carma-platform developers increasingly use the tool such as cdasim developers, it needs to be more user-friendly.
How Has This Been Tested?
local VM integration tested
Types of changes
Checklist: