rigetti / rigetti/pyquil

UserWarning: SIMPLE-WARNING: Chip specification contained fidelity 1.0d0 > 1.

Open
#1,004 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug :bug:
Dominant language
Python
Stars
1.5k
Forks
358
Avg merge
1d 58m
Merged PRs (30d)
4

Description

Issue Description

Several tests get this warning. It is not apparent why, considering the specs_dict in conftest.py does not contain any fidelities greater than 1.

How to Reproduce

To pick one example:

(pyquil) erik-macbook:pyquil erik$ pytest pyquil/tests/test_quantum_computer.py::test_qc
===================================== test session starts ======================================
platform darwin -- Python 3.7.4, pytest-5.1.2, py-1.8.0, pluggy-0.13.0
rootdir: /Users/erik/src/pyquil
plugins: requests-mock-1.7.0, timeout-1.3.3, rerunfailures-7.0
collected 1 item

pyquil/tests/test_quantum_computer.py .                                                  [100%]

======================================= warnings summary =======================================
pyquil/tests/test_quantum_computer.py::test_qc
  /Users/erik/miniconda3/envs/pyquil/lib/python3.7/site-packages/rpcq/_client.py:177: UserWarning: SIMPLE-WARNING: Chip specification contained fidelity 1.0d0 > 1. Truncating to 0.99999d0.
    warn(f"{warning.kind}: {warning.body}")

-- Docs: https://docs.pytest.org/en/latest/warnings.html
================================ 1 passed, 1 warnings in 0.10s =================================

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 with pyquil/tests/test_quantum_computer.py::test_qc and the specs_dict in conftest.py, then trace the warning reported at rpcq/_client.py:177. Determine where the fidelity value becomes 1.0d0 despite the test specification, and verify that the test no longer emits the warning while still passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.