Skip to content

Conversation

@shihzy
Copy link
Contributor

@shihzy shihzy commented Apr 11, 2019

Doc review.

  • Went through changes to existing docs this release and made updates.
  • Reviewed new docs - custom protobuf.
  • Added a Training Using Concurrent Unity Instances Page
  • Minor tweaks here and there

@shihzy shihzy requested review from harperj and xiaomaogy April 11, 2019 22:00
* If you intend to make modifications to `ml-agents` or `ml-agents-envs` please check the Installing for Development in the [Installation documentation](Installation.md).

#### Steps to Migrate
* Make sure to remove the `ENABLE_TENSORFLOW` flag in your Unity project settings
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need this in from v0.7 to v0.8.

@xiaomaogy
Copy link
Contributor

Looks good to me aside from the comments. Remove that then merge.

* `--train` – Specifies whether to train model or only run in inference mode.
When training, **always** use the `--train` option.
* `--num-envs` - Specifies the number of parallel environments to collect
* `--num-envs=<n>` - Specifies the number of concurrent, parallel Unity environment instances to collect
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Concurrent and parallel are saying the same thing here.

environment will use the port `(base_port + worker_id)`, where the worker ID
are sequential IDs given to each environment from 0 to `num_envs - 1`.
Defaults to 5005.
* `--base-port` - Specifies the starting port for each concurrent, parallel Unity environment instance. Each instance will use the port `(base_port + worker_id)`, where the `worker_id`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bit confusing: "the starting port for each concurrent, parallel Unity environment instance". This is the starting port from which all other ports are given sequential port numbers. Not the starting port for each.

@harperj
Copy link
Contributor

harperj commented Apr 11, 2019

Couple of comments, but no show stoppers

@eshvk
Copy link
Contributor

eshvk commented Apr 12, 2019

@unityjeffrey Can I squash and merge this?

@shihzy shihzy merged commit 2e945ba into release-v0.8 Apr 12, 2019
@shihzy shihzy deleted the release-v0.8-docs branch April 12, 2019 16:45
LeSphax pushed a commit to LeSphax/ml-agents-1 that referenced this pull request May 3, 2020
* update title caps

* Rename Custom-Protos.md to Creating-Custom-Protobuf-Messages.md

* Updated with custom protobuf messages

* Cleanup against to our doc guidelines

* Minor text revision

* Create Training-Concurrent-Unity-Instances

* Rename Training-Concurrent-Unity-Instances to Training-Concurrent-Unity-Instances.md

* update to right format for --num-envs

* added link to concurrent unity instances

* Update and rename Training-Concurrent-Unity-Instances.md to Training-Using-Concurrent-Unity-Instances.md

* Added considerations section

* Update Training-Using-Concurrent-Unity-Instances.md

* cleaned up language to match doc

* minor updates

* retroactive migration from 0.6 to 0.7

* Updated from 0.7 to 0.8 migration

* Minor typo

* minor fix

* accidentally duplicated step

* updated with new features list
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants