-
Notifications
You must be signed in to change notification settings - Fork 326
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
[Algorithm] Update DQN example #1512
Conversation
…te_dqn_example # Conflicts: # examples/dqn/dqn_carpole.py
Update dqn example
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, some minor comments
examples/dqn/dqn_carpole.py
Outdated
@@ -0,0 +1,171 @@ | |||
""" | |||
DQN Benchmarks: CartPole-v1 |
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.
Benchmarks in the repo is intended for runtime benchmark.
I would call this evaluation. At the end of the day, I think that what we will want is the following directory tree:
torchrl/
├── benchmarks/
│ ├── component_x/
│ │ ├── benchmark_workflow_1/
│ │ ├── benchmark_workflow_2/
│ │ └── ...
│ ├── algorithm_y/
│ │ ├── benchmark_workflow_1/
│ │ ├── benchmark_workflow_2/
│ │ └── ...
│ └── ...
├── evaluation/
│ ├── component_x/
│ │ ├── evaluation_metrics_1/
│ │ ├── evaluation_metrics_2/
│ │ └── ...
│ ├── algorithm_y/
│ │ ├── evaluation_metrics_1/
│ │ ├── evaluation_metrics_2/
│ │ └── ...
│ └── ...
└── ...
…into update_dqn_example
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/rl/1512
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (9 Unrelated Failures)As of commit 97e7aa5 with merge base 25bd8a5 (): FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@albertbou92 the example CI is failing bc we did not update the runs there |
Description
Reproduce known DQN benchmarks.
Motivation and Context
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
You can use the syntax
close #15213
if this solves the issue #15213Types of changes
What types of changes does your code introduce? Remove all that do not apply:
Checklist
Go over all the following points, and put an
x
in all the boxes that apply.If you are unsure about any of these, don't hesitate to ask. We are here to help!