You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
Thanks for your great work! We intend to evaluate some Tum sequences with your code. We found that there are some floaters in the rendering image and depth(We provide some visualizations about fr2_xyz and fr3_long_office sequence). Can you give me some suggestions or experience about this phenomenon? Do you think Hash collision is a potential cause?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @ming82871, thanks for your interest in our work. There are several potential reasons for this issue. 1) For rendering these results, have you used depth-guided sampling? As our truncation region is quite small, you need to use either depth-guided sampling or importance sampling (or just a sufficiently large amount of sample points) to make sure there are sample points within the truncation region. 2) Co-SLAM keeps and trains on only a small fraction of pixels with a small number of iterations for efficiency, you may not be able to get a high PSNR for rendering due to the insufficient number of pixels used for training.
Hi!
Thanks for your great work! We intend to evaluate some Tum sequences with your code. We found that there are some floaters in the rendering image and depth(We provide some visualizations about fr2_xyz and fr3_long_office sequence). Can you give me some suggestions or experience about this phenomenon? Do you think Hash collision is a potential cause?
Thanks!
The text was updated successfully, but these errors were encountered: