Skip to content

Tags: lgtm-migrator/DALI

Tags

v1.20.0-dev

Toggle v1.20.0-dev's commit message
Update VERSION to 1.20.0dev

Signed-off-by: Kamil Tokarski <[email protected]>

v1.19.0

Toggle v1.19.0's commit message
Fix TL0_python-self-test-base-cuda CUDA setup (NVIDIA#4362)

- fixes the changes and restoration of the previous cuda env setup
  in TL0_python-self-test-base-cuda test

Signed-off-by: Janusz Lisiecki <[email protected]>

v1.18.0

Toggle v1.18.0's commit message
Enable CUDA 11.8 and Hopper support (NVIDIA#4308)

- adds CUDA 11.8 based build
- extend the image decoder to support H100 Hopper

Signed-off-by: Janusz Lisiecki <[email protected]>

v1.17.0

Toggle v1.17.0's commit message
Enable CUDA 11.8 and Hopper support (NVIDIA#4308)

- adds CUDA 11.8 based build
- extend the image decoder to support H100 Hopper

Signed-off-by: Janusz Lisiecki <[email protected]>

v1.19.0-dev

Toggle v1.19.0-dev's commit message
Update VERSION to 1.19.0dev

Signed-off-by: Kamil Tokarski <[email protected]>

v1.18.0-dev

Toggle v1.18.0-dev's commit message
Update VERSION to 1.18.0dev

Signed-off-by: Kamil Tokarski <[email protected]>

v1.16.1

Toggle v1.16.1's commit message
Fix device pick in Numpy reader tests (NVIDIA#4104)

Signed-off-by: Albert Wolant <[email protected]>

v1.16.0

Toggle v1.16.0's commit message

Verified

This commit was signed with the committer’s verified signature. The key has expired.
JanuszL Janusz Lisiecki
Fix lack of reset when `iter()` is called on the DALI framework itera…

…tor (NVIDIA#4048)

- the DALI framework iterator when `iter()` is called checks if any
  data has been consumed yet. If it hasn't it doesn't reset to prevent
  improper operation when DALI FW iterator prefetches the first batch after
  creation, and invocation of something like `enumerate(iterator)`,
  would reset the iterator and extend the length of the first epoch
  (prefetched data in the FW iterator would be added to the freshly
  reset iterator). The flag that is set when any data has been consumed
  was set only in the `next()` method and not `__next__()`. This PR
  fixes this problem and adjusts the test

Signed-off-by: Janusz Lisiecki <[email protected]>

v1.17.0-dev

Toggle v1.17.0-dev's commit message
Update VERSION to 1.17.0dev

Signed-off-by: Kamil Tokarski <[email protected]>

v1.15.0

Toggle v1.15.0's commit message
Fix dltensor operator tests (NVIDIA#3984)

* Fix dltensor operator tests (missing imports)
* Fix backend_impl shadowing Pipeline import

Signed-off-by: Kamil Tokarski <[email protected]>