Instantiate Transforms Using Hydra #524
Labels
boilerplate
Code is repetitive
enhancement
New feature or request
generalise
Code needs generalising
Milestone
Is your feature request related to a problem? Please describe.
Transforms are currently defined via the config but are not instantiated using
hydra
. This results in a clunky YAML syntax and various conditionals so a user can outline the program of transforms they want. There are also somethings that are not currently possible, such as passing args to transforms that are not primitive types.Describe the solution you'd like
Use
hydra.utils,instantiate
to build the transforms. This can handle nested instantiates (superseeding some of the currentlyminerva
defined functionality` as well as opening up new functionality.Describe alternatives you've considered
Continue to add new conditionals and adaptions of existing transforms for new use cases as and when required.
Additional context
Other elements of the config already support
hydra.utils.instantiate
such as the optimiser or loss function. Making this change will continue the move towards consistency and better UX acrossminerva
.The text was updated successfully, but these errors were encountered: