Refact: New Repo for MuJoCo

[detlefarend]

Motivation The wrapper code and related howto files of 3rd party package MuJoCo shall be relocated to a new repository to prevent MLPro from incompatible changes.

Benefit

• MLPro stays stable
• 3rd party support becomes optional
• 3rd party support packages will be listed in the MLPro extension hub

Are the proposed changes backward compatible?

• [ ] Yes
• [ ] No

To do

• [x] Creation of new repository MLPro-Int-MuJoCo (template: MLPro-Extension)
• [x] Relocation of related wrapper code and howto files to new repository
• [x] Relocation of related documentation to new repository
• [ ] Preparation for MLPro 1.4.x without MuJoCo
• [ ] Release MLPro-Int-MuJoCo 1.0.0
• [x] Whitelist MLPro-Int-MuJoCo in MLPro-Extension
• [ ] Update MLPro-Int-SB3 plus related howtos

Branch wrappers/relocation2

See also https://github.com/fhswf/MLPro/wiki/30-MLPro-Extension

[steveyuwono]

Hi @detlefarend, just reviewed this, I have a question regarding the integration. It is clear that the mlpro.wrappers.mujoco codes are going to be moved into the new repository. However, in the mlpro.bf.systems module, we have a System class that can be configured to work with a Mujoco file. In such cases, we need to initialize the wrapper if it is called, as shown in this link Then, this also affects the EnvBase class in _mlpro.rl.modelsenv. Should these integrations also be removed from MLPro, and updated System and EnvBase classes be created within the wrapper?

[detlefarend]

Hi @detlefarend, just reviewed this, I have a question regarding the integration. It is clear that the mlpro.wrappers.mujoco codes are going to be moved into the new repository. However, in the mlpro.bf.systems module, we have a System class that can be configured to work with a Mujoco file. In such cases, we need to initialize the wrapper if it is called, as shown in this link Then, this also affects the EnvBase class in _mlpro.rl.modelsenv. Should these integrations also be removed from MLPro, and updated System and EnvBase classes be created within the wrapper?

Hi @steveyuwono, I also checked the code. The design doesn't follow our usual wrapper concept, but it encapsulates the optional MuJoCo parts suitable. It should be enough to redirect the wrapper access in ll 1169, 1259 to mlpro_int_mujoco. The only idea I have to improve something is to embed the imports in a try/except statement with an error log that points out the need for installing our MuJoCo extension.

[steveyuwono]

Hi @detlefarend, just reviewed this, I have a question regarding the integration. It is clear that the mlpro.wrappers.mujoco codes are going to be moved into the new repository. However, in the mlpro.bf.systems module, we have a System class that can be configured to work with a Mujoco file. In such cases, we need to initialize the wrapper if it is called, as shown in this link Then, this also affects the EnvBase class in _mlpro.rl.modelsenv. Should these integrations also be removed from MLPro, and updated System and EnvBase classes be created within the wrapper?

Hi @steveyuwono, I also checked the code. The design doesn't follow our usual wrapper concept, but it encapsulates the optional MuJoCo parts suitable. It should be enough to redirect the wrapper access in ll 1169, 1259 to mlpro_int_mujoco. The only idea I have to improve something is to embed the imports in a try/except statement with an error log that points out the need for installing our MuJoCo extension.

Hi @detlefarend , okay, well noted. Thank you for the information.