Using configs from different config groups #3574
Unanswered
dorotat-nv
asked this question in
Q&A
Replies: 1 comment
-
Hey, that is an interesting use case. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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 exampleconfig /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.searchpath
s from the non-primary configs to thehydra.searchpath
as this approach gives the most visibility to where the configs are locatedBeta Was this translation helpful? Give feedback.
All reactions