From fda818463b6d428da03d074a10733a4aeebae5ca Mon Sep 17 00:00:00 2001 From: Vincent Moens Date: Thu, 1 Aug 2024 02:15:16 +0100 Subject: [PATCH] Fix torchrl and tensordict requirements (#2986) --- .ci/docker/requirements.txt | 5 ++--- intermediate_source/pinmem_nonblock.py | 2 +- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/.ci/docker/requirements.txt b/.ci/docker/requirements.txt index e44feb39e2..00cf2f2103 100644 --- a/.ci/docker/requirements.txt +++ b/.ci/docker/requirements.txt @@ -28,9 +28,8 @@ tensorboard jinja2==3.1.3 pytorch-lightning torchx -# TODO: use stable 0.5 when released --e git+https://github.com/pytorch/rl.git#egg=torchrl --e git+https://github.com/pytorch/tensordict.git#egg=tensordict +torchrl==0.5.0 +tensordict==0.5.0 ax-platform>==0.4.0 nbformat>==5.9.2 datasets diff --git a/intermediate_source/pinmem_nonblock.py b/intermediate_source/pinmem_nonblock.py index 78e57b6cf1..fa69507a0e 100644 --- a/intermediate_source/pinmem_nonblock.py +++ b/intermediate_source/pinmem_nonblock.py @@ -556,7 +556,7 @@ def pin_copy_to_device_nonblocking(*tensors): # CUDA-enabled device. # # In summary, copying data from CPU to GPU is safe when using ``non_blocking=True``, but for any other direction, -# ``non_blocking=True`` can still be used but the user must make sure that a device synchronization is executed after +# ``non_blocking=True`` can still be used but the user must make sure that a device synchronization is executed before # the data is accessed. # # Practical recommendations