From 0bb242daa55d3ffce56dbac9bc19c15e8312d583 Mon Sep 17 00:00:00 2001 From: armborst_f Date: Wed, 24 Sep 2025 01:54:36 +0200 Subject: [PATCH] prep mdm --- docs/mdm/minutes/index.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/mdm/minutes/index.md b/docs/mdm/minutes/index.md index 9715957..6f2bc85 100644 --- a/docs/mdm/minutes/index.md +++ b/docs/mdm/minutes/index.md @@ -157,14 +157,23 @@ https://elog-gfa.psi.ch/SLS+RF/2117?suppress=1 * Small aperture, 21 mm, 2m long copper vacuum chamber upstream of X11/UE36 was removed and replaced with 40 mm chamber with additional pumping intersection * Machine performance from loss / lifetime perspective now acceptable, i.e., > 9 hour lifetime * Beam size remains increased by factor ~2, indicating remaining vacuum issue - * SU measurements and required vacuum (5e-7 mbar over 2 meter) to explain observed gas lifetime indicate remaining issue with UE36 in X11 + * SU measurements and required vacuum (5e-7 mbar over 2 meter) to explain observed gas lifetime indicate remaining issue with UE36 in X11 which also implicates undesirable localization of gas scattering losses * Post Mortem Diagnostics Issue * Due to negative measured doses on ARS09-DDRM-1530 and ARS09-DDRM-3500 the RadFET based dose distribution table is meaningless at the moment * Incidents/Issues * Risky beam dump Nr. 6 * [https://elog-gfa.psi.ch/SLS/62451](https://elog-gfa.psi.ch/SLS/62451) - * Caused by BPM Sector reboot and communication issue between machine experts concerning the orbit deviation beam dump + * [https://elog-gfa.psi.ch/SLS+RF/2121](https://elog-gfa.psi.ch/SLS+RF/2121) + * Happened during BPM Sector reboot + * Beam dump controller only triggered by RF stations + * Post mortem data clearly shows that beam was lost before dump kicker was fired + * Communication issue between machine experts concerning disabling the orbit deviation beam dump seems irrelevant * It would be good if the disabling and reenabling of the orbit deviation beam dump for sector reboots could be automized in a safe way + * Upcoming migration to gitea + * the migration is scheduled for the end of November, i.e., right in the middle of the first real SLS 2.0 user operation + * controls has announced one day of service interruption and warned that they will be completely busy preparing and performing migration until then + * any gitlab CI/CD has to be manually rewritten in order to work with gitea + * Changed repository naming, hierarchy, structure and AD integration to be taken into account * **Linac/LTB Optimization** by {{Lukas}} * ...