support eval_time in fit_best() and rank_results()
#144
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`fit_best.workflow_set()` handles `eval_time` as much like `fit_best.tune_results()` as it can, and the same goes for `rank_results()` and `select_best.tune_results()`
simonpcouch
commented
Feb 22, 2024
hfrick
approved these changes
Feb 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An initial, incomplete go at introducing full support for survival in workflowsets. Still some more work to do and tests to add, though my COVID brain is tired, so I'm going to go nap.😴fit_best.workflow_set()handleseval_timeas much likefit_best.tune_results()as it can, and the same goes forrank_results()andselect_best.tune_results().Note that this PR will introduce a dev tune dependency. Related to #142.