Please consider using Hydra

[omry]

Hi,
I am the author of OmegaConf and Hydra.
Happy to see you are using OmegaConf, please take a look at Hydra. It's specifically designed with research in mind and I think it can help your project a lot.
Hydra is building on top of OmegaConf, which you are already using so it should be easy to give it a shot.

[tridivb]

Hi,

Thank you for the feedback. I checked out Hydra and it looks good. I decided to go with OmegaConf cause I was familiar with it and in the interest of time. Once I test Hydra with my framework, I can migrate to it. That will probably take a while though.

[omry]

Sounds good.
as a heads up, OmegaConf 2.0.0 will be coming soon and there are some subtle incompatibilities.
See details in the RC release notes.

It would be great if you can test it ahead of time to make sure you are prepared.

[tridivb]

Thanks for the info. I will then set the dependency to the current version till I finish testing out either the new one or Hydra.

[tridivb]

@omry Is there a way to define a YACS like default.py using Hydra. I am having some issues defining a default.yaml. I tried following the steps (https://hydra.cc/docs/tutorial/defaults) but if I place it outside a config group and run my script like python main.py, it doesn't load (just shows a blank dict).

eg.

|---default.yaml
| |
| |---conf1.yaml
| |---conf2.yaml
.
.
Just consider the config.yaml for this project and imagine the above hierarchy/ I want the default.py to be loaded if no config is provided else be overwritten/merged with another config passed through the command line. This should work if I understand the documentation correctly.

I also want the integrate my python logger with the hydra logger. Currently I log the output both to console and file but with different formatters. In such a case, how should I define the job logging parameters?

[omry]

@tridivb, can you join the chat? it will be easier to communicate there in real time.