Skip to content
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

test fit_best.workflow_set() with survival #200

Merged
merged 3 commits into from
Feb 28, 2024
Merged

Conversation

simonpcouch
Copy link
Contributor

Mirrors the tests for fit_best.tune_results() as closely as possible, switching out model + preprocessor with a workflowset containing the same!

Tests for tidymodels/workflowsets#144.

)

expect_silent(dynamic_res <- fit_best(grid_dynamic_res))
dynamic_res <- fit_best(grid_dynamic_res, eval_time = 1)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added these two lines to mirror the existing fit_best() tests but am a bit unsure of the intent.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The expect_silent() is there because we want this function to make a choice for metric and eval_time silently, unlike most other functions where it warns you about that.

The second one I'm not entirely sure about. Ideally, we'd test that it does indeed pick the best model for a specific eval time (but there is nothing currently confirming that) so it's just making sure that it doesn't error 🤔

@simonpcouch simonpcouch requested a review from hfrick February 22, 2024 15:31
)

expect_silent(dynamic_res <- fit_best(grid_dynamic_res))
dynamic_res <- fit_best(grid_dynamic_res, eval_time = 1)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The expect_silent() is there because we want this function to make a choice for metric and eval_time silently, unlike most other functions where it warns you about that.

The second one I'm not entirely sure about. Ideally, we'd test that it does indeed pick the best model for a specific eval time (but there is nothing currently confirming that) so it's just making sure that it doesn't error 🤔

@simonpcouch
Copy link
Contributor Author

Just started rerunning checks with the most recent finetune commit on that branch. :)

@simonpcouch simonpcouch merged commit 6414fd4 into main Feb 28, 2024
5 checks passed
@simonpcouch simonpcouch deleted the workflowsets-144 branch February 28, 2024 16:20
simonpcouch added a commit that referenced this pull request Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants