David B., Jim B., Patrick T.

We looked at H1:ALS-Y_REFL_SERVO_IN1EN from '00:00:00 Nov 2 PDT' to '03:00:00 Nov 2 PST'. The correct behavior is observed:

...
11/02/2014 01:59:59.005479920 PDT 	Off 	NO_ALARM 	NO_ALARM
11/02/2014 01:59:59.055615806 PDT 	On 	NO_ALARM 	NO_ALARM
11/02/2014 01:00:01.060458106 PST 	Off 	NO_ALARM 	NO_ALARM
11/02/2014 01:00:01.110599290 PST 	On 	NO_ALARM 	NO_ALARM
...

Note that PDT and PST should be specified for searches covering times of the changeover.

Here is the list of commissioning task for the next 7-14 days:

Locking team:

1. Fix ALS DIFF feedback path (ESD/SUS crossover).
2. DRMI stability with new 3f detector modification.
3. Check RF power on 2f detectors.
4. Carrier sweeps with DRMI locked o new 3f.
5. Common hand-off to transmitted power.
6. Lock interferometer.
7. Resolve down stream clipping issues in the SRC.

Modecleaner team:

1. Investigate long-term alignment stability of mode cleaner.
2. Minimize intensity noise coupling through mode cleaner.
3. Optimized auto alignment scheme to minimize coupling.

Alignment team:

1. Revisit EY green WFS beam path and look for ghost beams.
2. Make EY green WFS work again.
3. Install EX green WFS auto-centering hardware.
4. Commission an arm alignment controls topology which can be used for initial alignment.
5. Integrate green WFS into initial alignment.

RF:

1. Make an assessment of RF cross talk into the IMC AOM.
2. Investigate EMI radiation by the VCOs and the fixed frequency OCXO.

The question of whether Operators have been checking the Observation Intent button came up this morning (basically we have).  I was curious to see how much this button is being used and how quick Operators are to Unclick it at the beginning of our shifts.   

I went ahead and trended/Conlog-ed the channel (H1:ODC-GRD_OPERATOR_OBSERVATION_READY).  Attached is a trend of the channel over the last 60 days.  Over this time we've had (6) "Undisturbed" segments (only counting segments over 30min):

1. 9/18
2. 10/2
3. 10/5
4. 10/8
5. 10/11 (over a weekend)
6. 11/7

In all of these instances, the Button was taken to "Commissioning" within the first few minutes-hour of the Operator shift. 

Note for Operators: 

• Please make sure this is one of the first things you check at the beginning of your shift!
• If there was an Undisturbed Segment overnight, please check the Access System for any incursions during the segment and make an alog entry stating when these incursions were (this has been added to the Operator Checksheet).

Note On Overnight Measurements & Request To Limit Early Morning Access (i.e. Cleaning)

With Operator shfits starting at 8am, there can be instances when the cleaning crew can enter the VEAs when we are in an "Undisturbed" Observation Intent state.  Now if there is ever a need  to limit cleaning activity due to overnight measurements:  please send an email to Jodi and/or Christina so they have a heads up for the cleaning team.  Otherwise, one can do what was suggested by Ed M. in his alog last week (i.e. post signs on doors requesting to postpone cleaning in the morning).

I manually added H1:LSC-PD_DOF_MTRX_LOAD_MATRIX to Conlog. The script that generates the channel list needs to be modified to add this channel. Otherwise if a new channel list is generated by the script and used, this channel will be removed. I will plan to make the change to the script on Tuesday as part of maintenance.

This morning ISS diff power was at ~11.6%. REFSIGNAL was @ -2.02V. I adjusted REFSIGNAL to -2.11. diff power is currenly at ~7%.

Attached is ten days of minute trends for some channels at EndX and EndY for the HEPI Pump systems.

At EndX, the Pump is still controlled(Ch2) by the last pressure sensor on the Pump Station skid(Ch1.)  At EndY, the control was switched early Thursday to the actual differential pressure across the actuators measured in the VEA (Ch5.)  On Friday, you can see where I smoothed the Supply & Return pressures and the Max/Mins of the differential pressure and the subsequent drive to the Pump Motor.  It looks like the diurnal temperature fluctuations are increased significantly when the daily fluctuations or the daily minimum exceed some threshold.

We still have room to improve the grounds noise but I don't believe there is any reason not to switch all the Pump Stations to the differential control.

• 3IFO work:  NO craning, but LVEA bifurcated for laser state in LVEA (and will go until noon)
• SEI--tomorrow HAM2/3 matrices change. 
• HAM oplevs were re-installed (suresh)
• EX cabling, and then EY cabling (Filiberto & crew)
• Talk about whether
• OFI measurement in H2 enclosure (Gerardo)
• Vacuum rack investigations (Richard)
• Preparing for cold snap

no restarts reported

model restarts logged for Sat 08/Nov/2014
2014_11_08 00:27 h1fw1
2014_11_08 17:29 h1fw1

both unexpected restarts.

Nic, Evan

We have gotten DRMI to lock on the 3f signals using the new, modified BBPD serving as REFLAIR_B.

Some good UTC times for 3f locking: 2014-11-09 0:56:50, 01:13:10, 02:41:00

Judging by POPAIR_B_RF18_I_ERR, the lock is kind of ratty both on 1f and 3f.

I think the reason Alexa and I couldn't lock yesterday is that we had the wrong relative gain for RF135Q/RF45Q. Nic and I remeasured it today and got 2.0. It is still true, however, that the ramping matrix doesn't give the expected behavior; it seeems to approach the requested value almost asymptotically, taking far longer than the specified ramp time.

We then adjusted the gains in the 3f input matrix to reduce gain peaking in the demodulated spectra of RF27 and RF135. We have written the following matrix elements into the lscparams guardian file:

• RF27I → PRCL = −4.0
• RF135Q → MICH = 2.0
• RF27I → SRCL = −0.6
• RF135I → SRCL = 1.7

Attached are our measured OLTFs of PRCL, MICH, and SRCL while locked on 3f. The DTT files are in my directory under Public/2014/11/DRMI3f.

model restarts logged for Fri 07/Nov/2014
2014_11_07 06:28 h1fw1

unexpected restart of h1fw1, first one since Monday.

Alexa, Daniel, Evan

In order to use the new REFLAIR_B, we have made the following changes:

• The whitening gains are now 30 dB and 18 dB for RF27 and RF135, respectively.
• The dark offsets for RF27 and RF135 have been measured and nulled.
• The demod phases have been adjusted to 115.5° and 20° for RF27 and RF135, respectively. By driving PR2 at 131 Hz and SR2 at 184 Hz, we find that the PRCL and SRCL signals can now be made to appear in the correct quadratures (see first attachment).
• By driving a 5.75 Hz line in PRCL (and subsequently SRCL and MICH), we have measured the relative gains between the 1f and 3f signals:

  	PRCL	SRCL	MICH
  RF27I/RF9I	−0.49	−3.9
  RF135I/RF45I		2.4
  RF135Q/RF45Q			0.46 2.0

  The RF27I/RF9I measurement for SRCL is low SNR for some reason. [Edit, 2014-11-05: I think I must have taken the RF135Q/RF45Q measurement upside-down. I retook it today and got a magnitude of 2.0.]

By using these gain measurements to adjust the DRMI 1f matrix elements, we have tried to transition from DRMI 1f to DRMI 3f. Howver, so far it keeps dropping lock.

The demodulated 1f and 3f spectra (taken while DRMI is 1f locked) are attached (units are cts/rtHz).

(Keita Daniel)

A spare BBPD with serial number S1200247 has been modified by removing and bypassing U1, the first RF amplifier stage. The attached BBPD_tf1.pdf file shows the transfer function before and after. Plot tf2 shows the ratio.

We took a baseline intermodulation product measurement by sending a two tone signal into the AM laser. The first tone was at 45 MHz and generated a line with -15 dBm amplitude. The second tone was a 90 MHz line also at -15 dBm. Plot IP2.png shows IP2 and IP3 lines at 135 MHz and 180 MHz with amplitudes of -57 dBm and -60 dBm, respectively.

The plot labeled IP2M shows the same measurement after the removal of U1. Close-in plots IP2M135 and IP2M180 show spectra with lower resolution bandwidth. The intermodulation lines are visible at a level around -115 dBm. One might consider this an upper limit, since the dominant distortion could be in the AM laser head. The IP2M135A plots shows one of the lines moved by 100 Hz. This now separates IP2 (lower frequency) and IP3 lines.

Finally, the IP2Mplus plot includes 20 dB higher drive levels to bring the lines back to -15 dBm. The 135 MHz lines shows up at -90 dBm which seems puzzeling low compared to the above measurement.

BBPD S1200234 has been replaced with BBPD S1200247 on the ISCT1 table. This will be our new REFLAIR_B.

Daniel has modified #247 by removing the MAR-6SM amplifier. From Koji's measurements (LHO#14901), we expect this to increase the IP2/IP3 of the amplifier chain and therefore lower the intermod products in RF27 and RF135.

The dc readout should be the same (i.e., we expect to read out ≈ 27 mW from the PD), but the rf readouts should be reduced by a factor of 10 in amplitude.

After installing, I resteered the beam (both in pitch and yaw) onto the PD using REFL-M3.

(For Evan and Nic)

Our current alignment procedures:

1. Lock green to both arms. Make sure all the sus guardians are in the proper configuration, ie. SUS_ETMs, SUS_ITMs, and SUS_TMSs are all aligned.  H1:ALS-X_TR_A_LF_OUTPUT should be a little above 1 cnts, H1:ALS-Y_TR_A_LF_OUTPUT will be a little below 1 cnt. Align ITMs and ETMs as needed (if hopless, check TMS alignment on ITM baffle PD1 and PD4). Make sure both ALS_XARM and ALS_YARM guardians are set to LOCK_NO_SLOW. 

