Looked into the RMS binary reset for the PUM ETMX chassis.

1. On the PUM Chassis, disconnected the DB37 binary input cable and grounded Pin 18 on the chassis side. This untripped the RMS watchdog.

2. Looked at the output of the binary output interface chassis. Did not see any voltage change when I cycled through the reset in MEDM. This was looking at Pin 18.

3. Spoke to Dave and determined the output for the RMS reset on the binary output inferface chassis is on the second DB37 connector on Pin 2. 

3. Tested our cable going from the the binary output interface chassis to the PUM chassis and confirmed it is a one to one pin layout.

It looks like we need a special cable with Pin 2 on male side tied to Pin 18 on female side. For now I reconnected all cabling and left all orignal electronics in place.

EY is reported to be operational, so I will compare cabling with that of EX. As of now, EX RMS reset is still not operational.

Filiberto Clara

Worked on the DBB 200W beam path alignment this morning.  One side effect of the power outage that I hadn't considered was that it reset the DBB alignment PZTs to zero.  This is actually a good thing as these PZTs need to be as close to zero as possible, and were rather far off in vertical alignment due to the previous bad DBB alignment.  This reset essentially forced me to completely realign the beam to the DBB PMC, but with the added benefit of not having to tailor my alignment to also minimize the PZT voltage; it's already at zero.

For this alignment I scan the DBB PMC by ramping its PZT at 10Hz and look at the output of the DBB PMC TPD on an oscilloscope.  As a single scan of the PZT covers several FSRs of the DBB PMC the oscilloscope output shows the different higher order mode peaks that resonate in the PMC as the PZT ramps.  Alignment is then done by identifying and reducing the TEM10 and TEM01 peaks.  At first I didn't really get anywhere and the beam transmitted by the DBB PMC looked really ugly no matter what I did to the alignment, so I checked the distance between the 2 mode matching lenses.  Should be ~168mm (this is where I left it last time I worked on the DBB), was more like 187mm (not sure why this moved, didn't see the change documented in the alog).  Moved DBB_MML2 to make the distance 168mm, which then gave me a signal through the DBB PMC that I could use in alignment (had a transmitted beam that was somewhat round).  Horizontal and vertical alignment is now much better than previous, alignment peaks have almost vanished.

I then worked on the mode matching by moving one of the mode matching lenses slightly (~0.3mm, can do this with the DBB MEDM screen.  Note to self, positive movement on the MEDM screen moves the lenses AWAY from DBB_M1), realigning to the DBB PMC (as moving lenses changes alignment), then assessing whether or not this change improved the mode matching peaks in the PZT scan.  Lather, rinse, repeat.  All told I moved DBB_MML1 by +1.6mm and DBB_MML2 by +4.0mm.  This appeared to improve the mode matching peaks signficantly and the beam transmitted by the DBB PMC is much more round (although still slightly oblong in the vertical direction to my eye).  Even with these apparent improvements the DBB PMC would not lock, so there is still alignment/mode matching work to do (or something else going on that I haven't considered/worked out yet).  I will continue this work in the mornings as commissioning allows.

It should be noted that all this work was done solely on the 200W beam path.  Due to the resetting of the DBB PZTs and the subsequent realignment of the 200W path, the 35W path into the DBB will need significant realignment.  At this time the 35W path into the DBB is not usable.  I will realign/mode match the 35W beam path once the 200W path is done (as the 35W alignment depends on the 200W path being aligned/mode matched).

Chiller filter replacements, planned power outage, re-calibreation of flow sensor pulse calibration...etc

~1000 - 1430 hrs. local 

(2001 era pump shorted following power cycling power cord) Work is complete.  Pump cart removed and HAM10 in its as found (nominal) state.

(All time in UTC)

14:57 Jeff K. running charge measurement both ETMs.

15:07 Joe to LVEA checking batteries on folk lifts and etc.

15:21 Gerado to MY. WP#5920

15:35 Fil+Ed to CER

15:43 Chris S. taking pest control to LVEA (~20 min)

15:48 HEPI weekly inspection at End stations (Hugh)

15:50 Ken installing lightbulbs in CER

15:52 Kristina+Karen to LVEA

16:07 Chris+Mich taking pest control to end stations

16:12 Joe out

16:21 Jason to PSL working on diagnostic breadboard

16:33 Nutsinee running CO2 RS script (~20 mins).

16:35 Ken open up the roll up door between high bay and LVEA to bring a lift through.

16:39 Fil to EX working on PUM chasis

17:09 Portable truck on site

17:29 Jeff B. to EX

17:35 Kyle to HAM10 (WP#5923)

          Ed installing Newtonian chasis in CER (TCS rack)

17:43 Joe to LVEA

17:48 Gerado to EX (WP#5922)

17:57 Kristina+Karen to End stations

         Carl+Ross+Terra to EY (PI ESD work)

18:02 Jeff B back

18:17 Chris+Mich out

18:25 Hugh back. HEPI Maintenance done.

         Joe back

18:50 Jason out

18:53 Karen leaving EY

18:55 Gerado out of EX

19:15 Kyle out

19:22 Kristina leaving EX

19:40 Terra+ out

          Fil to EX

19:44 Terra+ to EX

19:55 Dave restarting h1susb123 model and iop, ITM PI model, and DAQ

20:01 Ed to MX

20:04 Kyle to HAM10 (ion pump)

20:26 Gerado to LVEA

20:32 Fil back

20:34 Chris+Mich to LVEA (clean room inspection)

20:40 Gerado out

20:44 RIch to EX (ESD work)

20:55 Mich to LVEA

21:00 Mich out

21:11 Terra+ out

14:17 Jeff Bartlett is taking over until 4.

Betsy, Jeff K, TJ

Yesterday it was found that bringing the suspension Guardians straight to ALIGNED right after a power outage/reboot/etc may be a bit too agressive. We have changed the initial request state to be SAFE so the operator, or who ever else, could then check each suspension before bringing it to its appropriate state.

Added the following channels to the exclude list:

H1:SUS-ETMX_PI_OSC_DAMP_OSC_LINE1_COSGAIN
H1:SUS-ETMY_PI_OSC_DAMP_OSC_LINE1_COSGAIN
H1:SUS-ETMX_PI_OSC_DAMP_OSC_LINE2_COSGAIN
H1:SUS-ETMY_PI_OSC_DAMP_OSC_LINE4_SINGAIN
H1:SUS-ETMX_PI_OSC_DAMP_OSC_LINE4_COSGAIN
H1:SUS-ETMY_PI_OSC_DAMP_OSC_LINE3_COSGAIN
H1:SUS-ETMX_PI_OSC_DAMP_OSC_LINE2_SINGAIN
H1:SUS-ETMX_PI_OSC_DAMP_OSC_LINE4_SINGAIN
H1:SUS-ETMY_PI_OSC_DAMP_OSC_LINE3_SINGAIN
H1:SUS-ETMX_PI_OSC_DAMP_OSC_LINE3_COSGAIN
H1:SUS-ETMY_PI_OSC_DAMP_OSC_LINE4_COSGAIN
H1:SUS-ETMX_PI_OSC_DAMP_OSC_LINE3_SINGAIN
H1:SUS-ETMY_PI_OSC_DAMP_OSC_LINE2_SINGAIN
H1:SUS-ETMX_PI_OSC_DAMP_OSC_LINE1_SINGAIN

Re wandering 59Hz bump first seen around 25 May and reported Jun 1: With the DQ channels, I checked to 125Hz and it does not show itself.  Maybe the power cycle cleaned it out.

Otherwise, attached are the CPS spectra for all the BSCs:

The ETMX St1 V1 looks much better now.  The ITMX St2 H3 is a little better but the ITMX St1 V1 is quite noisy now.  I better check this tomorrow to see if it changes.

Routine Maintenance but since the Motor greasing is just an annual event figured it warrented a log entry.  Of note, found that many of the zerk fittings would not open and pass the grease.  So found one that did and installed that one as needed.  Will open an FRS ticket and purchase better zerks to replace the negative function units.

Sheila, Evan, Haocun

We drove the ETM's in pitch and yaw, and took measurements for the HARD loop.

As Evan posted in aLOG 27518, the usual "IN1/IN2" method for FFT-based OLTF measurements were biased because the IN2/EXC coherences were low, so I exported the data of CLTF's using IN1/EXC (whose coherences were higher), and converted them into OLTF's.

The measurements for both pitch and yaw of CHARD and DHARD are plotted together with the modelling curved as attached:

- The measurements were taken under 2W of laser power. The blue curves are the modelling DHARD plots at 2W, and the red or orange dots are measurement values.

- Only values with IN2/EXC coherence higher than 0.4 were used, otherwise the data were dropped.

- I tried to calculate the uncertainties of the measurements using the method in aLOG 10506, shown as error bars on the plots.

- Number of measurements taken:

  CHARD Pitch: 111

  CHARD Yaw: 44

  DHARD Pitch: 121

  DHARD Yaw: 33

We will take more measurements with same UGF values in the model and do more comparasion.

[Dave, Rich, Terra, Carl]

We have removed DAC card_num=7 from h1susitmypi and re-ordered the outputs on DAC card_num=6 in accord with the update to D1500464.
Specifically H1:IOP-SUSB123_MDAC6_TP_CH0-7 now follow the ordering ITMX UR LR UL LL, ITMY UR LR UL LL.

there is a collision of DAC channels on h1iopsusb123, we will rebuild and restart all the models on this frontend when new code is available.

RCG 3.0.3 upgrade.

Jim, Dave:

All the frontends were rebuilt against RCG TAG 3.0.3 on Friday afternoon before the shutdown. The build started with an empty H1.ipc file to clean out any unused IPC chans. After all the frontends were restarted today, they are now running with  3.0.3 

Infrastructure Restart

Richard, Carlos and Jim:

The CDS infrastructure was restarted between 7:00 and 8:30. These include networking, DC power, timing, DNS, DHCP, NTP, NFS, auth.

Front End Startup

Richard, Jim, Dave:

h1boot was started. Then h1psl0 was started as an non-dolphin FEC. This permitted the DAQ to be restarted (needs a running front end). Then the remaining non-dolphin MSR FECs were started. The Richard started EX, EY, MX and MY FECs. Finally we started the MSR dolphin machines. All started up once the fabric was complete.

h1lsc0 reported timing issues. The timing card on this IO Chassis is independently powered, I activated this DC supply and the system started normally.

h1pemmy needed on more IOP restart, as is expected for these non-IRIGB units.

During the startup of the SWWDs, all MSR dolphin channels were found to be not working. We tracked this down to the Dolphin switches not being powered up, this was easily resolved.

Eagle eye-ed Jim noticed the system time on h1psl0 was way off (by 7 hours). We assumed because it was the first to be started soon after h1boot (which perhaps had not NTP synced). We manually set the time and handed control back to NTPD.

EPICS Gateways

Dave:

All the epics gateway processes on cdsegw0 were restared using the start.all script. This started too many gateways resulting in duplicate data paths, the redundent gateways were removed and the script was corrected.

h1hwinj1

Jim, Dave:

We started the PSINJECT process on h1hwinj1. Again the SL firewall prevented EPICS CA access, which we re-remembered and fixed. CW injection to PCAL is running.

Slow Controls SDF

I started Jonathan's SDF monitor pseudo-target on h1build.

Vacuum Controls and FMCS cell phone notification

I got the cell phone alarm texter running again on cdslogin.

PI Model changes

Tega, Dave

A new PI_MASTER.mdl file was created at 15:10 Friday, which just missed the 3.0.3 build cut-off time. We recompiled and restarted the four models which use this file (h1omcpi, h1susitmpi, h1susetmxpi and h1susetmypi). A DAQ restart was also required.

NDS processes not giving trend data

Jeff, Jim, Dave

here was an interesting one, the nds processes were giving real-time data but no archived trend data. The cronjob which was keeping the jobs directory in check by deleting all files older than one day, today cleaned out the directory and then deleted the jobs directory itself. Re-creating the directory and stopping the cronjob from erasing it again fixed the problem.

h1tw0 raid issues

Carlos, Ryan

h1tw0 did not like being power cycled and the new RAID controller card stopped working again. It looks like we are going to have to recreate the raid again tomorrow.

DAQ instability

Dan, Jim, Dave

sadly we leave the system with an unstable h1fw0. Earlier in the day h1fw1 was unstable, then h1fw0 became very unstable. Dan did some QFS diagnostics, I did some NFS diagnostics, we cannot see any reason for the instablities, all NFS/disk access is well within bandwidth with no indication of packet/re-transmission errors.

Kissel started the charge measurements on the SUS ETMs this morning around 8am.  However, I just discovered that both ITM and the ETMx ISI's have been tripped since ~4am, so the ETMx data isprolly junk.  Boo.  Not sure why this wasn't addressed this morning.  ISI's are back up now.

Summary

On Friday, Pcals were turned off for the June 3-5 power outage (LHO alog 27558).

• Today it was verified that PcalX and PcalY settings were restored with the default values stored in the SDF system.
• The PcalX laser was turned on with a switch on the MEDM screen and the power was set to 5.0 V (nominal). Then we closed the OFS loop.
• The PcalY laser switch was also set to ON and laser power was set to 5.0 V (nominal), but the photodetectors' (TxPD, OFS PD and RxPD) readings indicated that the laser was not on. Currently we are investigating the problem, for now the PcalY laser switch was set to OFF.

Details

After finding out that PcalY PDs are not measuring any power I went to the End-Y and checked following:

• all of the power switches on a PcalY modules are set to ON,
• all of the cables are properly connected,
• +12 / -12 V is coming to Pcal laser power cable,
• +24 / -24 V is coming to AOM driver power cable,
• all other power indicator LEDs on the front panels of the modules were on,
• Pcal laser is not on,
• Shutter is not powered (the power indicator LED on the shutter is off).

From this limited information and under the assumption that nothing is broken in the Pcal system, one of possible sources of the issue might be that control signals are not reaching the Pcal Interface module through an EtherCAT connector. The laser on/off and power level (5.0 V) signals should come through this interface (the Pcal Interface Chassis back-side board circuit is given in D1400149).

The issue in currently under investigation.

Summary:
After the test on CW injections (LHO alog 27409), I decided to revisit the ETMX Pcal actuation function and inverse actuation filter because I have some concern that the new actuation function is not as accurate as I initially desired. Following a similar procedure as LHO alog 27176, I created new filters and obtain an inverse actuation function that is within 5% in magnitude and 5 degrees of phase up to 2 kHz, and within 5% and ~10 degrees of phase up to 3 kHz. The new inverse actuation filters are loaded into the PINJ_TRANSIENT bank. Waveforms using the inverse actuation filters should assume a time advance of 240 usec. Attached are the actuation function files, one without the 240 usec delay and one with the 240 usec delay.

Details:
In the same way as LHO alog 27176, I created new AI analog and AI digital approximations. The new approximations are actually not very good by themselves, but when used in conjunction with all of the filters in the PINJ_TRANSIENT bank, it accurately reproduces the true Pcal actuation function within 5% in magnitude and 5 degrees in phase up to 2 kHz.

Changes:

1. Analog AI approximation was [8k,8k:7.15k,7.15k], and is now [7.9k,7.9k:3.5k,3.5k]
2. Digital AI approximation was [7k,7k,7k,7k:pair(4300,30),pair(7000,50)], and is now [7.5k,7.5k,7.5k,7.5k:pair(4500,40),pair(6500,60)]
3. The three 7k poles were moved to 7.5k

In addition, I used the Matlab quack3 function to produce SOS filters to be copied into Foton. I found that entering the values as zpk in Foton did not reproduce the Matlab results. A transfer function was exported from Foton and loaded into Matlab for detailed comparison. No significant differences were found

Attached are figure files showing the comparison of the AI analog/digital approximations, comparison of the approximate Pcal actuation function to the real actuation function, comparison of approximate inverse actuation function to real inverse actuation function, and the impulse response of the inverse actuation filters. Also attached is the actuation function with and without a 240 usec delay for use with the CW hardware injections.

Rana, Evan

WE measured the SRM to SRCL TF today to find the frequency and Q of the internal mode. Our hypothesis is that the thermal noise from the PEEK screws used to clamp the mirror into the mirror holder might be significant contribution to DARM.

The attached Bode plot shows the TF. The resonance frequency is ~3340 and the Q ~150. Our paper and pencil estimate is that this may be within an order of magnitude of DARM, depending upon the shape of the thermal noise spectrum. If its steeper than structural damping it could be very close.

"But isn't this ruled out by the DARM offset / noise test ?", you might be thinking. No! Since the SRCL->DARM coupling is a superposition of radiation pressure  (1/f^2) and the 'HOM' flat coupling, there is a broad notch in the SRCL->DARM TF at ~80 Hz. So, we need to redo this test at ~50 Hz to see if the changing SRCL coupling shows up there.

Also recall that the SRCLFF is not doing the right thing for SRM displacement noise; it is designed to subtract SRC sensing noise. Stay tuned for an updated noise budget with SRM thermal noise added.

** see  https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=27455  for pictures of the SRM compsoite mass.

Related alog: 27053, 25468,

I updated the ETMY L3 stage digital compensation filters (FM2, FM6 and FM7 of ETMY_L3_ESDOUTF_{UL,LL,UR,LR}_GAIN) to the more accurate ones which are based on the recent measurements by Evan and Jeff. The coefficients are already loaded, but we have not gotten a chance to use the ETMY ESD yet.

To minimize possible errors for editing the foton file, I wrote a python script which automatically populate the filters, rather than editing the file by hand. The script is in the SVN at

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER9/H1/Scripts/SUS/setETMYLVVNcompensations.py