X-ray delivery

• 7.8keV, 2.4mj, stable delivery, homogeneos intra train energy most of the time.

Optical laser delivery

• ns laser for particle imaging

Achievements/Observations

• AGIPD BG optimized by opening Q2 & Q4 quadrants a few pixels and adding Pb shield on IRU_SLIT4
• NKB focused optimized
• Data (75 nm Ag cube) and gas BG (no sample) measured with two different gases (N2 and He)

Issues

• AGIPD BG near the center (1-2 pixels) were quite strong even with tight sliting, but issue solved by opening two quadrants (Q2 & Q4) and moving CSS about 1-2 pixels (elog:12731)
• Found additional AGIPD BG in Q2M1 module (mid-Q range), but issue solved by adding Pd shield on IRU_SLIT4 (elog:12734)

We observed auto changes of the number of X-ray pulses last night and tonight.

It is related to 500 um thick Si attenuator in XTD2_ATT.

Even with 2.4 mm thick CVD (XTD2_ATT) IN, the number of pulses @SA1 changes to 28 whenever we insert 500 um thick Si attenuator.

Watchdog triggered this process. It has to be updated.

First row in the atttachment: The number of X-ray pulses @ SA1

Second row in the attachment: Status of 2.4 mm thick CVD in XTD2_ATT

Third row in the attachment: Status of 0.5 mm thick Si in XTD2_ATT

X-ray delivery

• 7.8keV, 2.5mj, stable delivery, homogeneos intra train energy most of the time.

Optical laser delivery

• ns laser for particle imaging

Achievements/Observations

• RGA installed and used for quantitative gas BG analysis
• Data (55 nm Ag cube) and gas BG (no sample) measured with two different gases (N2 and He)
• BG roughly 3.5x better with 3 l/min He flow, but only about 2x better with 3 L/min He + N2/CO2 for stable Tayler cone

Issues

• Pulses often changed from 352 to 28 for no apparent reason, discovered later that it was happening when closing silicon 500 XTD2 arm (elog:421)

X-ray delivery

• 19keV, 700-800uj

Optical laser delivery

•  ns laser

Achievements/Observations

• Vacuum pipe and He pipe for diamond outcoupling installed
• Aligned beam to downstream
• Saw the beam at tower position (Zyla camera)

X-ray delivery

• 19 keV, ~0.9 mJ/pulse, stable delivery

Optical laser delivery

•  no

Achievements/Observations

• Finalized allignment
• Got successful runs with impact from sound eventhough often timing misaligned due to jitter

Issues

• High jitter from output of transducer (Ch 2in oscilloscope) is problematic

X-ray delivery

• 19 keV, ~0.9 mJ/pulse, stable delivery

Optical laser delivery

•  no

Achievements/Observations

• Tried many possibilities to fix the jitter issue. We covered everything we could think of, but in the end it was not possible as we could not avoid restricting ourselves from the 0.4s delay required for the ultrasound, making us then suffer from the inter-train jitter.
• Returned to operational experiment setup, eventhough suffering from the jitter issue.

Issues

• High jitter from output of transducer (Ch 2in oscilloscope) could not be solved.
• Turbopumps went off, then we realized multiple power sockets were powerless (F7,8,9,10,11). We connected the turbos to another socket to resume operation, after which the previous sockets were also fixed. We must reconnect the turbos to the typical sockets sometime soon, best expectation to be comming Monday.

Beam drift in the horizontal direction (XTD9_XGM x position) started at around 10am and continuously drifted until 16:00.

After then, beam has been drifted back to original position within 4 hours.

X-ray delivery

• 16.9 keV, up to 30 pulses and 1.1 MHz for alignment, 1 pulse for data collection
• 900 uJ
• Beam pointing and stability issues towards end of shift

Optical laser delivery

• None

Achievements/Observations

• Crystal diffraction data from 4 different samples collected with detector close up two sample to detector position

Issues

• Jungrfau gain visualisation caused some concern - was confirmed with the hlp of DOC to be a known issue that the Medium and low gains are masked in that region leding to dark areas in corrected map
• sample collision with cone and OSA required realignment of the setup
• pointing stability of beam in the end of the day (BKR confirmed that the electron orbit is okay. So, we may need to contact PRC)

Beam drift in the horizontal direction (XTD9_XGM).

From ~16:00, X-ray beam started to drift in the horizontal direction. In total, ~0.3 mm drift observed within 2-3 hours.

Attachment 1: Beam X position in XTD2_XGM and XTD9_XGM

X-ray delivery

• 16.9 keV, up to 30 pulses and 1.1 MHz for alignment, 1 pulse for data collection
• 800 uJ
• Beam pointing and stability issues towards end of shift (again)

Optical laser delivery

• None

Achievements/Observations

• Crystal diffraction data from several samples collected with detector close up two sample to detector position

Issues

• The counts in the pupil has been dropping over the day and less than yesterday (one issue was a YAG screen in SPB_XTD9_IMGPI)
• pointing stability of beam in the end of the day (similar to yesterday)

After going in and reconnecting the camera, we observe att. 1.

According to logs the camera device server was restarted around 11pm, however the camera instance was never reinstantiated after the restart. The Karabo GUI did not indicate that properly, instead showed a frozen image that looked as if the camera works properly.

(see history of camera state in att. 2)

Device Server log shows that after camera connection was lost, the device server restarted?! Was this restart done on purpose?

2023-11-23T23:02:22.499 ERROR  karabo.AravisBasler2Camera  : SQS_AQS_UPP/CAM/A2A1920_2: Could not synchronize timestamp: GigEVision write_memory timeout
2023-11-23T23:02:27.504 ERROR  karabo.AravisCamera  : SQS_AQS_UPP/CAM/A2A1920_2: arv_device_get_float_feature_value failed: GigEVision read_memory timeout
2023-11-23T23:02:30.007 WARN  karabo.AravisCamera  : SQS_AQS_UPP/CAM/A2A1920_2: Control of the camera exflqr50765 is lost
INFO  Successfully loaded plugin: "libslsDetectors.so"
INFO  Successfully loaded plugin: "libaravisCameras.so"
2023-11-23T23:02:33.773 INFO  openMq  : Opened TCP connection to broker %s:%d.
2023-11-23T23:02:33.775 INFO  openMq  : Connection ping enabled (ping interval = %d second).
2023-11-23T23:02:33.778 INFO  openMq  : Connection connected to broker
2023-11-23T23:02:33.778 INFO  karabo.net.JmsConnection  : Opened TCP connection to broker tcp://sa3-br-sys-broker-2:7777
2023-11-23T23:02:33.779 INFO  karabo.core.DeviceServer  : Logfiles are written to: "/scratch/xctrl/karabo/var/log/cppServer/sqs_nqs_vmi_cam/device-server.log"
2023-11-23T23:02:34.785 INFO  karabo.xms.SignalSlotable  : Instance starts up in topic 'SQS' as 'cppServer/sqs_nqs_vmi_cam' - Karabo 2.16.6
2023-11-23T23:02:34.786 INFO  cppServer/sqs_nqs_vmi_cam  : DeviceServer starts up with id: cppServer/sqs_nqs_vmi_cam
2023-11-23T23:02:34.786 INFO  cppServer/sqs_nqs_vmi_cam  : Updated list of devices available: AlarmService,AravisBasler2Camera,AravisBaslerCamera,AravisCamera,AravisPhotonicScienceCamera,CameraImageSource,DataLoggerManager,FileDataLogger,FileLogReader,Gotthard2Control,Gotthard2Receiver,GotthardControl,GotthardReceiver,GuiServerDevice,ImageSource,InfluxDataLogger,InfluxLogReader,JungfrauControl,JungfrauReceiver,PropertyTest
2023-11-23T23:02:34.934 INFO  karabo.core.DeviceServer  : Sending instance update as new device plugins are available: AravisBasler2Camera,AravisBaslerCamera
2023-11-23T23:02:34.934 INFO  cppServer/sqs_nqs_vmi_cam  : Keep watching directory: "/scratch/xctrl/karabo/plugins" for Device plugins
2023-11-23T23:02:34.934 INFO  cppServer/sqs_nqs_vmi_cam  : Starting Karabo DeviceServer (pid: 235604) on host: sqs-rr-sys-con-cams-1, serverId: cppServer/sqs_nqs_vmi_cam, Broker: tcp://sa3-br-sys-broker-2:7777
2023-11-23T23:02:35.073 INFO  karabo.core.DeviceServer  : Successfully connected to time server 'SQS_RR_UTC/TSYS/TIMESERVER'

