Evaluate Class Resolver as an alternative to passing objects to model and taskmodule constructors.

[ChristophAlt]

See: https://github.com/cthoyt/class-resolver

[ArneBinder]

Looks Interesting!

Posting just for reference, might be related (in combination with hydra.utils.instantiate): Hydra Structured Configs

[ChristophAlt]

I think you should be able to use structured configs with this approach as well. The current problem is if we pass objects to models and taskmodules:

• it breaks our process of persisting models and taskmodules, because we persist the constructor parameters and on reload the model or taskmodule is instantiated based on stored parameters. This process only allows serializable types, no complex objects as constructor parameters.
• it requires more project specific code, e.g. changes / additions to the initial template, because hydra.instatiate must be used extensively
• it does not play well with many hyperparameter optimization frameworks, because those rely on string arguments

[ArneBinder]

I totally agree with the first two points, but regarding the third: hydra makes it quite easy to overwrite any subcomponent via command line or passing any overwrite config parameters to instantiate which looks like a very good fit for hyperparameter tuning in my opinion.