-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting up MARL Benchmark with SMARTS 0.6.1 #1126
Conversation
This should now be unblocked since #1138 is merged. |
It looks like #1230 will possibly block this. |
#1235 has merged in to address a secondary exception can block training. |
2335a22
to
5f4842f
Compare
Checkpoints are magically working for some reason on my environment... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look fine to me. I'm just wondering why the directory restructuring was needed. Would relative imports accomplish the same thing?
- `marl_benchmark/agents/`: YAML files and some RLlib-based policy implementations | ||
- `marl_benchmark/metrics/`: Class definition of metrics (default by a basic Metric class) | ||
- `marl_benchmark/networks/`: Custom network implementations | ||
- `marl_benchmark/communicate.py`: Used for Networked agent learning |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- `marl_benchmark/communicate.py`: Used for Networked agent learning | |
- `communicate.py`: Used for Networked agent learning |
- `marl_benchmark/scenarios/`: Contains three types of scenarios tested in the paper | ||
- `marl_benchmark/wrappers/`: Environment wrappers | ||
- `marl_benchmark/evaluate.py`: The evaluation program | ||
- `marl_benchmark/run.py`: Executes multi-agent training |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like prepending the new folder name just adds noise to the documentation.
I am not entirely certain why the directory was restructured. However, it does make the benchmark obviously packageable. |
This pull request is being closed as the |
Restructured
baselines/marl_benchmark
folder to allow setting up withsmarts==0.6.1
and updated package requirements insetup.py
andREADME.md
to resolve training procedure errors.