Skip to content
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

Python version on Quantum Cloud logs execution twice when NVQ_LOG_LEVEL=trace #1660

Open
4 tasks done
rtvuser1 opened this issue May 10, 2024 · 0 comments
Open
4 tasks done

Comments

@rtvuser1
Copy link

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 running the python version of bernstein-vazirani.py on Quantum Cloud, with the env var set: NVQC_LOG_LEVEL=trace
It appears that the backend is reporting execution twice. Is this expected? The cpp version only reports execution once.
The test below is with 0.7.1, and uses the supplied bernstein_vazirani.py and cpp examples.

Steps to reproduce the bug

python bernstein_vazirani.py --target nvqc
[2024-05-03 00:05:38.296] Submitting jobs to NVQC service with 1 GPU(s). Max execution time: 3600 seconds (excluding queue wait time).
[2024-05-03 00:05:38.567] Posting NVQC request now

================ NVQC Device Info ================
GPU Device Name: "NVIDIA H100 80GB HBM3"
CUDA Driver Version / Runtime Version: 12.2 / 11.8
Total global memory (GB): 79.1
Memory Clock Rate (MHz): 2619.000
GPU Clock Rate (MHz): 1980.000

===== NVQC Execution Timing ======

  • Pre-processing: 193 milliseconds
  • Execution: 20 milliseconds
    ==================================
[2024-05-03 00:05:39.245] Posting NVQC request now

===== NVQC Execution Timing ======

  • Pre-processing: 199 milliseconds
  • Execution: 23 milliseconds
    ==================================
    encoded bitstring = [1, 0, 0, 0, 1]
    measured state = 10001
    Were we successful? True

Expected behavior

Executing the cpp example with --target nvqc and logging set to trace reports Execution Timing just one time, not twice.

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

Not a regression

Environment

  • CUDA Quantum version: 0.7.1
  • Python version: 3.10.12

Suggestions

no

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant