-
Notifications
You must be signed in to change notification settings - Fork 296
Update benchmarking configs #650
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #650 +/- ##
=======================================
Coverage 97.52% 97.52%
=======================================
Files 86 86
Lines 8373 8373
=======================================
Hits 8166 8166
Misses 207 207 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
Good catch with the ("common", "env_name") -> ("environment", "gym_id") transition! I missed that during refactoring. Also seams sensible to download demonstration instead of computing from scratch. LGTM from my side. This is mostly configuration file changes. |
This commit patches in the changes from PR #650. It also fixes an error in the dagger configs by replacing "py/object" with "py/type". "py/object" failed the assert in sacred.config.utils.assert_is_valid_key. Finally, it adds a minimal test suite for the benchmarking configs. This commit makes progress on testing, but still does not test that all the benchmarking configs work. Running all the configs with the fast configs applied is too slow. Calling sacred's print_config command for all the configs is also too slow.
This commit patches in the changes from PR #650. It also fixes an error in the dagger configs by replacing "py/object" with "py/type". "py/object" failed the assert in sacred.config.utils.assert_is_valid_key. Finally, it adds a minimal test suite for the benchmarking configs. This commit makes progress on testing, but still does not test that all the benchmarking configs work. Running all the configs with the fast configs applied is too slow. Calling sacred's print_config command for all the configs is also too slow.
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.
LGTM too. Thanks for reviewing ernestum!
#653) * Fix benchmarking configs + Add a minimal test suite for those configs. This commit patches in the changes from PR #650. It also fixes an error in the dagger configs by replacing "py/object" with "py/type". "py/object" failed the assert in sacred.config.utils.assert_is_valid_key. Finally, it adds a minimal test suite for the benchmarking configs. This commit makes progress on testing, but still does not test that all the benchmarking configs work. Running all the configs with the fast configs applied is too slow. Calling sacred's print_config command for all the configs is also too slow. * Update the tests for benchmarking configs so that they do not require MuJoCo. * Remove unused global in test_benchmarking.py * Test all the benchmarking configs using print_config. Avoid the overhead of subprocess by running the print_config using the experiment's run method. Also, use a path relative to the script for BENCHMARKING_DIR instead of creating a path and then checking if it exists. * Minor fixes Co-authored-by: Adam Gleave <[email protected]>
Description
Added
demonstrations.rollout_typein all the configs to download rollouts from the huggingface hub. Also, updated config key names changed in #604.Testing
Tested the configs locally using:
python -m imitation.scripts.<train_script> <algo> with benchmarking/<config_name>.json