Open yashwant-d opened 2 years ago
After commenting all the non-CPU related code blocks after this line as well as un-commenting all the CPU related code in the plot function, I was able to generate the benchmark data for CPU only.
However, I am still struggling with the streamline case.
After examining the code a little it is found that even after giving the converted data to the file, which is further given to this msgsets_from_trace_concurrent it generates an empty list for the streamlined case. But, when I uncomment this msgsets_from_trace_start_end_streamlined, and update the previously mentioned function in this line also comment out the non-CPU/non-Streamlined related code after the line 1111. I am able to see the list generating out of msgsets_from_trace_start_end_streamlined, But most of the values are zeros. Further, when the code implementation reaches this line it gives the following error:
[ERROR] [launch]: Caught exception in launch (see debug for traceback): Caught exception when trying to load file of format [py]: list index out of range
PS: I and @yashwant-d are working together on this.
Hi @vmayoral,
I am trying to reproduce ROS Perception benchmarking data which is published on KRS Documentation i.e. this with KRS 1.0.
I ran CPU Only ROS Perception application which produced following trace data:
After this I launched the analysis launch file: https://github.com/ros-acceleration/acceleration_examples/blob/main/graphs/perception/perception_2nodes/launch/analyse_rectify_resize.launch.py
while keeping only image_pipeline_msg_sets_ms_cpu I have commenting out subsequent message_sets* as we didn't have trace data for gpu, fpga and other scenarios.
After launching the modified launch file, following errors are observed:
As per trace_tools architecture doc , there is a conversion required which generateds data model from tracedata i.e. converted file. if we run the launch file by passing converted file path, this leads to below error:
Can you please help in understanding what might be missing? Also can you share any example tracedata on which this analyze launch file works well? this would be helpful in comparison and narrowing down the issue.