Merge pull request #1224 from Unity-Technologies/release-v0.5

Release v0.5

Author: Deric Pang

.gitignore

@@ -1,27 +1,30 @@
-/MLAgentsSDK/[Ll]ibrary/
-/MLAgentsSDK/[Tt]emp/
-/MLAgentsSDK/[Oo]bj/
-/MLAgentsSDK/[Bb]uild/
-/MLAgentsSDK/[Bb]uilds/
-/MLAgentsSDK/[Pp]ackages/
-/MLAgentsSDK/[Uu]nity[Pp]ackage[Mm]anager/
-/MLAgentsSDK/Assets/AssetStoreTools*
-/MLAgentsSDK/Assets/Plugins*
-/MLAgentsSDK/Assets/Gizmos*
+/UnitySDK/[Ll]ibrary/
+/UnitySDK/[Tt]emp/
+/UnitySDK/[Oo]bj/
+/UnitySDK/[Bb]uild/
+/UnitySDK/[Bb]uilds/
+/UnitySDK/[Pp]ackages/
+/UnitySDK/[Uu]nity[Pp]ackage[Mm]anager/
+/UnitySDK/Assets/AssetStoreTools*
+/UnitySDK/Assets/Plugins*
+/UnitySDK/Assets/Gizmos*
 
 # Tensorflow Model Info
 /models
 /summaries
 
+# Training environments
+/envs
+
 # Environemnt logfile
-*MLAgentsSDK.log
+*UnitySDK.log
 
 # Visual Studio 2015 cache directory
-/MLAgentsSDK/.vs/
+/UnitySDK/.vs/
 
 # Autogenerated VS/MD/Consulo solution and project files
-/MLAgentsSDKExportedObj/
-/MLAgentsSDK.consulo/
+/UnitySDKExportedObj/
+/UnitySDK.consulo/
 *.csproj
 *.unityproj
 *.sln
@@ -38,7 +41,7 @@
 *.pidb.meta
 
 # Unity3D Generated File On Crash Reports
-/MLAgentsSDK/sysinfo.txt
+/UnitySDK/sysinfo.txt
 
 # Builds
 *.apk
@@ -49,10 +52,10 @@
 *.x86
 
 # Tensorflow Sharp Files
-/MLAgentsSDK/Assets/ML-Agents/Plugins/Android*
-/MLAgentsSDK/Assets/ML-Agents/Plugins/iOS*
-/MLAgentsSDK/Assets/ML-Agents/Plugins/Computer*
-/MLAgentsSDK/Assets/ML-Agents/Plugins/System*
+/UnitySDK/Assets/ML-Agents/Plugins/Android*
+/UnitySDK/Assets/ML-Agents/Plugins/iOS*
+/UnitySDK/Assets/ML-Agents/Plugins/Computer*
+/UnitySDK/Assets/ML-Agents/Plugins/System*
 
 # Generated doc folders
 /docs/html

CODE_OF_CONDUCT.md

@@ -67,7 +67,8 @@ members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct/
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct/
 
 [homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -1,54 +1,56 @@
 # Contribution Guidelines
 
-Thank you for your interest in contributing to the ML-Agents toolkit! We are incredibly
-excited to see how members of our community will use and extend the ML-Agents toolkit.
-To facilitate your contributions, we've outlined a brief set of guidelines
-to ensure that your extensions can be easily integrated.
+Thank you for your interest in contributing to the ML-Agents toolkit! We are
+incredibly excited to see how members of our community will use and extend the
+ML-Agents toolkit. To facilitate your contributions, we've outlined a brief set
+of guidelines to ensure that your extensions can be easily integrated.
 
-### Communication
+## Communication
 
-First, please read through our [code of conduct](CODE_OF_CONDUCT.md), 
-as we expect all our contributors to follow it.
+First, please read through our [code of conduct](CODE_OF_CONDUCT.md), as we
+expect all our contributors to follow it.
 
-Second, before starting on a project that you intend to contribute
-to the ML-Agents toolkit (whether environments or modifications to the codebase), 
-we **strongly** recommend posting on our 
-[Issues page](https://github.com/Unity-Technologies/ml-agents/issues) and
-briefly outlining the changes you plan to make. This will enable us to provide
-some context that may be helpful for you. This could range from advice and 
-feedback on how to optimally perform your changes or reasons for not doing it.
+Second, before starting on a project that you intend to contribute to the
+ML-Agents toolkit (whether environments or modifications to the codebase), we
+**strongly** recommend posting on our
+[Issues page](https://github.com/Unity-Technologies/ml-agents/issues)
+and briefly outlining the changes you plan to make. This will enable us to
+provide some context that may be helpful for you. This could range from advice
+and feedback on how to optimally perform your changes or reasons for not doing
+it.
 
 Lastly, if you're looking for input on what to contribute, feel free to
 reach out to us directly at [email protected] and/or browse the GitHub
 issues with the `contributions welcome` label.
 
-### Git Branches
+## Git Branches
 
-Starting with v0.3, we adopted the 
+Starting with v0.3, we adopted the
 [Gitflow Workflow](http://nvie.com/posts/a-successful-git-branching-model/).
-Consequently, the `master` branch corresponds to the latest release of 
+Consequently, the `master` branch corresponds to the latest release of
 the project, while the `develop` branch corresponds to the most recent, stable,
 version of the project.
 
 Thus, when adding to the project, **please branch off `develop`**
 and make sure that your Pull Request (PR) contains the following:
+
 * Detailed description of the changes performed
-* Corresponding changes to documentation, unit tests and sample environments 
-(if applicable)
+* Corresponding changes to documentation, unit tests and sample environments (if
+  applicable)
 * Summary of the tests performed to validate your changes
 * Issue numbers that the PR resolves (if any)
 
-### Environments
+## Environments
 
-We are also actively open to adding community contributed environments as 
-examples, as long as they are small, simple, demonstrate a unique feature of 
-the platform, and provide a unique non-trivial challenge to modern 
+We are also actively open to adding community contributed environments as
+examples, as long as they are small, simple, demonstrate a unique feature of
+the platform, and provide a unique non-trivial challenge to modern
 machine learning algorithms. Feel free to submit these environments with a
-PR explaining the nature of the environment and task. 
+PR explaining the nature of the environment and task.
 
-### Style Guide
+## Style Guide
 
-When performing changes to the codebase, ensure that you follow the style
-guide of the file you're modifying. For Python, we follow 
-[PEP 8](https://www.python.org/dev/peps/pep-0008/). For C#, we will soon be
-adding a formal style guide for our repository.
+When performing changes to the codebase, ensure that you follow the style guide
+of the file you're modifying. For Python, we follow
+[PEP 8](https://www.python.org/dev/peps/pep-0008/).
+For C#, we will soon be adding a formal style guide for our repository.

Dockerfile

@@ -122,16 +122,11 @@ RUN apt-get update && apt-get -y upgrade
 # xvfb is used to do CPU based rendering of Unity
 RUN apt-get install -y xvfb
 
-
-COPY ml-agents/requirements.txt .
-RUN pip install --trusted-host pypi.python.org -r requirements.txt
-
-COPY README.md .
 COPY ml-agents /ml-agents
 WORKDIR /ml-agents
 RUN pip install .
 
 # port 5005 is the port used in in Editor training.
 EXPOSE 5005
 
-ENTRYPOINT ["python", "mlagents/learn.py"]
+ENTRYPOINT ["mlagents-learn"]