You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make Hyperion usable for other beamlines, we need to abstract our grid scan plans into smaller functions. A beamline-specific top level plan can then be constructed by importing all the relevant subplans. These subplans should be moved to the mx-bluesky repo..
This will also give I03 a clean way to switch between its current FGS and its panda FGS, since, for example, we can have two top level plans: I03_regular_grid_scan and I03_panda_grid_scan. which Hyperion can choose from based on a parameter.
Once we have separated our flyscan_xray_centre into two parts (flyscan, xray centre based off flyscan), it will help us to merge VMXM's fast grid scans
The text was updated successfully, but these errors were encountered:
In order to make Hyperion usable for other beamlines, we need to abstract our grid scan plans into smaller functions. A beamline-specific top level plan can then be constructed by importing all the relevant subplans. These subplans should be moved to the mx-bluesky repo..
This will also give I03 a clean way to switch between its current FGS and its panda FGS, since, for example, we can have two top level plans:
I03_regular_grid_scan
andI03_panda_grid_scan
. which Hyperion can choose from based on a parameter.Once we have separated our
flyscan_xray_centre
into two parts (flyscan
,xray centre based off flyscan)
, it will help us to merge VMXM's fast grid scansThe text was updated successfully, but these errors were encountered: