anthony.sanchez@LIGO.ORG - posted 08:47, Thursday 27 April 2023 - last comment - 08:47, Thursday 27 April 2023(69065)
Tonys First attempt at Calibration Sweep Measurements
My first attempt at Calibration Sweeps created a report here :
/ligo/groups/cal/data/H1/reports/20230426T224835Z
This measurement was interupted by a lockloss .
Jeff and I spoke about what measurments it was able to get done before the lock loss and were surprised that it didn't make any BroadBand measurements. We had also edited line 28 of /ligo/groups/cal/ifo/H1/pydarm_cmd_H1.yaml by adding: - pcal before - bb. I will have to look more into what this script does to understand why it performed like this.
Images attached to this report
Comments related to this report
Tony's sentence "We had also edited line 28 of /ligo/groups/cal/ifo/H1/pydarm_cmd_H1.yaml by adding: - pcal before - bb." is referring to the changes mentioned in LHO:69059. His sentence "Jeff and I spoke about where what measurments it was able to get done before the lock loss and were surprised that it didn't make any BroadBand measurements." is reflecting that the command used to run "pydarm measure --run-headless" -- which is nicely copied over to the report directory exactly for this historical record -- /ligo/groups/cal/data/H1/reports/20230426T224835Z/pydarm_cmd_H1.yaml indeed shows that it *should* have taken a "bb" at the beginning at least. Instead, the contents of the directory are /ligo/groups/cal/data/H1/reports/20230426T224835Z/ DARMOLG_SS_20230426T224835Z.xml PCALY2DARM_SS_20230426T230552Z.xml SUSETMX_L1_SS_20230410T162452Z.xml PCALY2DARM_SS_20230410T164209Z.xml SUSETMX_L2_SS_20230410T165928Z.xml PCALY2DARM_SS_20230410T171645Z.xml SUSETMX_L3_SS_20230410T173402Z.xml so -- we're not sure *when* we lost lock during the measurement suite, so maybe it's OK that we don't have a PCALY2DARM_SS that pairs with the SUSETMX_L3_SS, but we should at *least* have a "start of the suite" BB measurement. Actually -- looking at what's in the directory, it looks like we lost lock in the middle of or after 2023-04-26 23:05:52 UTC, since all the other actuator measurements are from 2023-04-10. Bummer. We'll check with the development team to understand.
it should have taken a broadband at the start. we'll look into why it didn't. if we lost lock during the measurement the operator will need to kill the pydarm measure command (ctrl-c) and then clear the test point via diag