FXE received the beam and did not change accelerator settings.

Beam alignment to FXE was re-established using the new values for the old M1/M2 offset.

Monochromator aligned to the SPB energy setpoint.

THz source aligned to Xrays and several reference positions for Xray pointing taken. Further steps require THz radiation, which is not available at this point.

Xrays realigned back to SPB XTD9 screen.

The xray beam drifted significantly on wednesday and thursday (18. and 19.) but then was not drifting on friday (20.), see attached trendline of the M2 actuator that kept the beam at fixed position on M3.

Today also seems that beam pointing is stable. But unclear what happened earlier...

This is to report some findings during operation that should be looked into (mostly to avoid in the future, because both negatively affect data quality of the user expt at FXE):

• At the moment, the 99:1 mode affects 4 to 5 pulses out of 100 in SA1, see first screenshot that shows in the top right the IPM reading with each blue point denoting the average pulse energy in a train. This was not always the case. After initial setup on thursday it did affect only a single train out of 100.
• On 27.10., the switching of SA2 between 1 and multiple bunches affected SA1 beam heavily, see the jumps in SA1 pulse energy in the second screenshot shown here:
  • The pulse energy dropped by 15% and
  • the pointing changed vertically by 150 um on the FXE PI (data not shown, but available from karabo trendlines)

Edit 8.11.: Added screenshot (grafana/ctrend) to show that the vertical displacement was permanent (not corrected by the feedback)

We had some trouble with the DAQ. It was not able to start runs properly.

We got the following error messages:

initially:

[00:01:27]: Problem of communication with data manager

[00:01:30]: Start new run ...

[00:01:38]: Failed starting data recording

DM: error at registerRun (Request to MDC timeouted)

after trying to start the run again:

[00:05:35]: Start new run ...

[00:05:35]: Failed starting data recording

DM: error at registerRun (Problem of communication with MDC

#Info: MDC-1100: MDC web server error: Error creating run

#Details: {'run_number': ['must be unique per proposal', 'has already been taken'], 'experiment_id': ['has already been taken']})

Cycling the DAQ resolved the issue.