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

muffle "X should be in range (0, 1)" warning #788

Merged
merged 3 commits into from
Dec 18, 2023
Merged

Conversation

EmilHvitfeldt
Copy link
Member

This PR aims to close #758.

A calling handler is used, and when then warning "X should be in range (0, 1)" is found, then it is muffled

@EmilHvitfeldt EmilHvitfeldt requested a review from topepo December 15, 2023 01:16
@@ -578,13 +578,21 @@ fit_gp <- function(dat, pset, metric, control, eval_time = NULL, ...) {
}

opts <- list(...)

withCallingHandlers({
Copy link
Member Author

Choose a reason for hiding this comment

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

i chose to do one call to withCallingHandlers() around the whole if instead of two because it felt better.

no strong opinion either way

@topepo topepo merged commit 5b3a971 into main Dec 18, 2023
9 checks passed
@topepo topepo deleted the suppress-GPfit-warning branch December 18, 2023 01:46
Copy link

github-actions bot commented Jan 2, 2024

This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GP: X should be in range (0, 1)
2 participants