NikoL, Dimitri Estevez (Virgo), SudarshanK (remotely), RickS

This morning, we calibrated the Yend Pcal readback channels using the working standard (WSH) that we had delivered to Yend yesterday afternoon and left powered up overnight.

We encountered a couple of software issues related to the updates to calculate the force coefficients in the frontend, but we were able to complete the measurements.

The power sensor coefficients calculated today were very close to the values we calculated from the measurements made on December 13.

We decided to go ahead and switch to using the force coefficients calculated in the frontend (using JeffK's new code).  We updated the epics values using the data from our Dec. 13th measurement and captured in the .txt file attached in that entry.  We "put" the values into the epics records by just copying and pasting the text in the lho_yend_pcal_epics_created-20190115.txt file attached to this entry and in the SVN at

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Results/CALCS_FE/yend_pcal_epics_created-20190115.txt

The new  Pcal power sensor calibration values (N/V) and comparisons with the previous values are:

We are using In-air POP_X WFS so I shook ISCT1 to check for coupling. The figure shows that none was found.

I noticed that the long trend data of ETMY charge has not been plotted and posted since October.  Both ETMs have had charge data collected in Dec, but ETMY data has been throwing errors in the Long_Trend.m matlab plotting script.  Since Georgia was the last to have successfully plotted the data, I solicited her for a hint.  She reports that in October, she had to create a separate script which had the LR data removed in order to get it to run successfully.

So, for the future, in order to plot the longer trend data of charge use the following scripts in /ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Scripts:

for ETMX use the normal Long_Trend.m

for ETMY use Long_Trend_ETMY_LHO.m

(I've updated the wiki page for this https://awiki.ligo-wa.caltech.edu/wiki/ESD_OPLEV_Charge)

Attached is the plot with the new data set measured in Dec.  Note, charge on ETMY was up near ~50V before we vented Nov 13, 2018 in an to attempt to fix the LR ESD connection.  The attempt was unsuccessful, however we managed to blow off some of the accumulated charge before closing again.  So, there is that.

Daniel, Nutsinee

Attached two plots of LO and TTFSS control signal. One shows TTFSS control signal when LO was locked (Dec 27) and the other shows TTFSS control signal when LO was unlocked (Jan 2). Everything is calibrated in green Hz/V (say free-running laser would be ~200Hz/sqrt(Hz) at a 100Hz). 

Our scheme makes the laser follows the OPO, thus the TTFSS control signal should see mostly free-running laser noise. And whatever's left is taken care of by LO. Thus we look at LO spectrum for OPO length noise. LO fast signal is fed to additive offset of the TTFSS and slow signal goes to OPO PZT. 

The feature at and around 1.4kHz is what we thought might be the actual length noise of the OPO as the line disappear from TTFSS control signal when you turn on the LO loop. But there are lines between 10lHz-30kHz that only shows up on the TTFSS control signal when the LO is locked. Suggested that they are introduced by the LO loop (possibly OPO PZT). Could be notched out. For the rest of the noise, I'm not sure if we know where they came from. Part of it could be PSL LO fiber noise. It'd be nice to compare to a spectrum taken with the OMC. 

To get the laser PZT calibration I moved OPO PZT by 0.5 V (corresponds to ~10MHz), looked at TTFSS PZTMON (not /25) and 158MHz beat note. The PZTMON read out is then multiplied by the filters on the interface board to get the actual voltage sent to the laser PZT. The result is 1.7MHz/V (in red). 

For LO fast output calibration V/Hz I relied on TTFSS IMON Vpp/FWHM. There's a factor of 100 at the additive offset. 

Files in m/sqrt(Hz) and rad/sart(Hz) attached below.

Note that h1inj1 and h1inj2 at LHO have now been patched, rebooted, and brought up to SL7.6

Ana, Madox, Yasmeen, Stefan

We went to EX and EY to remove the CNS II Timing Diagnostic System GPS clocks and measure the GPS antenna cable lengths as part of work permit 8044. This will have NO IMPACT on anything outside of timing diagnostics.

EY

• 2pm got to EX
• 2:05pm disconnected power to CNS II EX
• 2:15pm left EX to get TNC adapter (whoops)
• 2:30pm returned to EX to do TDR measurement
• It is LMR-195 cable in the end station, velocity factor 0.8. Cable name: CDS_GPS_ANT_VEA
• 2:46pm finished TDR at EX and left

EY

• 3pm arrived at EY
• 3:02pm disconnected CNS II
• EY Cable name: CDS_GPS_ANT_VEA

We suspect that the cable connects to a cable in VEA after 90 ft which goes up to the roof. The total measured length at both end stations was about 210 ft;, however, this might be wrong if the cable to the roof has a different velocity factor than the LMR-195 going from VEA to the CNS II clock. Same for EX. We will go out tomorrow to EX to look at the cable type connecting from VEA to the rooftop GPS antenna and measure its length.

TITLE: 01/15 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY:

Busy Busy Maintenance Day!
LOG:

• HAM2 rails & HAM6 cleanroom already rolled 
• Contractors:  portapotties
• Early-16:53:  FSS work (Peter King)
• 15:35 Kissel arrives
• 15:40:  Cleaning started Karen (EY) & Vanessa (EX) to out buildings
  • Vanessa & Karen (LVEA)
• ~15:40 ISI config taken to SC_OFF_NOBRSXY (JeffK)
• 15:45 Corey arrives
• 15:45 Richard to CER & PSL to help PeterK
• 15:50-17:00 SEI PROC & corner boots (JeffK, Jim)
• 15:51 VAC walk-thru (Chandra)
• 16:09-18:40 EY PCal meas (Rick, Niko, Dmitri)
  • Transitioning to HAZARD AT EY
  • 16:50 Niko & Dmitri joining
• 16:08 Cara out to help, if needed, in LVEA
  • 16:14 Betsy & Christina out to LVEA
• 16:18 SEI proc & SEI corner reboot (jk, jw)
• 16:16 TCSy Chiller swap.  TCSy laser OFF (tj)
  • 17:09 swapped!  & confirmed OK at 17:23.
• 16:30 Fire Dept testing x-arm building (most likely MX) 
• 16:36-19:15 IO Mirror damping start (Robert, Cheryl)
• 16:39 - 20:44 removing HV power supplies at HAM6 to do EX ground checks (fil, ed)
  • Ed replaced HAM6 HV power supplies fil removed for EX
  • 19:20 Ed, Deisy, Stevie joining
  • ESD on temporary power, awaiting check from Robert.
• 17:00-17:40 ISCT6 parts (Nutsinee)
• 17:15-19:31 MX, EX safety walk-thru (Chandra)
• 17:10-17:20 CAL EX model work (Jamie, JeffK)
• 17:18-18:40 EY laser HAZARD!
• 17:35 -19:44 SRM set-up work (Danny, TVo)
• 17:35-18:30 Barriers for East Bay (Betsy, Travis)
• 17:39-20:00 rack noise hunting (Dick, Marc)
• 18:06 accelerometer cable check (Ed)
• 18:44 - 21:00 EY HWS beam align (Danny)
  • 19:48 TJ joining
  • ~21:00 EY Transitioned to SAFE
• 18:45 LVEA HAZARD! (tj)
• 19:00 EY back to HAZARD (danny)
• 19:15-19:25 IO PSL component loose on table (Cheryl)
• 19:34-20:00 PEM Inventory check for non-table (Kara)
• mid-morning Cal EX, EY model work for ODC (Jamie)
• mid-morning ASC ODC work (Keita, Jenne)
• 20:45-20:49 Single-bounce measurements for SQZ (Sheila)
• 21:20 Starting Init Align
• 21:52 EX & EY need to remove gps clocks (Timing crew)
• 22:13 EY trip for:
  • Plugging in phone (Ed)
  • Transition to Hazard (Ed)
  • Check ISCTEY for why WFSB has no light on it. (Jenne, JeffK)
    • Found cables in beam path (Jeff took photos).
  • 22:43 Transition to SAFE (Ed)
• 0:00 H1 is being taken to NOMINAL_LOW_NOISE (so far it is currently at PREP_ASC).  Handing off to Jeff K.
  • Note:  OMC didn't lock on first attempt, but Jenne & Jeff are addressing this at the PREP_DC_READOUT step......

Post-Michelson Locking NOTES:

1) Diag_Main gave us an Xarm polarization above 20% message---->  TJ took it down to 17 via remote medm screen

2) Trying TJ's new guardian INIT_ALIGN node 

INIT_ALIGN Guardian notes:

• Currently one might be able to take it all the way to MICH_DARK_ALIGNING, and then tweak the BS, and go MANUAL to SRC_ALIGNING & continue on....
• by going MANUAL to SRC_ALIGNING (& then finish off with INIT_ALIGN_COMPLETE

But for today's attempt, it didn't lock a DARK michelson.  So went through usual exercise of going DOWN---ultimately determined we needed to go DOWN with ALIGN_IFO.  Tweaked BS & then took  INIT_ALIGN to SRC_ALIGN (via MANUAL command), but the SRC was pretty misaligned & so guardian was stuck in a loop.

So old school manual fix for misaligned SRC is (Jenne, JeffK):

• Go to DOWN with ALIGN_IFO
• Misalign SRM
• Look at AS_C centering & center this spot via SR2
• Once AS_C looks centered, go back to SRC_ALIGN with ALIGN_IFO.

A new h1calinj model has been installed on the h1oaf1 machine.  This model will hold all front-end injection handling logic, including the injection EXC test points, under the channel prefix "H1:CAL-INJ_".  The existing injection handling code in the h1calex model ("H1:CAL-PINJX_") has been left as is for now to facilitate transitioning and testing.

The first two attached images are of the top-level contents of the new h1calinj model, and of the contents of the "INJ" CAL_INJ_MASTER2 library part that contains all the core logic.  The top of the latter shows the main injection signal flow.  The two "CW" and "TRANSIENT" filter banks at the upper left hold the EXC inputs and calibration filters for the continuous-wave (CW) and transient (TRANSIENT) injection inputs respectively.  The outputs of the two modules are summed and the overall "MASTER" output goes through an output switch ("MASTER_SW"), and then finally a switch ("END_SW") that determines which of calex or caley receives the injection signal ("H1:CAL-INJ_{X,Y}" via cdsIPCxRFM).  Below the main signal path is logic to determine the presence of signals at various points in the injection path, and bundle that info into a single status word ("STATUS_OUT").

IPC receivers for the INJ_MASTER output sent from h1calinj (H1:CAL-INJ_{X,Y}) were added to the h1calex and h1caley models.  EPICS and acquired test point monitors of the received signals were also added.

NOTE: a single 2**14 Hz, 61 us cycle delay will be added to the injection path because of the IPC needed to carry the signal from the vertex to the ends.

The new acquired fast channels are:

• H1:CAL-INJ_CW_OUT_DQ
• H1:CAL-INJ_TRANSIENT_OUT_DQ
• H1:CAL-INJ_MASTER_OUT_DQ
• H1:CAL-INJ_STATUS_OUT_DQ
• H1:CAL-INJ_X_OUT_DQ
• H1:CAL-INJ_Y_OUT_DQ

The STATUS channels (the H1:CAL-INJ_STATUS_OUT_DQ uint32 fast channel and the H1:CAL_INJ_STATUS slow channel) have the following bits:

0. MASTER
1. CW
2. TRANSIENT
3. CBC
4. BURST
5. DETCHAR
6. STOCH

A value of zero (0) indicates no signal of the specified type is present, and a value of one (1) indicates the presence of the specified signal.

The h1calinj model also holds the "TINJ" EPICS status bits, nominally set by the INJ_TRANS guardian node.  NOTE: the "H1:CAL-INJ_TINJ_" EPICS records were previously hosted by the ext_alert_ioc.py soft IOC running on the h1fescript0 machine.  The records were removed from the soft IOC and the process was restarted.

The final image attached is a new MEDM screen CAL_INJ_CONTROL2.   All functionality and status bits in the h1calinj model, and the monitors in h1calex and h1caley, are exposed.

As mentioned above, all the existing INJ infrastructure remains in place.  We leave it up to the INJ group to update the INJ_TRANS guardian, the psinject process, downstream monitors, etc.  We would like to schedule the removal of the old INJ infrastructure as soon as possible,

Investigation of noise coupling into the EX ESD power supply monitor channels (alog 46038) continues. ESD electronics powered off temporary power supplies.

F. Clara, R. McCarthy, E. Merilh

ODC removal (as per ECR 12045) has begun.  Summary:

• All ODC IPC senders were removed from all CS ISIs, HAM1 HPI, h1asc, h1iscey, h1caley front end models.
• All existing INJ logic was left in place, including the full INJ ODC monitoring path from h1calex -> h1iscex -> h1odcmaster (see subsequent log on INJ changes).
• All IPC receivers were removed from h1odcmaster, and all inputs were grounded, except the IPC receiver from h1iscex (see below).
• OBSERVATORY READY/INTENT/OBSERVE logic was removed from ODC.  This will be replaced by functionality in the guardian system (to be done).

Detailed front end changes:

• h1odcmaster: All IPC receivers were removed, and the corresponding inputs to the ODC MASTER block were grounded, EXCEPT the H1:ODC-X_CHANNEL_RFM IPC receiver from the X end (h1iscex).  All GRD EPICS channels were removed.  All OBSERVATION READY/INTENT logic was removed.  The primary H1:ODC-MASTER_CHANNEL_LATCH channel was left in place.
• h1iscey: All ODC blocks and related IPC senders/receivers were removed.
• h1iscex: All ODC-related IPC senders/receivers were removed, and the corresponding inputs to the ODC block were grounded, EXCEPT the  H1:CAL-X_ODC_SHMEM IPC receiver from h1calex.
• h1caley: The PINJY block was completely removed, including all PINJY ODC logic.  The IPC SHMEM sender to h1iscey was also removed.  A new IPC RFM receiver from the h1calinj model was added (see subsequent log about INJ changes).
• h1asc: All ODC blocks and related IPC senders were removed (see subsequent log about ASC model changes).
• SEI: All ODC-related IPC senders were removed from all corner station ISI models, and the HAM1 HPI model (see subsequent log about SEI model changes)

Further removal of ODC from the rest of the system (ISC, SUS, PEM, etc.) is deferred to later maintenance. 

I swapped out IO_MB_M3, which is a 2 inch steering mirror just before the power rotation stage at the North end of the PSL.  The new optics position was slightly different than the old optic's position.  I used my GigE cameras and the single bounce of IMC_IN off MC1 to the IMC WFS, to restore the alignment of IMC_IN.

Here are the changes in the IMC, measured by how many urads the three IMC mirrors moved, and what that calculates to be in mm.

Changes in the beams on the cameras are listed below:

NOTE: GigE 1 is the PMC Trans beam, and due to temperature changes it's beam changed, which influences the beam positions on the other two cameras.

The camera image pixels have not yet been calibrated, so that they can be displayed in either mm, or possibly the angle change.

Robert added damping to the bottom periscope mirror and IO_MB_M3 during this time.

As time was limited, I'll plan to add a picture of IO_MB_M3 next week.

- Cheryl, Robert

Restarted CW hardware injections at GPS 1231624918 (Jan 15 2019 22:01:40 UTC). They seem to have crashed on January 8 (maintenance disruption?). 

It would be good to get monit running so that restarts occur automatically.

A few weeks ago I noticed my daily build was reporting adcparser errors with h1asc. The parts array was of fixed size=5000 and h1asc had grown to about 5200 parts. I increased the limit to 6000.

Yesterday I noticed the error had come back, and sure enough h1asc had grown to 6894 parts. As a side note, this seems to be a rather large increase in a short amount of time.

I have bumped up the limit from 6000 to 10,000

Previously in alog46336 I felt like I was bottomed out on some of the measurements phase delay wise. To get more phase delay so we can be more confident in our measurement I gave 3MHz phase delay box to CLF (I have a feeling that phase delay box hooked up to LO/OMC gives me a bit less phase, not sure if that make sense, I will post more detail alog on the ellipse rotation later). Add CLF sign flip on top of that (which gives us extra 90 degree as Daniel suggested) I was able to go from OK to GOOD then back to OKAY measurement on both squeezing and anti squeezing. Flipping LO sign didn't help (180 deg). And using Q error signal to lock the CLF seems to have given me some extra phase adjustment (not sure why, CLF common mode board input 2 now has Q error signal goes into it). This way I know that I've seen the best sqz/asqz (by monitoring LO Q error signal go up and down while adjusting the phase, we locked with I).

After correcting for some of the minor loss typos and added data taken yesterday after I've acquired more phase delay, here I attached another loss estimate plot. I also give phase noise of 10 mrad this time since assuming that what we measured out of the LO IMON isn't all the phase noise there is. The result hasn't changed. We have more loss compared to when Haocun took a measurement here. We are still in the process of checking red transmission then and now.

Fringe visibility during Jan14 measurement was 99%. In the model I use 97%.

I did some injections on HAM1, for comparison with 42694 and 42722

I reduced the amplitude compared to 44856, so these excitations aren't showing up in DARM, but people can look for them in the REFL WFS and table top L4Cs.  

The Z excitation started at 2:11:50 UTC, was stopped after a large glitch at 2:23 UTC Jan 15th. 

The X excitation started at 2:27 UTC, but there were several large glitches.  a relative glitch free time was from 2:37-2:44, the excitation continued until 2:44 UTC. 

The Y excitation started at 2:55 UTC, and was on until 3:06.  We had to turn the dither lines back on partway through that because the PRC1Y was slowly going unstable. 

Dan, Hang

Using the dithering lines we set up for the past few days for sensing matrix measurement, and the suspension calibration provided in DCC:T1100378, we calibrated the spectra of the ASC error points into physical rad/rtHz. The results were attached.

The best sensor we have is AS45 for DHARD, and the sensing noise is ~ 1e-14 rad/rtHz. While a single QPD has a sensing noise similar to AS45, when we use a QPD combo for CHARD to decouple CSOFT, the sensing noise get slightly worse at ~ 3e-14 rad/rtHz level. The soft loops' sensing noise is about a factor of 10 higher than the hard loops at a few x 1e-13 rad/rtHz level.

On the other hand, the REFL sensors are significantly noisier than AS45/TR QPDs. Using the REFL sensors the CHARD sensitivity is only 1e-12 rad/rtHz at 10 Hz and the slope suggests that it is not shot noise limited. This indicates the necessity of doing CHARD blend from the noise point of view.