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

T2Hahn/T1/RamseyXY/T2Ramsey create delay lengths not supported by the backend #881

Closed
wshanks opened this issue Aug 11, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@wshanks
Copy link
Collaborator

wshanks commented Aug 11, 2022

Informations

  • Qiskit Experiments version: 57fd212
  • Python version: 3.10
  • Operating system: Fedora

What is the current behavior?

The experiments listed in the title create delay lengths not supported by the backend. For IBM backends, this can produce an error like Error message: Delays must be a multiple of 16 samples. Error code: 8043..

Steps to reproduce the problem

Run one of the experiments listed in the title on a backend with pulse_alignment > 1 in backend.configuration().timing_constraints.

What is the expected behavior?

The experiment runs without an error from the backend.

Suggested solutions

The problem is that these experiments overwrite the timing_constraints transpile option entirely, rather than just setting values within it and leaving others with their default values from the backend. This prevents the transpiler pass that adjust delay timings from knowing all of the timing constraints to use when adjusting delay values. The solution is to make sure all of the default values from the backend are preserved.

@wshanks wshanks added the bug Something isn't working label Aug 11, 2022
@wshanks wshanks self-assigned this Aug 11, 2022
wshanks added a commit to wshanks/qiskit-experiments that referenced this issue Aug 11, 2022
This was a workaround for IBM backends that did not report their timing
constraints. All backends now report timing constraints so the
adjustment is no longer needed and as implemented is causing problems
(qiskit-community#881).

The scheduling_method adjustment is also removed because it should not
be necessary.
wshanks added a commit to wshanks/qiskit-experiments that referenced this issue Aug 12, 2022
This was a workaround for IBM backends that did not report their timing
constraints. All backends now report timing constraints so the
adjustment is no longer needed and as implemented is causing problems
(qiskit-community#881).
wshanks added a commit that referenced this issue Aug 16, 2022
This was a workaround for IBM backends that did not report their timing
constraints. All backends now report timing constraints so the
adjustment is no longer needed and as implemented is causing problems
(#881).
@wshanks
Copy link
Collaborator Author

wshanks commented Oct 17, 2023

Closed by #881.

@wshanks wshanks closed this as completed Oct 17, 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

No branches or pull requests

1 participant