-
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
[Feature] Add modules.OrnsteinUhlenbeckProcessModule
#2297
[Feature] Add modules.OrnsteinUhlenbeckProcessModule
#2297
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/rl/2297
Note: Links to docs will display an error until the docs builds have been completed. ❌ 11 New Failures, 1 Pending, 2 Unrelated FailuresAs of commit 04b1511 with merge base c4b2eb0 (): NEW FAILURES - The following jobs have failed:
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. |
modules.OrnsteinUhlenbeckProcessModule
modules.OrnsteinUhlenbeckProcessModule
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
nit: Since we want to deprecate the OU wrapper, can you add a deprecation warning? 2 releases from 0.5, so it will be in 0.7!
Thanks!
OrnsteinUhlenbeckProcessModule | ||
OrnsteinUhlenbeckProcessWrapper |
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.
OrnsteinUhlenbeckProcessModule | |
OrnsteinUhlenbeckProcessWrapper | |
OrnsteinUhlenbeckProcessModule |
since we want to deprecate it
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.
hmm upon reflection, let's keep this one, people may still see it in their code
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.
Yeah I'd think it's typically a good idea to keep the old documentation and only remove it at the point when the deprecated feature is actually removed
f7ca3f5
to
04b1511
Compare
I've added the deprecation warning |
Description
Add
OrnsteinUhlenbeckProcessModule
, which serves the same purpose asOrnsteinUhlenbeckProcessWrapper
, but derives fromTensorDictModuleBase
rather thanTensorDictModuleWrapper
Motivation and Context
part of #2295
Types 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!