J. Kissel, A. Viets
WP #6572
ECR E1700121
II 7828

Because I'm not sure how long it'll take to make the MED screens and fully commission the new parts' settings until we have results, I just want to get an aLOG in there that confirms we've installed the front-end infrastructure changes to begin tracking the SRC detuning as a function of time.

This required modifying 
/opt/rtcds/userapps/release/cal/common/models/CAL_CS_MASTER.mdl
to include many new EPICs records that store various DARM loop model component values at the already-existing PCAL line frequency (7.93 Hz), and as a bonus, I also installed all of the infrastructure to compute the SRC detuning frequency in the front-end as well -- it was an easy extension of the existing software to calculate the optical gain and cavity pole frequency, following the math in T1700106 and LHO aLOG 35105.

I've installed values for these new EPICs records using svn up'd versions of
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/CAL_EPICS/writeH1_CAL_EPICS.m
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/Common/Scripts/CAL_EPICS/writeO2_TDEP_EPICS.m
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/DARMmodel/Scripts/computeEPICS.m

To do/aLOG:
 - Take screen shots of the new model infrstructure to show the implementation
 - Update TDEP MEDM overview screen to include the new math
 - Install demodulation parameters and lowpass filters for new 7.93 Hz demod
 - Install low-passes on F_S and Q_S output banks
 - Compare against GDS pipeline output

I reset both PSL power watchdogs at 19:16 UTC (12:16 PDT).  This completes FAMIS 3645.

Greg, Aaron and John are in the midst of the GDS/DMT update.

Re: WP 6567

The yum updates and reboots of the DMT computers is done. I've also restarted the dmt processes on each box.

The next step is for Aaron Viets to restart the calibration using gstlal-calibration-1.1.5.

This morning I swapped the ITMy oplev laser, per LHO WP 6565.  This was in response to this alog from K. Venkateswara and J. Kissel, indicating an ~0.44 Hz feature on the ITMy oplev (that showed up after the laser swap on March 7th) was possibly due to an issue with the laser and causing range issues.  The old laser SN was 189-1, the new laser SN is 191.  This laser will need a few hours to come to thermal equilibrium, once that is done I will assess whether or not the laser needs a power tweak for glitch-free operation; I will leave WP 6565 open until this is complete.

Carlos has returned the HWS card to h1hwsex (was in the spare machine h1hwsmsr1).

Unplugged one extension cord, but that is it.

The cell phone texter alarm system was reconfigured, all eight LN2 Dewar low level alarms will now start at 15% full instead of the previous 20%.

h1pemcs was modified to return two test ADC channels to the frame, both at 2048Hz.

Jeff made his h1calcs model change. This only added slow channels to the frame (203 chans).

I changed the DAQ master to add the new H1EDCU_SEISMON.ini file.

11:44PDT: DAQ was restarted for the above.

[Kyle, Chandra]

In preparation for anticipated vertex vent, we tested vacuum equipment:  QDP80 roughing pump, Kobelco purge air skid, and vertex turbo & scroll pumps. All ran satisfactorily. Purge air measured -43.7degC dew point. A few notes:

• need access to LVEA later today or tomorrow to de-energize vertex turbo station after turbo is fully spun down
• left cooling water valved in to QDP80s and the Kobelco energized for further cooling after being powered down
• swapped battery pack on vertex turbo station with one that was fully charged
• purged the QDP80/turbo header with clean air before turning pump off (header/purge air isolation valve back in closed position)
• noted a leaky flange on purge air line under XBM
• found that the Kobelco oil temp. was hot - needed to crack open the cooling valve in back *slightly* more (~1/8 turn)
• recommend better labeling of control cables to QDP80 pumps
• need to make a long control cable for vertex turbo station (we used jumper and powered up QDP80 from XBM turbo station)
• installed a filter on vertex scroll exhaust
• had fun

[Vaishali, JimW, Jenne]

During maintenance, while no one needed the IMC, we tried out our new L2A decoupling filter for MC2.  Recall that Jim found that it would be helpful in alog 35330, and we measured and fit TFs for it in alog 35397.

We found that (a) the pre-existing L2A decoupling was in fact worse than doing nothing at all, and (b) that our new filter works well. 

In the attached screenshot, the upper left corner is the Foton Bode plot of our decoupling filter.  In the other 3 DTT panels we have the coherence and transfer functions of 3 different MC2 L2A configurations. For these measurements, the IMC was unlocked, but MC2 still aligned.  The red traces in all panels are with no L2A decoupling at all.  The blue traces are with the old L2A "decoupling" gain.  That was a flat gain, and clearly was making things worse than doing nothing at all, over a pretty broad frequency range.  The green traces are with our new L2A decoupling filter on, and we win almost 20dB of isolation below a few hundred mHz.  

We have accepted the new L2A settings for MC2 in the safe and observe SDF files, so they should always be on now.   

these models' filter files were static files located in the chans/ directory. I put them into SVN control and made symbolic links from the chans/ directory to there new location under userapps.

[Jeff K, Aaron V]

I have produced new GDS filters for LHO that include new paramters (pcal correction factors and EPICS) necessary to compute SRC detuning parameters. It will also be possible to subtract the calibration lines from the strain, producing the additional channel GDS-CALIB_STRAIN_CLEAN, if we desire. The filters can be found in the calibration SVN at this location:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/GDSFilters/H1GDS_1175954418.npz

For information on GDS calculations of SRC detuning parameters, see:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=35041  (note that we now compute Q-inverse instead of Q)
https://alog.ligo-la.caltech.edu/EVNT/index.php?callRep=11785

The filters were produced using this Matlab script in SVN revision 4537:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/TDfilters/H1_run_td_filters_1175954418.m

The parameters files used (all in revision 4537) were:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/2017-01-24/modelparams_H1_2017-01-24.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/2017-01-24/H1_TDparams_1175954418.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/CAL_EPICS/callineParams_20170411.m

ASD plots comparing GDS and the front-end CALCS model are attached. These agree with those on the summary pages from the same day (4/10), as expected. Also, time domain vs. frequency domain comparison plots of the filters are attached. Lastly, a time series plot of the kappas from GDS and CALCS is attached, as well as histograms. These show the expected output.

There were number of high frequency calibration lines injected using the automated Guardian scripts. These lines are injected using the Pcal at ENDX (ENDY is used for calibration purpose). The GPS time at which these lines were running are listed below:

TITLE: 04/11 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC

STATE of H1: Observing at 65Mpc

INCOMING OPERATOR: Jeff

SHIFT SUMMARY: Not much going on. PI Mode 23 rung up. I flipped the phase 180 degree and it seemed to stop ringing up. I later found an alog that operator shouldn't damp this mode. So what's the status now?

LOG:

13:56 Briefly out of Observe (accidentally). See alog35458

~13:56 UTC, I accidentally re-enabled the front end laser watchdog.

Been locked and Observing since Travis handed off to me. Not much to report.

TITLE: 04/11 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 72Mpc
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY:  A pair of locklosses, one unknown and one due to PI.  Otherwise, nothing to mention.
LOG:  See previous aLogs.