Larmor spin echo plan

[jackbdoughty]

spin echo plan for larmor src/ibex_bluesky_core/larmor_jack_plan.py
not intending to merge

[jackbdoughty]

A part of this file relies on #164. @Tom-Willemsen said happy to accept this and change later after 164 is merged

[jackbdoughty]

Example of how could use this interface:

from typing import Generator
from bluesky.utils import Msg
from ibex_bluesky_core.fitting import Linear
from ibex_bluesky_core.larmor_jack_plan import auto_tune_ib, EchoScanConfig, AutoTuneConfig


def foo() -> Generator[Msg, None, None]:

    esconfig = EchoScanConfig(
        axis="bob",
        start=0.0,
        stop=10.0,
        flipper="TE:NDW2452:SIMPLE:VALUE:P3",
        wavelength_bounds=[[0, 999999999],[0,1]],
        num_points=3,
        detector=1
    )

    atconfig = AutoTuneConfig(
        model=Linear.fit(),
        param="c1"
    )

    yield from auto_tune_ib(esconfig, atconfig)

[jackbdoughty]

Coverage issue expected as no unit tests for LARMOR inst script/plan

[rerpha]

bps.mv takes a device rather than a string - you could just make the axis_dev at this level and then pass it into echoscan_axis_ib() though

[rerpha]

(I know this won't be merged but just thinking before we copy and paste it onto LARMOR)

[rerpha]

Another thing - I don't think this sets the number of periods yet - it should probably be num_points * 2 - I think we want to do it at this level. or by calling with_num_periods when #164 is merged?

[jackbdoughty]

Another thing - I don't think this sets the number of periods yet - it should probably be num_points * 2 - I think we want to do it at this level. or by calling with_num_periods when #164 is merged?

i reckon waiting for #164 is a good idea for this

[Tom-Willemsen]

We installed this on LARMOR (with a few modifications) and were able to get some spin-echo scans going.

We now no longer need this PR to stay around now that we've installed on LARMOR.