Closed Saijin-Naib closed 3 years ago
ODM detects python3-pyopencl
and assumes you have GPU support. Is this a native install? Make sure you have the latest OpenSfM.
ODM detects
python3-pyopencl
and assumes you have GPU support. Is this a native install? Make sure you have the latest OpenSfM.
WSL2 install, updated via git pull and apt update && apt upgrade, and manual install of python3-pyopenCL. W10 Insider Dev host with experimental NVIDIA CUDA WSL2-enabled drivers. https://developer.nvidia.com/cuda/wsl/download
So in theory, I should have properly working OpenCL via GPU, but it looks like clinfo only picks up my i7-6700k. And even if I can't get GPU passthrough working, shouldn't the CPU-based OpenCL still work properly?
Output of clinfo:
root@GreenMachine:/code# clinfo
Number of platforms 1
Platform Name Portable Computing Language
Platform Vendor The pocl project
Platform Version OpenCL 1.2 pocl 1.4, None+Asserts, LLVM 9.0.1, RELOC, SLEEF, DISTRO, POCL_DEBUG
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix POCL
Platform Name Portable Computing Language
Number of devices 1
Device Name pthread-Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Device Vendor GenuineIntel
Device Vendor ID 0x6c636f70
Device Version OpenCL 1.2 pocl HSTR: pthread-x86_64-pc-linux-gnu-skylake
Driver Version 1.4
Device OpenCL C Version OpenCL C 1.2 pocl
Device Type CPU
Device Profile FULL_PROFILE
Device Available Yes
Compiler Available Yes
Linker Available Yes
Max compute units 8
Max clock frequency 4008MHz
Device Partition (core)
Max number of sub-devices 8
Supported partition types equally, by counts
Supported affinity domains (n/a)
Max work item dimensions 3
Max work item sizes 4096x4096x4096
Max work group size 4096
Preferred work group size multiple 8
Preferred / native vector sizes
char 16 / 16
short 16 / 16
int 8 / 8
long 4 / 4
half 0 / 0 (n/a)
float 8 / 8
double 4 / 4 (cl_khr_fp64)
Half-precision Floating-point support (n/a)
Single-precision Floating-point support (core)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Correctly-rounded divide and sqrt operations Yes
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Address bits 64, Little-Endian
Global memory size 23069630464 (21.49GiB)
Error Correction support No
Max memory allocation 8589934592 (8GiB)
Unified memory for Host and Device Yes
Minimum alignment for any data type 128 bytes
Alignment of base address 1024 bits (128 bytes)
Global Memory cache type Read/Write
Global Memory cache size 8388608 (8MiB)
Global Memory cache line size 64 bytes
Image support Yes
Max number of samplers per kernel 16
Max size for 1D images from buffer 536870912 pixels
Max 1D or 2D image array size 2048 images
Max 2D image size 16384x16384 pixels
Max 3D image size 2048x2048x2048 pixels
Max number of read image args 128
Max number of write image args 128
Local memory type Global
Local memory size 4194304 (4MiB)
Max number of constant args 8
Max constant buffer size 4194304 (4MiB)
Max size of kernel argument 1024
Queue properties
Out-of-order execution Yes
Profiling Yes
Prefer user sync for interop Yes
Profiling timer resolution 1ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels Yes
printf() buffer size 16777216 (16MiB)
Built-in kernels (n/a)
Device Extensions cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_fp64 cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp64
NULL platform behavior
clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) Portable Computing Language
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [POCL]
clCreateContext(NULL, ...) [default] Success [POCL]
clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) Success (1)
Platform Name Portable Computing Language
Device Name pthread-Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) Success (1)
Platform Name Portable Computing Language
Device Name pthread-Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
Platform Name Portable Computing Language
Device Name pthread-Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
ICD loader properties
ICD loader Name OpenCL ICD Loader
ICD loader Vendor OCL Icd free software
ICD loader Version 2.2.11
ICD loader Profile OpenCL 2.1
So it's a native install? (Did you build from source?)
Make sure you have rebuilt the SuperBuild directory; you need the latest OpenSfM patches to get GPU to work.
Edit: if it's not a native install, this might be a bug in the build process for WSL2 images.
Yeah, not native. WSL2 generated by the github actions, but updated code directory by using git pull and updated libs in the install by using apt update/upgrade.
How would I trigger the rebuild of the SuperBuild directory?
Natively you would do:
bash configure.sh reinstall
Natively you would do:
bash configure.sh reinstall
Ran that successfully, still failed when python3-pyopencl is present... Maybe I'm missing an OpenCL driver?
Mm, not sure. But if you set ODM_NO_GPU=YES
as an environment variable, you can make sure that ODM does not attempt to use the GPU driver and should fix the issue. I'm going to close this as it looks like it might be a configuration / build issue. :pray:
How did you install OpenDroneMap? (Docker, natively, ...)?
WSL2, latest ../code directory, latest libraries (apt update), and python3-pyopencl installed. Running under Windows 10 Dev Fast host with CUDA WSL2 NVIDIA Drivers.
What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)
N/A
What is the problem?
ValueError: Unknown feature type (must be SURF, SIFT, AKAZE, HAHOG or ORB)
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
Features passed to opensfm are accepted properly.
How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)
Private "livingroom" dataset, which normally processes just fine. Removing python3-pyopencl stops this error from being raised, and the dataset processes fully.