WinMLRunner v1.3.0

General

• Diagnostic warnings are emitted when operators fallback to CPU when the caller specified GPU.
• New -logCPUFallback command line argument added. This argument will output addition information about why CPU fallback occured.

Dependencies

• DirectML version bumped to 1.8.2.
• Microsoft.AI.MachineLearning version bumped to 1.11.
• OnnxRuntime version bumped to 1.11.

WinMLRunner v1.2.2

This change removes the ability of WinMLRunner.exe to load Windows.AI.MachineLearning.dll locally if the DLL is within the same directory as the executable. Instead, MicrosoftMLRunner.exe should be used for loading Microsoft.AI.MachineLearning.dll within the same directory. More details below.

Using Microsoft.AI.Machinelearning NuGet

MicrosoftMLRunner.exe uses Microsoft.AI.MachineLearning.dll in the immediate directory of the executable instead of loading Windows.AI.MachineLearning.dll from System32 (that is for WinMLRunner). MicrosoftMLRunner is useful to compare performance with an older version of WinML or to test a newer version of WinML's NuGet. For more information, please reference Microsoft.AI.MachineLearning NuGet page.

WinMLRunner v1.2.1.2

Fixes bug: #324

WinML Dashboard v0.7.0

• Support to convert to opset10 models
• Updated WinMLRunner

WinMLRunner v1.2.1.1

New Features:

• -Tensor [function] : load the input as a tensor, with optional function for input preprocessing

  • Optional function arguments:
    • Identity(default) : No input transformations will be performed
    • Normalize : float scale factor and comma separated per channel means and stddev for normalization.

• Example Usage:

• WinMLRunner.exe -model ./densenet121.onnx -Tensor Normalize 255 0.485,0.456,0.406 0.229,0.224,0.225 -CPU -SaveTensorData First -PerIterationPath <tensorDataPath>

WinMLRunner v1.2.0.2

New Features:

• Evaluating folder of images is now available with -inputimagefolder flag.
  example:

.\WinMLRunner.exe -model .\SqueezeNet.onnx -inputimagefolder .\images\

• Standard deviation of metrics are now written to performance files

Updates and fixes:

• DxCore API calls have been updated to latest.

WinMLDashboard v0.6.1 (Preview)

New Features:

• Model Debugging Support
  • You can now capture and visualize intermediate data as it flows through your model when you run it through WinMLDashboard
  • More information can be found here: https://github.com/microsoft/Windows-Machine-Learning/blob/master/Tools/WinMLDashboard/README.md
• Other various UI Changes

Bug Fixes

• Security fixes

WinMLRunner v1.2.0.1

New change:

Delayload DXGI and D3d11.dll with DxCore Path

WinMLRunner v1.2.0.0

New Features!

• DxCore support to select compute device. Use the functionality with :
  • -GPUAdapterName : run model on GPU specified by its name. NOTE: Please only use this flag on DXCore supported machines.
• Models with Image Denotation as Input are now supported
• Tensors can now be bound backed by GPU memory.
• Performance File metadata can be added with: AddPerformanceFileMetadata(const std::string& key, const std::string& value). This is only exposed when WinMLRunner is consumed as a static library.

Bug Fixes:

• Maximum -iterations now bumped up to 1024 iterations.
• Outputting performance files now has more robust way to specify destination.
  • -BaseOutputPath [<fully qualified path>] : base output directory path for results, default to cwd

WinMLRunner v1.0.1.0

New Features:

• Added new flag:
  -TopK <number>: print top <number> values in the result. Default to 1
• PIX programmatic capture!
  • PIX is a tool to capture Direct 3D 12 GPU work. With this new release, WinMLRunner will automatically capture PIX traces if it is launched with PIX.
    • 1st Frame: Will contain PIX captures for Session Creation and 1st iteration Bind, 1st iteration Evaluate
    • Nth Frame: Will contain PIX captures for Nth iteration Bind and Nth iteration Evaluate
  • More information about PIX here.
• .jpeg is now a supported input file format.

Bug Fixes

• If multiple compute devices are specified, WinMLRunner will continue to run the remaining devices even if the the model run fails on one of the devices.
• Print out error message if the input is an unsupported file extension.