wai-quantum: the tensor-engine member's kernel compiles for a device #302

Merged

dcharlot merged 1 commit from wai/tensor-engine-device-compile into main 2026-10-17 16:52:17 -04:00

Conversation 0 Commits 1 Files changed 2 +43 -13

dcharlot commented 2026-10-17 11:18:00 -04:00

Owner

Copy link

What

The tensor-engine member's helper compiled its kernel for the simulator only. On a device, every test of the member failed at the first request with failed to resolve name 'nl.ndarray'.

• Cause. The kernel was defined inside main(), with the kernel toolchain imported there. The simulator runs the kernel as Python, so the names resolved. Compiling for a device traces the kernel's source and resolves its names in the kernel's module, where they were absent.
• Fix. The kernel now sits at module level. main() still imports the toolchain after the target is chosen (the toolchain reads the target at import), but binds it as module globals.
• Second fix, found on the way. Compiling for a device runs the toolchain's compiler from PATH. The interpreter the member is given (WAI_QUANTUM_TENSOR_ENGINE_PYTHON) need not be on PATH, and in that case the compiler is launched as None. For a device target, the helper now puts its interpreter's directory first on PATH.

Checked

• Off the device, with the toolchain's own compiler at the pinned version, in a clean container:
  • before the fix, the error reproduces exactly;
  • after it, the kernel compiles for the device target, and the request stops only where execution needs the device's runtime.
• The simulator path answers a request as before.
• The repository checks pass: comparative prose, vanity metrics, public names, lockfiles, workflow concurrency, tests in CI, orphan sources.

The run on the device itself follows this PR.

🤖 Generated with Claude Code

## What The tensor-engine member's helper compiled its kernel for the simulator only. On a device, every test of the member failed at the first request with `failed to resolve name 'nl.ndarray'`. - **Cause.** The kernel was defined inside `main()`, with the kernel toolchain imported there. The simulator runs the kernel as Python, so the names resolved. Compiling for a device traces the kernel's source and resolves its names in the kernel's module, where they were absent. - **Fix.** The kernel now sits at module level. `main()` still imports the toolchain after the target is chosen (the toolchain reads the target at import), but binds it as module globals. - **Second fix, found on the way.** Compiling for a device runs the toolchain's compiler from `PATH`. The interpreter the member is given (`WAI_QUANTUM_TENSOR_ENGINE_PYTHON`) need not be on `PATH`, and in that case the compiler is launched as `None`. For a device target, the helper now puts its interpreter's directory first on `PATH`. ## Checked - Off the device, with the toolchain's own compiler at the pinned version, in a clean container: - before the fix, the error reproduces exactly; - after it, the kernel compiles for the device target, and the request stops only where execution needs the device's runtime. - The simulator path answers a request as before. - The repository checks pass: comparative prose, vanity metrics, public names, lockfiles, workflow concurrency, tests in CI, orphan sources. The run on the device itself follows this PR. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 1 commit 2026-10-17 11:18:01 -04:00

wai-quantum: the tensor-engine member's kernel compiles for a device ... adc86f0175

The helper defined its kernel inside main() and imported the kernel
toolchain there. The simulator runs the kernel as Python and found the
names; compiling for a device traces the kernel's source and resolves its
names in the kernel's module, so it found none ("failed to resolve name
'nl.ndarray'") and every device test failed at the first request. The
kernel now sits at module level; main() binds the toolchain as module
globals after the target is chosen.

Compiling for a device also runs the toolchain's compiler from PATH, and
the interpreter the member is given need not be on it, so the helper puts
that interpreter's directory first on PATH for a device target.

Checked off the device with the toolchain's compiler: the kernel compiles
for the device target; the simulator path is unchanged.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot merged commit d244ff7bd4 into main 2026-10-17 16:52:17 -04:00

dcharlot referenced this pull request from a commit 2026-10-17 16:52:18 -04:00

Merge pull request 'wai-quantum: the tensor-engine member's kernel compiles for a device' (#302) from wai/tensor-engine-device-compile into main

dcharlot referenced this pull request from a commit 2026-10-18 00:40:02 -04:00

Merge origin/main into wai/d2c-m8; CHANGELOG keeps every entry

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Transaction-Science/open-standards!302

No description provided.