Commit 2e5701c
Fix NaN handling in AUPRC metric calculation (#3523)
Summary:
Pull Request resolved: #3523
Improved the NaN handling logic in the AUPRC (Area Under Precision-Recall Curve) metric calculation to correctly handle edge cases where division by zero occurs.
The changes address NaN values that arise from 0.0/0.0 divisions in both recall and precision calculations:
**Recall NaN handling:**
- NaNs occur on the right side of the recall tensor due to cumsum starting from the left (num_fp) but being flipped
- Changed NaN replacement value from 1.0 to 0.0 to match the 0.0 value appended on the right side
- Removed the conditional check since we should always handle NaNs consistently
**Precision NaN handling:**
- Added explicit NaN handling for precision tensor (previously missing)
- NaNs in precision occur on the right side similar to recall
- Replace NaNs with 0.0 (not 1.0 as stated in comment) to prevent NaN propagation in _riemann_integral
- This prevents the entire AUPRC result from becoming NaN when any precision element is NaN
Added detailed comments explaining the root cause of NaN values and the rationale for the chosen replacement values.
Reviewed By: iamzainhuda
Differential Revision: D86464670
fbshipit-source-id: ee8a1a76f8bfa50d38e1f10965c8175c72a130af1 parent cf63c52 commit 2e5701c
1 file changed
+10
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
65 | 65 | | |
66 | 66 | | |
67 | 67 | | |
68 | | - | |
69 | | - | |
70 | | - | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
71 | 78 | | |
72 | 79 | | |
73 | 80 | | |
| |||
0 commit comments