Trailing frame cache is not invalidated when client changes lidar interpreter properties
One Velodyne client was not aware of the new ‘caching’ mechanism used in trailing frame, so when he changed the option “Intra firing adjustment”, this was not seeming to do anything because he had 30 trailing frames.
The client reported a unclear bug (not his fault, caching is quite hidden), which made us waste time on investigations between v3.5.3 and v4.0.0
migrated from: https://gitlab.kitware.io/ComputerVision/LidarView/issues/30