TITLE:  1/7 DAY Shift:  16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC     

(Corey from 16-20UTC & Bartlett from 20 - 00UTC)

STATE of H1:  

Incoming Operator:  Cheryl

Support:  

Quick Summary:

Calibration work continues.

Shift Activities:

• 16:00utc Calibration work begins (Kissel et al.)
• 17:04 Filled PSL Chiller 175mL
• 18:45 H1 down.  MICH OLG calib work begins
• 20:00 Handing off to Bartlett to finish the shift

HWInjReport 1132963217 - 1136155727

Performed a run spanning the time period from 1132963217 (Dec 01 2015 00:00:00 UTC) to 1136155727 (Jan 06 2016 22:48:30 UTC)

Parameters

The following parameters were used for this run:

• GPS Start Time = 1132963217 # Beginning of time span, in GPS seconds, to search for injections
• GPS End Time = 1136155727 # Ending of time span, in GPS seconds, to search for injections
• Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
• Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
• IFO Coinc Time = 0.012 # Time window, in seconds, for coincidence between IFO injection events.
• Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
• Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
• Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
• Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
• Check CAL_RAW = True # Check CAL-INJ_ODC_CHANNEL_OUT_DQ channel in RAW frames.
• Report Normal = True # Include normal (IFO-coincident (network injections only), consistent, scheduled, and of known type) injections in report
• Report Anomalous = True # Include anomalous (non-IFO-coincident (network injections only), inconsistent, unscheduled, or of unknown type) injections in report
• Use CONDOR optimizations = True # Enable optimizations that assume execution on a CONDOR machine

Scheduled Injections

During this time period, 12 scheduled injections were found to have occurred

• CBC 1134345924.000 (coherentbbh10_1128678894_)
• CBC 1134348928.000 (coherentbbh11_1128678894_)
• CBC 1134353728.000 (coherentbbh15_1128678894_)
• CBC 1134354928.000 (coherentbbh16_1128678894_)
• CBC 1134356128.000 (coherentbbh17_1128678894_)
• CBC 1134357328.000 (coherentbbh18_1128678894_)
• CBC 1134359800.000 (coherentbbh11_1128678894_)
• CBC 1134361000.000 (coherentbbh12_1128678894_)
• CBC 1134362200.000 (coherentbbh13_1128678894_)
• CBC 1134363400.000 (coherentbbh14_1128678894_)
• CBC 1134364600.000 (coherentbbh19_1128678894_)
• BURST 1134581196.000 (WNB_burst_1134573920_1_)

Only 1 injection was found to not occur:

• BURST 1134577813.000 WNB_burst_1134573920_1_

Network and IFO Injections

Of the occurring scheduled injections, only two occurred as single-IFO injections:

• CBC 1134357333.938 (L1) (coherentbbh18_1128678894_)
• CBC 1134348934.048 (L1) (coherentbbh11_1128678894_)

All other scheduled injections occurred as H1-L1 coincident injections. The only UNSCHEDULED injections were 5 CALRESETs at L1 and 1 CALRESET at H1.

Discussion of Anomalies

The CALRESET injections have the same pattern of occurring with only certain paired combinations of the frame flags indicated by HWInjReport, as seen previously. However, all of the occurring scheduled injections have the anomaly of not occurring in the CAL-INJ channel and not having the TRANSIENT bit set to “off” to indicate the presence of a transient injection. They do occur, consistently, in the ODC-MASTER channel for HOFT, RAW, and RDS frames and the GDS-CALIB channel for HOFT frames.

Per Operator Shift Checksheet activity for Thursday Task, I topped off the Crystal Chiller by adding 175mL of water.

TITLE:  1/7 DAY Shift:  16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC     

STATE of H1:   OBSERVING (but taken out at 8am for calib)

Outgoing Operator:  Jim

Quick Summary:

As I walked in, H1 was in Observing, but Jeff was staging for his first Calibration measurements, which promptly started at 16:00UTC.  Also heard from Joe B. at LLO and how they are also starting as well.  

At the moment both interferometers are up and running for calibration work.  In the LVEA the useism continues to be high at about 0.75um/s; virtually no winds.

1/7 Owl Shift 08:00-16:00UTC

State of H1: Observing 80Mpc

Shift Summary: Quiet shift. Locked at 9:00UTC, not much else to report

Quiet shift so far. Locked about 9:00 UTC, been in Observe since. Wind is low, microseism is high, range is ~80MPC. POP bleed off seems to have been resolved after the work earlier today. 

00:00-08:00UTC, 16:00-23:59PT

State of H1: unlocked

Fellow: Sheila

Incoming Ops: JimW

Shift Summary: 

• H1 locked most of the shift
• Old ASC offsets alogged, new ones need to be traslated from trends, of maybe Jenne has a copy
• After ASC offloading was interupted by the lock loss, H1 needs an initial alignment to recover (JimW working on that)
• Low Noise used to find better ASC offsets

Lock Loss:

• One lock loss from a button push
• One lock loss from Earthquakes
• One lock loss from CSOFT mode ringing up
• One lock loss from ASC offloading

Offsets were set back to previous values.

Previous/current values are:

•  H1:ASC-X_TR_A_PIT_OFFSET  0
•  H1:ASC-X_TR_A_YAW_OFFSET -0.095
•  H1:ASC-X_TR_B_PIT_OFFSET -0.11
•  H1:ASC-X_TR_B_YAW_OFFSET -0.067
•  H1:ASC-Y_TR_A_PIT_OFFSET -0.128
•  H1:ASC-Y_TR_A_YAW_OFFSET -0.174
•  H1:ASC-Y_TR_B_PIT_OFFSET -0.516
•  H1:ASC-Y_TR_B_YAW_OFFSET -0.1

[Jenne, Kiwamu, Sheila, JeffK]

Today, the interferometer decided that it didn't want to go from ASC_PART2 to ASC_PART3 without some hand-tuning each lock.  However, after some investigation, it's still not entirely clear what the right thing to do is :(

The things we were playing with were the offsets in the CSOFT and DSOFT pitch filter banks (can only be tweaked *after* the loops are on, since there's an integrator always on in each of those filter banks) and the transmon qpds' ASC-[x,y]_TR_[a,b]_[pit,yaw]_OFFSETs.  These things are kind of the same, but you need to adjust the transmon offsets if you want to do some adjusting before the loops are closed, and you need to adjust the CSOFT and DSOFT offsets if you want to do some adjusting after the loops are closed.

We've had locks where we didn't survive if we didn't re-zero the qpd offsets before going to part3, and we've had locks where we didn't survive part3 if we didn't adjust the CSOFT and DSOFT offsets.  But, we've also had locks where the opposite was true.

Anyhow, at this point, I think our advice is to try going through the guardian like normal (no by-hand offsetting), and if that fails one or more times, call a commissioner (it's me for now, so please call).  For example, the last lock, I re-set the qpd offsets during asc part 2, but forgot to engage the CSOFT and DSOFT offsets, and we seemed to be just fine.  So, it's not totally clear yet what the final prescription should be.

GRB alert arrived at 01:37:28UTC, and it's currently 2:22UTC.

H1 was locked before the GRB arrived, and is still locked.

We are about 10 minutes from completing the stand-down time.

Title: 1/6 Shift 16:00-24:00 UTC (8:00-16:00 PST).  All times in UTC.

State of H1: Locking/Commissioning

Shift Summary: We have been struggling to acquire lock all day due to issues with ASC loops.  Commissioners are working on it and hopefully we are nearing success.  Microseism is trending up and is currently at 0.6 um/s.  Wind is calm.

Incoming operator: Cheryl

Activity log:

19:00 Kyle and Gerardo to Mid Y

19:54 Kyle and Gerardo back

23:34 Kyle to Mid Y

23:54 Kyle back

HWInjReport 1132272017 - 1133039434

Performed a run spanning the time period from 1132272017 (Nov 23 2015 00:00:00 UTC) to 1133039434 (Dec 01 2015 21:10:17 UTC)

Parameters

The following parameters were used for this run:

• GPS Start Time = 1132272017 # Beginning of time span, in GPS seconds, to search for injections
• GPS End Time = 1133039434 # Ending of time span, in GPS seconds, to search for injections
• Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
• Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
• IFO Coinc Time = 0.012 # Time window, in seconds, for coincidence between IFO injection events.
• Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
• Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
• Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
• Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
• Check CAL_RAW = True # Check CAL-INJ_ODC_CHANNEL_OUT_DQ channel in RAW frames.
• Report Normal = True # Include normal (IFO-coincident (network injections only), consistent, scheduled, and of known type) injections in report
• Report Anomalous = True # Include anomalous (non-IFO-coincident (network injections only), inconsistent, unscheduled, or of unknown type) injections in report
• Use CONDOR optimizations = True # Enable optimizations that assume execution on a CONDOR machine

Scheduled Injections

There were no injections scheduled to occur within this time period.

Network and IFO Injections

Only a single CAL-INJ reset in L1 was found to occur within this time period

• CALRESET 1132710277.000 (L1)

This was, of course, UNSCHEDULED.

Discussion of Anomalies

No anomalies of interest were found.

HWInjReport 1132084817 - 1132350679

Performed a run spanning the time period from 1132084817 (Nov 20 2015 20:00:00 UTC) to 1132350679 (Nov 23 2015 21:51:02 UTC)

Parameters

The following parameters were used for this run:

• GPS Start Time = 1132084817 # Beginning of time span, in GPS seconds, to search for injections
• GPS End Time = 1132350679 # Ending of time span, in GPS seconds, to search for injections
• Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
• Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
• IFO Coinc Time = 0.012 # Time window, in seconds, for coincidence between IFO injection events.
• Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
• Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
• Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
• Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
• Check CAL_RAW = True # Check CAL-INJ_ODC_CHANNEL_OUT_DQ channel in RAW frames.
• Report Normal = True # Include normal (IFO-coincident (network injections only), consistent, scheduled, and of known type) injections in report
• Report Anomalous = True # Include anomalous (non-IFO-coincident (network injections only), inconsistent, unscheduled, or of unknown type) injections in report
• Use CONDOR optimizations = True # Enable optimizations that assume execution on a CONDOR machine

Scheduled Injections

There were no injections found to be scheduled during this time period.

Network and IFO Injections

There were no injections found to occur during this time period.

Discussion of Anomalies

No anomalies found during this time period.

J. Kissel

In efforts to finally nail down the mysterious "zero" around 50 [Hz] in the UIM (see LHO aLOG 24296), I've measured the TOP, UIM, and PUM driver using three different measurement configurations. The hope is that, with this "matrix" of differences, we can find out what's going on with the UIM to see if its something specific to the driver, or specific to the OSEM chain upstream of the driver. From what I've seen watching the measurements go by on the SR785, both the TOP and PUM stage show similar zero-like behavior as the UIM, though the TOP mass has a pole-like behavior above the zero and eventually rolls off. Both the PUM and the UIM look as though they are rolling up to "infinity" by 10 [kHz], without even a phase shift indicating their might be a pole "soon" in frequency.  More detailed analysis and plots to come.

The data has been committed to the repo here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/Electronics/
EYPUMDriver/2016-01-05/TFSR785*.txt
EYTOPDriver/2016-01-05/TFSR785*.txt
EYUIMDriver/2016-01-05/TFSR785*.txt
where the key to each driver's measurement set is in the log files,
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/Electronics/
EYPUMDriver/2016-01-05/2016-01-05_EYTOP_Measurement_log.txt
EYTOPDriver/2016-01-05/2016-01-05_EYUIM_Measurement_log.txt
EYUIMDriver/2016-01-05/2016-01-05_EYPUM_Measurement_log.txt

I also attach a white board sketch that indicates each of the measurement configurations.
   (0) [Not shown] The "reference" measurement is identical to the reference setup shown in page 2 of the 2nd attachment in 18518, which is divided out of every transfer function to get rid of the response of the differential driver.
   (1) This is measuring the response of the coil driver as it is typically measured on the bench by CDS. It uses a differential to single-ended receiver and the 40 [ohm] internal load (as I only found out later, the documentation on this box, D1000931 leaves something to be desired), so the response differs from configuration (2) only by a scale factor of 2.
   (2) This is measuring the response of the coil driver as is typically done in the field when the OSEM and/or satellite amplifier is not available. The box (D1100278) is, as far as the coil chain is concerned, only a two 20 [ohm] (for a total of 40 [Ohm]) resistor load.
   (3) This is the "real life" scenario, where we measure the response of the driver with the full SatAmp and OSEM included as a load on the output of the driver. It is in this configuration is where the magic happens, apparently.

[Sheila, Jenne, Travis, JeffK, EvanH]

The transmitted powers through the IFO are dropping on a several-hour timescale, and we don't know why. It looks like this was also happening at the end of yesterday's 31 hour lock.  (POP_LF is shown for the last day or so in the attached plot.)  These are the only 2 locks in the last 10 days that have this trend - for all the others the powers stay nice and steady.

The power into the interferomter as measured by both IMC_Trans and IM4_Trans is steady, so it's not anything from the PSL or IMC. 

We have looked at all the alignment and length control signals that we can think of, as well as the witness channels on the bottoms of the optics, and we aren't seeing anything that jumps out at us as a cause of this power drop.

Intriguingly, the REFL power is dropping as well as the transmitted powers, so perhaps we're losing our mode matching throughout the lock?  Sheila found that the TCS CO2 power is different after Tuesday maintenence this week, although it's not changing throughout these locks.

Anyhow, we're not sure what is wrong, so we're not sure what we would tweak if we could, so we're leaving the IFO alone.  But, I suspect that once POP_LF gets down near 15,000 counts we'll lose this lock. 

HWInjReport 1129593617 - 1131828544

Performed a run spanning the time period from 1129593617 (Oct 23 2015 00:00:00 UTC) to 1131828544 (Nov 17 2015 20:48:47 UTC)

Parameters

The following parameters were used for this run:

• GPS Start Time = 1129593617 # Beginning of time span, in GPS seconds, to search for injections
• GPS End Time = 1131828544 # Ending of time span, in GPS seconds, to search for injections
• Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
• Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
• IFO Coinc Time = 0.012 # Time window, in seconds, for coincidence between IFO injection events.
• Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
• Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
• Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
• Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
• Check CAL_RAW = True # Check CAL-INJ_ODC_CHANNEL_OUT_DQ channel in RAW frames.
• Report Normal = True # Include normal (IFO-coincident (network injections only), consistent, scheduled, and of known type) injections in report
• Report Anomalous = True # Include anomalous (non-IFO-coincident (network injections only), inconsistent, unscheduled, or of unknown type) injections in report
• Use CONDOR optimizations = True # Enable optimizations that assume execution on a CONDOR machine

Scheduled Injections

Only two injections were found to be scheduled during this period:

• CBC 1131397639.000 (coherentbbh0_1126259455_)
• CBC 1131405159.000 (coherentbbh0_1126259455_)

However, neither of these injections were found to actually occur within the examined time period.

Network and IFO Injections

There were no normal injections that occurred within the examined period. There were a number CAL-INJ resets, all single-IFO with the same curious pattern to the frame flags as denoted in the immediately prior HWInj report (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=23485). There was a single-IFO burst injection in H1

BURST 1129673117.000 (H1)

with the only anomaly being that it is UNSCHEDULED. There was a single UNKNOWN injection in L1

UNKNOWN 1129673117.000 (L1)

This injection was confirmed to occur only within the CAL-INJ channel of RAW frames with the TRANSIENT bit indicating an injection but none of the specific injection-type bits, CBC, BURST, DETCHAR, or STOCHASTIC, indicating an injection. It was confirmed to not occur in ODC HOFT, ODC RDS, ODC RAW, or GDS HOFT frames.

Discussion of Anomalies

It is interesting that the single-IFO injections BURST 1129673117.000 (H1) and UNKNOWN 1129673117.000 (L1) are found to occur at the exact same time but within different IFOs. Even further, the fact the BURST injection in H1 is perfectly normal, other than being UNSCHEDULED, while the UNKNOWN injection in L1, in addition to being UNSCHEDULED, is inconsistent. HWInjReport currently does not check the HW bit or the CW bit in the CAL-INJ channel for RAW frames for the presence of injections; however, upon examining these bits directly, it was found that while the HW bit indicated an injection, along with the TRANSIENT bit, the CW bit did not indicate an injection (my first thought was that this may be a CW injection only occurring in L1). This means this was a truly UNKNOWN, UNSCHEDULED injection occurring only with L1. Given both injections occur at the exact same time and the L1 injection is a truly UNKNOWN type (practically a ghost injection, by the bits), it is likely this was intended to be a normal network injection; however either user-error or a catastrophic software error corrupted the proper setting of the bits.