Release 0.11.1 #594
Closed
Release 0.11.1 #594
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
…he damned build (why didn't this error occur when I ran it the first time? Who knows)
* Added cli command logging * Added python version info to cli logging * Added package list on cli error * Added emacs and vim to the manylinux container
…in error Also update gitignore to include some built artifacts FLEETSW-5135: Loop PCAP without itertools.cycle FLEETSW-5134: add "on-eof" option to viz; loop by default FLEETSW-5134: add on-eof option to OSF viz Add missing test file Fix persnickety flake8 nonsense Whoopsie, remove private plugins from test in test_plugins.py Add a message that lets users know how to get a traceback on plugin load failure
- moved traj.py from internal with refactor - add viz_utils and tests with helpers - fallback to no scipy functions if not present
* Moved ouster-cli docs to its new public location
* fix source_osf plugin bug * create isolated test fixtures for test_cli.py * shift remaining tests for source_osf from sdk_extensions * hide osf viz functionality
* Update FW compatibility table in SDK Docs * Add link to lifecycle policies in docs * Update -m help message for ouster-cli source/PCAP viz * Change ouster-cli -f to -m to match source * Add timeout option to ouster-cli source PCAP viz * Change default init_client log to specify 'expecting' port instead of making it seem like it's configuring * Change all -f to -m for --meta in ouster-cli * Fix bug with util benchmark not taking relative paths properly
- reads sensor packets measures: packets drops and cpu load avg
- add axis helper to show at scan origin - use resolve_metadata() in sdk.examples.viz for simpler use
* Apply formatting to all files in ouster-sdk See FLEETSW-5031
* Skip 0.9.1.dev0 as that is a dev wheel for systems eng
* Fix final logic on detecting fragmentation in ouster-cli pcap info * Set signal multiplier by default for ouster-cli sensor config * Remove deprecated pybind11 direct call to module and replace with PYBIND11_MODULE * Remove deprecated pybind11 == compartor for .is() * Remove deprecated encoder_ticks_per_rev * Add type hints in documentation for data_format, set_xyz
* Fix libpcap cmake install issue * Example added to test the cmake install path
Stop recording OSF on loop detect by default Dont allow recording decreasing timestamps into OSF files from the CLI You can continue recording anyways dropping these messages using existing -c flag Fix `ouster-cli source x.osf info` outputting confusing start times for empty files. ## Comments for reviewers: - optionally, any additional info to help reviewers ## Testing: - describe the steps you took to test this PR Closes FLEETSW-6136
Check string pointer for zero-initialization rather than enum value on profile string addition. Closes FLEETSW-6170
Closes FLEETSW-6171
Closes FLEETSW-6123
…ource.metadata doc string
Co-authored-by: Ussama Naal <[email protected]>
twslankard
requested review from
Samahu,
celentes,
Krishtof-Korda,
kkaly and
chrisbayruns
Samahu
approved these changes
May 16, 2024
Samahu
requested changes
May 16, 2024
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.
No description provided.