-
Notifications
You must be signed in to change notification settings - Fork 640
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
Compatibility with latest timm and torch #234
base: master
Are you sure you want to change the base?
Conversation
Thank you, this would fix thygate/stable-diffusion-webui-depthmap-script#319 @dwofk could you please merge this? |
@thias15 These are quite necessary changes. Could you please merge this? |
Backports isl-org/MiDaS#234 Fixes #319 Fixes #323
Backports isl-org/MiDaS#234 Fixes #319 Fixes #323
This change does not work with timm==0.6.12 installed on existing systems. |
@nagadomi I can change the PR to match lllyasviel's fix. I was under the assumption that this was the only issue preventing systems from updating to the latest timm. |
@AyaanShah2204 I think that would be great to support both timm==0.6.12 and timm==0.9.5 |
Torch Compatibility
We're working with the latest nightly version of torch. They seem to have added type asserts to interpolate (this commit).
This causes a runtime error because the size we pass in is of type
numpy.int32
. A simple int-cast should fix this without any side effects.Timm compatibility
Blocks.drop_path()
was deprecated and replaced withBlocks.drop_path1()
andBlocks.drop_path2()
in this commit. This has been causing a runtime error referenced in this issue.This has affected things downstream in ZoeDepth and Auto1111's controlnet extension.