CARMA Analytics is a secure, scalable and cloud agnostic data architecture to enable research analysis on big data sets by defining repeatable and scalable processes for ingesting data, creation of a data repository to fuse, process and perform quality assurance.
Apache License 2.0
3
stars
3
forks
source link
ROS2 trace: Generate plugin specific planManeuever and planTrajectory service latency #84
Fix 1: In https://github.com/usdot-fhwa-stol/tracetools_analysis/pull/1, some errors that prevented from assigning correct owner_info to service have been fixed. Now the script can distinguish services and clients based on their owner despite generating from same base class and having identical service types.
Fix 2: It also stops using line chart as it may conceal cases where there is data missing intermittently during operation as the line just connects between two separated segments. As you can see below, either the vehicle disengaged or something else happened for plugins to not get called for almost 20 seconds twice:
Previous:
The gap is not so clear, which we may miss.
I noticed the gap more from here:
I was creating analysis scripts for controller performance of carma-platform and needed to use ros2 tracing for latency analysis. It turned out the services were not correctly assigned owner info so that the services were not distinguishable between different nodes but from same base class.
How Has This Been Tested?
integration tested with carma-platform live vehicle recorded tracing data
Types of changes
[X] Defect fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that cause existing functionality to change)
Checklist:
[X] I have added any new packages to the sonar-scanner.properties file
[ ] My change requires a change to the documentation.
PR Details
Description
Fix 1: In https://github.com/usdot-fhwa-stol/tracetools_analysis/pull/1, some errors that prevented from assigning correct owner_info to service have been fixed. Now the script can distinguish services and clients based on their owner despite generating from same base class and having identical service types.
Fix 2: It also stops using line chart as it may conceal cases where there is data missing intermittently during operation as the line just connects between two separated segments. As you can see below, either the vehicle disengaged or something else happened for plugins to not get called for almost 20 seconds twice:
Previous: The gap is not so clear, which we may miss.
I noticed the gap more from here:
So changing to Scatter plot:
Different planManeuvers being distinguished:
Related GitHub Issue
NA
Related Jira Key
https://usdot-carma.atlassian.net/browse/ARC-207
Motivation and Context
I was creating analysis scripts for controller performance of carma-platform and needed to use ros2 tracing for latency analysis. It turned out the services were not correctly assigned owner info so that the services were not distinguishable between different nodes but from same base class.
How Has This Been Tested?
integration tested with carma-platform live vehicle recorded tracing data
Types of changes
Checklist: