Skip to content
This repository was archived by the owner on Aug 21, 2023. It is now read-only.

Commit a76f773

Browse files
committed
Remove API references
1 parent 8aa0a46 commit a76f773

1 file changed

Lines changed: 14 additions & 14 deletions

File tree

qiskit/advanced/terra/programming_with_pulses/building_pulse_schedules.ipynb

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,11 @@
1818
"source": [
1919
"# Building Pulse Schedules\n",
2020
"\n",
21-
"Building [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule)s is very straightforward, yet there are a few ways to compose them. We're going to explore these different methods here.\n",
21+
"Building `Schedule`s is very straightforward, yet there are a few ways to compose them. We're going to explore these different methods here.\n",
2222
"\n",
23-
"Tip: [`Instruction`](https://qiskit.org/documentation/api/qiskit.pulse.Instruction.html#qiskit.pulse.Instruction)s can be treated just like [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule)s -- that means all the methods we use here work equally well for composing [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule)s with [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule)s, [`Instruction`](https://qiskit.org/documentation/api/qiskit.pulse.Instruction.html#qiskit.pulse.Instruction)s with [`Instruction`](https://qiskit.org/documentation/api/qiskit.pulse.Instruction.html#qiskit.pulse.Instruction)s, or between the two.\n",
23+
"Tip: `Instruction`s can be treated just like `Schedule`s -- that means all the methods we use here work equally well for composing `Schedule`s with `Schedule`s, `Instruction`s with `Instruction`s, or between the two.\n",
2424
"\n",
25-
"As the basis for trying out the composition methods, let's initialize a couple dummy [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule)s."
25+
"As the basis for trying out the composition methods, let's initialize a couple dummy `Schedule`s."
2626
]
2727
},
2828
{
@@ -41,11 +41,11 @@
4141
"cell_type": "markdown",
4242
"metadata": {},
4343
"source": [
44-
"### [`insert`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.insert) or `|`\n",
44+
"### `insert` or `|`\n",
4545
"\n",
46-
"The [`insert`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.insert) method schedules an [`Instruction`](https://qiskit.org/documentation/api/qiskit.pulse.Instruction.html#qiskit.pulse.Instruction) or [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule) at a particular time. Let's use it to give each of our schedules a different instruction.\n",
46+
"The `insert` method schedules an `Instruction` or `Schedule` at a particular time. Let's use it to give each of our schedules a different instruction.\n",
4747
"\n",
48-
"The insert schedule method overloads the `|` (or) operator for [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule)s, so we will use this special syntax on schedule `B`. When using this syntactic sugar, the `time` argument is implicitly zero."
48+
"The insert schedule method overloads the `|` (or) operator for `Schedule`s, so we will use this special syntax on schedule `B`. When using this syntactic sugar, the `time` argument is implicitly zero."
4949
]
5050
},
5151
{
@@ -76,9 +76,9 @@
7676
"cell_type": "markdown",
7777
"metadata": {},
7878
"source": [
79-
"### [`shift`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.shift) or `<<`\n",
79+
"### `shift` or `<<`\n",
8080
"\n",
81-
"Sometimes we need to offset one schedule from `time=0`. For instance, when using `|`, we use [`shift`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.shift) to add an instruction at a time besides zero."
81+
"Sometimes we need to offset one schedule from `time=0`. For instance, when using `|`, we use `shift` to add an instruction at a time besides zero."
8282
]
8383
},
8484
{
@@ -109,7 +109,7 @@
109109
"cell_type": "markdown",
110110
"metadata": {},
111111
"source": [
112-
"Let's see how we can use [`insert`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.insert) to compose schedules `A` and `B` together."
112+
"Let's see how we can use `insert` to compose schedules `A` and `B` together."
113113
]
114114
},
115115
{
@@ -140,9 +140,9 @@
140140
"cell_type": "markdown",
141141
"metadata": {},
142142
"source": [
143-
"### [`append`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.append) or `+`\n",
143+
"### `append` or `+`\n",
144144
"\n",
145-
"The [`append`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.append) method is like [`insert`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.insert), but the insertion time is determined for us. The [`Instruction`](https://qiskit.org/documentation/api/qiskit.pulse.Instruction.html#qiskit.pulse.Instruction) or [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule) being added will begin when all the channels common to the two become free. If they contain no common channels, then the [`Schedule`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule) will be appended at `time=0`. In psuedocode:\n",
145+
"The `append` method is like `insert`, but the insertion time is determined for us. The `Instruction` or `Schedule` being added will begin when all the channels common to the two become free. If they contain no common channels, then the `Schedule` will be appended at `time=0`. In psuedocode:\n",
146146
"\n",
147147
"```\n",
148148
"time = 0\n",
@@ -152,7 +152,7 @@
152152
"\n",
153153
"The append schedule method overloads the `+` (add) operator for Schedules.\n",
154154
"\n",
155-
"Let's continue with schedule `A` and schedule `B`. Remember that they both have instructions scheduled on the same channel, [`DriveChannel`](https://qiskit.org/documentation/api/qiskit.pulse.DriveChannel.html)`(0)`. Schedule `A` contains positive amplitude pulses, and schedule `B` contains negative amplitude pulses."
155+
"Let's continue with schedule `A` and schedule `B`. Remember that they both have instructions scheduled on the same channel, `DriveChannel(0)`. Schedule `A` contains positive amplitude pulses, and schedule `B` contains negative amplitude pulses."
156156
]
157157
},
158158
{
@@ -184,7 +184,7 @@
184184
"source": [
185185
"Let's see what happens when there are no common channels.\n",
186186
"\n",
187-
"Warning: Common channels is not the same as common qubits. Measurements require different channels than gate operations, even on one qubit. If you simply append a measurement to a schedule, you'll likely schedule your measurement at `time=0`, not what you were expecting! Instead, use the shift operation, with [`schedule.duration`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.duration) as the time argument."
187+
"Warning: Common channels is not the same as common qubits. Measurements require different channels than gate operations, even on one qubit. If you simply append a measurement to a schedule, you'll likely schedule your measurement at `time=0`, not what you were expecting! Instead, use the shift operation, with `schedule.duration` as the time argument."
188188
]
189189
},
190190
{
@@ -216,7 +216,7 @@
216216
"source": [
217217
"This time, the new instruction being appended was added at `time=0`, because it did not have any instructions on `DriveChannel(0)`.\n",
218218
"\n",
219-
"Be wary: [`append`](https://qiskit.org/documentation/api/qiskit.pulse.Schedule.html#qiskit.pulse.Schedule.append) only \"slides\" the appended schedule into the original around channels that are not common between them. The following example demonstrates this point."
219+
"Be wary: `append` only \"slides\" the appended schedule into the original around channels that are not common between them. The following example demonstrates this point."
220220
]
221221
},
222222
{

0 commit comments

Comments
 (0)