Ouster Gemini Data Access and Troubleshooting

This document provides troubleshooting and additional information on accessing data from Ouster Gemini.

Event Recording and Data Access

• Event Recording with Object and Occupation Lists: To log clips with DETECT while capturing object and occupation lists, enable these lists in the Json Data Recorder and TCP Relay Server configurations.

• /data/storage/ Contents: The data under /data/storage/ contains counting numbers by different classifications in each Region of Interest (ROI).

• Accessing Raw Data (pcap files):

  • It is possible to get raw data (pcap files) individually but for the same time period from the Lidars via the DETECT interface.

  • Use the Ouster SDK to replay datasets recorded with Ouster Detect.

    1. Install Ouster SDK.

    2. Run the following command, adjusting the arguments to match your .json and .pcap files:

    ouster-cli source -m <your_metadata.json> -soft-id-check <your_pcap_file.pcap> viz

    • This allows you to visualize individual sensors from a pcap containing multiple sensors.

  • You can use different metadata .json files to read out different sensor's point cloud data from the same PCAP file.

  • Ouster SDK enables viewing, manipulating, and exporting points to various formats for third-party point cloud software analysis.

    • See the SDK guide for more information: https://static.ouster.dev/sdk-docs/python/examples/conversion.html#converting-pcaps-to-other-formats

TCP Port Issues

• TCP Echo Shows Data, but Python Script Doesn't Receive It:

  • If the web TCP tester works but your Python script doesn't receive data, ensure that the client secret in your code matches the one in Gemini Detect. Refer to the Ouster documentation for details on using Detect API client credentials: https://static.ouster.dev/ouster-detect/appendix/appendix.html#using-detect-apis-client-credentials

  • Use the simple example from the Ouster Gemini Documentation to test data retrieval from different ports. Adapt the port number in the example to match the port you are trying to read from.

• Ports Not Listening: If you find that certain ports (e.g., 3304, 3305, 3306) are not in a "LISTEN" state, you may need to add these ports to the allowed list in the compose.yaml file.

  • Caution: This file will be overwritten during any Gemini update, so keep a backup of your changes.

  • Edit the /opt/ouster/compose.yaml file.

    • Sample original compose.yaml

      • Open

        

  • Under the web-gui service, add the ports:

  web-gui: # ... other configurations ... ports: "${DETECT_PORT}:443" "3302:3302" "3303:3303" "3304:3304" # Add this "3305:3305" # Add this "3306:3306" # Add this # ... other configurations ...

  • sample after change compose.yaml

  • Open

    

  • After making these changes, run the following commands: