WP 7043
FRS 8250
aLOG 36568

Replaced analog input Beckhoff terminal on EtherCAT Slow Controls Chassis 6, S1400077. Terminal replaced was an EL3104, middle terminal, slot 10. This was to address a drift seen in the readback signals.

The primary and redundant h(t) pipelines were restarted at GPS second 1182010698. This pipeline restart is not accompanied by any filter changes, but does pick up gstlal-calibration-1.1.7. For more information on this version of the code, please see its redmine page.

For more information about the filters currently being run, please see the following aLOG entries:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=36864
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=36842

I performed the weekly PSL FAMIS tasks this morning.

HPO Pump Diode Current Adjust

All pump diode currents were increased by 0.1A, new and old currents summarized in the table below.  The first attachment shows a 15 day minute-trend of how the DBs have decayed since the last current adjustment, while the 2nd is a screenshot of the main PSL Beckhoff screen for future reference.

I looked at and optimized the DB operating temps as well.  I changed the temps on all the diodes in DB1 from 28.0 °C to 29.0 °C; the operating temps of the other 3 DBs remained unchanged.  The HPO is now outputting ~157.7 W.  This completes FAMIS task 8427.

PSL Power Watchdog Reset

I reset both PSL power watchdogs at 15:35 UTC (8:35 PDT).  This completes FAMIS task 3655.

TITLE: 06/20 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Cheryl (Patrick covering at beginning of shift)
SHIFT SUMMARY:

A bit of a rough shift with 0.44Hz oscillation seen with ASC PIT signals and on oplevs (primarily ITMy).  

So had a few hours of CORRECTIVE MAINTENANCE (No FRS has been filed.)
LOG:

• 8:24-9:07:  H1 taken OUT of OBSERVING due to ASC instability.  Marking as CORRECTIVE MAINTENANCE.
• 9:07 Locked at NLN & Back to OBSERVING.  NO SDF Diffs to deal with.
• 9:20 Back to CORRECTIVE MAINTENANCE due to ASC Pit oscillation.
• 12:50 Back to OBSERVE
• 14:00 0.44 Hz noise returns & lose lock at 14:10
• 14:54:  ~~ MAINTENANCE Begins ~~
• 14:54 Transitioned SEI CONFIG to VERY_WINDY_NOBRSXY
• 14:55 Christina to EX for cleaning

Decided to slowly take H1 up to Nominal Low Noise, while watching the ITMy oplev & ASC (watched 0.05 Hz "live" spectra, oplev blrms channels on dataviewer, & the ASC Control signals).  

Miraculously, H1 eventually made it to Nominal Low Noise & the culprits of the evening did not appear.  So H1 was cautiously taken to OBSERVING at 12:50 utc.  

Unfortunately, at 14:00 the 0.44Hz noise returned (ITMy oplev spectra looked bad, ITMy oplev blrms increased, and the ASC control signals all showed the 0.44Hz feature).  Took H1 out of OBSERVING, marked it as CORRECTIVE MAINTENANCE & tried to make adjustments to ASC CSOFT gain (went from 0.6 to 0.8 w/ a 30sec TRAMP), but H1 eventually dropped out of lock.

Attached is the ITMy Oplev Summary Page (unfortunately it doesn't show after 14:00utc yet).

As Jeff alluded to in his summary, Sheila posted an alog about Oplev damping back in April, but I stopped looking at oplevs since the offcenter ITMX & ETMX had been that way for over a week (i.e. they were not a new feature).

After looking into ASC Land, I returned to the oplevs after going through Sheila's alog and then also looking at Krishna's alog.  Summary of Oplev operations over the last couple of months:

• Stopped using Oplevs to Damp Pitch for ETMx, ITMx, & ITMy on 4/7/17.  (ETMy was already not being used & we haven't been damping Yaw for a while.)
• BS is damped briefly while locking, but then zeroed out before getting to Nominal Low Noise.

So with Oplevs not actively not controlling optics, I didn't focus on them.  However, we still use them for monitoring position of the optics.  And with that, I returned to checking them out after reading Krishna's alog about ITMy.  I took spectra of all (4) test masses (ref from last night's lock & from when we had trouble with H1 tonight).  Of all the test masses, ITMy appears to be much more noisy, and it all begins down at 0.44Hz (this is the same oscillation seen in the ASC signals previously alogged tonight).

Following Krishna's diagnosis, I looked at the BLRMS signals for the oplevs in the H1 Summary Pages & one can clearly see ITMy starting to clearly look unhealthy compared to other optics toward the end of Jeff's shift starting between 4:00 -5:00 utc (look at bands between 0.3 to 10Hz).  The behavior isn't like what Krishna saw (back then ITMy reached values of 1.0+ urad for short times & in this case ITMy is just under 0.1urad, but stays there for longer stretches). 

Since we don't use oplevs for damping, could the issue be noise  from the light of the ITMy oplev being seen by H1?  Or is there an ASC effect which is also being observed with the ITMy oplev?

H1 locked back up to 70Mpc, but within 5min ASC Pit signals started to ring up at 0.44Hz.  This time H1 couldn't hobble with the ASC noise & quickly dropped out of lock on its own.

Marking as CORRECTIVE MAINTENANCE again until this can be resolved.

H1's issue can clearly be seen in:

• ASC CONTROL's:  H1:ASC-CSOFT_P_OUTPUT
• ASC ERROR's:  H1:ASC-MICH_P_INMON
• On most of the LSC signals on the PRMIsb striptools as well
• DARM Spectra from 10-100Hz.

snapshot of ASC striptools are attached.

TITLE: 06/20 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

ASC Pit Control & Error signals are huge & this is resulting in broadband noise on DARM from 10-100Hz & obviously resulting in a low range.  I will start investigating further while we are still locked.  The ITMx & ETMx oplevs have been at/beyond their limits in pit & yaw, but they've been like that for atleast a week.

Shift Summary: After the IFO relocked, ran A2L check script. Pitch is a bit rung up, since we are in commissioning mode decided to run the repair script to make things better.  

LLO called about a GRB alert. LHO did not receive notice from Verbal Alarms. In one hour hold.

Around 06:00 (23:00) the ASC Pitch Control and Error signals started to ring up. Could find no apparent reason. Sheila’s aLOG #35371 talks about this and OpLev damping. ITMX and ETMX OpLevs are off center. However, OpLev damping appears to be off on ITMY and ETMY. Range is suffering.

   LLO called about GRB Alert. In one hour stand-down for the alert. 

   LHO did not receive notice via Verbal Alarms. 

  Back to Observing for about 3 hours. Environmental and seismic conditions are good. Range has been   in the upper 60Mpcs. All monitors are green and clear. 

Today I spent some more time moving POP spot positions as well as soft again.  In the end we have gone back to where we were over the weekend. 

• The first attachment shows that there are some alignments for which we can have lower jitter than the alignment we had over the weekend.  The degradation in sensitivity you see at low frequency is because the A2L was not tuned, and probably also because the SRCL FF might need to be returned for these new alignments. We can move the IFO to the locations where the jitter is better (P= 0.15, Y=0.2 for example) and use the soft offsets to make the recycling gain better (CSOFT +DSOFT Y offsets =0.07 brought the recycling gain back to 28 from about 24).  Returning to these alignments where the jitter coupling had been seen to be better didn't result in a lower noise than over the weekend though- for some reason going back to the same spot on the POP QPD doesn't mean we get the same spectrum.  
• The second attachment shows scatter plots of reycling gains and BLRMS in 3 bands made in the same way as the attachments to alog 36957, but with todays spot move added as well as a BLRMS around our largest jitter peak at 350Hz. You can see again from this plot that things aren't always the same when we return to the same POP A spot locatin, although all this data is taken with our usual soft offsets.  
• We lost lock a couple of times due to what I think is the SRCL FF.  We had an oscillation in SRCL (and the FF path) around 3 to 4 Hz, which does not show up in MICH. 
• It might be possible to move the soft offsets to get better recycling gain at the location where our jitter was good, and redo this scan of POP offsets to see if we can have a better compromise position.  It might not be a good use of time though, especially if we can't rely on the ASC to bring us back to the same spectrum in the future.  
• Things that probably are worth putting some time into:
  • better roll off for DHARD, this noise is worse than CHARD now that we put more agresive filters in CHARD
  • LSC noise- decoupling PRCL from SRCL in the input matrix, turning back on the MICH actuator digitalization, and SRCL FF retuning

At John W.'s request, I took another measurement now that several days have passed since pumping was stopped 

Pumping stopped last week at 14 microns -> Today's "post-pumping" reading was 29 microns (warm day, 92F).

TITLE: 06/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:  locked and then commissioning
LOG:

• 16:15-16:55UTC - Karen in optics lab
• 17:35UTC - commissioning, beam walk, Sheila
• 22:45UTC - end of active active commissioning
• 23:00UTC - end of shift - relocking
• after relocked and in NLN:  EvanG, 15 minutes for hardware injection, WP7046

In the past week we have had two timing alarms:

The first was a short (one minute) alarm from EY GPS (CNS-II). I trended all the EPICS channels on this system and only found that the Dilution of Precision (DOP) and the Receiver mode channels showed any variation at this time (number of satellites locked did not change). Does this mean it is a real or bogus error?

The second was a longer alarm (9 minutes) with the MSR master's GPS receiver (I think the internal one). The only channels in alarm were  "GPS locked", the the MSR comparator channel-01 (MFO GPS). This would suggest a real problem with the Master's GPS receiver?

Time to pass this over to the timing group for further investigation (Daniel, Zsuzsanna, Stefan?)