Fix: with SAC, a new training batch should be sampled for each gradient step #208
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…nt_step.
DDPG/TD3/SAC for robotics tasks #65
Increasing the number of parallel simulations accelerates the replay buffer data refresh rate in SAC and other off-policy algorithms. However, to fully leverage this increased data collection, the model should be updated more frequently. This can be achieved by increasing
self._gradient_steps
.Issue:
- Current Behavior: The current implementation reuses the same training batch across multiple gradient steps, which can lead to overfitting and inefficient use of the new data collected from parallel simulations.
- Expected Behavior: According to the SAC algorithm implementation, a new training batch should be sampled for each gradient step to ensure diverse and fresh experiences are used for updates.
Fixed Implemented: