Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WinMLRunner - remove 5D block on GPU (bug) #324

Closed
2 tasks
fdwr opened this issue Jul 13, 2020 · 1 comment
Closed
2 tasks

WinMLRunner - remove 5D block on GPU (bug) #324

fdwr opened this issue Jul 13, 2020 · 1 comment
Assignees

Comments

@fdwr
Copy link
Contributor

fdwr commented Jul 13, 2020

Current behavior

WinMLRunner rejects 5D tensors, with the message "Input feature input shape is too large. GPU path only accepts tensor dimensions <= 4 : 5", even though DirectML supports 5D tensors (and will likely support more than that too).

https://github.com/microsoft/Windows-Machine-Learning/blob/master/Tools/WinMLRunner/src/Run.cpp#L296

Expected behavior

WinMLRunner should just let any dimension count through - let the API decide if it is supported or not.

Minimal reproduction of the problem with instructions

Any model with 5D bindings.

WinMLRunner.exe -gpu -model unet3d.channels_first.keras2onnx.onnx

(source is models.zip from here: #215)

Environment

Windows Build Number: 18363.900

App min and target version: Current master, commit 8ca3e52 on 2019 Oct 15

OS Version (Server, IoT Core, Desktop, etc): Desktop

Graphics Driver version:

DxDiag:

WinMLTools specific:
- Source training framework: (e.g. CoreML, Scikit-learn, …)
- WinMLTools version

Visual Studio

  • 2017 (version: NA)
  • 2017 Preview (version: NA)
@ryanlai2
Copy link
Contributor

Released WinMLRunner with bug fix: https://github.com/microsoft/Windows-Machine-Learning/releases/tag/1.2.1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants