wright-plans

A set of Bluesky Plans with a focus on experimental orchestration within the Wright Group.

installation

Install the latest released version from PyPI:

$ python3 -m pip install wright-plans

conda-forge coming soon!

Use flit to install from source.

$ git clone https://github.com/wright-group/wright-plans.git
$ cd wright-plans
$ flit install -s

usage

wright-plans extends Bluesky in three major ways:

• support for WrightTools-style units
• support for "constants", algebraic expressions for hardware relationships as described below
• support for specialized tuning procecdures unique to Wright Group experiments

The plans defined by this package all end in _wp so that their names never collide with plans defined within Bluesky itself or other Bluesky plan providers. Feel free to mix these plans into an existing environment if that makes sense. Refer to the Bluesky documentation for documentation on how to utilize these plans within a simple Python script or notebook environment. A minimal example follows:

>>> import yaqc_bluesky
>>> motor1 = yaqc_bluesky.Device(39000)
>>> motor2 = yaqc_bluesky.Device(39001)
>>> sensor = yaqc_bluesky.Device(39002)
>>> import bluesky
>>> RE = bluesky.RunEngine()
>>> import wright_plans
>>> RE(wright_plans.grid_scan_wp([sensor], motor1, -1, 1, 11, "mm", motor2, -1, 1, 11, "mm")

For usage within a bluesky-queueserver, consider bluesky-in-a-box.

Note that the runs generated by these plans are guaranteed to be compatable with WrightTools via the from_databroker method.

>>> import databroker
>>> import WrightTools as wt
>>> mongo = databroker.catalog["mongo"]
>>> run = mongo[-1]  # get most recent run from catalog
>>> wt.data.from_databroker(mongo)
<WrightTools.Data>

Plans from the broader Bluesky ecosystem may or may not be compatible with from_databroker. Bluesky is capable of arbitrary orchestration, and some experiments violate the core assumptions of WrightTools. Still, the rest of the Bluesky data processing ecosystem is avaliable for such plans.

constants

Constants provide a tool for driving auxilliary hardware with algebraic expressions relating to the position of scanning hardware.

For example, a scan involving two tunable light sources, w1 and w2, might have the monochromator (wm) track the algebraic sum 2 * w1 + w2. This is an especially important capability for Coherent Multidimensional Spectroscopy as described in Neff-Mallon and Wright 2017.

Constants in wright_plans allow for arbitray linear combinations of other hardware with compatible units. Constants are units aware and do addition/multiplication in the specified units.

Constants are defined using the Constant class with ConstantTerm elements.

An example of the scan described above:

>>> import yaqc_bluesky
>>> w1 = yaqc_bluesky.Device(39000)
>>> w2 = yaqc_bluesky.Device(39001)
>>> wm = yaqc_bluesky.Device(39002)
>>> sensor = yaqc_bluesky.Device(39003)
>>>
>>> import bluesky
>>> RE = bluesky.RunEngine()
>>>
>>> from wright_plans import Constant, ConstantTerm, gridscan_wp
>>> constants = {wm: Constant("wn", [
...     ConstantTerm(2, w1),
...     ConstantTerm(1, w2),
... ])}
>>> RE(grid_scan_wp([sensor], motor1, -1, 1, 11, "mm", motor2, -1, 1, 11, "mm", constants=constants)

Each entry in the constants dictionary describes the tracking behavior of one Movable, multiple devices can be set to track in a single scan by passing as a dictionary {motor1: constant1, motor2: constant2}.

plans

Wright plans provides provides the following plans, plan signatures can be found by their docstrings: