-
Notifications
You must be signed in to change notification settings - Fork 0
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
non-cognate forms #5
Comments
Luckily, we don't need to eliminate it, it is enough to change the COGID by just inserting a question mark in the field and then pressing enter. Entering a question mark will force the application to search through all existing COGIDs and take one that is not yet used. So these words will then be separated in future analyses and judged as non-cognate by all algorithms. |
Re-opening this issue for consistency. Please close, if the non-cognate cases have been resolved in the data. |
where should I place the q mark "?" ? is it in the CGID column in the exact row where that word is located? |
Yep! Just clear the COGID in that exact row you want to change and Just try playing a bit with this feature. In case you want to go back, Ah, and don't forget to hit enter after placing the question mark (or go |
A few cognate sets have(might have) a word from one language that is actually not a cognate to the whole set.
How should we handle that for the purpose of this project? Should we simply eliminate that toke from the alingment database?
Here is a list of entries
COGID # 15, 22, 38, 62, 96
The text was updated successfully, but these errors were encountered: