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_template.yaml: default values should lead to good baseline model #189

Closed
remtav opened this issue Mar 2, 2021 · 2 comments
Closed

Comments

@remtav
Copy link
Collaborator

remtav commented Mar 2, 2021

Config_template should reflect a "generally-good-to-start-with" configuration, that is, trying to cover common use cases of GDL and output an "ok" model to start with. For example, we could set batch size=4, num_gpus=1, num_epoch=50, architecture to a simple pretrained unet that has been giving good results for us (@victorlazio109 which one?), etc.

This issue has been raised by @bstdenis. Don't hesitate to comment Mr. St-Denis!

@CharlesAuthier
Copy link
Collaborator

Not agree, I think that the config_tamplate.yaml should only be a exemple that work out of the box on any computer (so no GPU and small batch size) and see that everything is running (so small amount of epochs). One think that we can do is a config_unet.yaml that include what you want plus adding the weights of a unet trained in a folder. In the doc we can talk about it show some stats and saying the minimum required to train/run the unet.

@CharlesAuthier
Copy link
Collaborator

This could be close after the PR switch to hydra.

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

3 participants