-
Notifications
You must be signed in to change notification settings - Fork 11
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
Unable to install #81
Comments
Hi, There should be a log file in path %localappdata%\opuscat\logs, which should have more details about the error. Could you send me the log file, or copy-paste the error message included in it? -Tommi |
Here you go, thank you! 2023-06-30 10:56:23.220 +02:00 [INF] Setting Tls12 as security protocol (required for accessing online model storage WRN: Assembly binding logging is turned OFF. 2023-06-30 11:11:57.256 +02:00 [INF] Setting Tls12 as security protocol (required for accessing online model storage |
The Install model from zip is used to install models that have been packaged as zip files, it's mainly intended for special cases, e.g. when you want to distribute a fine-tuned model to other people. From the log file it seems that you tried to open the OpusMTEngine zip file with it, that's why it fails. As for the Install OPUS model from Web problem, it's a bit more mysterious. The log file mentions that a the YamlDotNet library is missing, so it might just be that the OpusMTEngine zip extraction has failed some reason. I'd suggest extracting the zip file into another location (for instance into a folder on your desktop) to see if it works there. |
It did not work on the desktop. However, "Install Opus Model from Web" worked after copying the files to C:\Users. So the issue has been solved now, thank you. |
I was unable to install OPUS-CAT after downloading the files (https://github.com/Helsinki-NLP/OPUS-CAT/releases/tag/engine_v1.2.0). Please see the error messages below from when I attempted to "install model from zip" and "Install Opus Model from Web".
The text was updated successfully, but these errors were encountered: