Sheila added a "Brief Version" of the initial alignment procedure to the OPS wiki page.  It is a the top of the IA wiki, above the more verbose version used by the operators up to now.  The idea is that as we become more familiar with locking the IFO, we'll need more of an outline of what to do than a step by step procedure with all the possiblilites spelled out.  She is hoping this will speed up the lock acquisition time and increase the duty cycle.

Struggled with wind all night.  Never got past DRMI 1f.  I did initial alignment several times (for practice and to make sure I wasn't missing something).  Good luck TJ.

Times UTC

11:00 Leo and Betsy still taking charge measurements

11:03 Robert back from Y arm beam tube enclosure

1:32 Leo done with charge measurements

1:42 returned ETMx and ETMy ESD to nominal states

2:00 started initial alignment

Winds have been mid-20 to low-30 MPH since the start of the shift.  Locking attempts have been unsuccessful, stalling at DRMI 1f so far.  I talked to Gary in the CR at LLO a couple of times now to give him a heads up that we are in for a tough evening.

from Corey, Janeen, Gary, and Vern

Today, in consultation with the Joint Run Planning Committee of the LVC, the following timetable for concluding ER7 was settled upon.

    The end date of focused data taking was 2015 June 11 8:00 am PDT.
    The end date of ER7 is 2015 June 14 8:00 am PDT.

Between these dates H1 and L1 will be run in a best-effort mode to have coincident locks, with intent bits set (getting us closer to and maybe surpassing the 48hr CBC target); however, they will share the time with the following invasive measurements that have been deemed as critical before the end of ER7:

    PEM Injections (H1 [Schofield] & L1)
    Stochastic Burst Injection (H1 [Kissel] & L1)
    Calibrations (H1 [Kissel] & L1)
    Guardian (L1) and Opportunistic Commissioning (L1 and H1)

All but the Stochastic Burst injections do not require coincident locks and their proposers have been encouraged to wait for a loss of lock by one of the IFOs before starting their activities.  Once begun, they should be carried to completion to a degree reasonably possible.  We expect quiet coincident times to be available in the late evening and early morning hours and the opportunities for invasive measurements to be more likely during the daytime hours. The Stochastic injections will have to be done when the proposers are ready and the IFOs locked.  The intent bits should be unset during the injections.

SCHEDULED WORK:

Nothing is totally set in stone, BUT if one of these items is scheduled to happen, it will happen (even if there is double-coincidence!).  For example, if one of the above is scheduled to happen and that person comes to you to say they are ready:

    Ask for an estimate of how long they'll be
    Call the LLO Control Room (225.686.3131) & let the Operator know how long H1 will be down
    Change Intent to Commissioning
    End lock of H1, if asked to.  (Is there a preferred way to take H1 down?)
    Make a note of this activity in the ALOG

OPPORTUNISTIC WORK:

Others may be more flexible with when they can start their work and may choose to do so at an opportunistic time (i.e. H1 [or L1] is DOWN).  In this case, do the same steps as noted above.

LLO Calls To Say L1 Will Be Down:

If L1 calls in to say they will be down to work on one of the activities above, it's up to local staff and you (the on-shift operator) to determine how to proceed.  Since we won't have double-coincidence, then we should jump on an opportunity to complete one of the above tasks.  So make an announcement to those who might be interested (i.e. Robert or Jeff) if they're in the Control Room.  If they're not in the Control Room, send an email to them (they'll likely be keeping an eye on the Summary Pages, too).  If there are no takers for H1, you can leave the Intent as Undisturbed.

COORDINATION BETWEEN CONTROL ROOMS

This is a new state for running in ER7, and coordination between sites is paramount.  So please don't hesitate to talk to the LLO Operator!

 

I've produced a 10 minute stochastic injection stream for simultaneous application at LHO and LLO when both machines are locked simultaneously. Hopefully there will still be a window of opportunity to run this test. The injection file is at h1hwinj1:/ligo/home/edward.daw/injections/SB_H1_ER7_V3.txt
The livingston counterpart file is at l1hwinj1:/home/edward.daw/injections/SB_L1_ER7_V3.txt

After the LHO IFO dropped lock around 1pm, Leo and I jumped on making more charge measurements of ETMx and ETMy via the oplev/ESDs.  However, we immediately recreated that there seemed to be no coherence in the ETMy measurements.  We fumbled around for a while looking at no coherence with signals here and there and then invoked Kissel.  Sure'nuf, the ESD drive on ETMy wasn't driving in "LO" or "HI" voltage mode.  Richard headed to end Y and re-discovered that turning things off and reterminating the DAC cable fixed the problem - see alog 13335 "Lock up of the DAC channels".

The ETMy measurements are now in progress.  Again.

Meanwhile, we attempted to look at why the ETMx LL ESD drive wasn't working and confirmed what Keita saw last night - it doesn't work.  We see the requested drive in the monitor channels which means that the signal goes bad somewhere beyond the chassis (toward the chamber).  As usual, "no one has been down there" but we're not sure how we can use this ESD to lock the IFO with a dead channel.  Richard reports that he will go there tomorrow to investigate.

Observation Bit: Undisturbed 

08:00 – Take over from Nutsinee – IFO locked at LSC_FF 
08:07 Robert – Working at End-Y, but not in the VEA
08:29 - Adjust ISS Diffracted power from 11.1% -2.06v to 8.3% -2.09v
09:32 - Beam tube cleaning crew start work on X-Arm
09:55 Christina & Karen – Open/close rollup door to OBS receiving
10:00 Christina & Karen – Staging garb in the OSB cleaning area
11:52 – Beam cleaning crew stopping for lunch 
13:05 - Lockloss
13:10 IFO in down state for ETM charge testing
13:30 Richard – Going to End-X
13:31 – Beam tube cleaning crew start work on X-Arm
13:50 Gerardo – Going to Mid-Y to get a cable
14:12 Gerardo – Back from Mid-Y
14:25 Richard – Back from End-X
14:36 Richard – Going to End-Y to check cabling for ETM charge testing
15:25 Robert – Going to Beam tube near Mid-Y
15:46 – Beam tube cleaning crew finished for the day
16:00 – Hand over to Travis

Andy, Jess

Since the 79.2 MHz fixed frequency source was powered off alog, we have not seen any RF beatnote/whistles in DARM at Hanford. We see them in DARM at Livingston, however, but the mechanism is much more complicated than Hanford. The mechanism is not the PSL VCO beating against a fixed frequency.

Since we still see whistles at Hanford in auxiliary channels, we thought we'd revisit them, to see if that gives us clues for L1. We looked at the lock of Jun 11 starting at 6 UTC. We see whistles in PRCL, LSC-MCL, and sometimes in SRCL. Choosing two times, we find that the whistles correspond exactly to a beatnote of the PSL VCO frequency with a fixed frequency of 78.5 MHz (or something within a few hundred Hz of that). So it's the same simple mechanism as before, just against a different frequency.

Attached are plots of two times in PRCL where we predict the exact shape of the whistle, using IMC-F as a proxy for the PSL VCO frequency. SRCL and MCL are similar. We'll go back and check other locks to see if there's any evidence for other frequencies or shifts in the frequency.

I've taken a look at guardian state information from the last week, with the goal of getting an idea of what we can do to improve our duty cycle. The main messages is that we spent 63% of our time in the nominal low noise state, 13% in the down state, (mostly because the DOWN state was requested), and 8.7% of the week trying to lock DRMI. 

Details

I have not taken into account if the intent bit was set or not during this time, I'm only considering the guardian state.  These are based on 7 days of data, starting at 19:24:48 UTC on June3rd.  The first pie chart shows the percentage of the time during the week the guardian was in a certain state.  For legibility states that took up less than 1% of the week are unlabeled, some of the labels are slightly in the wrong position but you can figure out where they should be if you care. The first two charts show the percentage of the time during the week we were in a particular state, the second chart shows only the unlocked time. 

DOWN as the requested state

We were requesting DOWN for 12.13% of the week, or 20.4 hours.  Down could be the requested state because operators were doing initial alignment, we were in the middle of maintainece (4 hours ), or it was too windy for locking.  Although I haven't done any careful study, I would guess that most of this time was spent on inital alingment.

There are probably three ways to reduce the time spent on initial alignment:

• reducing the number of times that we do initial alignment.  We don't really know how often we need to be doing this, and we might be able to do some offloading in full lock before powering up and see if that gives us an alignment that is good for lock acquisition.
• There are a few improvements to the ALIGN_IFO guardian that might help a little. 
• Last, as the operators get more experience with the alignment procedure it should become faster.

Bounce and roll mode damping

We spent 5.3% of the week waiting in states between lock DRMI and LSC FF, when the state was already the requested state.  Most of this was after RF DARM, and is probably because people were trying to damp bounce and roll or waiting for them to damp.  A more careful study of how well we can tolerate these modes being rung up will tell us it is really necessary to wait, and better automation using the monitors can probably help us damp them more efficiently. 

Locking DRMI

we spent 8.7% of the week locking DRMI, 14.6 hours.  During this time we made 109 attempts to lock it, (10 of these ended in ALS locklosses), and the median time per lock attempt was 5.4 minutes.  From the histogram of time for DRMI locking attempts(3rd attachment), you can see that the mean locking time is increased by 6 attempts that took more than a half hour, presumably either because DRMI was not well aligned or because the wind was high. It is probably worth checking if these were really due to wind or something else.  This histogram includes unsuccessful as well as successful attempts.  

Probably the most effective way to reduce the time we spend locking DRMI would be to prevent locklosses later in the lock acquisition sequence, which we have had many of this week.

Locklosses

A more careful study of locklosses during ER7 needs to be done. The last plot attached here shows from which guardian state we lost lock, they are fairly well distributed throughout the lock acquisition process. The locklosses from states after DRMI has locked are more costly to us, while locklosses from the state "locking arms green" don't cost us much time and are expect as the optics swing after a lockloss. 

If you look at the Online EarthQuake Arrival Predictor, it shows the 5.7 mag EQ in Japan, along with many others.  This is just the largest in the last day or so.  I've overlayed the predicted arrival time of the Rayleigh waves on the STS2 ground seismometers and the BS stage2 inertial sensors--see attached.  Unfortunately the IFO was not in lock at the time.

Anyway, need a bigger EQ still to assess the prediction as the Ground sensors.  Just to be more thorough, I shifted and extended the plot a little and now include the predicted arrival times of the P & S waves, second attachment.  I got rid of the Z ground seismometer and added the transmitted arm power for a IFO indicator.  Did the arrival of the p wave ring up the BS ISI?  Ehh I don't think so given the ground seismo unless the prediction is off by ~90 seconds.  But I think the prediction could be off by that much given the complexity of travel paths and assumptions of the velocitys.  With this data set I'd say the ISI is being beat around by the locking attempts, not by this red earthquake.

Adjust the ISS diffracted power from 11.1% -2.06v to 8.3% -2.09v 

Cleared the HEPI L4C watchdog counter for ITMY. All others were green and clear.

Scott L. Ed P.
6/8/15
The following are some of the dirtiest area we have seen on the X-arm.
Cleaned 58 meters ending 8.4 meters north of HNW-4-068.

6/9/15
 Maintenance day which means we can use the Hilti HEPA vacuum, the most effective vacuum for cleaning out the support tubes. We have been holding off on using this vacuum during ER7 because of the loud thump emitted from the internal cleaning system of the hepa filter.
We will go back and clean 2 sets of support tubes and cap them, as well as move forward to clean as many supports as reasonable before the end of maintenance day at noon.
Cleaned 30 meters of tube ending at HNW-4-070. Test results posted on this A-log.
 
Robert Schofield came out to the area where we are cleaning to look at our procedure and methods of actual cleaning of the tube to investigate possible glitches seen by the control room operators during lock.

6/10/15
Remove lights, cords, vacuum machines, and all related equipment from enclosure and thoroughly clean all equipment, then relocate to next section north.
Started cleaning at HNW-4-070, cleaned 15 meters of tube.

To date we have cleaned a total of 3418 meters of tube. 

Since we got a few coincident burst hardware injections this morning, and the rest of ER7 (now through Sunday 8:00 PDT) will be split between local measurements/commissioning and running, I have disabled the scheduled burst hardware injections for the rest of ER7.  To be precise, I left the next few dozen in the schedule but I set their amplitudes to zero, in order to test the long-term behavior and stability of tinj; tinj will call awgstream to inject them, but because awgstream will just add zero strain to the instrument, these should have no effect and will not appear in ODC bits or database segments.

There is still a plan to add a stochastic injection sometime before ER7 ends, if time permits.

00:00 The ifo locked right before I came in. Wind speed is <20 mph. 90 mHz blend filter is used for BSC2.

           I noticed the BS oplev sum is saturated (> 80000 counts). Is this alright? It's been around this value for 10+ days.

01:55 There's a big bump at ~30 Hz that caused a big dip in the BNS range. SUS Oplev plots didn't show anything suspicious. The bump at this frequency happened through out the night, just not as big.

02:00 A 4.7 MAG earthquake in Ecuador shook PR3 a little and BNS range dropped slightly (from 61 Mpc to 60 Mpc), but that's all it did. No WD tripped. 

08:00 We've been locked for 8+ hours and still going strong at 61 Mpc! We had 5+ hours of coincidence with Livingston tonight. Handling the ifo to Jeff B.

Sudarshan, Kiwamu, Darkhan,

Abstract

According to the PCALY line at 540.7 Hz, the DARM cavity pole frequency dropped by roughly 7 Hz from the 17 W configuration to the 23 W (alog 18923). The frequency remained constant after the power increment to 23 W. This certainly impacts on the GDS and CAL-CS calibration by 2 % or so above 350 Hz.

Method

Today we've extracted CAL-DELTAL data from ER7 (June 3 - June 8) to track cavity pole frequency shift in this period. The portion of data that can be used are only then DARM had stable lock, so for our calculation we've used a filtered data taking only data at GPS_TIME when guardian flag was > 501.

From an FFT at a single frequency it is possible to obtain DARM gain and the cavity pole frequency from the phase of the DARM line at a particular frequency at which the drive phase is known or not changing. Since the phase of the resultant FFT does not depend on the optical gain but the cavity pole, looking at the phase essentially gives us information about the cavity pole (see for example alog 18436). However we do not know the phase offset due to time-delay and perhaps for some uncompensated filter. We've decided to focus on cavity pole frequency fluctuations (Delta f_p), rather than trying to find actual cavity pole. In our calculations we have assumed that the change in phase come entirely from cavity pole frequency fluctuations.

The phase of the DARM optical plant can be written as

phi = arctan(- f / f_p),

where          f is the Pcal line frequency;

                     f_p - the cavity pole frequency.

Since this equation does not include any dependence on optical gain, the technique we use, according to our knowledge, the measured value of phi does not get disturbed by the change of the optical gain. Introducing a first order perturbation in f_p, one can linearize the above equation to the following:

               f_p^2 + f^2
(Delta f_p) = ------------- (Delta phi)
                    f

An advantage of using this linearized form is that we don't have to do an absolute calibation of the cavity pole frequency since it focues on fluctuations rather than the absolute values.

Results

Using f_p = 355 Hz, the frequency of the cavity pole measured at the particular time (see alog 18420), and f = 540.7 Hz (Pcal EY line freq.), we can write Delta f_p as

Delta f_p = 773.78 * (Delta phi)

Delta f_p trend based on ER7 data is given in the attached plot: "Delta phi" (in degrees) in the upper subplot and "Delta f_p" (in Hz) in the lower subplot.

Judging by overall trend in Delta f_p we can say that the cavity pole frequency dropped to about 7 Hz after June 6, 3:00 UTC, this correspond to a time when PSL power was changed from 17 W to 23 W (see lho alog 18923, [WP] 5252)

Delta phi also show fast fluctuations of about +/-3 degrees, and right now we do not know the reason that causes this "fuzzyness" of the measured phase.

Filtered channel data was saved into:

aligocalibration/trunk/Runs/ER7/H1/Measurements/PCAL_TRENDS/H1-calib_1117324816-1117670416_501above.txt (@ r737)

Scripts and results were saved into:

aligocalibration/trunk/Runs/ER7/H1/Scripts/PCAL_TRENDS (@ r736)

Using two hours of undisturbed data from last night's 66 Mpc lock, I repeated Den's sum/null stream analysis in order to see if we have a similar 1/f^1/2 excess in our residual.

I took the OMC sum/null data (calibrated into milliamps), undid the effect of the DARM OLTF in order to get an estimate for the freerunning OMC current, and then scaled by the DARM optical gain (3.5 mA/pm, with a pole at 355 Hz) to get the equivalent freerunning DARM displacement. The residual is then the quadrature difference between the sum and null ASDs.

The attachment shows the sum, null, and residual ASDs, along with the anticipated coating Brownian noise from GWINC. [Just to be clear: the "sum" trace on this plot corresponds to our usual freerunning DARM estimate, although in this case it comes purely from the error signal rather than a combination of the error and control signals.]

If there is some kind of excess 1/f^1/2 noise here, it is not yet large enough to dominate the residual. Right now it looks like the residual is at least a factor of 2.2 higher than the expected coating noise at all frequencies. We already know some of this is intensity noise.

The other thing to note here is that we are evidently not completely dominated by shot noise above 1 kHz.

Posted are data for the two long term storage dry boxes (DB1 & DB4) in use in the VPW. Measurement data looks good, with no issues or problems being noted. I will collect the data from the desiccant cabinet in the LVEA during the next maintenance window.   

After a measurement of charge on each ETM yesterday, I took a few more on each today.  Attached show the results trended with the measurements taken in April and Jan of this year.  There appears to be more charge on the ETMs than in previous measurements, although there is quite a spread in the measurements.  The ion pumps at the end stations are valved in.