I ran the DARM offset step code starting at:
2024 Jun 13 16:13:20 UTC (GPS 1402330418)
Before recording this time stamp it records the PCAL current line settings and makes sure notches for 2 PCAL frequencies are set in the DARM2 filter bank.
It then puts all the PCAL power into these lines at 410.3 and 255Hz (giving them both a height of 4000 counts), and measures the current DARM offset value.
It then steps the DARM offset and waits for 120s each time.
The script stopped at 2024 Jun 13 16:27:48 UTC (GPS 1402331286).
In the analysis the PCAL lines can be used to calculate how the optical gain changes at each offset.
See the attached traces, where you can see that H1:OMC-READOUT_X0_OFFSET is stepped and the OMC-DCPD_SUM and ASC-AS_C respond to this change.
Watch this space for analysed data.
The script sets all the PCAL settings back to nominal after the test from the record it ook at the start.
The script lives here:
/ligo/gitcommon/labutils/darm_offset_step/auto_darm_offset_step.py
The data lives here:
/ligo/gitcommon/labutils/darm_offset_step/data/darm_offset_steps_2024_Jun_13_16_13_20_UTC.txt
See the results in the attached pdf also found at
/ligo/gitcommon/labutils/darm_offset_step/figures/plot_darm_optical_gain_vs_dcpd_sum/all_plots_plot_darm_optical_gain_vs_dcpd_sum_1402330422_380kW__Post_OFI_burn_and_pressure_spikes.pdf
The contrast defect is 0.889 ± 0.019 mW and the true DASRM offset 0 is 0.30 counts.
I plotted the power at the antisymmetric port as in this entry to find out the loss term between the input to HAM6 and the DCPDs, which in this case is (1/1.652) = 0.605 with 580.3 mW of light at the AS port insensitive to DARM length changes.