How can I view the record file which only including the trafficlight info
Closed this issue · 3 comments
System information
- OS Platform and Distribution (e.g., Linux Ubuntu 18.04):18.04
- Apollo installed from (source or binary):source
- Apollo version (3.5, 5.0, 5.5, 6.0):5.0
- Output of
apollo.sh config
if onmaster
branch:
Steps to reproduce the issue:
- Running Apollo5.0 and LGSVL simulator 202006
- Using "cyber_recorder record -o data/bag/xxxx.record -c /apollo/perception/traffic_light" get the traffic lights information
I only want to know the traffic lights detection result per frame. And the cyber_monitor can not show it. What I want to know is if
there are other ways to view the xxxx.record file?
Supporting materials (screenshots, command lines, code/script snippets):
You can follow the "modules/tools/record_parse_save" to export the data. You need to create a new script to export apollo::perception::TrafficLightDetection
@daohu527 thank your reply. According to your method I got the traffic light info.
In addition, I have three more questions. Looking forward to your answer.
- Dose the cyber recorder records the message frame by frame?
After investigation, I know that apollo uses camera pictures to detect traffic lights(Am I right?). So I try to check the traffic light detection result by the image info. But I found that the message numbers are different between traffic light and camera.
- In the traffic light channel, I found "timestamp_sec" and "camera_timestamp", I think that the "camera_timestamp" correspond to the "timestamp_sec" in the camera channel.
But when parse the camera info, it uses the "measurement_time" in the script code. Otherwise, the accuracy of "timestamp_sec" and "measurement_time" are not the same. What is the "measurement_time"?
What I want to know is that how can I pick the right camera picture?
- I found that the 4 traffic lights result are all the same in the record file.
But the detection results are not the same when running the detection. Is it correct?
Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.