This report will include this week and last week. We were able to clean the joints, install metal strips and caulk on 360 meters of enclosure.

Kyle, Gerardo 

Today we tested the functionality of the ion pump mounted at X2-8 using a local controller and cable -> pump works as expected -> We also changed the oil and filter on the diesel generator and finished installing the heat tapes etc. on the ion pump-connecting vacuum hardware -> We will start the 72 hr. bake out of the new ion pump Monday morning.  We will need access to BT port X2-8 every 10 hrs. or so between 0900 Monday morning thru Wednesday afternoon to refuel the generator.

Keita, Evan

We went in and removed the couplers between the EOM driver and the EOM (see 23472), as well as the extra phase delay cable on the ISC rack which was being used to match the coupler-induced delay.

Removing the couplers got rid of the extra noise on the 45 MHz OOL readback (see attachment).

Strangely, putting the couplers on the spare driver in the CER (which is terminated with a 50 Ω resistor, rather than an EOM) does not produce this extra noise (see attachment).

We have turned the spare driver back on and reconnected it to the digital system.

HWInjReport 1129593617 - 1131828544

Performed a run spanning the time period from 1129593617 (Oct 23 2015 00:00:00 UTC) to 1131828544 (Nov 17 2015 20:48:47 UTC)

Parameters

The following parameters were used for this run:

• GPS Start Time = 1129593617 # Beginning of time span, in GPS seconds, to search for injections
• GPS End Time = 1131828544 # Ending of time span, in GPS seconds, to search for injections
• Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
• Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
• IFO Coinc Time = 0.012 # Time window, in seconds, for coincidence between IFO injection events.
• Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
• Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
• Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
• Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
• Check CAL_RAW = True # Check CAL-INJ_ODC_CHANNEL_OUT_DQ channel in RAW frames.
• Report Normal = True # Include normal (IFO-coincident (network injections only), consistent, scheduled, and of known type) injections in report
• Report Anomalous = True # Include anomalous (non-IFO-coincident (network injections only), inconsistent, unscheduled, or of unknown type) injections in report
• Use CONDOR optimizations = True # Enable optimizations that assume execution on a CONDOR machine

Scheduled Injections

Only two injections were found to be scheduled during this period:

• CBC 1131397639.000 (coherentbbh0_1126259455_)
• CBC 1131405159.000 (coherentbbh0_1126259455_)

However, neither of these injections were found to actually occur within the examined time period.

Network and IFO Injections

There were no normal injections that occurred within the examined period. There were a number CAL-INJ resets, all single-IFO with the same curious pattern to the frame flags as denoted in the immediately prior HWInj report (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=23485). There was a single-IFO burst injection in H1

BURST 1129673117.000 (H1)

with the only anomaly being that it is UNSCHEDULED. There was a single UNKNOWN injection in L1

UNKNOWN 1129673117.000 (L1)

This injection was confirmed to occur only within the CAL-INJ channel of RAW frames with the TRANSIENT bit indicating an injection but none of the specific injection-type bits, CBC, BURST, DETCHAR, or STOCHASTIC, indicating an injection. It was confirmed to not occur in ODC HOFT, ODC RDS, ODC RAW, or GDS HOFT frames.

Discussion of Anomalies

It is interesting that the single-IFO injections BURST 1129673117.000 (H1) and UNKNOWN 1129673117.000 (L1) are found to occur at the exact same time but within different IFOs. Even further, the fact the BURST injection in H1 is perfectly normal, other than being UNSCHEDULED, while the UNKNOWN injection in L1, in addition to being UNSCHEDULED, is inconsistent. HWInjReport currently does not check the HW bit or the CW bit in the CAL-INJ channel for RAW frames for the presence of injections; however, upon examining these bits directly, it was found that while the HW bit indicated an injection, along with the TRANSIENT bit, the CW bit did not indicate an injection (my first thought was that this may be a CW injection only occurring in L1). This means this was a truly UNKNOWN, UNSCHEDULED injection occurring only with L1. Given both injections occur at the exact same time and the L1 injection is a truly UNKNOWN type (practically a ghost injection, by the bits), it is likely this was intended to be a normal network injection; however either user-error or a catastrophic software error corrupted the proper setting of the bits.

SudarshanK, RickS

Evan and Keita are done. Attempting to relock. ISI blends are on Quite_90 per Jim's request.

While trying to understand and deal with the Beckhoff SDF diffs in OBSERVE mode, I stumbled on a weird channel that toggled states around 4pm local last Wed Nov 11 (01 UTC WED 11th).  (Note, this occured well before the windy troublesome locking period when we saw a power glitch on Tuesd Wed 17th.)  If the VCO Frequency Servo is set to "Int" (see the center of the medm pic attached below), do we care what this EXTFREQUENCYOFFSET channel is doing?  And where is the medm for this EXTFREQUENCYOFFSET channel anyways? - Even with commissioners, we couldn't immediately find it...  And, and, what's with the glitch in the middle of the 20 day trend on Wed 11th?

Attached are the updated charge trends with this weeks newest data.  So far so good...

Evan and Keita are going into the H1 PSL enclosure to remove the RF AM monitor coupler from the EOM driver cable. This will take us out of lock.

The strip charts were stopping and starting periodically as evidenced by flat lines in the signal plots. Restarting the computer seems to have fixed it for now.

Out of observing briefly while Jeff B. went to end Y. Otherwise no issues.

O1 days 62,63

model restarts logged for Thu 19/Nov/2015 No restarts reported

model restarts logged for Wed 18/Nov/2015 No restarts reported

Jeff B. has been given permission to drive to end Y to take pictures in the receiving area and hallway to the VEA.

TITLE: 11/20 [DAY Shift]: 16:00-00:00 UTC (08:00-16:00 PDT), all times posted in UTC
STATE Of H1: Observing @ ~ 80 MPc.
OUTGOING OPERATOR: Jeff B.
QUICK SUMMARY: From the cameras the lights are off in the LVEA, PSL enclosure, end X, end Y and mid X. I can not tell if they are off at mid Y.
0.03 - 0.1 Hz seismic band is between ~ 0.01 and 0.04 um/s. 0.1 - 0.3 Hz seismic band is between ~ 0.1 and 0.4 um/s.
Winds are between ~ 0 and 5 mph.
ITMX, ITMY and BS ISI blends are on 45mHz. EMTX X and ETMY Y ISI blends are on 45mHz. ETMX Y and ETMY X ISI blends are on Quite_90.

Activity Log: All Times in UTC (PT)

08:00 (00:00) Take over from Ed
08:23 (00:23) GRB – LHO locked in Observing mode, LLO down – Ignored alert
08:45 (00:45) Lockloss – Unknown - ITM-Y & ETM-Y saturations at time of lockloss.
09:23 (01:23) Relocked in Observing mode
11:15 (03:15) Seismic_FOM_STS display crashed (Seismic DMT on nuc5) - Restarting 
15:00 (07:00) Tumbleweed bailing on X-Arm near CS – Then will go to LSB
16:00 (08:00) Turn over to Patrick
	


End of Shift Summary:

Title: 11/20/2015, Evening Shift 08:00 – 16:00 (00:00 – 08:00) All times in UTC (PT)

Support: None needed
 
Incoming Operator: Patrick

Shift Summary: Lockloss cause unknown. Relocked with no problems. IFO back into Observing mode. 
Seismic FOM (top display nuc5) crashed. Restarted the nuc. Waiting for Kerberos ticket to renew (at 12:00 (04:00), and will try to restart.

Good Owl shift. IFO in Observing mode for the past 6.75 hours, with a 76Mpc range. Three ETM-Y saturations during the second half of the shift. Wind is calm to light (0-4mph) Seismic activity is low, microseism centered around 0.35um/s.  

Previously I had noted a slow oscillation in the output power of the front end laser.  The
plot AmplifierPower.png partly shows the oscillation but unfortunately the fluctuation seen
is the one dominated by the humidity change in the Laser Room.  However the fluctuations are
more obvious in the pump diode power plot (DiodePower.png).  The question is then what is
driving these fluctuations?

DiodeTEC.png shows the voltage applied to the Peltier cell to cool the pump diodes.  The
fluctuation is clearly seen here.  It is also evident in the pump diode voltage (DiodeVoltage.png)
and current (DiodeCurrent.png).  It is possible that we have a small oscillation in the output
of the front end laser's two power supplies.  Or as Richard pointed out to me, it's possible
that the two power supplies are beating against each other.

The oscillation is not evident in the pre-modecleaner reflected light signal, and so is probably
just a curiosity at the moment.

Turned on the power watchdog for the laser, since it wasn't reset when the power glitch happened the other day.
13:14-something UTC.

(Borja, Vinny Roma)

This is a continuation of the work started yesterday here. Today, during maintenance, we worked all morning on the hunting of the 60Hz glitch noise and we can now confirm that the issue was identified and solved.

At  2015-11-17 17:10 (UTC) we arrived at the EndY station. We noticed an aircon unit outside of the building (although different model to that reported at Livingston) also used for cooling old clean rooms and no longer in use. We were sure that it was not running at the times that we observed the 60Hz bursts. We also noticed a fridge ON as we came in...more on this later.

We carried portable magnetometers similar to the ones used at the sites but plugged into oscilloscopes for portability. The area we concentrated most of our noise hunting was the electronics bay (EBAY) as from previous measurements we noticed that the bursts were stronger at the magnetometers located there (MAG_SUSRACK and MAG_SEISRACK) in comparison with MAG_VEA (see attached figure 'Comparison_MAGs_QUAD_SUM.png'). Looking at the spikes in more detail (see 'Zoom-spikes_Mag_VEA_and_EBAYs.png') we observe that while the spikes in MAG_VEA has a frequency of 60Hz, the spikes on MAG_EBAY_SUS and MAG__EBAY_SEI has double the frequency. This seems to be cause to a non-linear response of the transducer to the magnetic field, stronger in MAG_SEI than in MAG_SUS as both are identical sensors we assume the magnetic field from the spike is stronger at the SEI magnetometer.

Another clue that pointed to EBAY as the area of interest is the coherent plot attached of the MIC_EBAY and MIC_VEA_MINUSY with MAG_EBAY_SEI, we can clearly see correlations at 60Hz and harmonics being always stronger at MIC_EBAY. Notice however that we were never able to hear the burst so we assume the microphones pick them up electromagnetically.

In order to confirm that the bursts were actually real signals (instead of rack related issues) we swapped the axes of both magnetometers on EBAY as we observed they had different signal strenght. The change in the observed signal strength after the swap was compatible with the axes changes. Notice that we undid these changes after the morning work, so now is all back to normal.

Then we moved the portable magnetometer around the EBAY racks and noticed no strong magnetic noise anywhere with the exception of the 'PEM Endevco Power supply' which powers the accelerometers. The magnetic field around this box was very strong and MAG_EBAY_SEI is not far away from it. We also noticed that this was the only device connected to the wall AC power supply (see attached pictures) and this is also the case anywhere this PEM power supply is used.

We attach a time plot of EY_MAG_EBAY_SEI during the whole morning working period and we can see several things:

1) The time interval between bursts is much shorter and less regular than before (this was also observed previously when work was done at the End station). Compare attached plots from yesterday night ('Latest-60Hz_Bursts', very regular 85minutes separation between spikes) and today ('Morning_60Hz_timeplot_MAG', totally irregular with as short separation as 3 minutes).

2) The burst structure is different than the one previously related to 60Hz glitch noise (see here). For instance see the red circled area. During this time the vacuum cleaner was on near EBAY.

At this point we realized human activity with electric devices plugged to the wall at the station was involved with the generation of 60 Hz bursts although with a different signature to the bursts we knew and came to hunt.

Suddently for almost an hour (between hours 1.7 and 2.5 in plot 'Morning_60Hz_timeplot_MAG') we saw nothing. Then the burst became more spaced so after a while we tried to reproduce the vacuum cleaner burst signature by switching it on. The vacum cleaner was in the same room as the fridge and we noticed that the fridge was now turned OFF (we later learned that John and Bubba turned it OFF).

Then everything started to make sense...the fridge compresor only needs to be on when the temperature inside the fridge drops below a threshold which it can happen every 1.5 to 2 hours or longer depending on the environment temperature and quality of the fridge insulation. Notice that the interval between burst was shorter in summer than current months. Then the compresor is usually on for a few tens of minutes until the temperature is winthing desired range and then the compresor turns off. So in order to confirm the fridge as the cause of our 60Hz burst and glitches we tested turning it ON and we saw a burst (circled green on the previous plot at hour 3.5). And as we turned it OFF then the 60Hz burst dissapeared.

It appears that the fridge was ON the whole O1, this will no longer happen. But notice that any device drawing current from the mains seem to generate 60Hz bursts at least picked up by the magnetometers in EBAY, so soon we thought that maybe this is relared with the only device in that room that is plugged to the mains and that has a considerable Magnetic contamination...the 'PEM Endevco Power supply'.

So after lunch we went back to EndY station (arriving at UTC 23:07:00) with the intention of checking if unplugging the PEM Power Supply from the wall would be enough for the EBAY magnetometers not seeing the current draw by the fridge as this was turned on and off on 1 minute intervals for 3 times. For comparison we did the same test before with the Power supply still plugged and turned on. Unfotunatelly we see no difference between these two cases on MAG_EBAY_SEI as per attached plot 'Checking_PEM_Power_Supply_Coupling.png' magenta circle is with PEM Power Supply ON and brown is with the Power supply OFF. Interestingly however we can see a small spike at about UTC (23:34:00) when the turned off the Power supply and at 23:55:00 when we turned it back on.

Notice the spikes at the beginning correspond to our arrival to End station probably due to switching ON the shoe cleaner at the entrance and the desktop computer at EBAY.