-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
calculate_risk_score() seems to have wrong logic #182
Comments
Here's a little script showing the current/original implementation of calculate_risk_score(), and 3 alternate implementations that might be the desired logic: I believe that I personally prefer the semantics of three, but my opinion is not very important.
Output:
|
Hey @snickell , thank you for sharing this information including the options and the code. Indeed, there is a bug in our calculation. I like your option three, which provides more context, and I will use it. |
The change was done |
In #138 @asofter says:
At least in the context of ban_topics.py and toxicity.py I don't think it behaves as described above, but of course I could be very wrong in my understanding.
Here's what happens with the current implementation of
calculate_risk_score()
:Notice that as you increase score, approaching the threshold, risk_score actually decreases from 1.0 to 0.0. Then once score is greater than the threshold, risk_score is pinned to 1.0.
The text was updated successfully, but these errors were encountered: