scnc
/
qiskit
mirror of https://github.com/Qiskit/qiskit.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove reference to `transpile` from Pulse docs (#12448) 

* Remove reference to `transpile` from Pulse docs

This reference to `transpile` was mistakenly inserted as part of 1a027ac
(gh-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.

* Update qiskit/pulse/builder.py

Co-authored-by: Will Shanks <wshaos@posteo.net>

---------

Co-authored-by: Will Shanks <wshaos@posteo.net>
This commit is contained in:
Jake Lishman 2024-05-20 19:10:25 +01:00 committed by GitHub
parent 16acb80a03
commit 8e3218bc07
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
qiskit/pulse/builder.py
View File

@ -74,8 +74,8 @@ a pulse:
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 used like a
normal Qiskit schedule.
Pulse programming has a simple imperative style. This leaves the programmer
to worry about the raw experimental physics of pulse programming and not