Attached are the September temperature and relative humidity plots for the SUS and 3IFO controlled environment storage boxes. All RH data is good. There were a couple of temperature spikes on DB1 and DB4 but no issues with humidity. 

Richard et al hooked up the missing temperature probes in the electroncis rooms. Attached is the new medm screen.

Channel names

                H1:PEM-C_MSR_RACK1_TEMPERATURE
                H1:PEM-C_MSR_RACK2_TEMPERATURE
                H1:PEM-C_CER_RACK1_TEMPERATURE
                H1:PEM-C_SUP_RACK1_TEMPERATURE
                H1:PEM-X_EBAY_RACK1_TEMPERATURE
                H1:PEM-X_EBAY_RACK2_TEMPERATURE
                H1:PEM-Y_EBAY_RACK1_TEMPERATURE
                H1:PEM-Y_EBAY_RACK2_TEMPERATURE
 

Betsy, TJ

Walked through and followed the checklist as closely as we could. There is still a power distribution box on near ISCT6 that seems to be plugged into many differenet things. Last week this was deemed OK for the time being so we left it as is. There are many cables still hanging from racks not plugged into anything. These will need to be cleaned up in a future Maintenance Day.

Lights are OFF

Monitors/Work Stations OFF

Wifi OFF

Phones disconnected and batteries taken out of handsets

Cranes in "parking spots"

Cleanrooms OFF

ISC table fans OFF

Forklifts are not charging

I have been somewhat curious about how our power recycling cavity's optical gain changes throughout a lock stretch.  This is a somewhat different analysis to Sheila's from aLog 21073, where she looked at what optical gain we first lock at. 

My first attachment shows the power recycling gain for both Hanford and Livingston for the first ~21 days of O1. Hanford is green xs, Livingston is blue dots. For Hanford, I estimate the PRC gain by multiplying the Yarm transmission by the PRM transmission.  For Livingston, I estimate the PRC gain by dividing the POP DC power by the power input to the IFO.  Both of these methods assume that the signals I'm using are appropriately calibrated, but they're the same way that seems to be used at each respective site by others.  So, while I don't guarantee the absolute values of the PRC gains in my plots, the trends are what I'm looking at.  Note also that these are every lock stretch that gets as far as the power-up state, regardless of comissioning/observing intent.

I am only plotting the PRC gain at times when the IFOs have completed their respective power-up states (LHO = INCREASE_POWER, LLO = RF_LOCKED_AT_25W).    I don't have much to say about this plot other than that overall, LHO seems to be a little more consistent at getting to the same PRC gain each lock. 

Perhaps more illuminating are the following 2 plots (one per IFO), where I have lined up the maximum PRC gain from each lock stretch (t0 for each trace is the time where the maxima occurs.  The start of the traces are the time when the state following the power-up state begins).  There are 49 traces on the LHO plot, and 111 on the LLO plot, so I'm just trying to look at the general character of the traces, rather than pick any one particular trace out of each plot. 

Here at LHO we have a large spike in the recycling gain right after we power up, then we settle out.  At LLO, they seem to have a much smaller, more smooth hump before settling out, although the time constant seems to be roughly similar between both sites.  At LLO (at least according to their guardian state names) they spend some time at 10W before going to full power, so that could be the reason for the difference in character. 

WP5538

the ext_alert.py code running on h1fescript0 was upgraded to version r11827

Starting from 1128187392 GPS, the DCS (LDAS) rds frames (frame-type H1_RDS) were updated to include all the channels needed by gstlal_compute_strain to calibrate the data:

H1:CAL-DARM_CTRL_WHITEN_OUT_DQ
H1:CAL-DARM_ERR_WHITEN_OUT_DQ
H1:CAL-PCALY_RX_PD_OUT_DQ
H1:CAL-CS_LINE_SUM_DQ
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_TST_REAL
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_TST_IMAG
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_REAL
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_IMAG
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_INV_REAL
H1:CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_INV_IMAG
H1:CAL-CS_TDEP_REF_CLGRATIO_CTRL_REAL
H1:CAL-CS_TDEP_REF_CLGRATIO_CTRL_IMAG
H1:CAL-CS_TDEP_PCALY_LINE2_REF_C_NOCAVPOLE_REAL
H1:CAL-CS_TDEP_PCALY_LINE2_REF_C_NOCAVPOLE_IMAG
H1:CAL-CS_TDEP_PCALY_LINE2_REF_D_REAL
H1:CAL-CS_TDEP_PCALY_LINE2_REF_D_IMAG
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_TST_REAL
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_TST_IMAG
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_REAL
H1:CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_IMAG
H1:SUS-ETMY_L3_CAL_LINE_OUT_DQ
H1:CAL-CS_TDEP_REF_INVA_CLGRATIO_TST_REAL
H1:CAL-CS_TDEP_REF_INVA_CLGRATIO_TST_IMAG
H1:ODC-MASTER_CHANNEL_OUT_DQ
H1:CAL-DELTAL_CTRL_TST_DQ
H1:CAL-DELTAL_CTRL_PUM_DQ
H1:CAL-DELTAL_CTRL_UIM_DQ
H1:CAL-DELTAL_RESIDUAL_DQ
H1:CAL-DELTAL_CTRL_DQ

Some of the faster channels were already in the rds frames. This increases the rds data rate from ~2.1 MB/s to ~2.2 MB/s

The same changes was made at LLO, with H1->L1.

The H1 and L1 DCS (LDAS) rds channel list are here:

http://www.ldas.ligo-wa.caltech.edu/ldas_outgoing/createrds/channels_H1_RDS/channelList-O1-H1_RDS.txt
http://www.ldas.ligo-la.caltech.edu/ldas_outgoing/createrds/channels_L1_RDS/channelList-O1-L1_RDS.txt

The attached plots show the inspiral range integrand, and cumulative integral, for a stretch of recent H1 strain data. This is just the standard integration of the strain noise power, weighted as (frequency)^(-7/3). I was also interested in the impact the 35-40 Hz calibration lines have on the range calculation, so the plots include a cumulative integral curve for which the calibration lines have been artificially removed from the strain spectrum (the strain noise in the 35-38 Hz band was replaced with the average strain noise at nearby frequencies). These curves (magenta) show that the calibration lines reduce the range calculation just a bit -- by just less than 1 Mpc.

The inspiral range for the spectrum used is 75 Mpc. 90% of the total is accumulated by 150 Hz; the second plot thus shows the same data from 0-150 Hz. At the lower frequency end, 10% of the total range comes from the band 16-26 Hz.

This morning I did a few things:

First I made some injections to the EMTX ISI (WP5528).  This data can be used to make a projection to the normal level of noise. 

I made 3 guardian changes (WP 5533):

I added a new state to the OMC_LOCK guardian which tries to keep the OMC off resonance, and the ISC_LOCK guardian requests this for the early part of lock acquisition.

Added a function which checks that the ETM pit oplevs have an rms less than 0.5 urad before we attempt to start locking again.   This will prevent tidal from acculating junk while the optics are still swinging. 

Changed the decorators in the ISC_LOCK guardian so that we do not check the DRMI lock once CARM is locked on the transmitted power (this will reduce th confusion in lockloss logs).

I also copied a bunch of medm screens and filters in the ASC ADS system from LLO, as well as scripts with help from Carl, Adam and Marie.  This is in preparation to try using Marie's modifications to Hang's A2L script.  

This morning, I took another set of 5 charge measurements on each ETM.  This morning was much quieter at the end stations and the measurments also ran through to completion, so the data from today look better than last weeks points.  Attached are the trends including todays new data.  The charge is hovering around ~20 V.

I looked back at the first TCS X slewing that Kiwamu, Stefan, and I did at the start of August. It seems that during this slewing, there was no null of the IMC jitter coupling. On the other hand, we already know that the coupling passes through a null close to the beginning of each lock stretch (22208).

First, the caveats: (1) the ISS outer loop was off during this test, and (2) one can see that the shape and location of the jitter peaks is different from what we normally observe in DARM.

The first attachment is a normalized spectrogram of DARM error during the slewing. It can be seen that the jitter peaks around 250 and 350 Hz increase monotonically from start to finish.

As a check, I looked again at the complex coherence between the IMC WFS error signals and DARM at the beginning and the end of this test (at 01:19:00 and 03:19:00, 2015-08-03 Z). Unlike what we see at the start of each lock, there is no sign flip of the coupling:

This seems to indicate that thermal tuning of the X arm alone is not enough to minimize the coupling. Either the null that we see at the beginning of each lock cannot be reached by thermal tuning, or we need thermal compensation on both arms.

Attached is 2 weeks of data.  No pressure fluctuations seen == Pumps running well.  Also on the plots are the Control Out from the VFD.  Looks like outside temperature trends showing at EndY and that is likely the reason for the large fluctuations on the L0 (CS) control--facility adjusting HVAC.  The daily and weekly glitches at the EndY continue unabated.

Levels steady for several weeks now.  No further maintenance required.

Motivated by our locking difficulties at the end of last week, I downloaded guardian state data for the last two weeks to look into our locklosses durring the CARM offset reduction.

To start with the good news, the script that I use to do this automatically makes a few figures that tell us about our duty cycle, and we are doing well overall. As usual, I am only looking at the guardian state, and not considering any intent bits.  My reaasoning is that the hardest part is getting and keeping the IFO locked, and that is currently the important limit to our duty cycle. 

• We have been locked in the nominal low noise state for 83% of the time (compared to 68% for the last week of ER8).  A good part of the improvement is probabably because the ground has been quieter in the last 2 weeks, although I didn't try to quantify that. (guardian state pie chart is the first attachment).
• About half of our DRMI locks result in nominal low noise locks (33/64).  A lockloss pie chart is in the second attachment. We have fewer locklosses in the late stages of the guardian, which could be because we are waiting for the first sets of ASC loops to engage before we engage the soft loops (alogs 21583 21587)
• The median low noise lock stretch was 5.5 hours long, while the longest was 59.7 hrs long.  A histogram of the length of low noise locks is in the third attachment.

The main weakness in our lock acquistion sequence now seems to be the early steps of CARM offset reduction, as we saw yesterday. 

•  We certaintly have a harder time with these early steps of CARM offset reduction when the ground motion is high, which explains most of our down time from the 2nd to the 3rd.
  • The 4th attachement show a histogram of locking attempts bined by ground motion, which is the maximum of the sum of the Y direction blrms for 30mHz-100mHz and 100-300mHz bands durring the locking attempt. I chose the Y direction at Y end because that tends to have more wind induced tilt, so this should include the impact of wind, earthquakes and useism.  You can see that we struggle to lock when the ground motion in these bands is above 250nm/sec, although occasionally we do suceed.  In the version of the plot attached here, I called a locking attempt sucsesfull if it reached the low noise state, but the plot doesn't change much if you instead make it for locks which make it past the stage where the DHARD ASC loops come on. 
  • The 5th attachment shows the ground motion over the last week, with a plot of the range to illustrate where the long stretch of downtime was.  Clearly, this was mostly time when the ground motion was high enough to cause us locking difficulties.
• One thing that might be hurting us in these early stages of CARM offset reduction is OMC flashing, see alog 22237. We will pull this off resonance using the guardian soon.  These OMC flashes are mostly not bright enough for us to see them on the AS camera, and it may just be that we see more OMC flashes when there is more light at the AS port because of bad alignment or high ground motion. 

Link to the DQ shif paget: DQ Shift page.

Summary:
 * October 1 had locks lost doing injections looking for scattered light in the X end. Otherwise a nice set of data, with a duty cycle ~80%.
 * October 2 and 3 there was some problems locking. High winds, beam splitter optical lever glitching, and ALS X/Y problems locking. At one point ~22 hours unlocked.
 * October 4, recovered from the past two days and had some long locks with a duty cycle ~80%.

I reset the PSL FE watchdog at 16:14 UTC (09:14 PDT).

TITLE: Oct 6 DAY Shift 15:00-23:00UTC (08:00-04:00 PDT), all times posted in UTC

STATE Of H1: Commissioning

OUTGOING OPERATOR: Patrick

QUICK SUMMARY:IFO in commissioning mode as Maintenance Day begins.

Expected Internet outage of about 15 minutes as one of our ISPs performs network maintenance this morning, between 0800 and 0900 Pacific (1500-1600 UTC).