[rllib] MADDPG no exploration options applied?
See original GitHub issueIs no exploration (parameter noise, ou exploration) possible/applied to chosen action values as in DDPG in the current version of contrib/MADDPG?
Also, would saving the trained model and restoring it be possible, to subsequently use compute_action
methods to query the trained MADDPG model?
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Algorithms — Ray 2.2.0 - the Ray documentation
The challenge in applying existing Q-learning algorithms to offline RL lies in the overestimation of the Q-function, as well as, the lack of...
Read more >ray.rllib.algorithms.maddpg.maddpg — Ray 2.2.0
"""Contributed port of MADDPG from OpenAI baselines. ... Apply a state preprocessor with spec given by the "model" config option (like other RL...
Read more >Algorithms — Ray 1.13.0
Contextual bandit algorithms typically consist of an action-value model (Q model) and an exploration strategy (epsilon-greedy, UCB, Thompson Sampling etc.).
Read more >RLlib Algorithms — Ray 0.7.5 documentation
"vtrace": False, # == These two options only apply if vtrace: False == # If true, use the Generalized Advantage Estimator (GAE) #...
Read more >RLlib Algorithms — Ray 0.8.7 documentation
No. No. LinUCB, LinTS. torch. Yes +parametric. No. Yes. MADDPG ... "vtrace": False, # == These two options only apply if vtrace: False...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey guys, my schedule just freed up. I’ll fix the action space issue and add exploration myself in the next few days.
On Wed, Feb 12, 2020 at 2:27 PM Justin Terry notifications@github.com wrote:
– Thank you for your time, Justin Terry
Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.
Please feel free to reopen or open a new issue if you’d still like it to be addressed.
Again, you can always ask for help on our discussion forum or Ray’s public slack channel.
Thanks again for opening the issue!