forked from ouster-lidar/ouster-sdk
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Performance improvements and bug fixes
* Should fix packet dropping in 2048x10 mode * Minor functionality changes to visualizer * Client sets lidar_mode * Client queries calibration values from sensor * Publish frame transforms and ROS image topics * See CHANGELOG.md for details
- Loading branch information
Dima Garbuzov
committed
Jan 28, 2019
1 parent
ed7c343
commit 88f08f0
Showing
38 changed files
with
1,952 additions
and
1,392 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,3 +4,4 @@ build/ | |
devel/ | ||
logs/ | ||
install/ | ||
doc/ |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
# Changelog | ||
|
||
## [1.10.0] - 2019-01-27 | ||
### Added | ||
- `os1_node` now queries and uses calibrated beam angles from the sensor | ||
- `os1_node` now queries and uses imu / lidar frames from the sensor | ||
- `os1_node` reads and writes metadata to `${ROS_HOME}` to support replaying | ||
data with calibration | ||
- ROS example code now publishes tf2 transforms for imu / lidar frames | ||
(addresses #12) | ||
- added `metadata` parameter to `os1.launch` to override location of metadata | ||
- added `viz` parameter to `os1.launch` to run the example visualizer with ROS | ||
- added `image` parameter to `os1.launch` to publish image topics to rviz | ||
(addresses #21) | ||
- added range field to `PointOS1` | ||
|
||
### Changed | ||
- split point-cloud publishing out of `os1_node` into `os1_cloud_node` | ||
- example visualizer controls: | ||
+ press `m` to cycle through color modes instead of `i`, `z`, `Z`, `r` | ||
+ `r` now resets the camera position | ||
+ range/intensity images automatically resized to fit window height | ||
- updated OS-1 client to use newer TCP configuration commands | ||
- updated OS-1 client to set the requested lidar mode, reinitialize on connection | ||
- changed point cloud batching to be based on angle rather than scan duration | ||
- `ouster_client` now depends on the `jsoncpp` library | ||
- switched order of fields in `PointOS1` to be compatible with `PointXYZI` | ||
(addresses #16) | ||
- moved example visualizer VTK rendering into the main thread (merged #23) | ||
|
||
### Removed | ||
- removed keyboard camera controls in example visualizer | ||
- removed panning and rotating of the image panel in example visualizer | ||
|
||
### Fixed | ||
- no longer dropping UDP packets in 2048 mode on tested hardware | ||
- example visualizer: | ||
+ point cloud display focus no longer snaps back on rotation | ||
+ fixed clipping issues with parallel projection | ||
+ fixed point coloring issues in z-color mode | ||
+ improved performance |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
# OS-1 Example Code | ||
Sample code for connecting to and configuring the OS-1, reading and visualizing | ||
data, and interfacing with ROS. | ||
|
||
See the `README.md` in each subdirectory for details. | ||
|
||
## Contents | ||
* [ouster_client/](ouster_client/README.md) contains an example C++ client for the OS-1 sensor | ||
* [ouster_viz/](ouster_viz/README.md) contains a visualizer for the OS-1 sensor | ||
* [ouster_ros/](ouster_ros/README.md) contains example ROS nodes for publishing point cloud messages | ||
|
||
## Sample Data | ||
* Sample sensor output usable with the provided ROS code is available | ||
[here](https://data.ouster.io/sample-data-2018-08-29) |
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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# OS-1 Example Client | ||
|
||
## Contents | ||
* `ouster_client/` contains a simple C++ client for the OS-1 sensor | ||
* can be built both with and without ROS. See the instructions in | ||
`ouster_ros` for building in a ROS environment | ||
|
||
## Building the Sample Client | ||
* The sample client requires a compiler supporting C++11 or newer and | ||
CMake | ||
* Build with `cd /path/to/ouster_example/ouster_client && mkdir build | ||
&& cd build && cmake .. && make` | ||
|
||
## Running the Sample Client | ||
* The sample client includes a small driver program that just prints | ||
some data to the terminal | ||
* Make sure the OS-1 is connected to the network and has obtained a | ||
DHCP lease. See accompanying documentation for more details | ||
* You should see a binary called `ouster_client_example` in your build | ||
directory on success | ||
* Run `ouster_client_example <os1_hostname> <udp_data_dest_ip>` where | ||
`<os1_hostname>` is the hostname or IP address of the OS-1 sensor, | ||
and `<udp_data_dest_ip>` is the IP to which the sensor should send | ||
lidar data |
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 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
Oops, something went wrong.