The TCS power guardian was having to consistently readjust, the tell tell sign that the calibration needs updating. I brought H1:TCS-ITMY_CO2_LASERPOWER_POWER_IN from 5.2 to 4.8 and that seemed to do the trick.

Dan put in custom mask #1 instead of the normal central heating mask, and I believe that the power monitor channel is after the mask. If this is true it would make sense that we would have to update the calibration then.

ETMX has been saturating for the last 20min and thought the control signals FOM looked normal, the DARM BLRMS looked awful. I suspected that this was due to the P2L and Y2L gain changes that I was warned about before commissioners left, so I tried bring them closer to their original values but it didn't seem to help much.

There was an SDF diff in the squeezer: nominally the SHG power servo is on, in this lock it was off, I am not sure why. Accepted the change, left the power servo off.

TITLE: 03/20 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY: Calm environment, at low noise, commissioners here working out the kinks.

TITLE: 03/20 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  PEM injections preventing us from going to Observing for first half of shift.  Currently sitting at NLN, but unable to go to Observing due to Guardian ISC_LOCK/ALIGN_IFO management confusion.  Commissioners working on a fix.
LOG: See previous aLogs.

We couldn't go into observation because ALIGN_IFO and ISC_LOCK were having disagreements about who was managing SQZ_MANAGER and complaining one was stolen by the other.

I removed SQZ_MANAGER from ALIGN_IFO line 40:

          node_list = sus_nodes + ['SQZ_MANAGER']

I reloaded and then all the warnings went away. I then put it back in, reloaded, and everything was fine.

DickG, MarcP

RF Noise    via CER TO ISC RACK CONTROL ELECTRONICS cabling:  RF= 9.100230 MHZ

For a locked working H1 IFO:
We have measured the coupling of a near RF frequency (pseudo noise) 9.100230 on cable ground..  
noise signal to "DARM"   as seen on control Room aLIGO DARM display.  
We here first try the main 9.100230 Mz cable, looking for a nearby beat "interference" as seen in DARM.
We couple an ISR RF signal at -20 dBV ie .1 Vrms and 9.100230 MHZ + 55 Hz, 65 Hz, and 105 Hz successively.

The coupling is inductive, via a ferrite core + single loop BNC to ISR RF Gen. around the main 
CER to ISC Rack 9.100230 MHz cable;  the cable and loop are thus a 1:1 transformer; a new gadget.
The driven loop plus ferrite induces external shield current at ~ 50 ohm cable level at 0 dBV  ie 1V rms.
The ISR freq was at 9.100285, 9.100295, and 9.100335 MHz.

> A clean 1.3 e-18 m/sqrthz level DARM "noise signal" spike  was seen at 55 Hz, 65 Hz, and 105 Hz 
> for the 3 frequencies  consistent with beating somewhere in the IFO 9.100230 MHz control detection systems.

>> The IFO tolerated a 'visible' noise signal...stayed locked.

We expect a ground noise signal on one cable gets shared amoungst all of the CER to ISC cables.
The transformer stratagem for driving or detecting on cable promises to make possible finding and curing 
the sources and leaks in our large  and imperfect system.
 
>>> The ferrite cable xfmr coupled to an RF Anal or source   is a good cable ground current noise diagnostic.

We expect to map out and understand the cable and module cross couplings, sources, and leaks; 
and perhaps control module negative features, 
and propose cures, fixes.

Working on relocking such that we can finally go to Observe now that all scheduled injections are complete for the night.

UTC 00:40 to 04:40

Tonight we made acoustic and magnetic injections at the Y-end station. We still have shaker injections to do there, but we completed the first round of speaker and coil injections at EY.

Dan Brown has created a script which starts and stops the frequency and intensity noise lines 47636.  Unfortunately, with this script the rest of the commissioning team did not have control over the lines.

Today I made a guardian called AWG_LINES out of his script.  It's in /opt/rtcds/userapps/trunk/isc/h1/guardian/AWG_LINES.py.

All it does is turn off and on the lines while correctly starting, stopping, and clearing the injection testpoints. 
 
There are two states that matter: IDLE and INJECTING.  
IDLE is nominal, no injections are enabled, and this is the start this guardian should be in during observing.  
INJECTING should have all the lines enabled, and is good for our commissioning tasks right now.  I will set up ISC_LOCK such that the lines are turned on in NOMINAL_LOW_NOISE.  This will have to be changed for the run.  I haven't had a chance to properly vet this guardian so I am leaving it out for now.
More lines can be added to the SET_UP_INJECTIONS state if desired.

EDIT: I just tested this guardian, it works as expected.  Now ISC_LOCK requests 'INJECTING' every time it reaches NOMINAL_LOW_NOISE.

Accepted the SDF diff shown in the screenshot.  Sheila was unaware of when or why this changed, so advised me to just document and accept.

I'm assuming these changes were made purposefully during the PCal maintenance tune-ups today.  Screenshots attached for posterity.

We saw a big 3.1 Hz instability in DHARD P (and other loops) a few minutes after getting to low noise in our second lock today.  We were constantly saturating ETMX PUM, and the rage dropped.  This seems similar to a problem seen at LLO (maybe 42442, I'm not sure if  43785 is related as well).  

We stepped down the output matrix elements that send DHARD P to the ITMs, and that made things better although the oscillation and saturations continued.  Once we engaged the ADS loops and the converged things got better.  For now we still have DHARD P sent to the ETMs only, because Anamaria told us that is what LLO is doing for this problem.  

We are hoping that this was a cross coupling due to our spot positions being way off for ADS, so we are hoping that for the next few locks we can try to wait and make sure that ADS is converged a bit before doing low noise ASC.  

No alogs from today yet state the situation, so here is the current status - we're still recovering from Tuesday Maint currently locked in Low Noise, however we have a bit of a mess to work through.

The LSC computer was glitched this morning at 9am when EE rack fan isolation work was taking place.  CALINJ is now red out of nominal (OFF). Dave brought the LSC back up (details below eventually), then numerous activities took place as per the morning plan:

- PCAL maint checks at both EY and EX

- Fan isolation in corner LSC and ASC racks, EX and EY ISC racks

- IMC board work by Daniel

- Charge measurements of ETMX

- DAQ/EDCU work by Dave

- 1Hz comb troubleshooting - no alogs to report anything on this yet

- Minor PMC and REFCAV alignment tuneup

- PSL REFCAV EOM driver cable swap

However, once back up at ~3pm local, major noise was present and we saw numerous SDF settings changes in the OBSERVE file (which was clean during the locking last night) mostly related to the OMC (from LSC model).  These were probably settings not saved correctly to the SAFE SDF file and then hung around through the locking to low noise.  Sheila has just attempted to walk those back by hand but the lock blew.  Back to locking now.

PEM was supposed to have some time today, however the maintenance/relocking went long, so they will attempt to work for a few more hours while yielding some hour long segments for OBS MODE starting later in the evening.  Slow thermal TCS tuning may also resume while in OBS MODE overnight, similar to last night.

BruCo scan here for last night lock: https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_lho_1237033818/

Some highlights:

• INP1_Y at ~ 20-30 Hz (plot 1) also visible in IMC yaw (plot 5)
• the bump at ~48 Hz is visible also in REFL_B_RF9 (plot 2)
• Below ~20 Hz OMC_RIN (but is this just another witness of DARM motion?) (plot 3)
• At 480 Hz bump, coherence with IMC WFS stuff (plot 4)
• PRCL is close between 30 and 150 Hz (plot 6)