15:15 Gerardo to EX

15:30 Jason, JeffB, RickS to PSL enclosure

15:45 Sheila, Hang to EY

17:30 Sheila refocusing PR2 camera, Marc & Fil working on illuminator

17:45 Mark & ChrisS to EX for ion pump install

18:00 Kyle to EX

18:30 Haocun & Sheila to ISCT6, Gabriele & Georgia to PR2 camera

20:00 Kara, Phillipe to LVEA for PEM microphones

20:15 Marc, Nolan, Daniel to LVEA/CER for PFD replacement

21:00 Haocun to ISCT6

21:00 Richard to BSC123 area

21:30 Corey to LVEA

21:30 Fil to LVEA

(Mark D, Tyler G, Chris S, Kyle R, Gerardo M)

GV 20 was closed and the main turbo pump at X-End was valved in to the main volume during the installation of IP12.  The chevron baffle volume was vented slow using UHP N2, as well as the IP body.

After Mark, Tyler and Chris were done installing the pump, the volume of the ion pump was roughed down to 1.0 torr using an aux cart, work will continue with this IP next week, since still needs to be pump down and leak tested.

After opening GV20, the main turbo pump was isolated, and shut down.  The aux cart flex lines remain connected to IP12 and the metal valve is closed at the IP.

Sheila, Craig

Sheila asked me to look at all our POP PDs during PRMI locks now (GPS=1216359318) and on June 21 (GPS=1213724178) for checking if the ASC and LSC POP PDs saw different relative levels of light.  
If the LSC POP PDs saw less light now, we would have smoking gun for clipping in the LSC_POPAIR path, since the LSC POP PDs monitor light returning from the beamsplitter.

ASC and LSC POP PDs have the same relative amount of light on them now as in June.

Results
Below are the results of the comparison.  The first column of numbers are associated with the June 21 PRMI lock, and the second is PRMI from two days ago.  The third column is the raw ratio of the PDs, and the fourth is normalized for the input power as read by IM4 trans.


Channel Name                               PRMI Locked Time 1,   PRMI Locked Time 2,  Ratio Time 2/Time 1,   Power Normed Ratio
GPSTimes                                           1213724178            1216359318

H1:IMC-IM4_TRANS_SUM_OUT_DQ                     284.918762207,        67.9162597656,       0.238370612264,                  1.0
H1:IMC-IM4_TRANS_PIT_OUT_DQ                    0.407760709524,       0.477381646633,        1.17073965073,        4.91142606735
H1:IMC-IM4_TRANS_YAW_OUT_DQ                    0.883432805538,       0.855117201805,       0.967948198318,        4.06068611145

H1:LSC-POPAIR_B_RF18_I_ERR_DQ                   195.512329102,        16.1139144897,      0.0824189186096,       0.345759570599
H1:LSC-POPAIR_B_RF18_Q_ERR_DQ                  -94.1860046387,       -3.70564484596,      0.0393439009786,       0.165053486824
H1:LSC-POPAIR_B_RF90_I_ERR_DQ                   286.353973389,        44.0622596741,         0.1538733989,       0.645521700382
H1:LSC-POPAIR_B_RF90_Q_ERR_DQ                  -75.2995452881,        2.58768701553,     -0.0343652404845,      -0.144167274237

H1:LSC-POPAIR_B_LF_OUT_DQ                       24.9877510071,        2.98662781715,        0.11952367425,       0.501419484615
H1:LSC-POP_A_LF_OUT_DQ                          242.602081299,         29.790473938,       0.122795626521,       0.515145838261

H1:ASC-POP_A_NSUM_OUT_DQ                        11.5149688721,        1.42900109291,       0.124099433422,       0.520615518093
H1:ASC-POP_A_PIT_OUT_DQ                         0.29082262516,       0.965587258339,        3.32019305229,        13.9287014008
H1:ASC-POP_A_YAW_OUT_DQ                       0.0495703965425,        0.11970166862,        2.41478133202,        10.1303653717
H1:ASC-POP_B_NSUM_OUT_DQ                        10.5879678726,        1.31313991547,        0.12402190268,       0.520290255547
H1:ASC-POP_B_PIT_OUT_DQ                        0.952069103718,        0.95118021965,       0.999066352844,        4.19123125076
H1:ASC-POP_B_YAW_OUT_DQ                       -0.530693173409,      -0.561689078808,        1.05840647221,         4.4401717186


Buildups in RF9 are one third of what they were in June, while buildups in RF45 are two thirds of what they were.  Overall power is half.  All PD power levels are consistent.
POP_A seems way off in both pitch and yaw, but POP_B is the same.  
I checked every PD for differences in the signal chain.  There were none except for POPAIR_B_RF18_PHASE_R going from 12.0 to 42.0 degrees, and POPAIR_B_RF90_PHASE_R changing from 24.0 to 49.0 degrees.

Sanity Check
We can estimate what the PRMI POPAIR_B_LF power ratio should be from the new modulation depths and our POPAIR_B sidebands:

J. Kissel, H. Yu
WP 7730
ECR E1800201
IIET Ticket 10975

Given the recent apparent** success of BSC ISI ST2 to Top Mass feed forward with the QUADs (see LHO aLOGs 42875 and 42906), we've pushed a similar feed forward path into the beam splitter SUS's infrastructure to test out success there, to see if we want to modify the ECR to include this as well.

**I say apparent, only because we haven't yet measured the feed-forward's impact with any global sensors. Locally, it's a win!

A fair warning, this feed forward will be more interesting:
- Longitudinal for the beam splitter isn't just one Cartesian DOF as it is for the test masses, so we may need to figure out a way to actuate the ISI in longitudinal. Hopefully this can be done without a model change.
- Because of the back-reaction on the cage to ST2 of the ISI BS, we don't turn on ST2 isolation until well after we lock MICH in the IFO's acquisition sequence. Thus we should be sure to characterize the beam splitter with ST2 ON.

Attached are screen shots of the affected models and medm screens.
    /opt/rtcds/userapps/release/isi/h1/models/
        h1isibs.mdl
    /opt/rtcds/userapps/release/sus/h1/models/
        h1susbs.mdl
    /opt/rtcds/userapps/release/sus/common/models/
        BSFM_MASTER.mdl

    /opt/rtcds/userapps/release/sus/common/medm/bsfm/
        SUS_CUST_BSFM_OVERVIEW.adl
        SUS_CUST_BSFM_M1_ISIFF.adl

At ≈ 21:00UTC the PSL tripped. The cause is TBD. I was able to successfully restart it without incident. 

Nolan Marc Dick Daniel

We swapped the ALS PFD with a unit that had its LO TNC/PCB/SMA/SMA/coax/SMA input arrangement replaced by a simple TNC/coax/SMA. Furthermore, the TNC connectors are no longer isolated. This should reduce any crosstalk inside the PFD between the 2 ALS VCOs.

While we were at the rack we noticed that some of the N bulkheads in the VCOs and FDDs were very loose. One of them rattled when we wiggled the cable. We tightened them all. We noticed that one of the cables between the VCO and the FDD had 2 ~5dB attenuator installed, whereas the other one had none. This was fixed as well. Both FDDs now have a proper 13dBm at the input.

