jdavidberger

To make it easier to test: ```c++ #include "open3d/Open3D.h" #include "open3d/t/geometry/Image.h" using namespace open3d; using core::Tensor; using t::geometry::PointCloud; using t::geometry::RGBDImage; int main(int argc, char *argv[]) { auto voxel_grid = t::geometry::VoxelBlockGrid::Load(argv[1]);...

I looked into some of the code that was there and wasn't sure what the intention was for some of that. Are you thinking this should be a run-time parameter...

I checked out dev; seems like a lot is ifdef'ed out for the refactor so I couldn't trace through it while running. It seems like overrun behavior should be settable...

My two cents is to keep it at a run-time exception until it is clear which the default behavior should be. No-one will complain if code that throws an exception...

That should work actually; It doesn't assume it can see all lighthouses at once and should be fine with switching between in and out of FOV's. I've tested pretty extensively...

The dynamic recalibration thing is probably mostly at fault here; disable it completely with `--no-light-error-for-lh-confidence`. I'll run the recording when I get a chance to see if it tells me...

I should have said this -- the global scene solver requires you to put the device down; not just go slow. It'll drop a little sphere in the viz tool...

I think the not enough measurement issues tend to apply to that scene; but it should be that if you have at least one scene with enough measurements for that...

I don't have a pimax to test with; but based on how the lighthouse ecosystem typically works there is a decent chance just plugging it in might just work; or...

Revisiting old issues; and I'm not sure the remedy here necessarily. I think driving the HMD visuals falls outside the realm of libsurvive; but I'm not sure the best way...