When will the runners-related code be merged?

[MorningFrog]

It’s exciting to see that the development of skrl 2.x appears to have made significant progress. I noticed that the important runners-related code has not yet been merged into the develop branch. I’d like to know when it will be merged, or whether there are any current difficulties or other considerations.

Thank you for your great work on this project!

[Toni-SM]

Hi @MorningFrog

I am working on developing/merging all the changes and release skrl-v2.0.0 ASAP
Particularly, for runners, I estimate it will take 1 or 2 weeks.

[MorningFrog]

Thank you very much for your efforts.

[Toni-SM]

Hi @MorningFrog

Out of curiosity, what feature(s) do you expect from the runner in skrl 2.0?

[MorningFrog]

Thanks for your reply. @Toni-SM

It’s a bit of an imposition, but I would like to request the ability to define custom network structures directly in code and register them—via something like a “registry”—so that they can be used in configuration files (e.g., YAML).

In the current configuration system, the combinations of linear, conv2d, flatten, and activation layers do indeed cover most scenarios. However, when the network architecture becomes more complex or involves additional structures (such as a Gated MLP), writing the configuration file becomes cumbersome—or in some cases, impossible to express purely through configuration. Although it is currently feasible to bypass the runner and define everything in code as shown in the examples, it would be even better if this could also be achieved through the runner.

To enable this customization capability, there are two possible approaches:

• Define custom model instantiators and “register” them; or
• Define custom networks and “register” them.

Either of the two approaches would work.

This is just a small suggestion for your consideration—no worries at all if you decide not to implement it.

[Toni-SM]

Runner code was merged: #380

[MorningFrog]

Thanks for your effort!