-
Notifications
You must be signed in to change notification settings - Fork 0
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
transform_quantile_to_pmf #11
Conversation
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.
Generally looks good to me, just one comment about potentially adding a warning and modifying the function docs
if (! "quantile" %in% unique_output_types) { | ||
cli::cli_abort("{.arg model_out_tbl} must contain predictions with output type 'quantile'.") | ||
} | ||
model_out_tbl <- model_out_tbl |> dplyr::filter(.data[["output_type"]] == "quantile") |
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.
If we're allowing the model_out_tbl
to have non-quantile output types but are filtering those out, we should warn the user and/or note this in the function description (I prefer to do both).
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.
Thanks for the suggestion!
In 244ef6d I updated the documentation to clarify that the returned object has only the new-created pmf forecasts. I was thinking this would address your concern by more generally clarifying that everything in the input model_out_tbl
is discarded. Does that make sense?
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.
yes it makes sense to me!
This would fix #10