2. After you are satisfied with the green alignment, make sure LSC_CONFIGs guardian is managed, and run ISC_DOF guardian to INPUT_ALIGN. This should lock the IR to the x-arm and misalign the y-arm cavity. You should see LSC-X_TR_A_LF_OUT go to around 1cnts. This will start the asc wfs and adjust IM4, PR2 to improve IR input alignment. Verify that LSC_ASAIR_A_LF_OUTPUT goes about 4,000 cnts. Then on ISC_DOF run SAVE_INPUT_ALIGN, this will offload the asc wfs to the alignment sliders. You MUST save the alignment values (ASC --> IFO_ALIGN.adl). 

3. Then, on ISC_DOF run PRM_ALIGN. This will first lock PRX and engage the asc wfs for PRM to maximize the power buildup in LSC_ASAIR_A_LF_OUTPUT. Once you are satisfied with the power buildup, run ISC_DOR OFFLOAD_PRM so that the wfs are offloaded to the alignment sliders, again you must save the new alignment. 

4. Set ISC_DOF to DOWN, and LSC_CONFIGS to MICH_DARK_LOCKED. Using the AS_AIR camera align the BS manually and save your new alignment values. 

5. Return to ISC_DOF and run SRM_ALIGN. This will first lock SRY and engage the asc wfs for SRM to maximize the power buildup in LSC_ASAIR_A_LF_OUTPUT. Once you are satisfied with the power buildup, run ISC_DOR OFFLOAD_SRM so that the wfs are offloaded to the alignment sliders, again you must save the new alignment.  (This step only required for DRMI locking).

FOR PRMI SIDEBAND LOCK: Set ISC_DOF to DOWN, set LSC_CONFIGS to PRMI_SB_OFFLOADED

FOR DRMI: Use ISC_DRMI and go to desired state. You will need to align various optics on your own because this guaridan does not manage any of the sus states. 

------------------------------------------

ALS_COMM guardian runs on its own, and can be set to IR_FOUND. 

ALS_DIFF can be set to the LOCKED state. You will need to enter the LSC input matrix (H1:LSC-PD_DOF_MTRX_SETTING_1_28) on your own. At the moment the script leaves this as zero since our gains have been changing. The LSC_DARM boosts are also currently commented out. 

-----------------------------------------

A useful striptool: /ligo/home/alexan.staley/Public/StripTemplate

*note: Observation Intent Bit was set to "green" at some point last night. The aLog did not reflect this action. Also, aLog crashed sometime after 10:55 last night.

*note: Intent bit was not set to "commissioning" until 08:39

*Suggest that notification be posted for cleaning crews at main access points IF actual intention is for NO acces to (L)VEAs be granted as long as OIB is set to "green"

*note: Accesses made to LVEA while OIB set to "green": (this is purely FYI as cleaning crews have generally been given access prior to 08:00AM.) 

06:43 Cris into LVEA

07:08 Cris out of LVEA

07:09 Cris into LVEA

08:00 Daily Checklist performed. (Observation Intent Bit*) Nothing out of the ordinary to report. Every point functioning nominally.

08:!5 Betsy into LVEA

08:25 Karen into LVEA

08:32 Betsy out of LVEA

08:33 Karen out of LVEA

08:39 Observation Intent Bit set to "commissioning"*

09:00 Jeff and Andres into LVEA

09:12 Kyle headed to both end stations

09:18 Fil out to EX

09:50 Fil back from EX

09:58 Kyle back from Ends

10:00 Reservation System used to note commissioning activity

10:20 Suresh into LVEA w/comm appr

10:20 Mitch out of LVEA

10:14 Dale informed me of a group of high schoolers in for a tour ~13:00ish.

11:03 Corey out to LVEA w/comm appr

11:18 Suresh out of LVEA

11:30 Kyle informed me of a chilled water leak in the mechanical room. This leak is non-consequential to anything critical and he should have it repaired sometime after lunch.

11:31 Jeff and Andres out of LVEA

12:23 Krishna headed to EX. Not going into VEA.

12:51 Suresh backk into LVEA

13:37 Jeff and Andres into LVEA w/comm appr

13:38 Dale with tour group into control room ~10min

14:28 Jeff and Andres out of LVEA

15:30 Corey in control room with tour ~5min

15:39 Corey with tour out to roof.

I wanted to see if our ETMY F2P problems were saturation related. So I looked at the current monitors for the L1 OSEMs.

One thing that was quickly noticed is that while the three others show <100 counts in the readback when there is no drive signal, the LR coil shows -4000 counts. (For scale, saturation occurs around 13000 counts for the three normal looking coils).

This would seem to indicate some problem, possibly removing a third of our range in one direction of one of our coils. However, when you actually drive the coils to saturation, they all seem to have the same range from the point of view of the DAC, just with LR readback offset from zero by 4000 counts.

So this could just be a problem in the readback, not clear without looking at the analog electronics.