NVIDIA / NVIDIA/cuda-quantum

Kernel accepts np.array as an arg only if preceded by another arg

Open
#3,477 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale-notified
Dominant language
C++
Stars
1.1k
Forks
456
Avg merge
1d 22h
Merged PRs (30d)
165

Description

Required prerequisites
  • Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
  • Make sure you've read the documentation. Your issue may be addressed there.
  • Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
  • If possible, make a PR with a failing test to give us a starting point to work on!
Describe the bug

When I pass a numpy array as an arg to a kernel, I get the following error.

RuntimeError: error: Invalid runtime argument type. Argument of type <class 'float'> was provided, but list[float] was expected.

However, this error disappears when there is another arg preceding the np.array.

Steps to reproduce the bug

The following code gives an error:

import cudaq
import numpy as np

@cudaq.kernel
def kernel( b: np.array):
    q = cudaq.qvector(2)
    x(q[0])

bvec = np.zeros(8)
result = cudaq.sample(kernel, bvec).expectation()

Error:

RuntimeError: error: Invalid runtime argument type. Argument of type <class 'float'> was provided, but list[float] was expected.

However, the following code does NOT produce an error.

import cudaq
import numpy as np

@cudaq.kernel
def kernel( np: int, b: np.array):
    q = cudaq.qvector(2)
    x(q[0])

bvec = np.zeros(8)
result = cudaq.sample(kernel, 2, bvec).expectation()
Expected behavior

Should be able to pass a np array as an arg to a kernel.

Is this a regression? If it is, put the last known working version (or commit) here.

Not a regression

Environment
  • CUDA-Q version:
  • Python version:
  • C++ compiler:
  • Operating system:
Suggestions

No response

Contributor guide

Open the contributing guide

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

Start by running the two Python reproductions from the issue and compare argument handling when the NumPy array is first versus second. The work is done when the single-array kernel accepts bvec without the invalid runtime argument error, while the existing multi-argument example continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
numpy, python
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.