ROCm / ROCm/AMDMIGraphX

Run-time Accuracy Debugging ("Debug Tensors")

Open
#3,209 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
333
Forks
150
Avg merge
4d 19h
Merged PRs (30d)
54

Description

It should be possible to enable run-time accuracy debugging, i.e. inspection of values of a tensor, for the purpose of detecting 0s, or NaNs, or any other user-specified condition, for example specified via user provided code (e.g. a lambda) that can execute on the tensor.

It should be possible to disable this functionality at runtime, and in that case, there should be no (or at least minimal) performance penalty, compared to a model compilation with this capability not enabled.

When the user specified condition is satisfied, e.g. a 0, or all zeros in a row, or a NaN is detected in a tensor, a typical flow could be to copy the data to a CPU buffer, and terminate executing the frame.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points; begin by locating the runtime tensor execution and model compilation paths. Define how user conditions are registered, enabled or disabled, how matching tensor data is handled, and how the disabled path avoids a meaningful performance penalty.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
ai
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.