camilla.compton@LIGO.ORG - posted 14:54, Thursday 12 June 2025 (84997)
SQZ PSAMS Scan Ran, left PSAMS in Orginal Settings.
Jennie, Sheila, Camilla
Ran the userapps/.../sqz/h1/scripts/SCAN_PSAMS.py script with it optimizing SQZ with the 350Hz BLRMS rather than the high frequency ones to set SQZ angle.
Looking at the data (attached ndscope, heatmap, scans), it is hard to find a time to optimize both the bucket frequencies and high frequencies, which is a shame as in the past we've been able to improve this with the PSAMS.
It's best to look at the DARM BLRMs and try to minimize #3 (38-60Hz) and #4 (60-100Hz) for the best range.
For the heatmap, that we haven't found too useful in the past, there appears to be an issue with the "measured minimum sqz" color bar.
We tried the beloiw values, see attached ndscope:
- ZM4 @ 5.6, ZM5 @ -0.55
- Looked like high frequency would be good and low/mid frequencies fine, but range was bad.
- ZM4 @ 5.6, ZM5 @ -0.4
- Looks as good as nominal before test started with slightly better high freq, range wasn't as good as original
- ZM4 @ 6.0, ZM5 @ -0.4 (Nominal before test)
- Reverted to nominal as all other optiois seemed worse.
- However, range didn't immediately increase back to as high as it was before tests started.
Note we don't think that the 350Hz BLRMS is a good measure of the range as the yellow 350Hz BLRMS being good don't agree with good range times. We should add a 80-250Hz BLRMS in the place of BLRMS_2 with the hope that it would follow the range better.
Images attached to this report
