-
Notifications
You must be signed in to change notification settings - Fork 25
Feature: add enhanced treatment of sample as a protected column #261
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #261 +/- ##
==========================================
+ Coverage 91.36% 91.39% +0.03%
==========================================
Files 21 21
Lines 1366 1371 +5
==========================================
+ Hits 1248 1253 +5
Misses 118 118
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
Nice thanks a lot! So essentially this internally checks whether the prediction type is quantile, and if it is then it removes "sample" from the list of protected columns, right? What do you think about the additional (alternative?) feature that it would give a message / warning when you run |
Yes exactly
I am not sure why you would want to do that? Unless it offers safety elsewhere in your code it seems overly restrictive. I'm totally open to either so can either merge this in or close out and flag the desired implementation in the original issue. |
e1f66d5 to
f75e180
Compare
|
Merci! |
This PR adds support for scoring quantile forecasts that have a sample column. It closes #242. Whilst I've added some testing to protect against issues it may be the case that the "protected" column assumptions are baked into places I have missed and so this is still dangerous.
See the following example for the new functionality:
Created on 2023-01-12 with reprex v2.0.2