Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Melting Pot Version 2.0.0

See original GitHub issue

We are currently preparing the codebase for the next Melting Pot release, in which we will release new substrates and scenarios.

All this work will be done at HEAD on main, but we will keep the v1 substrates and scenarios working and unchanged up until we release v2.0.0.

However, there will likely be some disruption during this process (e.g. API changes, file moves). To avoid this please use tagged release v1.0.4.

Issue Analytics

State:
Created 10 months ago
Reactions:1
Comments:5 (1 by maintainers)

Top GitHub Comments

2reactions

GoingMyWaycommented, Nov 17, 2022

We are currently preparing the codebase for the next Melting Pot release, in which we will release new substrates and scenarios.

All this work will be done at HEAD on main, but we will keep the v1 substrates and scenarios working and unchanged up until we release v2.0.0.

However, there will likely be some disruption during this process (e.g. API changes, file moves). To avoid this please use tagged release v1.0.4.

@jagapiou Thank you John. Thanks for the great efforts made by your team to make the new Melting Pot.

0reactions

kinalmehtacommented, Nov 27, 2022

Thanks for these details. I don’t have any specific questions as of now. I was asking this to understand how it would affect results in my codebase if I directly swap in v1 environments with v2. I believe it doesn’t affect the self-play training in the scenarios you explained.

Thanks again for this awesome environment suite.