Look in GDA to work out what we need to do between grid and rotation

[DominicOram]

To be documented here

[DominicOram]

When we have this list discuss with @neil-i03 how much of it is actually needed

[DominicOram]

Between XRC and rotation collection we do the following:

• Detector is moved to collection location
• Check that the cryo is in - Can we just assume this in Hyperion?
• Bunch of stuff for plate screening - discussed with Neil that this is out of scope for now
• Snapshots - covered in https://github.com/DiamondLightSource/mx-bluesky/issues/388
• Backlight moved out
• Scatterguard in, generally moved to data collection pos - Can we just assume we're already in this position in Hyperion?
• Some logic to get the wavelength/transmission based on metal id i.e. https://jira.diamond.ac.uk/browse/I03-335 - Can we ignore this usecase for Hyperion for the time being?
• Move to requested wavelength - I suspect only relevant if we have changed based on metal id?
• Move to requested beam size - Hyperion is already doing this just after the grid scan based on xtal size
• Check the "sample current" is not too low - I can't even find in GDA where the sample current might be being read from, I suspect this can be removed
• Open the detector shutter
• Some configuration of a HighestExistingFileMonitor - I think this is for the GDA client to be able to pick up the latest file for reading, I don't think we care about this in Hyperion?
• Disable ROI - Hyperion should have already done this after the grid scan
• Wait on xbpm feedback - this is the same as for XRC except for wedged MAD we don't wait for stability, do we want that logic Neil?
• Read flux and do some dose scaling - I don't think this is being done properly on i03 yet anyway?
• Set transmission
• Configure parameters on detector around beam position, enegry threshold - we should check how many of these we really need to set if we haven't changed energy or moved the detector

[DominicOram]

@neil-i03 can you check any questions above? I think, as a first pass, we can get it down to:

• Configure and start arming detector
• Move detector
• Snapshots
• Move scattergaurd/apertures
• Change energy
• Open detetctor shutter
• Something like HighestExisting.. needed to make sure we're incrementing run number properly and not overriding files
• Wait on xbpm feedback - ignore wedged mad difference for now and go for it later
• Set transmission
• Do rotation