Skip to content
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

How to interpret the Score value and Reliable flag. #54

Open
loretoparisi opened this issue Mar 17, 2017 · 5 comments
Open

How to interpret the Score value and Reliable flag. #54

loretoparisi opened this issue Mar 17, 2017 · 5 comments

Comments

@loretoparisi
Copy link

Given that for a certain text the CLD2 response has a reliable flag and a detection object like:

{
    reliable: true
    detection : { name: 'ENGLISH', code: 'en', percent: 99, score: 1228 }
}

the detection can be considered reliable according to this flag i.e. detection.reliable=true. Which is the range of the detection.scorevalue and which is the exact meaning? I would like to set a min, max interval for the score value based on the flag, so havingreliable=truewhich is thedetection.scorevalues range? and which is that range forreliable=false` value?

Thanks.

@loretoparisi
Copy link
Author

Just questioning here about score and percent and a probability accuracy value...

@Natalie-Caruana
Copy link

Hi @loretoparisi I just came across this issue. Did you manage to find a solution?

@Natalie-Caruana
Copy link

Thanks for your prompt reply @loretoparisi . Will check these!

@Natalie-Caruana
Copy link

Natalie-Caruana commented Apr 29, 2022

Hi, I tried to look into these links but with not much luck. So the lower the value of the score, the better the prediction, but do you know what would be the best to flag prediction as reliable/not reliable as otherwise i'm finding it hard to get a useful meaning of this score. I'm using the python package pycld2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants