Skip to content

Sample property routing from #9566 with added support for routing to transform, scorers, prediction functions #15425

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

Closed

Conversation

hermidalc
Copy link
Contributor

@hermidalc hermidalc commented Nov 1, 2019

Reference Issues/PRs

This is relevant to SLEP006. I took code from #9566 and merged it with my code to also support routing to transform, scorers, and prediction functions within Pipeline and *SearchCV.

I also added my own hack to get feature properties routing and subsetting to work within Pipeline and *SearchCV. It's a hack because the only solution I could currently see is to fix in the source code what the name of the feature properties kwarg is, but I needed it now for my own work...

Any other comments?

This is intended to be exploratory to see what can work and how designs look when implemented.

@hermidalc hermidalc changed the title Param/property routing from #9566 with added support for routing to transform, scorers, prediction functions Sample property routing from #9566 with added support for routing to transform, scorers, prediction functions Nov 1, 2019
@cmarmo
Copy link
Contributor

cmarmo commented Sep 2, 2020

Thanks @hermidalc for your pull request.
@jnothman, @scikit-learn/core-devs this PR is related with SLEP06.
Is it going in the right direction? Should it be reviewed or do you prefer taking care of SLEP06 implementations? Thanks.

@adrinjalali
Copy link
Member

Thanks for the prototype @hermidalc , I think we're leaning towards solution 4 of the SLEP, currently being implemented in #16079 . As I understand, we almost have a consensus that it'd be a better solution.

Base automatically changed from master to main January 22, 2021 10:51
@cmarmo cmarmo added the Needs Decision - Close Requires decision for closing label Apr 15, 2022
@glemaitre
Copy link
Member

We can close this PR since the sample-props branch is going onward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Decision - Close Requires decision for closing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants