Fix docstring for log_interval
to differentiate between on-policy/off-policy logging frequency
#1855
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.
Description
log_interval
in the base class.Motivation and Context
log_interval
parameter of PPO'slearn
method as the "number of episodes before logging".log_interval
*n_steps
steps of rollout collection (notlog_interval
episodes as the documentation describes.) (See Issue PPO log interval on Stable baselines 3. #1847)learn
method insidebase_class.py
which I have updated to differentiate howlog_interval
is employed for on-policy v/s offpolicy.Types of changes
Checklist
make format
(required)make check-codestyle
andmake lint
(required)make pytest
andmake type
both pass. (required)make doc
(required)Note: You can run most of the checks using
make commit-checks
.Note: we are using a maximum length of 127 characters per line