Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fusible printing an empty .ply #28

Closed
UannaFF opened this issue Feb 20, 2019 · 2 comments
Closed

fusible printing an empty .ply #28

UannaFF opened this issue Feb 20, 2019 · 2 comments

Comments

@UannaFF
Copy link

UannaFF commented Feb 20, 2019

Hello! I managed to run everything for the MVSNet and I got the depth folder that looks exactly like your example but when I try to run fusible the .ply file is empty. Also it gives me the following message:

.
.
.

Resizing globalstate to 49
Run cuda
Run gipuma
Grid size initrand is grid: 9-7 block: 32-32
Device memory used: 337.707001MB
Number of iterations is 8
Blocksize is 15x15
Disparity threshold is 0.250000
Normal threshold is 6.283185
Number of consistent points is 3
Cam scale is 1.000000
Fusing points
Processing camera 0
Found 0.00 million points
Processing camera 1
Found 0.00 million points
Processing camera 2
Found 0.00 million points
Processing camera 3
Found 0.00 million points
Processing camera 4
Found 0.00 million points
Processing camera 5
Found 0.00 million points
Processing camera 6
Found 0.00 million points
Processing camera 7
Found 0.00 million points
Processing camera 8
Found 0.00 million points
Processing camera 9
Found 0.00 million points
Processing camera 10
Found 0.00 million points
Processing camera 11
Found 0.00 million points
Processing camera 12
Found 0.00 million points
Processing camera 13
Found 0.00 million points
Processing camera 14
Found 0.00 million points
Processing camera 15
Found 0.00 million points
Processing camera 16
Found 0.00 million points
Processing camera 17
Found 0.00 million points
Processing camera 18
Found 0.00 million points
Processing camera 19
Found 0.00 million points
Processing camera 20
Found 0.00 million points
Processing camera 21
Found 0.00 million points
Processing camera 22
Found 0.00 million points
Processing camera 23
Found 0.00 million points
Processing camera 24
Found 0.00 million points
Processing camera 25
Found 0.00 million points
Processing camera 26
Found 0.00 million points
Processing camera 27
Found 0.00 million points
Processing camera 28
Found 0.00 million points
Processing camera 29
Found 0.00 million points
Processing camera 30
Found 0.00 million points
Processing camera 31
Found 0.00 million points
Processing camera 32
Found 0.00 million points
Processing camera 33
Found 0.00 million points
Processing camera 34
Found 0.00 million points
Processing camera 35
Found 0.00 million points
Processing camera 36
Found 0.00 million points
Processing camera 37
Found 0.00 million points
Processing camera 38
Found 0.00 million points
Processing camera 39
Found 0.00 million points
Processing camera 40
Found 0.00 million points
Processing camera 41
Found 0.00 million points
Processing camera 42
Found 0.00 million points
Processing camera 43
Found 0.00 million points
Processing camera 44
Found 0.00 million points
Processing camera 45
Found 0.00 million points
Processing camera 46
Found 0.00 million points
Processing camera 47
Found 0.00 million points
Processing camera 48
Found 0.00 million points
ELAPSED 0.022905 seconds
Error: no kernel image is available for execution on the device
Writing ply file ../TEST_DATA_FOLDER/dtu_test_scan9/scan9/points_mvsnet//consistencyCheck-20190220-150052//final3d_model.ply
store 3D points to ply file

it looks like there's something wrong with the kernel image? Do you have any idea of what could be causing this? i'm running it on a Tesla K80 with CUDA 9.0.

@UannaFF
Copy link
Author

UannaFF commented Feb 20, 2019

sry, the key was to solve this cuda error Error: no kernel image is available for execution on the device, i just didn't know how. I'm going to tell you what i did in case someone else gets confused with this.

What I did to solve it:

  1. Go to this link and check the supported gencode and sm variations for my card https://arnon.dk/matching-sm-architectures-arch-and-gencode-for-various-nvidia-cards/
  2. In my case SM37 or SM_37, compute_37 , so I changed the following line in the cmake file:
    -gencode arch=compute_37,code=sm_37 to have the valid values for my card

After doing this, there's no more error and the reconstruction is good.

@ChenLiufeng
Copy link

ChenLiufeng commented Oct 22, 2020

my card is Tesla P100-PCIE , so I changed the following line in the cmake file:
-gencode arch=compute_60,code=sm_60 to have the valid values for my card. But it didn't work.@UannaFF
If I have two cards,how to change the cmake file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants