General Announcement:

• .

CTRL:

• issues SA3 vacuum loop
  • gets more and more diffcult to recover
    • problem not clear, PLC comminucation is lost without obvious reasons
    • no software changes took place from either CTRL nor EEE ... component issue?
• fastadc issues --> EEE
• mirror in SA3 not always following a move ommand XTD10 M1

DA:

EEE:

• OCD at HED --> hexapod
• fineDelay

VAC:

• preventive action in XTD10 for GATT scroll pump

XPD:

• SA2 imager XTD6 pop in 45 after M3 small mark on the imager --> imager still usable

DET:

• nothing to report

ITDM:

• OCD call data aggregator at MID
  • need to understand better how to avoid the situation
• users complained to maxwell service (DESY directly) about limited resources becuase of high load by other users
  • there are reserved nodes --> use them!
• issues with scratch
  • more than 300 TB had been accumulated within a relatively short time
    • it seems that data was calibrated to scratch not to proc
    • MID comments --> a special calib mode was used that could not save to proc which is why it was saved to scratch
• problem with one of the proxy servers --> degraded performance of data migration

XRO:

LAS:

• issue at SA1 with Galvo
  • after shift change to FXE, laser was not working --> Galvo was out of phase
  • FXE resetted something (not clear) and the laser came back
  • LAS investigating the issue

UNSYS: 

• nothing special
  • a couple of times the undulators opened suddenly without any command issued.
  • O. Henssler from DESY proveds the logs

SPB/SFX:

• coupling with SA1 and SA2 (SA2 using train on demand) is an issue
  • beam walks off the XTD9 XGM aperture
• offset mirrors M2
  • pitch movement got stiff
• smaract cotnrollers
  • most fixed by increasing timeout windows

FXE:

• shutter can be opened despite closed vavales

MID:

• used pulse on demand
  • users were happy

HED:

• damage on M3 mirror
  • due to focusing scheme --> 9keV and intermediate focus --> during alignment unfortunately the focusing point came too close to M3
• meeting with XPD and XRO at 11:30
• hexapod issue reported to EEE is not quite fixed
  • ´status is not reporting the correct status of the hexapod
  • hexapod started working at some point and fell back to weird operation later again
• CRL arm7 seems to be at the limit of the x-axis
  • if FEL stays where it is, XTD1 chamber might need to be moved
• JUNGFRAU issue
  • up to a point the data is fine in the preview
    • after some runs data seen in the preview is not written to file

SCS:

• nothing to report

SQS:

• l