-
Notifications
You must be signed in to change notification settings - Fork 1
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
describe doing value table wrong? #119
Comments
First of all: that table only shows the number valid datapoints. If a data point has an error in it or describes an unknown feature it won't show up in the table. That's where the discrepancy comes from. Second: Whether or not a feature is ‘known‘ seems to depend on gb20.txt. The binarised features aren't in there, yet. Should be fixable by copying the gb20.txt from the regular repo over to the ELDP one. Also, I wanted to check a sheet in regular grambank and picked HC_swed1254 at random. It said the following features are not valid:
Just to double-check: Anything surprising in this list? |
Thanks!
the binarised features gb20.txt though.. https://github.com/glottobank/Grambank/blob/4c280aec01e30fa8bf53ad622b3b8e51699b1649/gb20.txt#L4620
Yeah, a lot. I'll check :)! |
Doesn't this report from pygrambank
describe
look wrong for number of values in ELDP-glottobank/grambank/original_sheets/FCE_apal1257.tsvFor comparison, here's what I get in R
I take it it has to do with the binarised features somehow?
The text was updated successfully, but these errors were encountered: