You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the changes related to the WoEEncoder in #53 , there are still parts of the package that rely on the "old" calculation of WoE.
Namely, this refers to the functions in
scorecard.metrics.metrics
that are also used in the reporting functionality for IV, PSI etc.
Ideally, one would like that the WoE is calculated via the WOEEncoder everywhere, to avoid potential inconsistencies.
Update to the documentation might be needed as well. Check:
howto/psi_and_iv.ipynb
howto/Optimizations.ipynb
The text was updated successfully, but these errors were encountered:
Related: the IV-score in bucket_table() has a negative sign, as it depends on the sign of WoE which was altered. This might be unintuitive and should probably be changed. (credit to Mara de Rosa for finding the issue)
I have noticed that the WoE calculations from bucket_table method are not consistent with the WoeEncoder(). I believe these calculations should be consistent as they might mislead analyses.
After the changes related to the WoEEncoder in #53 , there are still parts of the package that rely on the "old" calculation of WoE.
Namely, this refers to the functions in
that are also used in the reporting functionality for IV, PSI etc.
Ideally, one would like that the WoE is calculated via the WOEEncoder everywhere, to avoid potential inconsistencies.
Update to the documentation might be needed as well. Check:
howto/psi_and_iv.ipynb
howto/Optimizations.ipynb
The text was updated successfully, but these errors were encountered: