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

Solve strange behavior with qubit_properties in Target. #13400

Merged
merged 1 commit into from
Nov 6, 2024

Commits on Nov 5, 2024

  1. Fix: Solve strange behavior with qubit_properties in Target.

    The previous implementation of the Target would always make sure to receive a real value for `num_qubits` or it would default to zero. Mistakenly because of the behavior of `Target::from_configuration` it was assumed that `num_qubits` could be `None` unless otherwise specified. However, the default behavior should be to make `num_qubits` zero unless specified otherwise.
    
    The following commits fix this behavior by fixing the signature of the rust `Target` to have default values and adding an extra check when comparing against `qubit_properties`.
    
    A test casde based on @wshanks findings in Qiskit#13393 was also included in these additions.
    raynelfss committed Nov 5, 2024
    Configuration menu
    Copy the full SHA
    6d54b6b View commit details
    Browse the repository at this point in the history