-
Notifications
You must be signed in to change notification settings - Fork 3
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
Centrality index #36
Comments
Another potential issue with this calculation is when the only conflict is of a single VL (with alternative readings) against himself. In which case, the index will be -2… |
C’est vrai... Faut qu’on change. Des idées, je te t’en parle dimanche.
Florian Cafiero
… Le 11 mai 2018 à 19:03, Jean-Baptiste-Camps ***@***.***> a écrit :
Another potential issue with this calculation is when the only conflict is of a single VL (with alternative readings) against himself. In which case, the index will be -2…
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Ok, while adding more tests I stumbled on the same error as in may of last year. A centrality index of -2 for the (rare and very theoric) case where there is a single conflict of a VL with itself. Should we change computation for this ? Or renounce altogether the use of 'alternateReadings' that are causing inconsistencies everywhere, and are very hard to manage ? @floriancafiero , any thoughts ? |
For now, we use the index offered in the paper
I'm asking myself questions on two aspects:
e = deg(u)
? For now, the code on this point is a bit of a hack. If the result is infinite, I normalise it to 2… We could always do,deg(u) / e
(perhaps better thandeg(u)/ e - deg(u) + 1
), which would normalise the result on 0 … 1 ?The current code, that can be really enhanced:
The text was updated successfully, but these errors were encountered: