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

Simulator method of FakeBackends changes num qubits in configuration #1769

Closed
chriseclectic opened this issue Apr 3, 2023 · 0 comments · Fixed by #1825
Closed

Simulator method of FakeBackends changes num qubits in configuration #1769

chriseclectic opened this issue Apr 3, 2023 · 0 comments · Fixed by #1825
Assignees
Labels
bug Something isn't working
Milestone

Comments

@chriseclectic
Copy link
Member

Informations

  • Qiskit Aer version: 0.12
  • Python version: 3.9
  • Operating system: MacOs

What is the current behavior?

When using AerSimulator.from_backend information such as the coupling map is taken from the backend, however if the simulation method is changed to "stabilizer", the number of qubits is set to a value larger than the coupling map.

Steps to reproduce the problem

backend = AerSimulator.from_backend(FakeMontreal(), method=method)
backend.configuration().num_qubits

Returns 10000 for stabilizer, 63 for extended stabilizer, 32 for statevector, 16 for density matrix.

In this case the fake backend has 27 qubits in its coupling map.

What is the expected behavior?

The number of qubits in the configuration should be set to the number of qubits in a coupling map if the coupling map is not None.

Suggested solutions

@chriseclectic chriseclectic added the bug Something isn't working label Apr 3, 2023
@hhorii hhorii self-assigned this Apr 4, 2023
@hhorii hhorii added this to the Aer 0.12.1 milestone Apr 4, 2023
@mergify mergify bot closed this as completed in #1825 May 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants