[Feature Request] support use case of composing the same config node in multiple places in the config tree
See original GitHub issue🚀 Feature Request
Be able to copy all the elements of one config in an other.
Motivation
In my code I have 2 modules which are trained, meaning that I have 2 optimizers. I would like to modify the parameters of one optimizer, but don’t want to copy have all default optimizer values written twice. I.e would like to do that python main.py module1.optimizer=adam module1.optimizer.lr=0.01 module2.optimizer.lr=0.01
but not have to define a optimize
twice. Something like that:
module1:
...
optimizer: ${optimizer.adam}
module2:
...
optimizer: ${optimizer.adam}
which would use the adam optimizer as default for module 1 and 2 without having to dupicate it.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
RFC 6020: YANG - A Data Modeling Language for the ...
1. Containers with Presence YANG supports two styles of containers, those that exist only for organizing the hierarchy of data nodes, and those...
Read more >Core Features - Spring
This section dives into the details of Spring Boot. Here you can learn about the key features that you may want to use...
Read more >Thinking in Compose | Jetpack Compose - Android Developers
Jetpack Compose is a modern declarative UI Toolkit for Android. ... If a piece of data is rendered in multiple places, it's easy...
Read more >Introduction to GitLab Flow
Production branch with GitLab flow. GitHub flow assumes you can deploy to production every time you merge a feature branch. While this is...
Read more >Configuration Options - Renovate Docs
Currently this setting supports helmv3 , npm , nuget , maven and sbt only, so raise a feature request if you have a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Another idea to play with:
group@path=name
or in defaults:
I kind of like this one.
until this is implemented, a workaround can be implemented as a symlink at the file system level: optimizer1/{adam,nexterov,sgd>.yaml optimizer2 -> optimizer1