2019-07-30 ~18:00 UTC - As per Dec 2018 instructions (LHO aLOG 45696), clicked HOLD OUTPUT button on Y-ARM camera. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=45696 - Noted that with the ISC_LOCK guarian in DOWN, we were getting reasonable *red* flashes in the arms (see front wall FOM strip tool of powers) - checked ITMY, EMY, and TMSY against 2019-07-30 06:56 UTC -- the last time we were in LOCKING_ARMS_GREEN (state 12 of ISC_LOCK). Sliders are at the same value. - With ISC_LOCK, INIT_ALIGN, ALIGN_IFO, and ALS_YARM guardian's "ALL STATES" screen open and accessible. 2019-07-30 18:09 UTC - Requested INITIAL_ALIGNMENT of ISC_LOCK. This initializes INIT_ALIGN (automated intitial alignment guardian), which at the start preps for green. - waited for INIT_ALIGN to complete PREP_FOR_GREEN, then requested PREP_FOR_GREEN and paused the guardian. - Switched ALIGN_IFO to "AUTO" so that no one is managing it - Requested ALS_YARM guardian (currently in UNLOCKED) to go INITIAL ALIGNMENT (remember green camera loops are OFF but holding the output to zero) Flashes were too low (0.5-ish). Getting ~5 second lock stretched, and then lock loss. - Also requested ALS_XARM to be INITIAL_ALIGNMENT. Successful. - Found that the green ALS cameras shown on the wall are showing the spool cameras not the ALS cameras. Whoops! - Requested ALS_YARM to be UNLOCKED. Flashes via camera images showing a pitch problem. Moved up TMS sliders a bit, but didn't get much action. Moved ETMY 1.3 urad in pitch, recovered good flashes. - Requested ALS_YARM to be INITIAL ALIGNMENT again -- success (again with camera DOF3 outputs held at zero) - with WFS converged, camera position / error signals are at ~0.3 in pit, 1.1-ish in yaw Now we want to get back on track with initial alignment, so we want to re-engage on the automatic initial alignment sequence. Both arms are in INITIAL ALIGNMENT, and INIT_ALIGN is PAUSED in PREP_FOR_GREEN. Move INIT_ALIGN guardian to MANUAL MODE. Request OFFLOADING_GREEN_WFS Move INIT_ALIGN back to AUTO Request INIT_ALIGN to to go to EXEC - Noticed that YARM wasn't converging, but only because it would occassionally lose lock. Figured it might be that snesor correction is still off site-wide (as is normal for maintenance day). - Drilling is still on going, so we don't want to turn on sensor correction inthe corner. So, use individual end station subordinates to be in their "nominal" state: H1:GRD-HPI_ETMY_SC_STATE_S > CONFIG_SC_ON H1:GRD-HPI_ETMX_SC_STATE_S > CONFIG_SC_ON H1:GRD-ISI_ETMY_ST1_SC_STATE_S > CONFIG_WINDY H1:GRD-ISI_ETMY_ST2_SC_STATE_S > CONFIG_FIR H1:GRD-ISI_ETMX_ST1_SC_STATE_S > CONFIG_WINDY H1:GRD-ISI_ETMX_ST2_SC_STATE_S > CONFIG_FIR Match H1:ISI-ETM[X/Y]_ST1_SENSCOR_[X/Y]_MATCH_GAIN set to 1.0 by hand. - ALS_YARM refuses to go to GREEN_WFS_OFFLOADED, because camera error signal is too large. << THIS CONFIRMS, INDEED, THAT THE CAMERA WAS BUMPED Move ALS_YARM to MANUAL Request OFFLOAD_GREEN_WFS Move ALS_YARM to AUTO Restore management of ALS_YARM to be INIT_ALIGN node (instead of the us, the "user") in a terminal >> caput H1:GRD-ALS_YARM_MANAGER INIT_ALIGN INIT_ALIGN now is happy, and quickly switches ALS_YARM through GREEN_WFS_OFFLOADED to UNLOCKED (which is normal). Now progressing through the rest of initial alignment automatically, but requesting INIT_ALIGN_COMPLETE. Having trouble with acquiring PRX. Following troubleshooting checklist T1600483-v8 Taking ALIGN_IFO to DOWN. Adjust PRM to maximize amplitude ASC_AS_A_DC requested PRC_ALIGN_OFFLOAD Meanwhile a DAQ restart is happening, which kills our NDSSCOPE sessions, and throws connection errors in DIAG_MAIN. Just decide to wait it out. Somehow ALIGN_IFO became unmanaged during the debugging request. INIT_ALIGN complains, because INIT_ALIN wanted PRC_ALIGNING not PRC_ALIGN_OFFLOADED. And at this point PRC_ALIGN_OFFLOADED is complete. To fix: caput H1:GRD-ALIGN_IFO_MANAGER INIT_ALIGN switch INIT_ALIGN to MANUAL, request MICH_BRIGHT_ALIGNING (to jump over the PRC_ALIGN_OFFLOAD step) switch INIT_ALIGN back to AUTO. Request INIT_ALIGN_COMPLETE Success (even Jenne's new automated SRC trick worked.) 2019-07-30 19:13 UTC Request Down > Init > Down of ISC_LOCK. Run through normal acquistion sequence. No problems with ALS. No problems acquiring DRMI. Not abnormally long, but it took ~5 minutes for DRMI ASC to converge. DARM_WFS turn on, no majorly large error signals. Requesting PARK_ALS_VCO. Move ISC_LOCK to MANUAL Request CARM_OFFSET_REDUCTION (skipping SHUTTER ALS) Move back to AUTO request PREP_ASC_FOR_FULL_IFO to resume CARM reduction. Lost loss mid-SOFT_LOOPS engagment. #PATTERN1 Lock loss at DRMI -- right at the star of the CARM reduction. PATTERN#2 Made it through to ENGAGE_ASC_FOR_FULL_IFO again, but lost light right at after requesting ENGAGE_SOFT_LOOPS again. #PATTERN1 Several successive lock losses because ALSX ARM WFS are suddenly deciding to steer the XARM off in to the weeds. #PATTERN3 Workaround: Turned off input on ALS X DOF1 PIT -- for a bit MAYBE WE NEED THE SAME INPUT LIMITERS AS THE RED ASC SYSTEM. In parallel -- updated GREEN Camera Alignment References to the time when the red ASC system is in the process of converging :: We lose lock before soft loops are engaged, and the soft loops are steering the optics/ spot positions via the ADS system to a place that is good for avoiding spot positions at MAXIMUM POWER, but likely bad for the acquisiion sequence. Ideally we'd want to hold in ENGAGE_ASC_FOR_FULL_IFO, but we lose lock before they converge. Keita argues that putting the green reference somewhere in the middle of the converge is better than the previously known wrong settings. OLD New H1:ALS-Y_CAM_ITM_PIT_OFS 268.97 240 H1:ALS-Y_CAM_ITM_YAW_OFS 302.27 208 Another lockloss at the beginning of the CARM reduction. PATTERN#2 Now that we have updated green alignment settings -- we're going for he full initial alignment sequence align, now USING the updated green camera reference settings. - Turn OFF the HOLD_OUTPUT on DOF3 for PIT and YAW on ALS Y. 20:57 UTC Request INITIAL_ALIGNMENT in ISC_LOCK, and run through the automated initial alignment sequence. Everything runs smoothly without any human intervention. 21:21 UTC Starting acquisition sequence. Lost lock at CARM_TO_TR #PATTERN2 Still fails. Bring IFO to PREP_TR_CARM, begin investing what we know of the CARM reduction. Lost in the weeds of figuring out what signals to look at. While we're figuring out our CARM lives, the DRMI build-ups decay a bit and look more noisey. Found via the LSC_CUST_SUMMINGNODE.adl screen (via ALS OVERVIEW) that the inputs to the IFO REFL servo / common mode board are H1:ALS-C_COMM_A_RF_ERR_OUT_DQ ---- REFLIN2 H1:ALS-C_REFL_DC_ERR_DQ ---- REFLIN1 So these are the error signals we're transitioning between. Drive a line in MC2 ISC INF as a poor-person's frequency noise drive comparison between the two channels. Since we don't suspect anything wrong with these error signals or the control transitions (we got past this ages ago), we suspect the change in ITMY aligment because of the new camera reference setting. remind ourselves that no ASC system is touching the ITMs -- but Green WFS are still on for ETMY and TMSY. SO -- we noodle the alignment of ITMY, looking for improvement in DRMI buildups and changes in the 30 Hz signal we're driving peak heights in the above two channels End up liking -0.4 YAw adjustment -- no change in frequency noise line, but DRMI build-ups look a bit better. Without any real smoking gun of whether this is better, we whistle in the dark, and try to go up. 22:36 UTC SUCCESS. No gauranteed repeatable success, but at least success. Further, instead of stalling at ENGAGE_ASC_FOR_FULL_IFO looking for good green offsets (and while that happens buildups are dropping as they normally do), we just directly going further through to ENGAGE_SOFT_LOOPS -- in order to "catch" the drop in build-ups with the SOFT loops as quickly as we normally do -- in to ENGAGE DC VIOLINS. i.e. to fix #PATTERN1 Successfully past through it, but a really rough and scary transition. 22:50 UTC hit ENGAGE DC VIOLINS. Began to see the same ~0.55 Hz oscillation that we saw earlier in the week when we stayed in the this state too long, so the IFO forced our hand so we requested INCREASE_POWER, this started to safe things. And at this point patience got the best of us, so we requested NOMINAL LOW NOISE. T'was an even more scary / rough go through the power up as ASC struggled to keep up (and likely is still starting at the wrong place) but it made it 23:02 UTC Nominal low noise. Accept the new camera positions -- but there's no gaurantee.