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

Revisit when we define fit, transform, and fit_transform #73

Open
kwinkunks opened this issue Sep 25, 2023 · 0 comments
Open

Revisit when we define fit, transform, and fit_transform #73

kwinkunks opened this issue Sep 25, 2023 · 0 comments
Labels
maintenance Not a bug now but could be one day

Comments

@kwinkunks
Copy link
Member

kwinkunks commented Sep 25, 2023

If code is in transform, it would also run during predict phase. But would only run if not last thing in pipeline... need to think about that.

I.e. if pipeline is [scaler, detector, estimator], then fit_transform is called in fitting, and transform is called in scoring or prediction. OTOH, if pipeline is [scaler, detector] then only fit is called in fitting, and predict is called in scoring or prediction (which these things are not designed for so don't implement -- but check this behaviour!).

Note that y is not passed to transform from fit_transform.

So detectors should work like:

  • fit: call transform
  • transform: put the detector here but note that y is not passed to transform from fit_transform
  • fit_transform: call transform (i.e. skip fit) because otherwise y is not passed

Should only use fit when we want to remember something from training for comparison later.

@kwinkunks kwinkunks added the maintenance Not a bug now but could be one day label Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Not a bug now but could be one day
Projects
None yet
Development

No branches or pull requests

1 participant