I have been trying to reconcile the difference in laser room temperatures as measured by a temperature
sensor on the PSL table and the PSL environmental temperature sensor.  Back tracking through the
schematics ... etc. the signal H1:PSL-FSS_DINCO_REFCAV_AMBTEMP_OUTPUT corresponds to approximately
-2.207 V.  That would imply that the ambient temperature is over 40 degC, which clearly it is not.
An infrared camera image suggests the ambient temperature is around 22 degC with a couple of people
inside the enclosure.

    What may account for the discrepancy?
 - broken AD590 temperature sensor
 - non-zero voltage coming out of the DAC card, which is the ambient temperature reference signal
 - broken LT1021-7 in the temperature box
 - something else I cannot account for (always a distinct possibility)

Will try and sort this out in the next few weeks.

Jenne, Evan, Jim, Sheila

After the maintence period today the readbacks for the bias out of the ETMY ESD were zero.  Fil went out to EY to check on this, and saw that there was no voltage coming from the monitor channel, but did not know if there was actually bias going to the ESD.  

We tried to lock but failed to make the transition to ETMY.  After that we set up ETMY to be in high range, high voltage, linearization on (so that it would match ETMX) and drove them both in pitch.  The attached spectrum shows ETMY moving about 1/10 as much as ETMX, although they have the same drive state and the same output counts. This means we can't really noise hunt tonight. 

Liyuan Zhang (CIT), PeterK, JasonO, RickS

LLO has had some pre-modecleaner (PMC) issues.   S/N 08, their original unit, was removed due a "glitchy" PZT and the replacement unit, S/N 10 degraded quickly, apparently due to hydrocarbon contamination.

During the past week we have assembled a setup in the "Triples" lab (upstairs in the Staging building) to evaluate the performance of PMCs and, eventually, to repair them.

The setup is show in the photographs below.  Basically, we modematched a 2-W Innolight NPRO to the cavities which were removed from the tanks.  We used a Pcal integrating-sphere-based power sensor to measure incident, transmitted, reflected, and leakage power (through the two flat miirrors, M3 and M4).  We have ordered an amplitude-modulating EOM for making transfer function measurements to measure the bandwidth, but for these tests whe just measured the FWHM of the Airy profile by sweeping the laser frequency.

Removing the PMC from the tank turned out to be pretty challenging because the PMC bodies were stuck to the viton sheets at the bottom of the tanks.  We devised a method for removing them that works pretty well.  One can use the tank mounting blocks, the PMC body clamping bolts, and some Newport or Thorlabs "B2" bases to put upward pressure on the PMC.  On the one cavity we tested, it released within a minute or two. (See attached photo).

The measured performance of the "glitchy" PMC is broadly consistent with what Liyuan measured at Caltech.   Here we measured average losses per mirror of about 80 ppm.   We don't yet have an uncertainty estimate for this setup yet.

The estimated losses for the "dirty" PMC is about 1400 ppm per mirror.

Measurement details are in the .pdf file, attached.

We plan to repeat these measurements and estimate uncertainties.  However they clearly indicate that the "dirty" cavity is much more lossy than the "glitchy" cavity.  About 15% of the incident power is lost inside the cavity, vs. about 1% for the "glitchy" cavity.

Visual inspection of all four mirrors (from the outside) on both cavities did not reveal any noticable contamination or damage.

[JimW, Jenne, EvanH, Kiwamu, Sheila, Gabriele]

The new version of DTT seems only capable of getting a single channel of data at a time. 

We have tried several different kinds of channels, and DTT will only give you the first channel in the list.  No good.

I removed the following frequently changing channels from Conlog by adding them to the exclude list and regenerating the channel list.

- H1:ALS-X_CAM_ITM_PIT_POS
- H1:ALS-X_CAM_ITM_SUM
- H1:ALS-X_CAM_ITM_YAW_POS
- H1:IMC-ODC_CHANNEL_OUTMON
- H1:IMC-ODC_CHANNEL_PACK_PRE_PARITY
- H1:IMC-ODC_CHANNEL_STATUS
- H1:LSC-ODC_CHANNEL_OUTMON
- H1:LSC-ODC_CHANNEL_PACK_PRE_PARITY
- H1:SUS-SR3_M1_DITHER_P_OFFSET
- H1:TCS-ITMX_HWS_SLEDPOWERMON
- H1:TCS-ITMY_HWS_SLEDPOWERMON
- H1:VAC-EX_X4_PT525_PRESS_TORR
- H1:VAC-EX_X5_PT526_PRESS_TORR
- H1:VAC-EY_Y4_PT425_PRESS_TORR
- H1:VAC-EY_Y5_PT426_PRESS_TORR

Alastair, Evan, Kiwamu, Patrick

The TCS rotation stages were not working correctly. Powercycling the chassis in the CER got the TCSY rotation stage to work again. Powercycling the same chassis a second time got the TCSX rotation stage to work again.

Installation is complete. Full details tomorrow ... but we have channels with suffixes S_ASPORT and P_ASPORT now. It's the SASS PORT that's the real problem. Too much SASS.

Check out the channels from TCS > MASTER > POLARIZATION

Added ETM ISI Ringup to DIAG_MAIN

To help the control room see that the ISI is ringing up I've added a test to DIAG_MAIN to look for this (as per Jim W's request).But to do this I had to create a function that could look for the peak to peak difference in a specified amount of time. I found it to be useful for other code as well, so I made it a module in the userapps svn under /sys/h1/guardian/peak2peak.py

Made new peak2peak.py

In this module the p2p function will get a chunk of data using cdsutils getdata.py, break that data into a specifed number of chunks, find the difference between the max and min of each chunk, and then return a list of the peak differences. Maybe it will be useful to others, so I pulled it out of DIAG_MAIN.py

Reintroduced avg_no_print.py

cdsutils getdata will print to stderr for every second that it retrieves data. This is a problem for the DIAG Guardians because the call for data is in a loop, and the log will quickly fill up with "fetching (GPStime)...". I took a copy of getdata but commented out this printing feature, and placed in the the same directory as DIAG_MAIN.py.

I file FRS4293

Jim, Evan

Does this behavior of the ETM ESD DAC outputs make sense? Here a large offset has been applied to the UL coil output filter. However, the screen suggests that it's being applied to the UR DAC channels.

This behavior is seen on both ETM ESD DACs, but not the ITM ESD DACs.

The output of the NPRO was measured in front of the phase-correcting EOM to be 1.46 W.
This was measured with the 10-W power head.

The diode currents for the front end laser were increased to bring the diode powers
back to near the 100% level.


Jason, Peter

As part of the prep work for firing up the high power oscillator, the optical surfaces were
inspected.  Some time back in 2014 there was a water leak over head 3 resulting in some of
the surfaces getting wet.

    The high power oscillator was opened.  A fragment of lens tissue was found - presumably
from the last wipe down of the laser that was done to accommodate a request from LLO - near
the lid switch close to head 4.  Some metal shards were in the location.  Small blue coloured
metal shards were also found near the Faraday rotator.  These we know to be from the blue
anodising of the lid of the oscillator.  There were signs of possible galvanic corrosion after
removing the side of the laser, and at the base of an internal support member.

    Signs of water drops on all four 4f lenses.  These were drag wiped off successfully:
Drag wiped 4f lens #1.  Mostly clean, small spot around 2 and 4 near the edge of the optic.
Drag wiped 4f lens #2.  Clean.
Drag wipes 4f lens #3, mostly clean, small spot around 2-2:30 near the edge of the optic.
Drag wiped 4f lens #4.  Possible dust spot between 11 and 12 o'clock, ~two-thirds from centre
to edge.

    After performing the drag wipe, the inside of the oscillator was wiped down again so as
to not kick up any dust during the remaining dust removal steps.

  The two quartz rotators looked fine.  All the laser rod surfaces appeared okay.  The dust
on the 45 degree dichroic mirrors was successfully blown off.

  There was a possible dust spot on output coupler at 3 o'clock as looking towards exit port.
This was blown off.

The pump light lenses looked okay with the possible exception of head 3, which looks like it
has some scratches.  The scratches were there before drag wiping, and it would see that the
laser operated previously with them.  O. Puncken was consulted.


Jason, Peter

Ran new cables at EX for CPS sync fanout install. Cables are run from SUS-R1 rack to CPS units on chamber. Fanout chassis and RF cable (71MHz) still need to be installed/pulled.

Filiberto C. & Ed M.

New lab dust monitors

Jeff B, Jim, Dave [WP5697]

As part of the install of the new OSB lab dust monitors:

generated new autoBurt.req file. Generated new DAQ EDCU INI file. Recanned conlog against autoBurt.req file.

New GDS version

Jim [WP 5696]:

completed this morning.

Clearing partially loaded filter modules

Was able to do full loads on susbs, susitmx, susitmy, susprm, sussrm. Still have partial loads on lsc, omc, suspr2 and sussr2 which are waiting for the system experts to clear.

DAQ reconfigure

DAQ EDCU was reconfigured for the missing h1tw0 and new DUST channels. Was applied during today's two DAQ restarts.

DAQ Restarts

In both DAQ restarts the dataconcentrator, tw1 and both framewriters started with no issues. In the first restart the broadcaster started by both NDS daqd process were no longer controlled by monit. A simple monit restart of the daqd processes cleared the error. On the second restart the broadcaster started, stopped and later restarted. Again both NDS processes did not start, and when they were restarted they failed. The error was that high dcuid nodes for the Beckhoff SDF system has been mistakenly added to the testpoint.par file, and only the NDS machines objected to this. The file was repaired and monit was able to restart the NDS daqd processes.

TCS model changes

Aidan and Dave [WP5688]:

Installed new h1tcscs model onto h1oaf0. DAQ was restarted.

New Beckhoff SDF code release

Jonathan [WP5695]:

Jonathan tested the new code on EY Beckhoff. He found an issue with enumerated binaries and backed this version out.

RACCESS monitoring/control of h1hwinj1

Jonathan, Jim, Dave:

Jonathan added the hardware injection machine h1hwinj1 to his RACCESS control system. MEDMs were updated accordingly.

H1OAF change to drive audio in control room

Richard, Evan, Dave [WP5704]:

h1oaf and h1pemcs models were changed to permit oaf to drive the 8th DAC channel of PEM's 18-bit DAC card. This analog signal is then routed from the CER to the control room using the audio channel in the digital video fiber link between the rooms.

New operator table install in the control room

Richard, Carlos, Jim, Dave:

The new powered, adjustable-height operator table was installed in the control room at the operator station. The access control PC, gate cam and alarm machines were shuffled to the left and a new workstation was installed on the new table.

HPI and ISI safe.snap work

Hugh, Dave:

Hugh worked on the safe.snap files for HPI and ISI. I was able to offer some help by creating a new script to convert sub-systems to safe SDF mode and converted all HPI and ISI to safe. Later I converted them back to OBSERVE mode.

New ECAT EPICS channels for corner station

Daniel, Dave:

Daniel made Beckhoff changes in the corner station. I updated the ECAT DAQ INI files and the target autoBurt.req files.

Server patching and rebooting

Carlos, Dave:

Carlos applied security patches and rebooted cdsssh, cdslogin and cdsadminctrl. We restarted the vacuum alarms system on cdslogin.

Installed Whitening Board (D1500389) to ETM Low Voltage Driver Chassis (D1500129) per ECR E1500417.

ETMY LV Driver S1500066
- Whitening board installed S1600032


ETMX LV Driver S1500073
- Whitening board installed S1600035

High voltage was disabled prior to disconnecting of any cables. Verified outputs were not railing when units were reinstalled. One thing worth noting, is that the wiring for the binary cables is not consistent at both end stations. For now, we left cables in the same configuration we found them this morning.

Filiberto C. & Ed M.

Day Shift: 16:00-23:59UTC (08:00-16:00PT)

State of H1: down all day, down more than 12 hours, currently JimW at EY to fix ESD driver

Shift Summary:

Activities logged in alogs 25155, 25163, and 25171

Other activities:

• reboot of DAC end of the day
• reboot of Beckoff control of rotations stages
• ESDY identified as not ok - JimW and Evan at EY

Executive summary: 

In regard to narrow lines, the (nearly) full O1 H1 data set is little changed from what was reported for the first week's data: a pervasive 16-Hz comb persists throughout the CW search band (below 2000 Hz), accompanied by a much weaker and more sporadic 8-Hz comb; there remain several distinct 1-Hz and nearly-1-Hz combs below 140 Hz, along with other sporadic combs. The 1459.5 hours of 30-minute FScan SFTs used here span from September 18 to the morning of January 3. The improved statistics make weaker and finer structures more visible than in the 1st week's data. As a result, many new singlet lines have been tagged, and it has become apparent that some previously marked singlets actually belong to newly spotted comb structures. The improved statistics also make it more apparent that the originally spotted combs span a broader bandwidth than marked before 

Details: 

Using 1459.5 hours of FScan-generated, Hann-windowed, 30-minute SFTs, I have gone through the first 2000 Hz of the DARM displacement spectrum (CW search band) to identify lines that could contaminate CW searches. This study is very similar to prior studies of ER7 data, ER8 data and the first week of O1 data, but for completeness, I will repeat below some earlier findings.

Some sample displacement amplitude spectra are attached directly below, but more extensive sets of spectra are attached in a zipped file. As usual, the spectra look worse than they really are because single-bin lines (0.5 mHz wide) appear disproportionately wide in the graphics

A flat-file line list is attached with the same alphabetic coding as in the figures.

Findings:

 A 16-Hz comb pervades the entire 0-2000 Hz band (and well beyond, based on daily FScans)
 A typically much weaker and sporadic 8-Hz comb (odd harmonics) is also pervasive (all harmonics are labeled in figures, even when not visible)
 A 1-Hz comb with a 0.5-Hz offset is visible from 10.5 Hz to 133.5 Hz (previously was visible from 15.5 to 78.5 Hz)
 A 1-Hz comb with zero offset is visible from 16.0 Hz to 102.0 Hz (previously was visible from 20.0 to 68.0 Hz)
 A 99.9989-Hz comb is visible to its 11th harmonic (was previously visible to its 8th harmonic)
 The 60-Hz power mains comb is visible to its 9th harmonic (was previously visible to its 6th harmonic)
 There is a sporadic comb-on-comb with 0.088425-Hz fine spacing that appears with limited spans in three places near harmonics of 77, 154 and 231 Hz (ambiguity in precise fundamental frequency)
 There is a doublet 31.4127 and 31.4149 Hz comb visible to their 2nd harmonics (previously marked as only a 31.4149-Hz comb)
 There are three near-1-Hz combs not previous appreciated:

 0.99999-Hz comb from 19.2500 to 50.2497 Hz
 0.99816-Hz comb from 30.9430 to 60.8878 Hz
 0.9992-Hz comb from 30.9738 to 48.9594 Hz

 There is a doublet comb with spacings of 2.07412 and 2.07423 Hz, visible from their 9th to 32th harmonics (18.7-66.4 Hz) 
 There is a hint of another doublet comb with spacings of 99.9735 and 99.9784 Hz, but they are marked as singlets for now


Line label codes in figures:

b - Bounce mode (quad suspension)
r - Roll mode (quad suspension)
Q - Quad violin mode and harmonics
B - Beam splitter violin mode and harmonics
C - Calibration lines
M - Power mains (60 HZ)
s - 16-Hz comb
e - 8-Hz comb (odd harmonics)
O - 1-Hz comb (0.5-Hz offset)
o - weaker 1-Hz and near-1-Hz combs (various offsets, including zero)
H - 99.9989-Hz comb
J - 31.4127 and 31.4149-Hz combs
K - 0.088425-Hz comb
t - 2.07412 and 2.07423 combs
x - single line (not all singlets in the vicinity of quad violin modes are marked, given the upconversion)

Figure 1 - 0-2000 Hz 
Figure 2 - 20-50 Hz sub-band (shows complexity of combs below ~70 Hz)
Figure 3 - 50-100 Hz sub-band (shows continuation of strongest 1-Hz comb with offset of 0.5 Hz)
Figure 4 - 1300-1400 Hz sub-band (shows how clean the noise floor is away from 8-Hz, 16-Hz lines at high frequencies

Attachments:
* Zip file with miscellaneous sub-band spectra (with line labels)
* Flat-file list of lines marked on figures