From Sheila's request, I ran BruCo on two times, 

Nov. 22, 7:30:00, https://ldas-jobs.ligo-wa.caltech.edu/~youngmin/BruCo/ER10-O2A/H1/Nov22/H1-OMC-DCPD-1163835017-600/

Nov. 22, 13:26:24, https://ldas-jobs.ligo-wa.caltech.edu/~youngmin/BruCo/ER10-O2A/H1/Nov22/H1-OMC-DCPD-1163856401-600/

From quick view on the results, ASC CHARD looks concerns around under ~25Hz.

At Reed Essick's request, I have scheduled DetChar safety study hardware injections for tonight starting at 4:00 PST Nov 23 2016. These are listed in schedule_1163473217.txt (SVN rev 5235):
1163937617 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163938117 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163938617 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163939117 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163939617 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163940117 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163940617 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163941117 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163941617 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163942117 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163942617 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163943117 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163943617 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163944117 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt
1163944617 H1 INJECT_DETCHAR_ACTIVE 1 1.0 detchar/detchar_03Oct2015_PCAL.txt

These are spaced 500 seconds apart and H1 needs to be in observation intent for the hardware injections to go through. We have coordinated this so as not to interfere with PEM injections.

The "roaming" 5001.3 Hz Pcal calibration line has to be turned off for this test, and since I am leaving for the night, it was turned off at 4:12 Nov 23 2016 UTC. We will turn it back on in the morning (apologies Sudarshan!).

I turned back on the 5001.3 Hz "roaming" calibration line (LHO aLOG 31738, it was turned off for the HW injection test, aLOG 31747) at 03:25 UTC but this did not drop H1 from observation intent. Is this the intended behavior? Perhaps it should have dropped us!

This afternoon we had 2 more locklosses due to the instability at 1.88 Hz which we have struggled with for a few weeks.  (31707) 

This time Keita and I looked at the filters for the soft loops, and saw that we have some kind of plant inversion from a long time ago that has a complex pole at 1.83 Hz, which was giving us 15bB of gain there unnecessarily. (reminder, the soft loops generally have bandwidths of a few hundred mHz, except for CSOFT P which needs to have gain at 0.5Hz to supress our dPdtheta instability).

We turned off these invY filters, and saw that the noise at 1.88Hz in several of our YAW ASC loops was reduced.  For the soft yaw loops, the peak at 1.88Hz was reduced by about 20dB (in the attachment, dashed lines are from last night's undisturbed lock stretch, the solid lines are from the last lock where the invY filters were off.)  There is still clearly extra noise at 1.88 Hz, so something else may be nearly unstable. 

I've scheduled a coherent bbh injection for 3:00 UTC as part of the end-to-end test. 

The schedule file (schedule_1163473217.txt) was modified and checked into the svn (https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/inj_trans/). I logged into each site's hardware injection machine (l1hwinj1 and h1hwinj1) and checked out the updated schedule file (/usr/local/home/hinj/Details/inj_trans). I then reloaded the INJ_TRANS guardian at each site. At LHO EvanG checked that the guardian was ok, he had to change the request to INJECT_SUCCESS (i forgot to check this).

Here is the new line in the schedule file:

1163905217 H1L1 INJECT_CBC_ACTIVE 1 1.0 Inspiral/{ifo}/coherentbbh7_1126259455_{ifo}.out

Each IFO will need to be in observation intent mode for the injection to go through.

J. Kissel
WP 6338

We've implemented the same bug fix to the CAL-CS front-end model that LLO has that connects the H1:CAL-CS_TDEP_DARM_LINE2_DEMOD_OSC into the sum for calibration line output of the CAL-CS model, shipped over to the OMC model to be added in just after the LSC-DARM banks. This oscillator is occasionally used for testing, so we need it hooked up. 
Check out LLO aLOG 29521 for screenshots of the model change.

This change merely required an svn update of the 
/opt/rtcds/userapps/release/cal/common/models/
CAL_CS_MASTER.mdl
to absorb the changes that Joe has already made, followed by an installation and restart of the h1calcs model. No DAQ restart was required, but the DAQ was restarted for various other changes made this morning.

J. Kissel, 
ECR E1600340
II 6665
WP 6338

I've installed the infrastructure that allows for control of the IFO's DARM DOF with either (or both) PCALs as designed by LLO (see LHO aLOG 29509). Unfortunately, because this was implemented quickly -- this is not decided in the LSC output matrix, but a combination of gains downstream. 

This change required an update to the common library part,
    /opt/rtcds/userapps/release/cal/common/models/PCAL_MASTER.mdl,
modifications to both PCAL model's top-level
    /opt/rtcds/userapps/release/cal/h1/models
    h1calex.mdl
    h1caley.mdl,
and a DAQ restart after installation and restarts of both end-station cal models. 
Also, I've updated the PCAL_END excitation screen,
    /opt/rtcds/userapps/release/cal/common/medm/PCAL_END_EXC.adl
However, I discovered that the PCAL overview 
    /opt/rtcds/userapps/release/cal/common/medm/PCAL_END.adl
also need modification to pass down the correct macro variables from that it received from the SITEMAP. Otherwise the new path to the new PCAL_DARM filter bank was ill-defined and wouldn't open. I've committed the changes to the top level models, as well and the PCAL overview screen in there respective locations in the SVN.    

For now, to transition from using ETM DARM control to PCAL DARM control, one should leave the LSC output matrix pointing to the correct end station's QUAD, but zero the 
H1:SUS-ETM[X/Y]_L3_ISCINF_L_GAIN (i.e. the first longitudinal input to the SUS), and turn on that end-stations PCAL DARM control bank, H1:CAL-PCALY_DARM. Of course, you have to design the appropriate filtering to account for the difference between the ESD drive and PCAL drive, which I have not yet done.

Krishna

I recentered the c-BRS based on a visual inspection of the instrument. The two interferometer arm-lengths were mismatched on the order of ~1 mm and were accordingly adjusted. The differential tilt signal may show some improvement, assuming it is not limited by other noise.

I have also been investigating the excess low-frequency signals in c-BRS by comparing it to a host of nearby sensors. So far, the likely suspect appears to be air pressure, though I don't yet understand the mechanism for the effect. I'll fill in more details tomorrow.

I have restarted the DCS Disk2Disk processes writing to archive at LHO with,

 set CHECK_SOURCE_MD5SUM 1

in the Disk2Disk .conf files, so that the CDS .md5 files are now compared with the md5sum found by Disk2Disk before the file gets copied to the LDAS archive. (The file must also pass FrCheck to be copied, as before.)

Evan, Dave

the CW hardware injection has not been running since the restart of the h1calex model at lunch time. Via monit, I restarted this process and it looks like the injection is running again.

J. Kissel for S. Karki

I've moved the roaming calibration line to its highest frequency we intend to go, and it's also the last super-long duration we need. We may run through the lower frequency points again, given that (a) they need much less data, and (b) those data points were taken at various input powers that will likely confuse/complicate the analysis. Below is the current schedule status.

Current Schedule Status:
Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 11 2016 21:37:50 UTC    Nov 12 2016 03:28:21 UTC      ~several hours @ 25 W
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00                   39322.0           Nov 12 2016 03:28:21 UTC    Nov 16 2016 22:17:29 UTC      days     @ 30 W (see LHO aLOG 31546 for caveats)
4301.3       40k                      10:00                   39322.0           Nov 16 2016 22:17:29 UTC    Nov 18 2016 17:08:49 UTC      days     @ 30 W          
4501.3       40k                      10:00                   39322.0           Nov 18 2016 17:08:49 UTC    Nov 20 2016 16:54:32 UTC      days     @ 30 W (see LHO aLOG 31610 for caveats)   
4801.3       40k                      10:00                   39222.0           Nov 20 2016 16:54:32 UTC    Nov 22 2016 23:56:06 UTC      days     @ 30 W
5001.3       40k                      10:00                   39222.0           Nov 22 2016 23:56:06 UTC

(see WP6332)

Also running turbo pump connected to PT180 hardware on dome of BSC8.  Coordinating with PEM folks to see if the IFO commissioning community can live with this noise source for a few days.  If so, we (Vacuum) would then bake the PT180 hardware while being valved-out from the YBM and while being pumped by these temporary pumps.  

Will be leaving these run past the official "Maintenance Day" period so as to see what these look like if/when the IFO is in low-noise.  May need to do some "on/off" tests as per Robert S. 

Jeff K, Kiwamu I, Darkhan T,

Overview

The CAL-CS EPICS records for tracking temporal variations of the DARM parameters have been updated at 2016-11-21 22:03:46 UTC. These values are identical to the ones in LHO alog 31677 from yesterday, i.e. D20161120_H1_CAL_EPICS_VALUES.m and D20161121_H1_CAL_EPICS_VALUES.m are identical.

New values have been accepted in SDF_OVERVIEW.

Details

Following DARM paramemter files were used to calculate these values:

${CalSVN}/Runs/ER10/Common/params/IFOindepParams.conf              r3752
${CalSVN}/Runs/ER10/H1/params/H1params.conf                        r3826
${CalSVN}/Runs/ER10/H1/params/2016-11-12/H1params_2016-11-12.conf  r3786

And the DARM model scripts from

${CalSVN}/Runs/O2/DARMmodel/*  r3814

The *.m file with EP1-9 values and the verbose output are attached to this report. All of the files have been committed to CalSVN at

ER10/H1/Scripts/CAL_EPICS/

D20161121_H1_CAL_EPICS_VALUES.m
20161121_H1_CAL_EPICS_VALUES.txt
20161121_H1_CAL_EPICS_verbose.log