Github user srowen commented on the issue:

    https://github.com/apache/spark/pull/15149
  
    Ah, do we need to update that? it looks like `threshold` is separate, and 
overrides `thresholds`. It's just used as a cutoff for the positive class, so 
it doesn't have same problem when it's 0. You could legitimately set it to 0 to 
always predict the positive class. 
    
    In the binary case, using this as a cutoff gives the same answer as this 
ratio-based rule anyway.
    
    (Really ... it _would_ make sense to allow _one_ threshold to be 0, which 
would effectively mean always predict the class, in the multiclass case. But 
let's leave that.)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to