==> Status of Taylor Cone unknown for runs 334 - 401

We had to physically unplug and replug the ethernet cable to the camera to get it to work again.

Achievements

• Optimized BOZ for Co and Fe
• Estabilished Stable liquid jet flow with 30 mM Fe(bpy)3

Problems

• Jet froze several times
• Chamber warmed up earlier in the day. This led to a "dusting" of CNCbl on many surfaces and in the large turbo. We cleaned the turbo with ethanol.

Plan for Night Shift

• Continue measuring stitic XAS with BOZ scheme.

Achievements

• Found coarse timing between XFEL and optical laser

Problems

• Did not see a observe fine timing signal from silicon nitride measurement

Plan for night shift

• Continue with liquid jet optimization and static measurements

Achievements

• Found RIXS signal from liquid jet
• Measured static RIXS and PFY-XAS spectrum of Co(cp)(CO)2

Problems

• hRIXS detector has a data latency issue and images were not being recorded in the DAQ. This required ~2-3 hours to solve plus time lost during night shift.

Plan for Next Shift

• find temporal overlap between X-ray and laser

Achievements

• Used scanning of liquid jet to improve S/N
• Measured x-ray PP XAS as a function of the delay between the two X-ray colors
• Scan energy of probe pulse with fixed pump energy

Problems

• No clear signature of ionized states observed in XAS yet

Achievements

• Located flat jet and attempted measurement of XAS at several incident energies 1300, 1305, 1315 eV

Problems

•  We have difficulty locating the beam on the sample
  • We have not found a signal on eith of the diodes in the Chem chamber.
  • Knife edges with the viking are daoable but require more extended analysis
• Jet froze due to a leakage from the side of the chip. The ice crusher has been avoided to solve
• The filter in the hRIXS was broken and had to be relplaced.

Achievement

• Measured tXAS at the Fe L-edge of Fe(bpy)3 using both delay and energy scans. 

Issues

• The cold traps ran empty on the chamber resulting in a pressure spike that interlocked the DSSC
• The rough vacuum of the chem DPS degraded causing TP5 to go into error. This resulted in valve closing and stopping the measurements
• Jet froze twice

Achievemnets

• Characterized the X-ray and laser danage on the STO2LNO2

Problems

• Cound not find fine timeing from XAS measurements performed on the sample
  • MCP sees 266 nm PP laser
  • SiN mesaurement not successful so far. It is possible that there is an issue with the SN membranes on the sample holder

Plan for next shift

• Find fine timing
• conclude damad sutdy of sample.

Achievements

• Characterized optical laser spot at sample

Problems

• FEL beam had very unstable intensity and spectrum. As a result no useful data could be collected during the night
  • FEL pointing seemed to be stable on all tunnel imagers. The issue was communicated to BKR, and they said that things looked fine from there perspective.
  • Large fluctuations in spectral distrubtion at SCS spectrometer were observed. See video at https://syncandshare.xfel.eu/index.php/s/emtwonCsQJJqpz6
  • Oth-order beam on SCS pop-in showed large intensity fluctuations with ~50% of the time showing no beam at all

Achievements

• Tested MCPs and APD for XAS
  • Both MCPs give a good XAS spectrum with no amplification, but small MCP requires higher bias voltage
  • No fluorescence signal observed on the APD
• Measured XAS of both samples
• Measured static RIXS of under-doped sample

Problems

• None

Plan for next shift

• Sample alignment (half clip+diffraction)
• Switch AFS laser to burst mode and find timing