-
Notifications
You must be signed in to change notification settings - Fork 84
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
Error with Pytorch Encoding #41
Comments
|
Ditto. Error message: |
Ditto with Possibly something that was deprecated in an old version of Pytorch? Have seen this issue on another repo about three and a half years ago. No idea if it has any relevance, but just in case I've linked it. |
Have you solved this problem? Thank you! |
Not yet. I have got no idea to solve it. |
This comment was marked as duplicate.
This comment was marked as duplicate.
After encountering the same ""ScalarConvert" has already been defined" issue I finally managed to install
Ref: zhanghang1989/PyTorch-Encoding#418 Have not yet tried running the LSeg code with this setup. Will do soon. |
Could not run the code as I got an
|
same issue. |
Hi guys, I think I have successfully solved the issue! I installed the packages mentioned in the requirements.txt with Pytorch 1.9 and cuda11.1. The newly released PyTorch encoding is not compatible with PyTorch 1.9. So, I rolled back to an earlier commit and successfully installed the package.
|
i have the same issue is anyone solved it? I think it's a version incompatibility issue.
|
hello,can you tell me which version of pytorch you rolled back? |
|
I am running windows and I have issues with installing this project, specifically for the torch encoding package.
Some primary error include:
error: ninja: error: loading 'build.ninja': The system cannot find the file specified.
and
Error building extension 'enclib_cpu'
These errors are usually in tandem with a giant list of other errors presumable in dependencies. When I tried to build the package via Docker, similar issues arose as well.
Things I have tried:
I am running on a Windows 10 machine.
Are there any fixes or guides to get lang-seg to work under these circumstances?
The text was updated successfully, but these errors were encountered: