-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Add Migrating.md for v0.9 #2347
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,5 +1,26 @@ | ||||||
| # Migrating | ||||||
|
|
||||||
| ## Migrating from ML-Agents toolkit v0.8 to v0.9 | ||||||
|
|
||||||
| ### Important Changes | ||||||
| * We have changed the way reward signals (including Curiosity) are defined in the | ||||||
| `trainer_config.yaml`. | ||||||
| * When using multiple environments, every "step" as recorded in TensorBoard and | ||||||
| printed in the command line now corresponds to a single step of a single environment. | ||||||
| Previously, each step corresponded to one step for all environments (i.e., `num_envs` steps). | ||||||
|
|
||||||
| #### Steps to Migrate | ||||||
| * If you were overriding any of these following parameters in your config file, remove them | ||||||
| from the top-level config and follow the steps below: | ||||||
| * `gamma` - Define a new `extrinsic` reward signal and set it's `gamma` to your new gamma. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| * `use_curiosity`, `curiosity_strength`, `curiosity_enc_size` - Define a `curiosity` reward signal | ||||||
| and set its `strength` to `curiosity_strength`, and `encoding_size` to `curiosity_enc_size`. Give it | ||||||
| the same `gamma` as your `extrinsic` signal to mimic previous behavior. | ||||||
| See [Reward Signals](Training-RewardSignals.md) for more information on defining reward signals. | ||||||
| * TensorBoards generated when running multiple environments in v0.8 are not comparable to those generated in | ||||||
| v0.9 in terms of step count. Multiply your v0.8 step count by `num_envs` for an approximate comparison. | ||||||
| You may need to change `max_steps` in your config as appropriate as well. | ||||||
|
|
||||||
| ## Migrating from ML-Agents toolkit v0.7 to v0.8 | ||||||
|
|
||||||
| ### Important Changes | ||||||
|
|
||||||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe instead of saying "it has changed in the trainer_config.yaml" (which is one of the yaml file that doesn't have any gail configured), say something like "we have changed the way reward signals (..) are defined in the configuration file, you can refer to gail_config.yaml as an example".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please ignore my previous comment. I just realized that this isn't explaining anything regarding the new features, just how to migrate from using the old features.