Quantum Computer symmetrize_readout argument is unused.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- quantum-computing
Research direction
Start by locating the QuantumComputer constructor and the run and run_symmetrized_readout methods referenced in the issue. Determine whether symmetrize_readout should be removed or connected to execution, including the readout discrepancy mentioned with #1003. Done means the argument no longer appears unused and the chosen behavior is covered by the relevant tests.
Written by the indexing model from the issue text.
Description
Pre-Report Checklist
- I am running the latest versions of pyQuil and the Forest SDK
- I checked to make sure that this bug has not already been reported
Issue Description
QuantumComputer accepts an argument symmetrize_readout which appears to do nothing, currently. We should either
- remove it
- check if it is set in
run, and if so automatically userun_symmetrized_readoutwith some defaultsymm_typeinstead. This will probably require dealing with the discrepancy between the two functions in how readout is handled (which maybe needs to be addressed separately anyway? e.g. #1003) - changed from a bool to record
symm_type
I think 1) is most appropriate. This seems like something that should be specified at run time rather than during creation of the QC object.
How to Reproduce
I just noticed that the parameter doesn't seem to be used anywhere.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 358
- Avg merge
- 1d 58m
- Merged PRs (30d)
- 4
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 rigetti/pyquil
-
documentation :memo:
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug :bug:
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
-
bug :bug: documentation :memo: v3
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
bug :bug:
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
devops :rocket:
Difficulty 5/5 Over a week Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100