Using Ouster OS0-128 each scan is captured every 5m and saved as .pcap alongside metadata.json file. Using ouster-sdk 0.16.2 I could easily open_source() for each .pcap file and visualize the road. I have recently switched to ouster-sdk 1.0.1 and I can’t process those files anymore. Each time I receive:
Process finished with exit code -1073741676 (0xC0000094)
Are previously captured .pcap files not compatible with the latest ouster-sdk?
What is a recommended way to load multiple sequential .pcap files? Or would you recommend other approach?
Below there is a minimal code to show the idea:
def frames_w_poses():
for pcap_file in pcap_files:
for frame in open_source(pcap_file, meta=json_files):
yield slam.update(frame)
viz = SimpleViz(
source.sensor_info,
accum_max_num=1000,
accum_min_dist_num=0,
accum_min_dist_meters=4,
rate=1,
on_eof="loop",
)
viz.run(frames_w_poses())
I saw that under Sample Library in Ouster Studio .pcap files are no longer available for download for latest RGB examples.
We still support pcap files .. and I don’t see a reason why a previous pcap wouldn’t work with the latest SDK (we have unit tests to check for that) .. this is likely a bug. Would it be okay to share a minimal pcap file that can generate the problem (you may share here or via the tech support portal).
also I would be curious to know if you can play the pcap file via the cli:
ouster-cli source input.pcap viz
The cli itself, support loading multiple pcap file in sequence as follows:
Sure. I’ve attached a few .pcap files along with a metadata .json file. It is only allowed to upload image files on this forum, so if that’s okay with you, I’ve uploaded them via WeTransfer.
I can confirm that with the 0.16.2 ouster-sdk version, I can visualize via CLI.
What I could not achieve:
Load multiple pcap files in sequence via CLI (0.16.2) ERROR: Failed to create scan_source for url ['scan_000000.pcap', 'scan_000002.pcap'] more details: PcapScanSource allows opening only one file at a time.
Visualize a pcap file via CLI with 1.0.1. Even with --traceback, it just shut down immediately.
I’ve also tried to share this data with you via Ouster Studio (both desktop and dev), but it could not process it. Please let me know if you can get access via WeTransfer and inspect the data.
I was able to download the files you sent via wetransfer and I was able to replicate your issue. We’ll be including a bug fix in the upcoming release, which we hope to publish by the end of the month.
