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

config reshape suggestion #25

Open
victor-moreno opened this issue May 23, 2024 · 0 comments
Open

config reshape suggestion #25

victor-moreno opened this issue May 23, 2024 · 0 comments

Comments

@victor-moreno
Copy link
Contributor

Hi,
A suggestion:
It is a pain to have to either edit the config file or deal with multiple config files because some steps overwrite files of previous steps. This is mainly for crossval/deploy and statistics for crossval, train & deploy. I think the procedure would benefit a lot if a complete analysis can be run with one unique config file from preprocess, if needed, to deployment.

The conflicts mainly arise at deploy. The procedure would benefit for a new config section "deployment:" to avoid conflicts with "modeling:" that contains all the required paths for the deployment step.
This should be very easy to implement, only changing cli.py instructing to read c from cfg.deployment.

statistics should be renamed or changed to a flag (True/False) so that after crossval, train or deploy, statistics are calculated (or not) and saved in an output_dir that do not overwrite each other.

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

1 participant