Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DirectML version 1.7.0 /1.8.0 cause some conv2d cases get wrong result

See original GitHub issue

I find that the microsoft.ai.directml.1.7.0 and microsoft.ai.directml.1.8.0 will cause some conv2d cases get wrong result. I provide one case to reproduce the issue, please refer to my branch for the sample code. Depend on PR#232 which can fix build issue when doing python setup.py install.

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

Jamathercommented, Apr 25, 2022

Can you provide us some information about your hardware and drivers so we can reproduce the issue? Also, does the issue occur if you use DML_EXECUTION_FLAG_DISABLE_META_COMMANDS? Thanks!

0reactions

mingmingtasdcommented, May 6, 2022

Thanks so much! I verified yet, close this issue. @Jamather @fdwr @huningxin

Top Results From Across the Web

DirectML version history | Microsoft Learn

In this article. Version table; Selecting a DirectML target version; DirectML version versus feature level; See also.

Failed to get convolution algorithm. This is probably because ...

I've seen this error message for three different reasons, with different solutions: 1. You have cache issues. I regularly work around this ...

onnxruntime-directml - PyPI

ONNX Runtime is a runtime accelerator for Machine Learning models.

Windows - DirectML | onnxruntime

DirectML Execution Provider. The DirectML Execution Provider is a component of ONNX Runtime that uses DirectML to accelerate inference of ONNX models.

DirectML - bytemeta

DirectML repo issues. ... DirectML 1.8.2 depthwise convolution slow? ... DirectML version 1.7.0 /1.8.0 cause some conv2d cases get wrong result.