Add support for shot-wise output for IonQ jobs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- quantum-computing
Research direction
Start by reviewing pull request #3535, which the issue identifies as the implementation. Check whether it requests the shot-wise endpoint only when requested and avoids it for ideal simulations; completion means those behaviors are reviewed and validated.
Written by the indexing model from the issue text.
Description
Summary: adds memory argument to support shot-wise output.
Details and comments:
- need to get shot-wise endpoint only when requested
- do not attempt shot-wise for ideal simulations
This feature is implemented here: https://github.com/NVIDIA/cuda-quantum/pull/3535, need review please.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 455
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/cuda-quantum
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA/cuda-quantum#5424 ·
-
[python] Kernel with a return only inside a dynamic-bound loop compiles without a return-type check Openstale-notified
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
NVIDIA/cuda-quantum#5369 · 2 comments ·
-
bug Exalate stale-notified
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NVIDIA/cuda-quantum#5361 ·
-
bug Exalate stale-notified
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
NVIDIA/cuda-quantum#5356 ·
-
stale-notified
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NVIDIA/cuda-quantum#5353 ·
All issues in NVIDIA/cuda-quantum
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·