WIP: [ouster] support for IMU data and pcap file format
#22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was
linked to
issues
Feb 2, 2024
Towards 1.0
Renaming from tag to subject. Rewriting README.md. Starting update of interfaces
Adding sketch to README.md. Updating zenoh-cli codec.
Still towards 1.0
Try except around json parsing.
* IMU data * Reading from pcap file
…keel into feature/ouster-pcap-imu # Conflicts: # interfaces/ouster/bin/ouster
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires #18 to be merged first.
Still requires additional work related to the pcap file format replay functionality. We ned to account for the timestamps and replay in "real-time" rather than "fast-time"!