This morning some models went from RCG3.2 to RCG3.2.3. Changes made in RCG3.2.1 mean that when an updated model is ran with mx_stream-3.2 (the code which sends the model's data to the DAQ), the keep-alive message coming back from the DAQ Data Concentrator is not interpreted correctly and the front-end DAQ bit is erroneously set bad.

The data from the model to the DAQ is perfectly correct, and the status of the data flow as determined by the Data Concentrator is correct.

There are three options:

1. make no changes, accept that the CDS overview will have red daq bits for some models

2. for models running 2.3.2, do not show the DAQ bit on the overview

3. for any front end with at least one model running 3.2.3, upgrade all the models on the computer to 3.2.3 (including IOP) and run mx_stream-3.2.3

I don't want to do 1), this can lead to red-fatigue when viewing the overview.

Option 3 is intrusive and will require customization of the monit script which starts mx_stream in order to start the correct version depending upon the computer name. It will require upgrading all models on h1susb123, h1seib2, h1susex and h1susey (and possibly on h1asc0 or downgrading h1asc model to RCG3.2).

For now I'm implemented option 2). A new composite fec-status MEDM called H1CDS_FE_3_2_3_MICRO_CUST.adl has been created and used for the models h1sus[i,e]tm[x,y], h1isibs, h1asc.

I tested these options on h1pemmx. It is currently running 2.3.2 on IOP and h1pemmx, and mx_stream-3.2.3.

I have reset the build release pointers back to RCG3.2 for now.

   Did inspection of air ducting into the PSL enclosure. All appears to be in order. I found no breaks or damage to the ducting. The seals between the ducting and the hole in the roof were all intact. The damper on the discharge ducting is moving freely and appears to be working. 

   I did find pieces of insulation like material inside the discharge duct. This may be an artifact of the duct assembly. 

   Inspected the fan/filter units on top of the PSL Anti-room. All the prefilters are intact. They have expected surface contamination, but nothing out of the ordinary. In the "plenum" area between the prefilter and the fan unit (on the three fan/filter units inspected)I found moderate amounts of dust. The dust is concentrated around the edges of the plenum box, indicating it is outside the area of the air being drawn into the fan. At some point it may be good practice to clean these units, but this is not a pressing issue.

   Conclusion: Good News - The air ducting system seems to be operating as designed. It does not appear to be contributing to spikes in the particulate counts within the PSL Anti-room or laser enclosure. The HEPI filters were not inspected due to the disruption an inspection would cause. 

WP 7710
alog 39695

Interface board replaced with v6 board. New board has whitening/gain for EFM signals. EFM gain increased:

R10/R16 changed to 10K
R14 changed to 4.99K

With ion pump replacement going on at EX, we decided to leave the ±18V going into chamber off.

S1102829 - Chassis
S1800797 - Interface board

J. Kissel, D. Barker
ECR E1700286
WP 7720
FRS / IIET Tickets 8759, 11032, 11066
 
We've made an (and hopefully last) attempt at installing the violin mode filter expansion pack. All signs point to success! As an addition to the three-weeks-ago first attempt, I've added a bit more output monitoring and control so as to 
    - prevent the violin mode filters from blasting the PUM upon accidental startup
    - facilitate a quick shut-off of ALL violin mode damping output, instead of having to turn off 40 filter bank outputs.
I've also identified a few MEDM screen bugs and fixed those up I've fixed up along the way.

The short summary of the story:
    - originally tried installing three weeks ago (LHO aLOG 42752)
    - found that the installation surpassed some real-time code generator (RCG) threshold and caused a bug in the binary IO system (LHO aLOG 42922)
    - Rolf found and fixed the bug (see LHO Ticket 11066, Comment #7), and was tried and tested at LLO (LHO aLOG 39785)
    - And now re-installed today, with a bit of improvement in output monitoring and control.

I've committed changes to:
Front-end model library part:
    /opt/rtcds/userapps/release/sus/common/models/
        FOUROSEM_DAMPED_STAGE_MASTER_WITH_DAMP_MODE.mdl

MEDM Screens:
    /opt/rtcds/userapps/release/sus/common/medm/quad/
        SUS_CUST_QUAD_L2_DAMP_MODE_MTRX.adl
        SUS_CUST_QUAD_L2_DAMP.adl
        SUS_CUST_QUAD_ITM_OVERVIEW.adl
        SUS_CUST_QUAD_OVERVIEW.adl
which are all common library parts, so the update at LLO should be very straightforward.

[Georgia, Gabriele]

We went to the LVEA to focus the PR2 camera on visible light, with various setting of the illuminator on. We took a few images with various zoom levels, and then set a zoom that provides a good view of the scraper baffle aperture. The image below shows the view with the illuminator on and the final zoom level.

We then focused again the camera on the infrared beam. We also wrote a simple python script to superimpose the IR image (in red) with the reference visible light image (background). The results is shown below in single bounce configuration:

For reference, photos of the table can be found in 38749:

WP7730 Beam Splitter ISI to SUS feed forward signaling

Jeff K, Dave:

New h1isibs and h1susbs models were installed. New IPC Dolphin channels added.

WP7719 QPD arm transmission on ASC ADS

Hang, Jennie, Dave:

New h1asc model was installed. Installation had an issue with the H1ASC.txt filter file having incorrect file permissions, I fixed this and installed a second time.

WP7721 Add AC power strip status channels to DAQ

Dave:

New H1EDCU_CDSACPWR.ini added to DAQ. This allows the trending of the ALS polarization correction box's powered status.

WP7720 RCG upgrade to 3.2.3, add violin mode damping filtermodule back to SUS-QUAD

Jeff K, Dave:

New h1susitmx, h1susitmy, h1susetmx, h1susetmy models were built against RCG3.2.3 and installed. All models from now onwards will be built using 3.2.3, including those built today.

Guardian DIAG_MAIN reports if polarization correction box is powered on for an extended time

TJ, Dave:

TJ modified DIAG_MAIN to report if polcorr box is powered on. This is intended as a reminder to power it off before going to science mode.

WP7724 Restrict who gets messages when Cell Phone Alarms system is stopped/started

Following the unexpected restart of the system last Saturday night, I have restricted who gets notified when the system starts (and when it is manually stopped). Only myself gets a cell phone text, everyone else only gets emails. System was restarted several times to test this. The daily CP, GP reports do not automatically get sent on restart anymore, they can be manually sent by issuing a SIGUSR2 signal.

DAQ Restart

Dave:

One DAQ restart at 10:38 to cover all of the above.

Pending filter module modifications manually loaded

Dave:

I loaded all filters for the following systems: h1susetmx*, h1sustmsx, h1alsex, h1asc* (systems marked * were loaded as part of their restart process).

h0epics restart

Carlos, Dave

h0epics unexpectedly went down. After Carlos got it running again, I started the EPICS IOC which reside on this system: h1weather[ex, ey, mx, my], h1dus[lvea, lab, ex,ey,dr], dewpoint.

J. Kissel

Since we'll be restarting the QUADs (ITMX, ITMY, ETMX, ETMY) again this morning, and now also the Beam Splitter (BS), I've reconciled the SDF system to the best of my ability. 


ETMX 
    - restored to optical lever damping OFF (was ON with a gain of 30)
    - restored ESDOUTF offsets and tramps to zero (left over from charge measurements)
    - ACCEPTED all outputs of existing violin mode damping filters to be OFF
    - ACCEPTED the new L2A filters and gains from Hang's Work a few weeks ago (I'm kind of surprised it wasn't already accepted).

ITMX
    - restored to optical lever damping OFF (was ON with a gain of 30)
    - ACCEPTED all outputs of existing violin mode damping filters to be OFF
    - ACCEPTED new values for misalignment offsets.

ITMY
    - reverted to optical lever damping OFF (was ON with a gain of 30)
    - ACCEPTED all outputs of existing violin mode damping filters to be OFF
    - ACCEPTED a ~100 urad change in R0 alignment offset.
    - ACCEPTED new values for misalignment offsets.

ETMY
    - reverted to optical lever damping OFF (was ON with a gain of 30)
    - ACCEPTED all outputs of existing violin mode damping filters to be OFF
    - ACCEPTED changes to ETMY_M0_LOCK_P/Y to have it's inputs OFF and FM1 OFF, but this appears to be manipulated by guardian, so we should investigate not monitoring these channels.

BS
    - reverted optical lever damping tramps to 20 sec (from 10)
    - reverted having limiters on the M1 LOCK filter banks.

For the ease of recovery, I've also saved all of the alignment offsets for the above mentioned suspensions.

Summary:  Ran Charge measurements for ETMx & ETMy from 7:23-8:30amPDT a little early this morning for morning commissioning work.  There was a big EQ which occurred during this measurement.

Morning Activity:

• 13:52 Christina & Karen started LVEA work
• 14:14 ISI config to SC_OFF_NOBRSXY for Maintenance
• 14:23 Charge Measurements started/attempted...actually took 5-min to start due to ISC_LOCK Guardian*
  • Original alignment slider values noted below**
• 14:37 Bartlett out to work on PSL plumbing inspection
• 14:43 noticed EQ on seismic DMTs(...turns out to be a 5.2 & 5.6 EQs near Gold Beach, OR)
• 15:30 Measurement complete & restoring.  ETMs had been in an MISALIGNED guardian state...will leave ALIGNED.

* ISC_LOCK would not go to DOWN (said there was no path from READY to DOWN, & would go for PREP_FOR_LOCKING).  Took to MANUAL & then selected DOWN; stayed in MANUAL for measurements.

Checking Data/Files:

I had trouble running the matlab files to analyze the data last week.  So, for today I'm only checking to see that the data was posted.  Similar to last week, we have 5-sets of measurement folders which contain the usual 5-data files per quadrant.  Sending an email to Georgia & JeffK to let them know I ran the measurement & data ready for analysis.

Restoration Notes:

• ETMx had some SDF diffs, but they were already there & weren't me, so I will leave them as is.
• ETMy SDF diffs I made were restored (there were some others on the list; will leave them as is).
• Did not see any BIO diffs to change/restore for this measurement.

**ETM ALIGNED Slider values (before centering Oplevs)

ETMx:

• Pit:  124.7
• Yaw:  -132.3

ETMy:

• Pit:  128.7
• Yaw:  -122.3