Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

T1, T2 not mapped to IBMQubitProperties #617

Closed
dieris opened this issue May 9, 2023 · 0 comments · Fixed by #619
Closed

T1, T2 not mapped to IBMQubitProperties #617

dieris opened this issue May 9, 2023 · 0 comments · Fixed by #619
Assignees
Labels
type: bug Something isn't working
Milestone

Comments

@dieris
Copy link
Contributor

dieris commented May 9, 2023

Information

  • qiskit-ibm-provider version: main
  • Python version: 3.11
  • Operating system: Windows

What is the current behavior?

The backend properties T1, T2 are not correctly mapped to the IBMQubitProperties t1, t2 in _decode_qubit_properties

Steps to reproduce the problem

For any backend_name,

from qiskit_ibm_provider import IBMProvider
backend =  provider.get_backend(backend_name)
backend.target.qubit_properties()

returns e.g.

[IBMQubitProperties(t1=None, t2=None, frequency=4883140335.692719, anharmonicity=-344828063.1378064),
...

What is the expected behavior?

t1 and t2 should be populated from the corresponding T1, T2 values

Suggested solutions

If we want to maintain lowercase t1, t2, as IBMQubitProperties, add .lower() to

@dieris dieris added the type: bug Something isn't working label May 9, 2023
@kt474 kt474 self-assigned this May 9, 2023
@kt474 kt474 added this to the 0.6.0 milestone May 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants