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

PipeOpThreshold has wrong predict type #712

Open
sebffischer opened this issue Feb 28, 2023 · 3 comments
Open

PipeOpThreshold has wrong predict type #712

sebffischer opened this issue Feb 28, 2023 · 3 comments

Comments

@sebffischer
Copy link
Sponsor Member

PipeOpThreshold claims to have predict_type "response" but actually outputs probabilities. Also, why is it not possible to change the predict type of the PipeOp?

@mb706
Copy link
Collaborator

mb706 commented May 22, 2023

The problem seems to be that PipeOpLearnerCV does not have the right predict_type. PipeOpTuneThreshold does not claim to have any predict type, but requires the incoming task to have probability predictions. The graph infers the predict type from the last pipeop in the (sequential) graph that announces its predict type. PO TuneThreshold does not announce any type, but PipeOpLearnerCV does -- just the wrong one.

@mb706
Copy link
Collaborator

mb706 commented May 22, 2023

Never mind, PipeOpLearnerCV also does not have any predict_type, since it is not a learner. "response" is just the default for a GraphLearner.

@mb706
Copy link
Collaborator

mb706 commented May 22, 2023

@mllg the "interesting" part of PipeOpTuneThreshold output is the response prediction. But since the probability prediction is present, that is returned as well. Should a GraphLearner that does threshold tuning, but where probabilities are also returned, have predict_type "prob" or "response"? I would give it "prob", but I am wondering if there is any part of mlr3 that prioritizes probability predictions unless a Learner has predict type "response"? (Or that prioritizes probabilities full stop, forcing PipeOpTuneThreshold to drop the probability predictions altogether so it has an effect?)

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

2 participants