[Feature Request] give users a way to provide their own exploration noise function?
See original GitHub issue🚀 Feature
Let the users provide, if they want, a function that is used to sample the exploration noise. Possibly an API something like the following (it may be very naive though), so that it can collect data from the agent and its policies, or take any arguments the users want:
def user_noise(agent, *args, **kwargs)
"""this user_noise function will be called at each step to generate the exploration noise"""
return exploration_noise
Motivation
The gSDE paper is extremely interesting, however, in some cases, using the before last policy layer may be a suboptimal choice; offering an API way to set other more specific exploration noise functions that depend on the agent internals exactly in the way the user wants would be great.
Issue Analytics
- State:
- Created a year ago
- Comments:18 (4 by maintainers)
Top Results From Across the Web
User-Personalization recipe - AWS Documentation
This allows Amazon Personalize to gauge item quality based on new interactions for already explored items and continually update item exploration.
Read more >Feature Requests: What are they and how to manage them
Feature requests are a form of product feedback you may frequently encounter as a SaaS product manager. They typically come in the form...
Read more >Feature Requests - Audacity Wiki
Double-click any point in a "silence " to automatically select the complete silence - useful for voice editing.
Read more >Solved: Re: How to avoid bothering teachers with student g ...
This sounds like it would make a great feature request. I searched around on this and found some related ideas that had been...
Read more >Play background sounds on iPhone to mask environmental ...
On iPhone, play calming sounds to mask unwanted environmental noise and help minimize distractions so you can focus or rest.
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
I understand your need. Have you considered the following workaround:
The intuition behind not using action noise for on-policy agents is that an on-policy algorithm learns from the actions it has taken. However, if you add noise to the action, it is no longer “taken by the agent” but by the agent augmented with noise. So you introduce a bias.