only cpu is used in gui mode fix and hacky gardio/timm fixes #90
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
isl-org#82 I implemented the fixes told in this issue
when launched as gui, zoedepth would only use cpu
utku-helvaci
changed the title
update zoedepth to be compatible with torch 2.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#82 (comment)
implemented the hacky fix from the said issue discussion
I've also did a hacky fix on my own to make it work on modern gardio
Also fixed the issue where if the zoedepth is run as gui it wouldn't run on the correct device and only on the cpu