* Torch setup.py
* Set torch to default
* Make torch default in setup.py
* Remove indents
* Remove other instances of TF being used
* Add tensorboard to setup.py
* Adding correst setup commands for verifying torch is installed (#4524)
* Adding correst setup commands for verifying torch is installed
* Editing the test_requirments to add tf and remove torch
* Develop torchdefault raise outside setup (#4530)
* Torch not imported error to raise at first usage
* Torch not imported error to raise at first usage
* [refactor] Use PyTorch TensorBoard utils (#4518)
* Convert stats writer to use PyTorch TB support
* Use common function to print params
* Update test
* Bump tensorboard to 1.15 to fix the tests
* putting tensorboard 1.15.0 as min version requirement
Co-authored-by: vincentpierre <vincentpierre@unity3d.com>
* [Docs] Initial documentation changes for making Torch the default (#4561)
* Initial commit
* Forgotten doc
* Removing the `Installation-Anaconda-Windows.md` as it is deprecated
* Readding the depreacted Installation-Anaconda-Windows.md but leaving it unchanged
* more references to tensorflow removed
* Update README.md
Co-authored-by: Ervin T. <ervin@unity3d.com>
* Change references to .nn to .onnx in docs (#4583)
Co-authored-by: Ervin T. <ervin@unity3d.com>
* [refactor] Add --tensorflow, enable Torch as default setting (#4582)
* Add --tensorflow option
* Switch framework to Pytorch default
* Update changelog
* Re-add --torch
* Edit warning
* Modify Yamato tests (#4584)
* Don't check for PB file in Yamato inference
* Only run inference on ONNX
* Update docs/Unity-Inference-Engine.md with correct tf2onnx versions
Co-authored-by: Chris Elion <chris.elion@unity3d.com>
* Add reward signal class comments
* More descriptive import of is_available
* Updated installation instructions for PyTorch
* More reward signal comments
* More Windows instructions
Co-authored-by: Vincent-Pierre BERGES <vincentpierre@unity3d.com>
Co-authored-by: Chris Elion <chris.elion@unity3d.com>
* Updates the ML-Agents Docker image based on things
we have learned from training in the cloud.
* Automatically pushes the image to our own GCP projects
on each release.
The goal of our issue templates was that all users should choose one
of these templates and fill it out to begin a discussion or report a
bug / feature request. The "blank issues" option is a way around this,
and this change disables it as an option.
* Update issue templates
Added three issue template types:
* bug reports
* feature requests
* discussion and general questions
The focus is on getting sufficient information in bug requests to help us reproduce the issue and communicating that we will be unable to generally support custom environments and participate in general discussions.
