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.

Sign up for GitHub

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

Remove reference to transpile from Pulse docs #12448

Merged
merged 2 commits into from
May 20, 2024
Merged

Remove reference to transpile from Pulse docs #12448

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dd5c7df
Remove reference to `transpile` from Pulse docs
jakelishman May 20, 2024
6a1b54a
Update qiskit/pulse/builder.py
jakelishman May 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions qiskit/pulse/builder.py
View file
Open in desktop
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)``.
jakelishman marked this conversation as resolved.
Show resolved Hide resolved

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
Loading