-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Feature: RecursiveDict.compress() to shorten paths to steps and their hyperparams #486
Comments
I would like to work on this issue. |
Idea 1:List of dicts containing step name and/or hyperparameter(s) and the parent list. Possible to remove parents for printing. It keeps the good order:
Idea 2:
|
One type of compressed format
|
@Rohith295 perfect ! I like |
Would be interesting to have this as well: |
Completed using the "use_wildcards" argument such as in |
Is your feature request related to a problem? Please describe.
Hyperparam names are too long in nested steps
Describe the solution you'd like
A way to compress the names so as to make them shorter. More specifically, I think that an automated algorithm for all existing ML pipelines could be built. That would be to do something like:
Then we'd see something like this in the pprint:
That is, the unique paths to some steps were compressed using the star (*) operator. The Star operator means "one or more steps between". But the way the paths are compressed would be lossless, in the sense that the original names could ALWAYS be retrieved given the original pipeline's tree structure.
Describe alternatives you've considered
Using custom ways to flush words and compress them. That seems good, but it doesn't seem to generalize to all pipelines that could exist.
Additional context
Hyperparameter names were said to be too long as well in #478
Additional idea
For hyperparameters, given the fact that in the future every model may need to name its expected hyperparams, then it may be possible to use their name only and directly if there is no other step with the same hyperparams. If another step uses the same hyperparam names, then compression with the "*" could go up in the tree to find the first non-common parent name or something.
More ideas are needed to be sure we do this the right way.
The text was updated successfully, but these errors were encountered: