-
Notifications
You must be signed in to change notification settings - Fork 4
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
98/ Subset expanded grid of valid values by output type #107
Conversation
…task-ids. Related to #93
Apologies to the reviewer...I think I've misunderstood what rebasing was supposed to do...the last 5 commits which are somewhat polluting the PR, were through a rebase to add linting fixes made in #99 so I didn't think they'd show up here given they are already in |
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.
One question of substance if we should just always throw an error if an invalid output type is specified. Then I had questions about indentation but it seems like linting passed so OK to just move on from those. I've approved as good enough to merge.
Thanks @elray1 ! Re: the linting, it's what
I think that's reasonable. |
93/add derived_task_id argument
Merge branch '98/subset-grid-by-out-type' into 93/3-batch-value-validation # Conflicts: # R/check_tbl_spl_compound_tid.R # R/v3-sample-utils.R # tests/testthat/test-check_tbl_spl_compound_tid.R # tests/testthat/test-check_tbl_spl_non_compound_tid.R
Co-authored-by: Evan Ray <[email protected]>
93/PR 3/3 - Propagate performance optimisation throughout checks & validation functions
This PR resolves #98 by introducing an
output_type
argument toexpand_model_out_grid()
which allows for producing output type specific subsets of the expanded grid of valid values.It also adds a bunch of low level internal functions for extracting information from round level configs
This will be used downstream in #93 as well as form the basis for #97