Open Joy881007 opened 3 months ago
Hi,
I have met distCUDA2
error when the initialised depth map is too sparse and the module failed to calculate nearest neighbor. Might be relevant in your case.
Can you provide more details on the possible reasons? Is this related to a large error in the estimate pose?
In my case it was not related to pose error, but it was to do with the number of Gaussians used for keyframe initialisation... if it is too few, simple knn fails to run nearest neighbor search. I am not 100% sure how this relates to this case, but just to quickly share my experience of the error message.
Although I am not familiar with LoFTR, is the pose error so big?
Hi, I am testing on an RTX 4090 + i5-13500 setup.
python3 slam.py --config configs/mono/tum/fr3_office.yaml
I'm changing the pose in tracking with the pose calculated using LoFTR. Specifically, the logic of the code is as follows:During the run, the following error occurred:
What could be the reason for this? Thank you