spatio_temporal_voxel_layer icon indicating copy to clipboard operation
spatio_temporal_voxel_layer copied to clipboard

A new voxel layer leveraging modern 3D graphics tools to modernize navigation environmental representations

Results 18 spatio_temporal_voxel_layer issues
Sort by recently updated
recently updated
newest added

The Kinect Azure is commonly used as depth camera and its frustum is not rectangular, it's either circular or an hexagonal depending on the mode. https://docs.microsoft.com/en-us/azure/kinect-dk/hardware-specification#depth-camera-supported-operating-modes It would be nice...

I noticed you removed the VISUALIZE_FRUSTUM "tool" in this [commit](https://github.com/SteveMacenski/spatio_temporal_voxel_layer/commit/a8d34416c986109e361cee889b2abcf1239acabd). It is still in the README though I still need to visualize my frustum to understand why voxels are disappearing...

Hello, FYI and to track the issue: In preparation for the Humble release I tried to build STVL under Humble beta with Ubuntu 22.04 and the blocking point seems to...

Hi, I was wondering if there is a way to offset the depth voxels. I have a robot where the depth cloud actually corresponds to what I measure, but the...

## Bug report I'm new in using the the stvl layer (b.t.w - another great job!), and might be doing something wrong. But according to the tutorials and to the...

Hi. For some reason I'm unable to install the package on ROS Noetic Docker image (ros-noetic-base): ``` E: Unable to locate package ros-noetic-spatio-temporal-voxel-layer ``` According to [ROS Index](https://index.ros.org/p/spatio_temporal_voxel_layer/github-SteveMacenski-spatio_temporal_voxel_layer/#noetic) everything seems...

Hello, I am trying to use STVL in conjunction with AirSim to simulate a drone with a depth camera. The problem is that the point cloud from the virtual depth...

This PR adds the `min_age_outside_frustum` parameter. I am open to discussion and debate about it (and also about the name of the parameter which I am not super happy with)....

In **theory**, this modification is just about readability. It should give EXACTLY the same result, but... In practice, we fixed also a problem with **min/max** distance, as reported in #164...