Dave, Daniel, Jim

Reprogrammed the MSR IRIG-B at 12:45 PDT with Rev. 113 code (provides compatibility with the display to be used in the Control Room). Last week, Jim and I used the test stand to confirm that the flywheels in the IRIG-B PCI cards could keep stable time over a few minute interruption in the IRIG-B signal. Reprogramming took 38 seconds; the whole process of reprogramming, rebooting, resyncing, and confirming the time zone/leap seconds took 102 seconds. I had to add the leap second scheduled for later today.

MEDM screens for MSR IRIG-B are nominal. The rack-mount LED display no longer works, since Rev. 113 changes the display signal to be compatible with the display model to be used in the Control Room. Work permit 5317.

J. Kissel, J. Betzwieser, A. Mullavey, D. Macleod
Work Permit #5313

Two changes to the h1calcs front end model that I acquired from simply updating the library parts which had been modified by Joe and Duncan at LLO:
(1) In the DARM / DELTAL calibration infrastructure (i.e. the CAL_CS_MASTER.mdl library part), moved the actuation path's integer cycle time delay to "after" the actuation function, such that the delay is only applied when DELTAL_RESIDUAL and DELTAL_CTRL are summed to form DELTAL_EXTERNAL. This way, the GDS pipeline can pick up DELTAL_RESIDUAL and DELTAL_CTRL, apply the necessary corrections (namely the super-nyquist frequency poles / zeros from AA, AI, ESD Driver, and OMC whitening), and sum them together with a more accurate (i.e. not limited by integer clock cycle) delay to form GDS-CALIB_STRAIN. See LLO aLOG 18845

(2)  In the hardware injection infrastructure (i.e. the CAL_INJ_MASTER.mdl), modified the ODC bit comparator to determine whether a hardware injection is present from "is HARDWARE_OUT == 0" to "is HARDWARD_OUT <= 1e-200." Further, the status of each filter in the hardware injection path is compared against new EPICs values called "${BANKNAME}_CTRL_EQ" and "${BANKNAME}_GAIN_EQ." These values will be set (and accepted into the SDF system) by the ODC team, but this has not been done yet. See LLO aLOG 18913.

These changes also come with corresponding updates to the MEDM screen overviews for each that reflect the new organization.

Swapped EtherCAT Corner Station Chassis 6 in CER.
Old unit S1400076 was swapped with modified unit S1400077.
Modified unit had Beckhoff terminals added for EOM drivers per E1300689-v5.

Leak tested RGA joints - OK 

Also, moved X-end crane to "Parking" position at ~1010 hrs. local

A comparison of the end station pump down speed with the last vent.

Hugh and I went to HAM3 this morning to see if we could find the cause of the 23 hz line. Finding nothing at the chamber, we decided to start turning stuff off to see if we could get it to go away. Taking the ISI and HEPI down did nothing, but turning the suspension off made the line go away. I then started turning the SUS back on and as soon as I took MC2 to aligned, the 23hz peak showed up. Jeff said that it was likely the sat amplifier needed power cycled, so Hugh is filing an FRS and this is being handed off to Richard. Attached image shows HAM3 GS-13s between 20 and 30 hz. Red is from last night, when everything was on, blue is everything off, green is MC2 aligned (everything else off).  HEPI L4Cs and both SUS also saw the peak.

The LHO GC border router has had its media converter and transceivers replaced with a single transceiver to improve reliability and diagnosability, along with the matching equipment at our primary ISP.

Dave, Jonathan, Greg, Daniel

Last Tuesday (June 23rd 2015 between 12:30 and 15:50 PDT), Dave and I took a GPS time output signal from one of the rear BNC ports on a Timing IRIG-B module in EY. We temporarily fed the signal into the 16kHz rack microphone channel (see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=19299):

H1:PEM-EY_MIC_VEA_MINUSY_DQ

in order to record the signal in frame. Dave then found the frame file, and Jonathan extracted the first second of the H1:PEM-EY_MIC_VEA_MINUSY_DQ channel (each raw frame file has 64 seconds of data and is named according to the first second) into both text and binary formats. I then read the binary file (a bunch of 32 bit floats) using Julia, and compared the resulting array to the NDS-generated text file to confirm that the values were the same. I plotted the signal and read it twice, recording the long/short/control pulse sequence each time to make sure I'd read it correctly. I then decoded it using the IRIG-B signal spec. Finally, I compared it to the ostensible recording time, as indicated by the filename. c00010000c010000100c100000100c001001110c100000000c101001000c0

The signal as I recorded it (control = c, short = 0, long = 1) along with the decoded time; it matches the GPS time of the frame (which is 16 seconds later than the UTC time of the frame). A plot of the data is attached.

c00010000c010000100c100000100c001001110c100000000c101001000c0
 0001 000 0100 010  1000 01   0010 1110 10        1010 1000 8
 8s       22m       21h       174d                15y

Which corresponds to June 23rd, 2015 at 21:22:08 GPS time.

The GPS time (from the name of the frame, as recorded in the attached text file dump) is 1119129728.

This corresponds to Jun 23, 2015, 21:21:52, which is 16s early, as expected, due to the 16 current leap seconds.

It seems, then, that the IRIG-B Timing Module's signal isn't misaligned with the DAQ (at least not catastrophically).

The GDS tools (foton, diaggui, awggui, diag, etc) have been updated to gds-2.17.1.1 to handle conversion of UTC to GPS times for the upcoming leap second.  The leapsecs.dat file which dataviewer reads has also been updated, so dataviewer sessions started after the leap second should do the UTC to GPS conversions properly.

This change affects Ubuntu 12.04, Ubuntu 14.04, and SL6 workstations.

Reset the accumulated WD counters for HAM2, HAM5, ETM-X, and ETM-Y

Reset the accumulated WD counters for HAM2, HAM5, ETMX, and ETMY

Scott L. Ed P.

6/25/15
Cleaned 68 meters ending 7.6 meters north of HNW-4-091.

6/26/15
Cleaned 51 meters ending at station HNW-4-094. Test results posted here.

Removed lights, begin relocating cords and lights to next (AND LAST SECTION ON X-ARM).

6/29/15
Complete hanging of lights and begin vacuuming support tubes and spraying diluted bleach/water solution on (many) soiled floor areas.
Expansion bellows are excessively dirty, therefore we will do a pre-clean on these and go back over with regular cleaning. Filled 200 gallon D. I. water tank.
Only able to clean 5 meters of tube after all of that.  

The contractor is on site to sweep the gravel and rocks off of the access roads at each arm. 

The sweeper machine moves at a very slow pace so please be aware of this when traveling up and down the arms.

I've collected transfer functions for all optics and all DOFs in HAM6.  Everything looks good and we should pump down.  A subset of the results, for OMCS L and OM1,2,3 P are attached; the xml files have been saved and committed to the SUS SVN.

A report on the performance of the seismic isolation subsystem during ER7 at both sites has been compiled on the DCC: G1500811

Summary: 

• High wind adversely affected uptime at LHO during ER7
• SEI watchdogs still trip without any apparent ground motion cause at both sites, but less frequently than one year ago 
• Noted SEI watchdog trip trends (sensors that trip semi-regularly with no apparent cause):
  • BS ST2 GS13 at LLO 
  • HAM 6 ISI CPS at LLO
  • EMTX HEPI actuator and ST1 T240 (within ~10 minutes) at LHO
• No sign of upconversion from trains at LLO, but not many instances of elevated ground motion in 1-3Hz range

ER7-driven requests from DetChar for the SEI team: 

• Work to improve uptime via mitigation of earthquakes and wind-driven ground motion and addressing WD trips uncorrelated with ground motion

To test if NDS clients after tomorrow will correctly apply the upcoming leap second, I injected a sub-second signal into a DAQ DQ channel today. The H1:PEM-EX_ADC_0_08_OUT_DQ channel is a PEM test channel with ADC bit noise on its input. I ran awgstream to inject a signal which is one second long, and all zero except for 1/16th of a second starting at the 0.5S mark. This 1/16th second block is a step function, with an amplitude of 1000 counts.

The time of injection is chosen to be modulo 64 in GPS time, so it will be the first second of a 64second DAQ frame. The time of injection is

The model runs at 16kHz, this channel is acquired to the DAQ at 2048Hz. The decimation filter is producing the ringing seen at the step transitions.

Gerardo, Bubba, Kyle 

Installed HAM6 East and South Doors 

***Noticed many scratches on HAM6 East Door chamber flange - yes, where the door O-rings contact -> This is due to the fact that spring clamps have been used to secure the soft-covers to prevent the purge-air from blowing them off as is the norm but, unlike the normal case, for this flange, the O-rings are located in grooves on the door instead of the chamber.  As such, the O-ring protectors are on the door and not the chamber.  So, the spring clamps clamp against the machined sealing surface of the chamber flange and only the C3 fabric acts as a barrier between the steel clamps and the steel flange and scratching is inevitable.  Let us not do this again!  In the future, O-ring protectors should be installed on the chamber flange in addition to the door flange for this special case.  


Kyle, Gerardo 

Connected pump carts to HAM5 and HAM6 annulus pump ports -> Began pumping annuli(?) -> Will pump HAM6 tomorrow.

I repeated the charge measurements on both ETMX and ETMY. Plots are attached.