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

Generate a pipeline_space.yaml as feedback on which parameter type your configurations have been converted to #84

Open
danrgll opened this issue May 3, 2024 · 1 comment
Milestone

Comments

@danrgll
Copy link
Contributor

danrgll commented May 3, 2024

Since the user only has to optionally define the type of the parameter, because otherwise it is automatically recognized by neps, he/she could want to have a lookup option (a yaml file) that we could provide in the root directory

@danrgll danrgll mentioned this issue May 3, 2024
12 tasks
@eddiebergman eddiebergman added this to the Declaritive milestone May 3, 2024
@danrgll
Copy link
Contributor Author

danrgll commented May 7, 2024

This idea could be extended to having just 1 yaml file where you can find all settings (optimizer.yaml, neps arguments and pipeline space)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants