-
Notifications
You must be signed in to change notification settings - Fork 166
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
pydarknet.is_compiled_with_gpu returns false #48
Comments
Same thing for me. |
I was running into the same issue trying to install from source with a custom darknet installation. It looks like the GPU environment variables is ignored if DARKNET_HOME is also set. T Line 28 in 062de22
if "GPU" in os.environ:
if "DARKNET_HOME" in os.environ:
logging.warning("GPU environment variable is skipped since DARKNET_HOME is specified")
else:
if int(os.environ["GPU"]) == 1:
logging.info("Darknet will be compiled with GPU support")
USE_GPU = True
else:
logging.info("Darknet will be compiled without GPU support")
USE_GPU = False This causes pydarknet to be compiled without the ability to set cuda device. Line 63 in 062de22
IF USE_GPU == 1:
--
64 | void cuda_set_device(int n) It looks to me like the |
@dquig Thank you for showing the cause of issue. I will go through the setup script again and correct it. |
I am getting the same thing. Have you fixed that. |
Hello. I am going to run several processes.. One on Gpu 1 and another one on GPU 2.
How can i do this? |
Fixed issue of ignoring GPU environment variable when custom DARKNET_HOME is set. |
I have followed the steps to run with gpu and opencv. But on importing pydarknet,
Both
pydarknet.is_compiled_with_gpu
andpydarknet.is_compiled_with_opencv
return FalseThe text was updated successfully, but these errors were encountered: