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
if we has a gpu ,why --cuda-device -1 ? it should be --cuda-device 0 or --cuda-device 1
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.
cause we didnot use GPu , want to use Gpu by node-odm correctly
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset AND task output log, uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
[Type answer here]
The text was updated successfully, but these errors were encountered:
Could we move this conversation over to the forum at https://community.opendronemap.org? The forum is the right place to ask questions (we try to keep the GitHub issue tracker for feature requests and bugs only). Thank you!
p.s. I'm just an automated script, not a human being.
How did you install ODM? (Docker, installer, natively, ...)?
docker nodeOdm
What is the problem?
【bug】
openmvs.py
gpu_config set --cuda-device -1 or --cuda-device -2, cant use GPUif we has a gpu ,why --cuda-device -1 ? it should be
--cuda-device 0
or--cuda-device 1
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.
cause we didnot use GPu , want to use Gpu by node-odm correctly
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset AND task output log, uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
[Type answer here]
The text was updated successfully, but these errors were encountered: