Get the App
SLTechnology News&Howtos  ›  Internet Technology  › 

How to open demo_3.5.record and read topic

Shulou Source: shulou.com Published: 2022-06-01 10:01:08 09月30日 Update

How to open demo_3.5.record read topic, I believe many inexperienced people are helpless about this, this article summarizes the causes and solutions of the problem, through this article I hope you can solve this problem.

Q: How to complete rostopic echo-b. bag-p/topic_name > .txt

A: Use cyber_channel echo /channel_name

Example Play record file\[caros@in-dev-docker:/apollo\]$ cyber\_record play -lf data/record/demo\_3.5.recordfile: data/record/demo\_3.5.record, chunk\_number: 3, begin\_time: 15468837738834894 (2019-01-08-03:12:57), end\_time: 1546888422886740928 (2019-01-08-03:13:42), message_number: 61615earliest\_begin\_time: 1546888377338834894, latest\_end\_time: 1546888422886740928, total\_msg\_num: 61615Please wait 3 second(s) for loading... Hit Ctrl+C to stop, Space to pause, or 's' to step.\ [RUNNING\] Record Time: 1546888377.433 Progress: 0.094 / 45.... Display channel list [caros@in-dev-docker:/apollo]$ cyber_channel listThe number of channels is: 32/apollo/canbus/chassis/apollo/canbus/chassis_detail/apollo/control/apollo/control/pad/apollo/drive_event/apollo/guardian/apollo/hmi/audio_capture/apollo/hmi/status/apollo/localization/msf_gnss/apollo/localization/msf_lidar/apollo/localization/msf_status/apollo/localization/pose/apollo/monitor/apollo/monitor/system_status/apollo/navigation/apollo/perception/obstacles/apollo/perception/traffic_light/apollo/planning/apollo/prediction/apollo/routing_request/apollo/routing_response/apollo/sensor/gnss/best_pose/apollo/sensor/gnss/corrected_imu/apollo/sensor/@ nss/gnss_status/apollo/sensor/gnss/imu/apollo/sensor/gnss/ins_stat/apollo/sensor/gnss/odometry/apollo/sensor/gnss/raw_data/apollo/sensor/gnss/rtk_eph/apollo/sensor/gnss/rtk_obs/tf/tf_static Display channel contents [caros@in-dev-docker:/apollo]$ cyber_channel echo /apollo/sensor/gnss/best_poseheader { timestamp_sec: 1545095763.0131655 module_name: "gnss" sequence_num: 3073}measurement_time: 1229130981sol_status: SOL_COMPUTEDsol_type: NARROW_INTlatitude: 37.415249592584814longitude: -122.00875424407722height_msl: 1.23227334395051undulation: -32.1datum_id: WGS84latitude_std_dev: 0.0124039669longitude_std_dev: 0.0176792257height_std_dev: 0.041889634base_station_id: "0"differential_age: 1solution_age: 0num_sats_tracked: 11num_sats_in_solution: 9num_sats_l1: 9num_sats_multi: 8extended_solution_status: 33galileo_beidou_used_mask: 0gps_glonass_used_mask: 51header { timestamp_sec: 1545095764.0130444 module_name: "gnss" sequence_num: 3074}measurement_time: 1229130982sol_status: SOL_COMPUTEDsol_type: NARROW_INTlatitude: 37.415306110750976longitude: -122.0087373614388height_msl: 1.2385389469563961undulation: -32.1datum_id: WGS84latitude_std_dev: 0.0123673109longitude_std_dev: 0.0177532453height_std_dev: 0.0420455635base_station_id: "0"differential_age: 1solution_age: 0num_sats_tracked: 10num_sats_in_solution: 8num_sats_l1: 8num_sats_multi: 8extended_solution_status: 33galileo_beidou_used_mask: 0gps_glonass_used_mask: 51header { timestamp_sec: 1545095765.0112305 module_name: "gnss" sequence_num: 3075}measurement_time: 1229130983sol_status: SOL_COMPUTEDsol_type: NARROW_INTlatitude: 37.415352879935718longitude: -122.00872341178777height_msl: 1.2605287469923496undulation:-32.1datum_id: WGS84latitude_std_dev: 0.0151290251longitude_std_dev: 0.020376863height_std_dev: 0.047324948base_station_id: "0"differential_age: 2solution_age: 0num_sats_tracked: 14num_sats_in_solution: 10num_sats_l1: 10num_sats_multi: 9extended_solution_status: 33galileo_beidou_used_mask: 0gps_glonass_used_mask: 51header { timestamp_sec: 1545095766.0121005 module_name: "gnss" sequence_num: 3076}measurement_time: 1229130984sol_status: SOL_COMPUTEDsol_type: NARROW_INTlatitude: 37.415389343576692longitude: -122.00871243535052height_msl: 1.2862052069976926undulation: -32.1datum_id: WGS84latitude_std_dev: 0.0137432581longitude_std_dev: 0.0162601564height_std_dev: 0.0376244374base_station_id: "0"differential_age: 2solution_age: 0num_sats_tracked: 15num_sats_in_solution: 13num_sats_l1: 13num_sats_multi: 11extended_solution_status: 33galileo_beidou_used_mask: 0gps_glonass_used_mask: 51header { timestamp_sec: 1545095767.0116713 module_name: "gnss" sequence_num: 3077}measurement_time: 1229130985sol_status: SOL_COMPUTEDsol_type: NARROW_INTlatitude: 37.415416242281566longitude:-122.00870413589038height_msl: 1.3115372871980071undulation: -32.1datum_id: WGS84latitude_std_dev: 0.0126857655longitude_std_dev: 0.0141515983height_std_dev: 0.0331060551base_station_id: "0"differential_age: 2solution_age: 0num_sats_tracked: 16num_sats_in_solution: 15num_sats_l1: 15num_sats_multi: 12extended_solution_status: 33galileo_beidou_used_mask: 0gps_glonass_used_mask: 51header { timestamp_sec: 1545095768.0136344 module_name: "gnss" sequence_num: 3078}measurement_time: 1229130986sol_status: SOL_COMPUTEDsol_type: NARROW_INTlatitude: 37.415433198552719longitude: -122.0086991019575height_msl: 1.3455344066023827undulation: -32.1datum_id: WGS84latitude_std_dev: 0.00993473455longitude_std_dev: 0.0119242864height_std_dev: 0.0302341301base_station_id: "0"differential_age: 1solution_age: 0num_sats_tracked: 16num_sats_in_solution: 16num_sats_l1: 16num_sats_multi: 13extended_solution_status: 33galileo_beidou_used_mask: 0gps_glonass_used_mask: 51 After reading the above contents, do you know how to open demo_3.5.record to read topic? If you still want to learn more skills or want to know more related content, welcome to pay attention to the industry information channel, thank you for reading!

Tags: Content methods more problems helpless for this examples reasons this skills documents articles experience industry information information channels channels Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Shulou Technology MySQL OPPO Reno Apple NVidia