From dd5c7dfef0a9a5353a40b67e49d9181d27f48b3f Mon Sep 17 00:00:00 2001 From: Jake Lishman Date: Mon, 20 May 2024 17:13:40 +0100 Subject: [PATCH] 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. --- qiskit/pulse/builder.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/qiskit/pulse/builder.py b/qiskit/pulse/builder.py index b7bdbe85c192..bfe92e16fda9 100644 --- a/qiskit/pulse/builder.py +++ b/qiskit/pulse/builder.py @@ -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