20.4.2024 / 22h51:
DOC informed PRC that the SASE2 topic broker had to be restarted.
The EPS power limit was reset by PRC to the previous value of 40 W.

DOC and DRC are working on the restart. HED is in hardware setup configuration change (not currently taking beam, thus no harm to experiment),
will start taking beam with new users sunday 7am, but would need before this some test runs for the detectors. 

Currently the SA2 topic watchdogs (for ATT, CRL, imagers) cannot be restarted - they crash quickly after restarting.
DOC/DRC are investigating this issue. Until the watchdogs are successfully restarted, extra care must be taken when using ATT, CRL, imagers in SA2.

Update 21.4.2024 / 1h43 by DRC:
In a similar fashion to the incident of last 5.04, the Broker process for the SA2 and LA2 topic has restarted.
This was noticed by the DOC crew and by the HED crew in parallel.
With the help of the CTRL OCD (Micheal Smith) we restarted both topics. As a lesson learned from the last interruption, the POWER_LIMIT
middlelayer device has been set up by the PRC, so that when the DOOCS bridges will be restarted by the DESY-MCS personnel,
the maximum power will not be set to 0.
Please check in due time if all systems are working as intended.

Staff: JK, SB, JE, AS, RW, FK

**X-ray delivery:**
- 21 keV, ~500 uJ

**Optical Laser:**
- None

**Achievements / Observations:**
- Measured several Schimadzu runs

**Issues**:
- the beam intensity was fluctuating significantly during the day; 
- Changed the objective of Schimadzu for wider field then the controller stopped working which took over 1 h; before starting working again.
- One of the attenuators has features on the scene; Si 3200

The intra-bunchtrain feedback (IBFB) was not active until today afternoon.
Although not strictly required or requested for the current week experiments,
it was decided to turn on this feedback, which should generally be active to
stabilize and improve the arrival time of the photon pulses along pulse trains.

In order to avoid complications during long data acquisitions, the PRC checked back with all ongoing experiments,
identified a suitable time slot, and the IBFB was activated without issues at aound 16h45.

Measurements to check the impact of bunch compression on FXE mono transmission were successful. We could change the peak current between 4 and 12 kA and saw changes in bandwidth between 17 and 100 eV (at 14 keV). Results are under evaluation.

SA1 brought to safe state:

• CRLs moved out
• Mono moved out
• CVDs in XTD2 ATT inserted
• PBLM-based feedback was started and kept running to avoid beam drifting off of M3
• Hirex shutter closed
• The M1/M2 offset was decreased a bit as compared to saturday mornings' value (was very close to total reflection limit and to safely use 100 bunches, it was decreased to be on the safe side). Should not affect further measurements for XFELO on sunday.

Dear all,

we calibrated the mirror vertical motors to their geometrically neutral.

Please be aware that saved values for beamline settings may no longer be valid. This mainly applies to the vertical motor positions, but will have an impact on Tx and Ry values as well.

As starting point, use XRO Optics Setpoints 'C' - this setting was last used to bring beam to SPB

- M3 TX moved to 0 in steps of 1 mm and beam on FXE Pop-In corrected with M3 RY (+) and M2 RY

- Started calibration with M3 Rz in steps of 0.5 (+) and corrected with M2 RY and RZ to find a position with a minimum of parasitic motion

- Iterations with M3 TY

- CRL 3 and 4 were inserted (using find target)

- The backlash correction was disabled

- Curve for M3 Rz position with Ry correction done. M2 RY/RZ corrections to move beam up and down to have it on the screen

- Curve for M3 Ty position with Ry correction done.

- Curve for M3 Rx position with Ry correction done

M3 vertical motors calibrated to 0

Starting shift with mirror motor calibration:

- beam is centered on FEL imager

- pblm in XTD9 is inserted

We removed both silicon solid attenuator and pblm

Starting shift with mirror motor calibration:

- found solid attenuator 0.5mm silicon inserted

- beam is centered on FEL imager

- pblm in XTD9 is inserted

