
146
NEW FOR SOFTWARE RELEASE S19.07 (JULY 2019)
New command
line tools
Scripts have been created to fix most common issues
related to power failures, converting older datasets to
the new formats, fixing vertex values, ascii/binary
converter, and modifying timestamps in a file
Adaptive Data
Replay
Playback part of a
.bag file
The Replay Raw Data Tool allows the user to specify the
start and duration time for replay of bag files
Optimized
playback times
Adaptive data replay runs based on processing
completion rather than slow replay speeds
Performance
Improvements
updated Velodyne
driver
Velodyne driver with timing improvements and data
Polygon exclusion
zone for images
Ability to block out section of camera image from use
when calculating feature points
New features for
32-line scanners
HDL-32E and VLP32C now work with the feature tracker
Scan lines are
crisper
IMU unwarping of scan data eliminates hexadecads
within the scan lines
Overall
robustness
Works better with
3
rd
party SW
GNSS and time offsets moved to .yaml file and out of the
ply headers so they are not lost when using 3
rd
party SW
More time for live
scan processing
Update rate of scanning screen reduced to 3 hz (from 10)
to give more time for processing.
Detection of lidar
state
Better detection of lidar data allows more consistent
operation and error status communication to use
Ply files have
ordered
timestamps
Point clouds and trajectory files no longer have
timestamps that are out of order due to parallel
processing
GNSS
Added Stencil
clock sync using
GNSS data
User can now manually set Stencil Clock based on the
current time from the GNSS using the GNSS monitor icon
on the desktop
Pose information
in global
coordinates
Stencil publishes global coordinates if the user sets the
global origin of the local maps
Added more time
offset options
Added GNSS/Stencil time sync algorithm for driving
scenarios. Improved data handling and loop closure
Easier
localization
New feature which
gives ability to tell
when Stencil is
locked onto the
prior map
New topic /map_localization_confidence provides a
confidence value based solely on the prior map. Provides
a much better indication when localization lock is
achieved and when it is lost.