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
I tried to infer and fuse on DTU dataset, but found the predicted results are different from your released ply models.
For example:
Your released point cloud for scan1 (mvsnet001_l3.ply): 26727801 points, fscore 0.191357
Predicted point cloud for scan1: 19405933 points, fscore 0.2162721
When I visualize the two point clouds, the completeness of predicted point cloud is much lower than released point cloud, especially around edges.
My environment:
Fusibile: compiled with cuda 11.4, sm86
Pytorch: 1.8.2+cu111
Python: 3.8.12
I tried to infer and fuse on DTU dataset, but found the predicted results are different from your released ply models.
For example: Your released point cloud for scan1 (mvsnet001_l3.ply): 26727801 points, fscore 0.191357 Predicted point cloud for scan1: 19405933 points, fscore 0.2162721
When I visualize the two point clouds, the completeness of predicted point cloud is much lower than released point cloud, especially around edges.
My environment: Fusibile: compiled with cuda 11.4, sm86 Pytorch: 1.8.2+cu111 Python: 3.8.12
Hi, I used gipuma to fuse the depth maps, but I the number I got is only half as the author provided. So if there is any parameters of setting I need to change?
I tried to infer and fuse on DTU dataset, but found the predicted results are different from your released ply models.
For example:
Your released point cloud for scan1 (mvsnet001_l3.ply): 26727801 points, fscore 0.191357
Predicted point cloud for scan1: 19405933 points, fscore 0.2162721
When I visualize the two point clouds, the completeness of predicted point cloud is much lower than released point cloud, especially around edges.
My environment:
Fusibile: compiled with cuda 11.4, sm86
Pytorch: 1.8.2+cu111
Python: 3.8.12
Here is my log file for scan1
log.txt
The text was updated successfully, but these errors were encountered: