-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Comparing changes
Open a pull request
base repository: Unity-Technologies/ml-agents
base: a277771
head repository: Unity-Technologies/ml-agents
compare: d24a865
- 7 commits
- 24 files changed
- 7 contributors
Commits on Sep 16, 2025
-
[Bugfix] Fix CUDA/CPU mismatch in threaded training (#6245)
* Ensure tensors use default device in torch policy and utils --------- Co-authored-by: maryam-zia <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for a83b3b8 - Browse repository at this point
Copy the full SHA a83b3b8View commit details
Commits on Sep 17, 2025
-
Fix visual observation tensor indexing for Unity inference. (#6239)
This change corrects the tensor indexing calculation in TensorExtensions.Index() to properly support CHW (channels-height-width) format used by both Unity's observation writers and ONNX models during inference.
Configuration menu - View commit details
-
Copy full SHA for db4c207 - Browse repository at this point
Copy the full SHA db4c207View commit details -
Update Changelog and test (#6246)
* Update Changelog * Update tests
Configuration menu - View commit details
-
Copy full SHA for d1147c1 - Browse repository at this point
Copy the full SHA d1147c1View commit details
Commits on Oct 22, 2025
-
Add torch version constraint to be equal or less than 2.8.0 to preven…
…t breaking onnx changes in torch 2.9.0 (#6251) * Pin torch version to 2.8.0 to prevent breaking onnx changes in 2.9.0 The ` 2.9.0` version results in an issue finding `onnxscript`. Pinning the `2.8.0` prevent this error. I'm not exactly of the exact root cause but it seems there were some backwards incompatible changes to onnx: https://github.com/pytorch/pytorch/releases/tag/v2.9.0#backwards-incompatible-changes. Stack trace on exiting training: ``` File "C:\Users\Samuel\miniconda3\envs\mlagents\lib\site-packages\mlagents\trainers\torch_entities\model_serialization.py", line 164, in export_policy_model torch.onnx.export( File "C:\Users\Samuel\miniconda3\envs\mlagents\lib\site-packages\torch\onnx\__init__.py", line 282, in export from torch.onnx._internal.exporter import _compat File "C:\Users\Samuel\miniconda3\envs\mlagents\lib\site-packages\torch\onnx\_internal\exporter\_compat.py", line 16, in <module> from torch.onnx._internal.exporter import ( File "C:\Users\Samuel\miniconda3\envs\mlagents\lib\site-packages\torch\onnx\_internal\exporter\_core.py", line 18, in <module> import onnxscript ModuleNotFoundError: No module named 'onnxscript' ``` * Add torch version constraint to be equal or less than 2.8.0 Previously commit forced only 2.8.0, however adding this constraint is a bit nicer, as I see in some of installation docs sometimes torch 2.2.0 is installed: https://github.com/Unity-Technologies/ml-agents/blob/release_22_docs/docs/Installation.md. * Update CHANGELOG.md
Configuration menu - View commit details
-
Copy full SHA for 631901b - Browse repository at this point
Copy the full SHA 631901bView commit details
Commits on Oct 30, 2025
-
Update installation doc (#6242)
* Update com.unity.ml-agents/Documentation~/Installation.md --------- Co-authored-by: manugaursharma <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for bc4d32e - Browse repository at this point
Copy the full SHA bc4d32eView commit details
Commits on Nov 14, 2025
-
* Test macos code signing for binaries * Adding dependency on signing job in pack
Configuration menu - View commit details
-
Copy full SHA for f248e98 - Browse repository at this point
Copy the full SHA f248e98View commit details
Commits on Dec 19, 2025
-
Upgrade ML-Agents to 4.0.1 (#6269)
* Upgrade Inference Engine to 4.1.1 * Update inference engine dependencies * Update CHANGELOG.md * trunk test are unstable changing to 6.3 temporarily * Fixing issue #6268 Co-authored-by: maryam-zia <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d24a865 - Browse repository at this point
Copy the full SHA d24a865View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff a277771...d24a865