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

An option for when to apply the postprocessor #18

Open
topepo opened this issue May 31, 2024 · 0 comments
Open

An option for when to apply the postprocessor #18

topepo opened this issue May 31, 2024 · 0 comments

Comments

@topepo
Copy link
Member

topepo commented May 31, 2024

This is related to discussions regarding back-transforming an outcome column.

Recipe steps have the skip option, which, when TRUE, does not apply the step to new data (i.e., only to the training set).

While not the same thing, we might think about having a mandatory flag called something like devel_only that specifies that we only apply it during the model development cycle (i.e., in the tuning/resampling/last_fit/best_fit cycles).

We could default to devel_only = FALSE for almost everything, but it would allow users to only execute it during functions like predict() or augment() when used outside of the aforementioned functions.

(I'm not dead set about the proposed argument name)

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

No branches or pull requests

1 participant