-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Update documentation #199
Update documentation #199
Conversation
Left some minor comments but mostly looks good :). With this amount of text I would run modifications through grammar-check just to be on the safe-side. |
Thanks for the comments =) |
Not really, I just personally copy-paste things to Word or GDocs :'D . Should probably invest in "proper" tools. |
Ran text through GDocs for crude grammar check. From my side this is good to go, feel free to approve and merge if you agree with the changes :) |
* Update doc and add new example * Add save/load replay buffer example * Add save format + export doc * Add example for get/set parameters * Typos and minor edits * Add results sections * Add note about performance * Add DDPG results * Address comments * Fix grammar/wording Co-authored-by: Anssi "Miffyli" Kanervisto <kaneran21@hotmail.com>
Description
closes #7
closes #166
Missing:
NOTE: in the get/set parameters, I used PyTorch native methods, as it was easier and cleaner.
Motivation and Context
Types of changes
Checklist:
make format
(required)make check-codestyle
andmake lint
(required)make pytest
andmake type
both pass. (required)Note: we are using a maximum length of 127 characters per line