Skip to content

Commit 5c384b5

Browse files
committed
h3->h2
1 parent 8e88bfc commit 5c384b5

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

doc/tutorial/overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ The most important concepts in bluesky are:
1919
- The **RunEngine** executes plans (possibly interacting with devices)
2020
- **Callbacks** do something with data emitted by the scan
2121

22-
### Plans
22+
## Plans
2323

2424
A plan is an _iterable_ of _messages_. A very simple plan, which doesn't do anything, is:
2525

@@ -42,7 +42,7 @@ def plan():
4242
yield from bps.null()
4343
```
4444

45-
### Devices
45+
## Devices
4646

4747
`ibex_bluesky_core` provides built-in support for a number of ISIS-specific devices. For example,
4848
blocks are available as devices:
@@ -60,7 +60,7 @@ Block objects provide several mechanisms for configuring write behaviour - see
6060
Likewise, the DAE is available as a bluesky device: see [the DAE Documentation](../devices/dae.md)
6161
for full examples including example configurations.
6262

63-
### Setting and reading values
63+
## Setting and reading values
6464

6565
Bluesky provides plan stubs for setting & reading values from bluesky devices: `bps.mv()` and
6666
`bps.rd()` respectively.
@@ -86,7 +86,7 @@ external code in a plan.
8686
For more details about plan stubs (plan fragments like `mv` and `read`), see
8787
[bluesky plan stubs documentation](https://blueskyproject.io/bluesky/main/plans.html#stub-plans)
8888

89-
### Scanning
89+
## Scanning
9090

9191
Having created some simple devices, those devices can be used in standard bluesky plans:
9292

@@ -110,7 +110,7 @@ def my_plan(det_block_name: str, mot_block_name: str, start: float, stop: float,
110110
For details about plans which are available directly from `bluesky` - like `bp.scan` above - see
111111
[bluesky's plan documentation](https://blueskyproject.io/bluesky/main/plans.html#pre-assembled-plans).
112112

113-
### The `RunEngine`
113+
## The `RunEngine`
114114

115115
The `RunEngine` is the central "conductor" in bluesky - it is responsible for reading a plan and
116116
performing the associated actions on the hardware. To get a run engine instance, use:
@@ -139,7 +139,7 @@ For more detail about the RunEngine, see:
139139
- [bluesky RunEngine docs](https://blueskyproject.io/bluesky/main/tutorial.html#the-runengine)
140140
- [bluesky RunEngine API docs](https://blueskyproject.io/bluesky/main/run_engine_api.html)
141141

142-
### Callbacks
142+
## Callbacks
143143

144144
Callbacks are bluesky's mechanism for listening to data from a scan. Some examples of common callbacks
145145
are:
@@ -185,7 +185,7 @@ be used for example to always configure a particular scan with plots and a fit w
185185
For more information on callbacks, see
186186
[bluesky callbacks documentation](https://blueskyproject.io/bluesky/main/callbacks.html).
187187

188-
### See also
188+
## See also
189189

190190
**Plans & plan-stubs**
191191
- Bluesky [experiment plans](https://blueskyproject.io/bluesky/main/plans.html#summary)

0 commit comments

Comments
 (0)