Day's Activities

• 7:09 Cris/Karen cleaning LVEA
• EY Dust Monitor investigation (Filiberto, Jeff B)
• 8:55 Picking up cable from EY (Elli, & Dave O)
• 8/58 Alexa stopped a script she was running overnight (will post alog)
• 9:00-11:17 Karen cleaning at EY
• 9:01 Escorting Control Solutions person for tour of End Stations (Bubba, John W)
• 9:05 Cris at EX
• 9:08 Joe D testing eye showers in LVEA
• 9:34 Parts search Chris S.
• 9:59 - 2:30 H2 laser enclosure measurements on OFI (Gerardo, Dave O, Elli)
• 10:11 Restarting server which authenticates ligo.org accounts; should only take a few minutes (Cyrus)
• 10:16-11:56 PEM cabling & output analog cameras down for a little (Filiberto, Aaron, Manny)
• 10:41 EY Pcal Camera work (Sudarshan)
• 10:43 Begin reboots of End Station SUS/ISC & DAQ (Dave, Daniel)
• 10:50-11:19 Parts search in LVEA & then EX to cover Pcal camera (Travis)
• 11:37 PEM microphones in LVEA (Sudarshan)
• noon DAQ Restart & Guardian reboot (Dave)
• 12:45 Praxair delivery to CP2
• 2:36 TCS parts search (Andres)
• 2:43-2:51 Checking on cameras (Corey)
• 2:44 Restore pressure regulators for upcoming vent at EY (Kyle)

EY Dust Monitors both appear to go INVALID

h1guardian0 restart: DB and PT

We rebooted the h1guardian0 machine for testing. As last week, the guardian nodes restarted automatically with no problems but conlog died. We were closely watching the conlog MEDM screen and saw all the numbers increment wildly for a second and then the IOC died. Patrick noticed that in both cases, it was one of the new guardian USRMSG channels which logged an exception (these are the 100 byte array PVs). During this morning's conlog channel reconfiguration we removed these channels from conlog, and will test with another guardian reboot next Tuesday.

End Station SUS and ISC changes: DS and DB

Daniel installed new SUS and ISC models in both end stations. The DAQ was restarted to support these changes (new INI files for ISC).

Beckhoff Code Changes: DS and DB

Daniel installed new Beckhoff code in all three locations. The following INI files were changed: h1ecatc1plc1, h1ecatx1plc[1-3], h1ecaty1plc[1-3]. The DAQ was restarted.

Code With Local Mods:

the attached files show front end and guardian files with local modifications which require commits to svn.

Partially loaded filter modules: DB

The load-all-coefficients button was pressed for the following models: h1suspr3, h1sussr3, h1susomc, h1susitmx, h1lsc, h1sushtts

Files without controls group access: DB

Shared files on the /opt/rtcds/userapps, /opt/rtcds/lho/h1/target and /ligo/svncommon which were not writable by controls group were modified to be so.

INI and Foton Checks: DB

Running DAQ INI files and filter module foton files were passed through inicheck and foton. Reports attached. Reminder we have DAQ channels with mixed case in their names.

DMT DAQ: DB

Verified all DMT channels are in the DAQ and there is no duplication

Regular weekly updates and also removed Guardian user message channels as they are suspected as the cause of errors upon Guardian restarts.

I've updated the TLS certificates on cdsldap0, which is the CDS translucent LDAP proxy that provides ligo.org authenticated logins to the control room.  It took longer than expected, because it didn't like the format of the new key file and slapd would die with a "main: TLS init def ctx failed: -207" message.  Running the key file through 'certtool --infile key.pem -k' and using the resulting base64 encoding made it work, apparently gnutls is picky in what it will use for a key, even though it's own tool can read the key as is...

These instruments have just been sitting on thefloor with no insulation so Krishna Jim and I got them under Trillium igloos.  We had trouble with the internal Cable routine and may revisit to improve that.

Directly following the restart of Guardian, Conlog exited with the following error:

Dec  9 10:34:34 h1conlog2 conlog: ../ecm_cac.cpp: 515: event_handler: pv name: H1:GRD-SUS_OMC_USERMSG: args.status is not ECA_NORMAL: ca_message: No reasonable data conversion between client and server types: Exiting.
Dec  9 10:34:34 h1conlog2 conlog: ../conlog.cpp: 331: process_cas: Exception: boost: mutex lock failed in pthread_mutex_lock: Invalid argument Exiting.

This is the same thing that was seen last Tuesday, but with a different channel name (H1:GRD-SUS_OMC_USERMSG instead of H1:GRD-HPI_ETMY_USERMSG).

It has been restarted.

Topped off the Chiller this morning (~190mL).

no restarts reported. Conlog frequently changing channels list attached. Sheila reports the channel which is changing continuously ( H1:ALS-Y_REFL_SERVO_IN1EN) is a Beckhoff PLC controlled channel, attempting to lock the Y-arm.

Interestingly the channel H1:FEC-92_MSG shows greater than 600 changes in one hour. This is the h1isietmx model. There were three load-all-filters-coefficients performed in one hour (between 13:00 and 14:00 PST yesterday) and the large number of filters in the model happens to give a total number of filters loaded > 600, so no problems there.

The contractors for the new DCS addition will be at it again today, all day outside with a larger piece of equipment. Some ground shaking. The inside portion of the construction will include hanging the indoor cooling units and taping of the sheet rock for the new wall.

We are in the process of preparing a cleaning of ETMY. Even so, it is not conclusive, ETMY has a clear problem as indicated by the green ring type absorption pattern which is thought to be due to first contact material left behind. At least 2 of the bright spots are extended and do not look like single point defects. A vent in EY is planned to start Monday next week. The opening of HAM1 has been delayed to next week as well to allow us to keep working with the Y-arm this week. Since we do not want to "bake" contaminants to the TMs, we decided to postpone any locking attempts and instead concentrate on a couple of task which previously had second priority.

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

Y-arm loss investigation:

1. Make another wider scan on ETMY.
2. Make a similar scan on ETMX.
3. Try to understand the ITMY scan.
4. Ring down measurements.
5. Mode matching measurements.

Seismic:

1. Investigate why the LHO performance is still lagging behind the LLO one.

Length team:

1. Characterize PRMI power build-ups.
2. RFAM measurements (including a EOM bias voltage).
3. Measurement of the Schnupp asymmetry using the aux. laser on IOT2R.
4. A good set of RFAM length measurements.
5. Commission updated tidal compensation/length relief strategy.

Alignment team:

1. DMRI WFS: add SRM alignment loops.
2. Make EY green WFS work again.
3. Add triggers to the auto-centering system, so it can be engaged automatically.
4. Add a "bleed" feature to the auto-centering system, so it automatically resets when it looses the beam.
5. Commission an arm alignment controls topology which can be used for initial alignment.
6. Integrate green WFS into initial alignment.
7. Revise initial alignment scheme.
8. Investigate the temperature dependence of the TM orientation (T step in EX with cavity locked).

Miscellaneous:

1. Fine tune Michelson contrast defect using ITMY TCS/CO2 laser.
2. Set up the HWS to check the thermal lens.
3. Investigate the long-term alignment stability of the mode cleaner ISS.
4. Add an "ISS engaged" state to the IMC guardian.

RF:

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

Measurement running overnight

Dan and I have left an MC measurement going overnight. It should only last about 6 hrs, so should be complete by the morning. In case I am not in early enough to turn everything off and it is interfering with people, do the following:

1. Turn off the input of MC common mode board Exc A (I will clear the awggui's that are running; as long as this excitation input is off they won't be doing anything)

2. Set the three LSC lockin oscillators Amp to 0

3. caput H1:ISC-EXTRA_C_REFL_AO_1  =  0

4. Disable MOD on IFR; this step is not really necessary and I can do it once I am in.

Evan, Krishna, Alexa, Dan, Kiwamu,

At some point in this evening, we noticed that the IMC kept dropping its lock for some unknown reason. It turned out that the HAM2 ISI sensor correction was amplifying seismic at 0.3-ish Hz which resulted in a large drive in MC2 to keep it locked. So we turned the sensor correction off for now. This fixed the issue.

Even though the MC2 coil DACs were not saturating, somehow the motion was big enough to unlock the IMC. It is still unclear why it could unlock. Anyway, after turning off the sensor correction, the amont of drive in MC2 suspension reduced by a factor of 5 or so and IMC became able to stay locked. With the sensor correction on, the MC length was moving approximately +/- 5 um according to IMC_X displacement monitors. We don't know what changed in the HAM2 ISI sensor correction as it has been running fine for a while recently. Only thing we immidiately noticed was that the seismic freq-limited RMSs were pretty high in 0.1-0.3 Hz and 0.03-0.1 Hz bands in this evening. The attached is a time series of the IMC_X signals when we did a simple test of turning on and off the sensor correction in the HAM2 ISI. Since we were a bit rough for turning on and off the correction, it gave a transient when switcing it, but one can still see that when the correction was running, the IMC_X signal increased by roughly a factor of 5.

S. Dwyer, J. Warner, H. Radkins, K. Venkateswara

We did a quick test of sensor correction (SC) along X direction to Stage 1 ISI, previously described in 15146. This attempts to use the ground seismometers located near the test mass chambers in feed-forward like manner to reduce the cavity motion. Sheila and Jim aligned and locked the X-arm using the green laser and data was recorded with SC OFF and ON.

The first pdf shows the signals with SC OFF and the second shows them with SC ON. The signals shown first are the Stage 1 T240s (inertial sensors), the CPSs (positions sensors) and the X arm control signal. The inertial sensors indicate a significant reduction in motion of Stage 1 on both ETMX and ITMX between 50-500 mHz. The microseismic motion is suppressed by factor of ~4. Yet, surprisingly, the X-arm control signal looks almost similar. The oplevs shown on pages 3, 4 indicate that the angular motion of the optics was unchanged so perhaps it might be limiting the control signal.
 

K. Venkateswara

I revived the BRS system after a crash towards the end of last week. It had successfully worked for a period of 16-17 days since the last restart.

As described in SEI alog 638, I've modified the pendulum response-inversion filter. I've also modified the tilt-subtraction scheme as described in the subsequent comments to the log. A high-pass filter at 5 mHz has been added in the sensor correction path (in the calibration filter bank) to roll off the low frequency increase in noise.

I've attached a pdf showing the output of the new tilt-subtraction scheme. The red 'super-sensor' curve looks similar to the blue ground curve, so we'll have to wait for a windy period to see if the tilt-subtraction has been improved or not.

Dave, Evan

Here is a larger scan of the the Y arm loss as a function of ETMY spot position. I tried to get out to a 6 cm radius from the nominal, but eventually the alignment was so bad that the arm broke lock. Also, I've masked out points for which the TRY dc value is less than 10 ct.

Also attached is Friday's measurement, with the colors rescaled to match the colors of today's measurement. Note that Friday's measurement is a smaller spiral. It's hard to know how to compare these measurements, but I've attached another plot where I suggest where Friday's small spiral may fit into today's big spiral.

Note that the zero points of the displacements are not consistent between different measurements; each time I have simply aligned the arm to get good buildup and then started the spiral. Attempting to reproduce the pointing from day to day would be a much more involved process.

SudarshanK, TravisS, EvanH, AlexaS, RickS

Using the Pcal beam localization cameras at both end stations, we took images of the ETM surfaces under three conditions: IR and Green resonating; IR only resonating, and Green only resonating.

Attached below are two composite images composed of four separate images taken with the same camera settings:
Upper Left: Xarm Green
Lower Left: Xarm IR
Upper Right: Yarm Green
Lower Right: Yarm IR

The images in the first composite were taken with the following camera settings: F8, ISO 200, 30 second exposure, WB-cloudy.

For the second composite image the aperture was F29 (~13 times less light)

The Yend camera was re-focused for the IR-only images, but the Xend camera was not re-focused.

J. Kissel, A. Pele

Ran transfer functions over the weekend, to assess if the SUS is free after first contact removal and closing doors. While the top stages look great, this is the first time I've been exposed to a factor of two missing between model and measurement for the lower stages. While we don't expect the model to account for the dynamics of the reaction chain (which is why we see a whole bunch of "extra" features in the main-chain dynamics), we don't expect an overall gain mismatch. Arnaud informs me that this is true of every QUAD except one stage of one (including L1 SUS ITMY). 

No reason to pull doors off, but we should figure out where this discrepancy lies. And also , we should develop a model of the lower stage dynamics which include both chains.