-
Notifications
You must be signed in to change notification settings - Fork 589
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
New ‘ModuleNotFoundError’ #270
Comments
It's hard to say for sure, but I would guess this has to do with the libraries being updated, possibly by some other project. Based on the pathing of the libraries in the error message (e.g. The general solution for this is to use virtual environments, either through python itself (using venv) or something like conda. These act like dedicated sandboxes where you'd install all of the libraries for a single project in one place, which only gets used by that one project, and therefore won't be affected by updates to other projects (which should have their own separate environments). (unrelated) Also, since you're using beit, I figured I'd mention that there there are improved models available that might be worth checking out. One is called Depth-Anything (specifically the vit-large model) and another much higher quality (but very slow to run) model called Marigold. |
Hi, until recently I could run this via a Google Colab notebook (with timm 0.6.13 and torch 2.0.1 to avoid other errors), but today running the following cell:
Produces the error output below:
Through experimentation, I find that deleting references to ‘torch._custom_ops' in the _meta_registrations.py file allows MiDaS to run, but obviously this is not the most correct fix. Any advice for a better solution? Thank you!
The text was updated successfully, but these errors were encountered: