-
Notifications
You must be signed in to change notification settings - Fork 186
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
Circuit drawer retains qubits from previously printed kernel(s) #1400
Comments
Reference C++ sample
Output:
|
I believe that this issue (or something similar to this issue) may also be preventing us from adding tests to the end of |
…#1406) * Fix value error bug with validating mlirTypeFromPyType for np.array Signed-off-by: Alex McCaskey <amccaskey@nvidia.com> * add the test Signed-off-by: Alex McCaskey <amccaskey@nvidia.com> * fix ci failure Signed-off-by: Alex McCaskey <amccaskey@nvidia.com> * Move new test due to issue #1400 --------- Signed-off-by: Alex McCaskey <amccaskey@nvidia.com> Co-authored-by: Ben Howe <bhowe@nvidia.com>
Update: The same behavior is seen in C++ when not in library mode. Test code:
Set
|
I've experienced this again using version 0.8.0. |
This time the incorrect circuits are slightly different than the example above.
|
restarting the python kernel seems to eliminate the error. |
…NVIDIA#1406) * Fix value error bug with validating mlirTypeFromPyType for np.array Signed-off-by: Alex McCaskey <amccaskey@nvidia.com> * add the test Signed-off-by: Alex McCaskey <amccaskey@nvidia.com> * fix ci failure Signed-off-by: Alex McCaskey <amccaskey@nvidia.com> * Move new test due to issue NVIDIA#1400 --------- Signed-off-by: Alex McCaskey <amccaskey@nvidia.com> Co-authored-by: Ben Howe <bhowe@nvidia.com>
Required prerequisites
Describe the bug
When using
cudaq.draw
API to print kernels, the qubits from previously drawn kernel are retained.Redrawing the same kernel repeatedly also keeps concatenating to the qubit count.
Steps to reproduce the bug
Output:
Expected behavior
Expected output:
Is this a regression? If it is, put the last known working version (or commit) here.
Not a regression
Environment
main
as of commit 30e1d3bSuggestions
No response
The text was updated successfully, but these errors were encountered: