-
Notifications
You must be signed in to change notification settings - Fork 10
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
240 quantile pivot #241
240 quantile pivot #241
Conversation
… `flatline_forecaster()`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome, thanks for this! If it isn't too gnarly, is it possible to change the column names from q
and tau
to something user defined/default to quantile/value? If not, it's easy enough to pass this through rename
after
This is a breaking change. Needs a version bump and/or a shim for the dperecated |
.data <- .data %>% | ||
tidyr::unnest(tidyselect::all_of(col)) %>% | ||
tidyr::pivot_wider( | ||
names_from = "tau", values_from = "q", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely hairy, unfortunately.
…ipredict into 240-quantile-pivot
Closes #240
@dsweber2 This isn't a "layer" but you should be able to call it directly on the predictions and get out something much closer to the submission format.
_wider()
version. But naming is better._longer()
version should be what you want.This function is a necessary precursor to #237