Dave B. added h1iscex model to the DAQ, DAQ restart
10:26 Dave B. restarted the EPICS gateway between the ops and fe LANs to diagnose the guardian software.
11:07 Cyrus R. changed HVE-EX:INSTAIR_PT599.LOW to 55
11:33 Dave B. restarting fw1 for disk repair

• ITMx
  • Pitch Error: 100 µrad up
    • Actual Pitch: 519 µrad down
    • Target Pitch: 619 µrad down
    • Tolerance: ±50 µrad
    • This was deemed good enough for the cartridge alignment and will be fine tuned to within tolerance once the cartridge is installed in WBSC3
  • Yaw Error: 30 µrad CCW
    • Target Yaw: 0.0 µrad
    • Tolerance: ±50 µrad
• CPx
  • Pitch Error: 145 µrad up
    • Actual Pitch: 1.255 mrad down
    • Target Pitch: 1.4 mrad down
    • Tolerance: ±1.4 mrad
  • Yaw Error: 291 µrad CCW
    • Target Yaw: 0.0 µrad
    • Tolerance: ±1.4 mrad
• ITMx/CPx Gap: 20.33 mm
  • Target: 20.0 mm
  • Tolerance: ±0.25 mm
  • Per Betsy, this is good enough for this pilot ITMx

To be on the safe side, I left the IAS equipment set up at the test stand until we get a good set of transfer funtions.

I've updated the low level alarm level settings on h0veex at the request of Patrick/Kyle for channel HVE-EX:INSTAIR_PT599.  The old value was '59', the new value is '55' for 'HVE-EX:INSTAIR_PT599.LOW'.  The DB file has been modified on vxboot to preserve this setting across VME boots, in addition to changing the current value via caput.

TMSX transfer functions are showing a bad coherence (see the attached snapshot of the dtt session for the pitch to pitch transfer function). Excitation was uniform white noise of amplitude 2500 from 0 to 50Hz, with a 0.01Hz bandwidth for Pitch

I told Corey and Keita to go ahead for cable testing, I will try new settings when they will be done.

(Kiwamu, Alexa)

 With the ISCTEY Prometheus laser set as follows,

PPKTP Crystal @ 32.27 C

NPRO Crystal @ 24.00 C

Diode A @ 23.00 C

Diode B @ 21.00 C

we measured the Current (A) vs Power(W) out of the laser aperature for the 1064nm beam (see pdf file).

We found the optimal configuration for the laser to be,

PPKTP Crystal @ 33.81 C

NPRO Crystal @ 24.00 C

Diode A @ 23.00 C

Diode B @ 21.00 C

Current 1.503A

such that at the aperature, the power of each beam was,

1064nm: 1.371W

532nm: 40.1mW

In this optimal configuration, we measured the power after the quarter-wave plate (QWP), half-wave plate (HWP), and Faraday Isolator (FI) for the 1064nm beam, and found it to be 1.282W. Thus, we deduced that the throughput of the FI was about 93%. Then we proceeded to examine the beam profile with the nanoscan.

The first picture (1064nmNoFI.pdf) shows the beam profile immediatly following the aperature of the laser.

The second picture (1064nmFILowCurrent.pdf) shows the beam profile after the FI with the current set to 0.803A (about 10mW of power)

The third picture (1064nmFIFullCurrent.pdf) shows the beam profile after the FI with the current set to 1.503A (about 100mW of power)

In these images, the top graph is of the horizontal profile and the lower graph is of the vertical profile. Immediatly after the laser aperature, we see a nice gaussian profile for the vertical profile. As expected, the horizontal profile does not fit a guassian as nicely. After the FI, the vertical profile deviates from the guassian shape. We attempted to adjust the FI alignment in order to improve this profile; however, it only worsened the profile. (Tomorrow I will collect raw data of the beam profiling after the FI).

(Note: See D1100607-v13 for table layout as a reference)

(Note: Temporary shin was placed below FI to obtain 4in required height)

I launched transfer functions for TMSX overnight after the bosems have been connected and centered today, using DTT templates from tmsy (white noise excitation).

Also, ITMX TF have been started at 18:43:25, for main and reaction chain from the generic matlab script LHO_Matlab_TFS.m

On top of UR sign flip of the lower mass of the beamsplitter, I realized that the signs of the coil output gain filters were not following the convention described in  DCC T1200015 (not yet fully updated) and E1100108, which should be +1 for a north magnet (UR and LL), and -1 for a south magnet (UL and LR) (cf medm snapshot attached).

Although, as the test from friday describes it (alog 7677), it works as if they were right -except for UR which has its special case- (sending a positive offset should give a positive response, with the good gains enabled).

Meaning, unless there is any other possibilities, that UL LL and LR magnets of M2 of the beamsplitter are flipped.

Livingston's BS medm screen has been checked, and is correctly following the convention

In previous aLOG https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=7620, the transmissibility (stage 0 of the ISI to stage 2 of the ISI) was computed using HEPI L4Cs as input motion. Due to a zero in some transfer functions from the HEPI actuators to the HEPI L4Cs, there is in Y transmissibility and Z transmissibility a sharp pole around 30Hz. The motion seen by the HEPI L4C around 30Hz is probably not representative of the actual input motion of stage 0. When driven by the HEPI, the motion should be falling in 1/f after 50mHz.

I used fitted transfer functions from the HEPI actuator drives to the HEPI L4Cs and the transfer functions from the HEPI actuators to the GS13s to compute the “ideal transmissibility”.

In attachment, figures show:|
-          The fitted transfer functions (magnitude and phase) to correct the input motion
-          The transmissibility using the L4Cs as an input motion
-          The transmissibility using the HEPI actuator drives and the Ideal response as input motion

When the HEPI dynamic is removed, the large transmissibility at 30Hz in Y and Z is considerably reduced.

910 – Tour of clean and bake for Professor Kajita from KAGRA, Pablo covering ops

930 – LVEA transitioned to Laser Hazard for IAS/SUS gap measurement

930 – Brief alarm on instrument air at EX…Kyle will investigate

1010 – Rick and Kiwamu giving quick tour in H1 PSL enclosure—area left in

  commissioning mode

1020 – Corey cleaning up and setting up for TMS cable testing at Test Stand

1035 – Jeff working with suspensions near high bay roll up door

1200 – Richard transitioning LVEA to laser safe.

1320 – Alexa energizing Prometheus laser in old squeezer NHZ (LVEA East Bay enclosure)

***I took over for Justin around this time ***

1400 - Cheryl/Keita working on setting OSEMs on TMS at Test Stand

Last Friday and today, I worked on installing remaining TMS cable and documenting each cable for TMS.  The table below documents cables we installed, positions on Cable Brackets, and what components they are hooked up to.  For in-air cabling, we only had the SUS cables run to the Test Stand; this is why I don't have names for these ISC TMS cables.

These cables are run mainly according to D1300007, although we did make some changes to improve workability (see photo).  One unfortunate thing here is, in D1300007, there is mention of a cable to be used, and there is a note that for this cable, having "metal ears" is optional.  So we went without them here, but with the ears NOT on the cable, it makes it impossible to disconnect a cable from a cable bracket  (see photo) without having to also remove the cable bracket from the table (this is because when the cables are connected via a set screw, the set screw access hole is blocked when connected cables are attached to the Cable Bracket).  LAME.

I also set up equipment for testing cables...mainly this was bringing lots of stuff which are needed for the Picomotor cables.

* For D1000921 S1104112 above, this cable was originally noted as S11041111 due to bag, but looks like the bag was mis-labeled.  S1104112 is what is really installed.

Cheryl and Keita backed out the TMSX OSEMs and I logged the OL values and calculated gains and offsets using the Matlab script /ligo/svncommon/SusSvn/sus/trunk/Common/MatlabTools/prettyOSEMgains.m:

>> prettyOSEMgains('H1','TMSX')
M1F1 25441 1.179 -12720
M1F2 22328 1.344 -11164
M1F3 28300 1.060 -14150
M1LF 23159 1.295 -11580
M1RT 26172 1.146 -13086
M1SD 28743 1.044 -14372

I entered the new gains and offset and updated and commited the safe.snap.

RAID controller 0 has failed in the SATABoy that is connected to FW1, as evidenced by the audible alarm and serial console log messages.  Looking at the uptime trend in DataViewer, it looks like FW1 crashed at ~02:23 UTC on 8 Sep and did not start (reliably) running again until 06:11 UTC the same day.  That range probably corresponds to the time when the controller failed, or started to fail.  Controller 1 appears to be active and working at present.  For now I've silenced the audible alarm until Dan can hopefully come up and have a look at it.

Filiberto investigated the TMSX issue (7675, 7676) and found a wrong cable had been used.

Now things are better, and there's a valid DC signal appearing, but there's still HF noise. Zooming out shows peaks at 1850 Hz and multiples (3700 Hz, 5550 Hz, signs of something at 7400 Hz), so something is presumably oscillating.

sw-msr-h1daq, being a Layer 3 switch, supports running a number of routing protocols; and apparently RIP and OSPF are enabled by default.  Since we only use this as a Layer 2 device these protocols were never configured, and because I wouldn't want to use them on this device anyway, I have disabled them in the config.

Moved the NW Vertical back to operation mode this morning after bleeding for the weekend.  Will continue commissioning.