We removed both silicon solid attenuator and pblm

Yesterday two motors of the SASE2 seeding mono were damaged. The mono was exchanged in the afternoon and pumped down. Currently, an issue with the vertical cystal motion is being investigated.  The vacuum improved much faster than expected after this intervention, so the hope is that the tunnel can be searched soon and electrons could go through SASE2 already this afternoon. Watch for updates in the program for SASE2 in the DESY logbook under 'Schedule'.     

In-house/commissioning beam time summary night 5

X-ray delivery:
12.7 keV, up to 128 pulses at 0.5MHz, ~1.3 mJ, one very short beam down.

Optical laser delivery:
PP laser for illumination

Achievements/observations:
- AGIPD1.2 tests with different trigger delays, gain modes, signal levels ...
- inhouse proghram completed

Issues:
Some sample delivery issues

In-house/commissioning beam time summary night 4

X-ray delivery:
12.7 keV, up to 128 pulses at 0.5MHz, ~1.3 mJ, one very short beam down.

Optical laser delivery:
PP laser for illumination

Achievements/observations:
AGIPD timing scan, fine and coarse
A few runs with Jungfrau

Issues:
Some sample delivery issues
Some Jungfrau pipeline issues (will be investigated by DOC during the day)

Staff: MS, RB, PS, RdW

In-house/commissioning beam time summary night 3

X-ray delivery:
12.7 keV, up to 288 pulses at 1.1MHz, ~1.3 mJ

Optical laser delivery:
PP laser for illumination

Achievements/observations:
Collected a lot of data with Jungfrau, burst mode 16 memory cells: 
- 1, 4 and 18 pulses/memory cell 
- one run of each setting 1, 4, 8, 10, 13 and 18 pulses/memory cell one after the other
- 8 pulses with 32% transmission
- 4 pulses with half the repetition rate (0.5MHz)

In-house/commissioning beam time summary night 2

X-ray delivery:
12.7 keV, up to 288 pulses at 1.1MHz, ~1.2 mJ

Optical laser delivery:
PP laser for illumination

Achievements/observations:
Collected a lot of data: continued 8 pulses per memory cell, around 1h30-2h 1 pulse and 3 runs with 18 pulses.
 

In-house/commissioning beam time summary night 1

X-ray delivery:
12.7 keV, up to 208 pulses at 1.1MHz, 1.1-1.5 mJ

Optical laser delivery:
PP laser for illumination

Achievements/observations:
Minimised air scattering background on Jungfrau
Collected serial crystallography data with 8, 10 and 13 pulses per memory cell and good hit rates

Issues:
Sample growing again from the catcher cone

X-ray delivery

• 12.72 keV, 10Hz, ~1.4 mJ/pulse, some beam drift in the horizontal direction observed (probably mirror related)

Optical laser delivery

• 487 nm ns laser for pump-probe
• 800 nm PP laser for jet illumination, stable delivery

Achievements/Observations

• Collected PP (pump-probe) dataset with 5 us time delay more than 12 hours
• Jet and data collection was stable most of the time

X-ray delivery

- 12.72 keV, 10Hz, ~1.4 mJ/pulse, continuous beam drift in the horizontal direction observed

Optical laser delivery
- 487 nm ns laser for pump-probe
- 800 nm PP laser for jet illumination, stable delivery

Achievements/Observations
- Collected PP (pump-probe) dataset with 5 us time delay more than 12 hours
- Collected 3 runs (5 minutes run) of dark state in the end of the shift
- Jet was quite stable most of the time

Issues
- Continuous beam pointing drift in the horizontal direction observed
- Vacuum spike at MKB_PSLIT section trip the beam shortly which might be related to the beam pointing drift

Continuous pointing drift in horizontal direction.

It may trigger a vacuum spike at SPB OH (MKB_PSLIT section) at 21:07 pm.

DOOCS panels are again incorrectly reporting the FXE shutter as opened when it is in fact closed. This had been fixed after it was last reported in February (elog:24), but reappeared now.

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.