Roadmap

For a closer look at the ongoing work: I24ssx board

Ongoing list of TODOs:

1. Improve alignment of chip: get it to work correctly for multiple zooms.

   • Close to being completed (see issue #44)

2. Refactor and fix the logger.

3. Use callbacks for file IO, eg. to write parameter and map files, nexus writer and ispyb deposition.

4. Solution for enabling users to run mx-bluesky instead of old scripts: blocked by permission issues.

   • This should also allow us to stop using the Pilatus to make directories during an Eiger collection.

   • The preferred permanent solution is to run mx-bluesky on the beamline kubernetes cluster. I24 should be due to get on in shutdown 4 2024.

   • Other possibility is to run the blueapi server on procServ. An example of this has now been set up on ws002 on the beamline and is being tested.

   • A temporary workaround in place for beamline staff, who should be starting to run this for testing/in house beamtimes. Staff have started using this set up in September 24.

5. Convert detector set up to use bluesky plans and ophyd_async devices.

   • Eiger device in dodal needs to be converted to ophyd_async and updated to work with different Eigers on several beamlines. This work is dependent on other work out of the scope of this project, see Dodal#700 and linked issues.

   • Investigate using the existing Pilatus in ophyd_async which writes HDF5 instead of CBFs, but we may want to make a CBF-writing Pilatus. However, the Pilatus detector is due to be removed soon.

6. Start looking into moving away from edm screens towards a web-based GUI.

   • Prepare generic react components to match the features in the edms.

   • Components for things currently managed by general purpose PVs (eg. map).

   • OAV viewer.

7. Start integrating Panda, at least for fixed-target collections.

8. Implementation of serial tools to be used at XFELS.

   • Reinstate removed code from sacla and move it to bluesky.

   • Add any plans/devices that might be needed for other locations.

9. Reinstate full mapping code using bluesky.

(TBC…)

Rough Roadmap

Work Ongoing	Rough Timeline	Completed
Fully test extruder collections	Nov. 24
Fix permissions and allow for user collections	Dec. 24 / Jan. 25
Convert the current detector set up code to bluesky plans using the device	Dependent on FastCS Eiger issues being completed
Set up callback for nexus writing	Dec. 24
Set up callback for ispyb deposition	Dec. 24
Set up callback for parameter and map file I/O	Dec. 24
Refactor logger	Nov. 24
Improve current alignment (moveonclick)	Nov. 24
Set up a PV backend, eg. pvws, for web GUI on the beamline.	Jan. 25
Prepare React components to switch from EDM to a web GUI	Dec. 24 / Jan. 25
Move the OAV viewer to a web GUI	Jan. 25 / Feb. 25

Experiment types required

• Extruder

  • Standard

  • Pump probe

• Fixed target (probably about 80-85% of serial on I24)

  • Standard chip collection – option for multiple exposures in each spot

  • Pump probe - see for short description https://confluence.diamond.ac.uk/display/MXTech/Dynamics+and+fixed+targets

    • Short delays

    • Excite and visit again

    • Long delays with fast shutter opening/closing

• (Future) Fixed target with rotation at each “window” (Preliminary work done by beamline staff on the PMAC program https://confluence.diamond.ac.uk/display/MXTech/Grids+with+rotations)

Details of zebra settings for each type: https://confluence.diamond.ac.uk/display/MXTech/Zebra+settings+I24

Note that most of the set up for the fixed target is actually done by the PMAC via PMAC strings.

---

Old roadmap for reference

Work Ongoing	Rough Timeline	Completed
Document how to set up the current visit, deploy the edm screens and run a simple collection	Ongoing
Chip collections using bluesky	Jan./Feb. 24
Extruder collections using bluesky	Feb. 24
Create an Ophyd device for the Pilatus detector and use it, along with the Eiger device, to collect data	Jan. 24
Start using Ophyd devices for the set up tasks - eg. zebra	15th Dec. 23
Use a plan to find the fiducials	15th Dec. 23
Create an Ophyd device for for the pmac and use it to move the chip stages	1st Dec. 23
Set up a first bluesky plan to move the detector stage and set up the detector in use	15th Nov. 23
Come up with a first parameter model	1st Dec 23
Start sending logs to graylog	Nov. 23
Permissions issues - run as a service	Dec. 23
Deploy a first version of mx-bluesky with the current iteration - tested on the beamline - of the serial tools. Set up a module load that they can use it for ssx data collections.	Nov. 23
Generic deployment for edm screens	Summer 23
Tidy up original code and add some tests	Summer 23