This lock we will change the IFO input power to 60W, see alog 70497.

Already done:

• ETM ring heater settings adjusted: 70644,70616.
• Input power changed in from 75W to 60W in lscparams.py and ISC_LOCK reloaded.

Just lost lock at 15:05UTC, 1371395177. Looks like LSC-PRCL rang up in te ~3seconds before lockloss, see attached. Note that we are in a different thermal configuration while we prepare to lower input power, 70646.

TITLE: 06/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc Lock Acquisition
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: At 4am Tony turned down the ETM ring heaters 70644,70616. Today we plan to change the IFO input power to 60W, see alog 70497.

VAC, SUS, SEI, CDS, dust monitors okay.

Just lost lock at 15:05UTC, 1371395177

13:18 UTC Lockloss
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1371388721

11:22 UTC Lockloss 22 minutes after turning the ring heaters down.
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1371381773

While referencing alog 70616 I changed
H1:TCS-ETMX_RH_SETUPPERPOWER
H1:TCS-ETMX_RH_SETLOWERPOWER
&&
H1:TCS-ETMY_RH_SETUPPERPOWER
H1:TCS-ETMY_RH_SETLOWERPOWER

all to 1W from 1.2W. Change made at 11:00 UTC.
Changes accepted in SDF at 11:02 UTC.

TITLE: 06/21 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:
IFO Current Status: NOMINAL_LOW_NOISE & OBSERVING
Current Range: 136Mpc
 

TITLE: 06/21 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 138Mpc
SHIFT SUMMARY: One lock loss during the shift that seemed coincident with people going into the LVEA to unplug some test equipment. We've been observing since then for almost 5 hours.
LOG:

• 2335 Started Cal sensing function measurement.
• 0006 Ended
• 0029 Jenne, Naoki to LVEA to unplug cables
• 0031 Lockloss
• 0209 Observing

Naoki, Sheila

As part of noise budget with 75W, we did laser noise injection (frequency noise, intensity noise, jitter noise). Here is the instruction of laser noise injection.

The injection templates are in ligo/gitcommon/NoiseBudget/aligoNB/aligoNB/H1/coupling.

Frequency noise

template: Frequency_excitation.xml

Switch CARM control from REFL A+B to REFL B only:

• REFL A and B both have 9dB digital gain with 75W
• Step down 1dB on REFL A and up 1dB on REFL B until the REFL A gain is 3dB and REFL B gain is 15dB
• Step down REFL A gain down to -32dB 
• Turn off the input 1 switch (REFL_SERVO_IN1EN) for REFL A

Measurement:

• Take the reference without excitation and update the reference
• Plug the cable to the excitation port of CARM CMB in PSL rack and turn on the digital excitation switch (EXC A) of CARM CMB
• Start injection
• After the measurement, turn off the digital excitation switch, unplug the excitation cable, and bring back the CARM control

Intensity noise 

template: ISS_excitation_LF.xml, ISS_excitation_MF.xml, ISS_excitation_HF.xml

• Turn off the 10Hz pole in ISS second loop (PSL-ISS_THIRDLOOP_POLE_MON), and put 1 in the digital excitation gain (PSL-ISS_SECONDLOOP_EXCITATION_GAIN). The 10Hz pole and the digital excitation gain can be accessed from medm screen of ISS second loop as shown in the attached figure
• Take the reference without excitation and update the reference
• Start injection
• After the measurement, bring back the 10Hz pole and the digital excitation gain

Jitter noise

template: IMC_PZT_P_inj.xml, IMC_PZT_Y_inj.xml

• Take the reference without excitation and update the reference
• Start injection

The calibration reports for Friday's and today's sensing function measurements have been uploaded (arx committed) to the LHO cluster under the cal account. The report directories can be viewed directly from the cluster at the links below.

Friday (06/16/2023): https://ldas-jobs.ligo-wa.caltech.edu/~cal/archive/H1/reports/20230616T161654Z/
Tuesday (06/20/2023): https://ldas-jobs.ligo-wa.caltech.edu/~cal/archive/H1/reports/20230620T234012Z/

===== Logs

Today's calibration report taken by TJ (LHO 70635)
Friday's calibration report taken by Ryan Short (LHO 70520)


===== How to commit reports to the cluster
At Jeff's request, I'm including some short instructions for committing new calibration reports to the LHO cluster's cal account. This can be done by anyone in the control room with access to a control room workstation, but, for now, this should be reserved for members of the calibration group. 

The calibration group's uncertainty estimates, which are produced hourly at each site's cluster, depend on the latest GPR results (among other things). The GPR results are bundled within every calibration report [directory] each time new measurements are taken and processed. So every time new calibration measurements are taken and a new report exists, the report and all of its associated files (i.e. the "report directory") need to be 1.) inspected by a member of the calibration group, 2.) tagged as "valid" to let the GPR routine know that it should include the measurement, and 3.) "[arx] committed" to the site cluster's cal account.

Calibration report directory tags are simply empty files located in the report's tags sub-directory. To tag a report as "[GPR] valid]" use:
touch /ligo/groups/cal/H1/reports/<report id>/tags/valid

where <report_id> should be replaced by the report's timestamp. For example, to tag today's report, which has report id 20230620T234012Z, as valid I used the command below.
touch /ligo/groups/cal/H1/reports/20230620T234012Z/tags/valid

Finally, to commit (sync or push) the new report to the site cluster, we use the arx tool:
arx commit 20230620T234012Z

The arx output will display the command's progress as it rsync's each file within the report directory to the appropriate place. Once that's done the report will visible on directly on the site cluster at ldas-jobs.ligo-[w,l]a.caltech.edu/~cal/archive/[H,L]1/reports/<report id>.

Sheila, Brina, Naoki

Before stepping down the input power from 75W to 60W, we did the noise budget injection of laser noise (frequency noise, intensity noise, jitter noise), LSC noise (MICH/PRCL/SRCL), and ASC noise (CHARD P/Y, DHARD P/Y, MICH P/Y). These measurements were done without squeezing. We will make the noise budget based on these measurement soon.

1371342704

Jenne and Naoki went into the LVEA to unplug a cable, but it looks like that knocked us out.

Started at 1635 UTC, just over 2.5 hours into the lock.

Followed the usual instructions on the TakingCalibrationMeasurements wiki, with the command used "pydarm measure --run-headless bb sens pcal" for this measurement.

Seismon was restarted with the correct velocity in H1:SEI-SEISMON_LHO_ML_VELOCITY_{0..5} channels.  The value is now the "Machine Learning" velocity estimate.  Associated channels, H1:SEI-SEISMON_LHO_ML_UNCERTAINTY_{0..5} give an uncertainty to this measurement.

J. Kissel

To help out studies of the end station VEA temperatures and HVAC system, I've created templates of the relevant channels similar to those described in LHO:70284, but for the X and Y-end VEAs.

You can find them in 
    /ligo/home/jeffrey.kissel/Templates/NDScope/
        xvea_temp_study.yaml
        yvea_temp_study.yaml

TITLE: 06/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
SHIFT SUMMARY: Busy maintenance morning. Locked by early afternoon and now working on some commissioning tasks.

Lock #1:

• Initial alignment from 19:21-19:59
• Locking went smoothly and unassisted
• NLN @ 20:46

LOG:

TITLE: 06/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: We've been locked for over 2 hours. We are currently in commissioning to run measurements while we prepare for the power down.

Plot 1 shows the dark noise in LSC-REFL_A_LF and REFL_B_LF (yellow/black), with 10W laser input with ISS second loop (red/blue) and w/o ISS second loop (magenta/cyan). The photocurrent in REFL_A and REFL_B was about 16mW each for the 10W measurements. It will turn to about 10mW in full lock. So, we are now about a factor 4 above dark noise.

Plot 2 shows the RIN of the 2 REFL PDs and their average, together with the ISS second loop sensors. The ISS inner and outer sensors have about 7-8mW of light each, so the measurements are limited by the shot noise of the inner PD. In full lock these sensors see about 60mW.

Here is a list of the things we need to change to return as closely as possible to a desirable 60W configuration.

• Ring heaters: 1W ring heater power on both ETMX and ETMY. No change to the current ITM ring heater settings because we are running at the same settings as 60W
• CO2 settings: 1.7W annular on both ITMX and ITMY (we are currently running with these settings). Depending on the amount of time we have to do TCS additional commissioning, it might be worth some time to see if we can improve frequency noise by changing these settings differentially (increase CO2X power). See this alog comment for more details: alog 68842
• OM2 TSAMS: no change
• ASC, control design: I don't believe we need to make any changes to the loops. There has been significant update to the recycling cavity loop design at 76W, but these are power independent. The HARD loops are running with loop compensators designed for about 400 kW of power. I think dropping to 380 kW should not negatively impact the loops, as the hard loops have been stable through thermalization which can change the arm power by 30 kW. The soft loop compensator design is the same. We may even be able to reduce some soft loops gains, as most of the soft loop gains were increased to compensate for the 430 kW operation.
• ASC, HAM1 FF: pending another 5-10 minute on/off test to collect data, we can either use the current filters, or revert to ones that I tuned on April 6 while at 60W. See alog. The filters are named by the date they were installed (so just turn on the ones labeled 0406). We did not need HAM1 FF in the yaw loops at 60W, so we can turn off all those filters first and then check the necessity again.
• LSC, control design: we should consider reverting the PRCL control loop design. Gabriele designed a new loop that could manage the gain loss at 430 kW in addition to adjusting the loop gains. We will likely still need to adjust the PRCL loop gain throughout the lock at 60W. Once we go down in power we should dedicate some commissioning time to determine the gain loss trend and commission accordingly. We should also check that the UGF of MICH and SRCL are where we expect them to be. The PRCL1 filters are FM2, 3, 4, 5, and 6 with a gain of 11.6 and none of the PRCL2 filters were in use.
• LSC, feedforward: we will need to tune the LSC feedforward. We had been running with an outdated LSC feedforward with the plan to remeasure and update it once we settled on a final configuration. All recent updates occurred at 76W. The filter for SRCL was FM2, labelled EDH used with a gain of 1. The filters for MICH were FMs6-9, however FM9 has been overwritten by a new filter. I will use the archive to recover it. The MICH filters used a gain of 0.97.
• CARM gain: the CARM gain was increase by 3 dB to counteract the loss of gain that occurred during thermalization. We should remeasure CARM and determine if we still need that gain increase. alog 69152
• ISS second loop gain: we reduced the ISS second loop gain to -5 dB. We should remeasure the loop and determine a better gain setting for 60W. alog 68789
• SRCL offset: we had been running with an offset of -175. This was also with the previous LSC-POP_RF45 whitening at 21 dB. We could revert the whitening change as well if we think it's better for noise considerations
• DARM offset: 20 mA, not sure if we want to revert this value

If you are looking for a timestamp to determine when the power change occurred, the last full lock at 60W was on April 6 from about 17:00 UTC to April 7 3:30 UTC.