-
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
3.0.10 failing terminology extraction #105
Comments
Hi @dcram, It seems that the latest version 3.0.10 has a different interface and options even from the ones in the documentation page of the GUI version. I am trying to do bilingual alignment, but I don't see any results under 'Alignment Results' tab. Any idea how can I do bilingual alignment the right way? Thanks, |
If I select the options available in the pipeline and try to do Align, I get this error: Corpus IndexedCorpus[tetxt-en......] are not contextualized. I think this is caused by the absence of SWT option in this version. I see this piece of code in src/main/java/fr/univnantes/termsuite/api/BilingualAligner.java
|
Hi @mzeidhassan In theory, you should not be able to run an alignment when requirements are not met. Requirements are:
Your configuration parameters for terminology extraction (items 1 and 2) look good. I would suspect either an empty terminology, or a non-empty terminology with no extracted contexts... Are you sure you can see multiple extracted terms in both your source and target terminologies ? |
Hi @dcram I am simply using the 'wind energy' dataset. I have dictionaries storied in 'dicos' directory. The dictionaries are tab-delimited text files like 'en-fr.txt. The file format is as follows:
Attached is a screen shot to show you what I am seeing. Do you see anything wrong? Thanks again for your support! |
Version 3.0.10 de termsuite (sur linux) : en sortie, j’obtiens bien les fichiers json des résultats de l’extraction terminologique mais il m’affiche un message d’erreur aussi bien dans le panneau Progress que dans le panneau central qui est vide de tout résultat.
The text was updated successfully, but these errors were encountered: