J. Kissel, R. Savage, LHO Operators Tallying up the progress so far on the schedule of PCALX excitations at high frequency (see plan in LHO aLOG 24802): Achieved Planned Frequency Amplitude Start Time Stop Time Duration Duration Success? (Hz) (ct) (mm-dd UTC) (mm-dd UTC) (hh:mm) (hh:mm) (Yes / No, reason if no) ------------------------------------------------------------------------------------------------------------------------------ 1001.3 35k 01-09 22:45 01-10 00:05 01:20 01:00 Yes 1501.3 35k 01-09 21:12 01-09 22:42 01:30 01:00 Yes 2001.3 35k 01-09 18:38 01-09 21:03 02:25 02:00 Yes 2501.3 40k 01-09 12:13 01-09 18:31 06:18 02:00 Yes 3001.3 35k 01-10 00:09 01-10 04:38 04:29 04:00 Yes 3501.3 35k 01-10 04:41 01-10 12:07 05:26 06:00 Good Enough! 4001.3 40k 01-09 04:11 01-09 12:04 07:55 08:00 Good Enough! 4501.3 40k 01-10 17:38 01-11 06:02 12:24 12:00 Yes 5001.3 40k 01-11 06:18 on-going (as long as we can get) Thanks to all of the operators who have been dilligently caring for these lines while we sleep! For the record, while these PCALX calibration lines are on, the majority (if not all) of the range is consumed, so we cannot perform PCALX hardware injections.
I used the high frequency calibration lines injected above to estimate the sensing function at those frequencies. For this analysis, SLM Tool was used to obtain the line amplitude and phase of these calibration lines at different relevant channels.
Sensing Function = DARM_ERR[ct] / PCAL_TXPD[m]
The DARM_ERR signal is dewhitened and the PCAL_TXPD is corrected to get metres using the scheme described in G1501518.
Furthermore, ratio of GDS/Pcal is calculated and is included in the attached plot.
A data quality flag has been created to capture times when these extra PCAL lines were in the data. It is H1:DCH-EXTRA_PCAL_LINES:1 and a description of this flag can be found on the detchar wiki.