Extending hydra configs from multiple directories with hydra.searchpath #2717
Replies: 1 comment
-
I can't think of a really good solution to this problem -- besides making Hydra support setting Here are two potential workarounds:
None of these workarounds is really satisfying since they are somewhat cumbersome and require updating either the command line (option 1) or the config (option 2) for all children of a config whose search path is updated. Edit: Note that in option 2 above you wouldn't duplicate the config, instead the config with |
Beta Was this translation helpful? Give feedback.
-
Hi! In my use cases, we have some dependencies between hydra configs for training different models - different config groups.
However, the configs may be located in different directories. I am wondering how to tackle it without the limitation of hydra.searchpath being allowed only in the primary config. Ie an example
config /A/conf/A.yaml
- some base configconfig /B/conf/B.yaml
that uses as a default/A/conf/A.yaml
withhydra.search.path = "/A/conf"
config /B/conf/B1.yaml
that uses as a default/B/conf/B.yaml
from the same folderconfig /C/conf/C.yaml
that uses as a default/B/conf/B.yaml
withhydra.search.path = "/B/conf"
Hydra will process with no problems configs in (1) and (2) but throws errors at (3) and (4) since they contain inherited hydra.searchpath from the defaults configurations.
Ideally, I would like to come up with a solution that attaches hydra.searchpaths from the non-primary configs to the hydra.searchpath as this approach gives the most visibility to where the configs are located
Beta Was this translation helpful? Give feedback.
All reactions