Skip to content

Commit

Permalink
Remove reference to transpile from Pulse docs
Browse files Browse the repository at this point in the history
This reference to `transpile` was mistakenly inserted as part of 1a027ac
(Qiskitgh-11565); `execute` used to ignore the `transpile` step for
`Schedule`/`ScheduleBlock` and submit directly to `backend.run`.

I am not clear if there are actually any backends that *accept* pulse
jobs anymore, but if there are, this is what the text should have been
translated to.
  • Loading branch information
jakelishman committed May 20, 2024
1 parent 16acb80 commit dd5c7df
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions qiskit/pulse/builder.py
Original file line number Diff line number Diff line change
Expand Up @@ -74,8 +74,8 @@
The builder initializes a :class:`.pulse.Schedule`, ``pulse_prog``
and then begins to construct the program within the context. The output pulse
schedule will survive after the context is exited and can be transpiled and executed like a
normal Qiskit schedule using ``backend.run(transpile(pulse_prog, backend))``.
schedule will survive after the context is exited and can be executed like a
normal Qiskit schedule using ``backend.run(pulse_prog)``.
Pulse programming has a simple imperative style. This leaves the programmer
to worry about the raw experimental physics of pulse programming and not
Expand Down

0 comments on commit dd5c7df

Please sign in to comment.