Greg, TJ, Dave

In order to prevent a repeat of the error encountered last Sunday morning at 03:07 PDT where a DAQ glitch on h1susey caused an invalid flag to be latched on the latest Calibration HofT code, we have put into place a temporary system to cover us until this bug is fixed in the calibration code. Trending these CRC errors shows a very low occurence (about 8 for O2 so far), however we have put this system into place on the off chance of another event in the next week.

The system has several moving parts:

Verbal Alarms

TJ has extended the verbal alarms system to monitor the CRC error counter for h1iopsusey. If this value goes above zero, the alarm will be announced just once. After the counter goes back to zero the alarm is primed ready for the next event.

Operator Instructions

I've written full instructions in the CDS wiki OperatorInstructions

Greg is the main point of contact for the operator

Restarting the DMT calibration code

For the short term, we are asking the operator to possibly restart the calibration hoft code by having open login sessions on the machines' consoles in the MSR. The instructions give details on how these are to be used.

Once the calibration code is fixed (hopefully next Tuesday 4/25) this system will be dismantled.

TITLE: 04/19 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 62Mpc
OUTGOING OPERATOR: Nutsinee
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.21 μm/s 
QUICK SUMMARY:

Recently back to observing after scheduled commissioning. No known issues.

TITLE: 04/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC

STATE of H1: Observing at 56Mpc

INCOMING OPERATOR: Patrick

SHIFT SUMMARY: Commissioning since morning. Recently back to Observe. No issue to report.

LOG:

15:55 Christina opening receiving roll up door

16:00 Commissioning started. Sheila started OMC dither. Chandra to LVEA

16:08 Chandra out

16:24 Robert to LVEA

18:14 Robert done/Jenne started

18:30 Hand off to Jeff/Lockloss

19:00 Back to NLN/ran a2l/ back to commissioning/ Robert to LVEA

19:13 Karen driving to VPW

19:30 Robert done. Sheila took over

19:40 Karen back

20:06 Jeff took over

20:14 Lockloss/ Jeff done

20:53 Back to NLN/ Robert to LVEA

21:33 Robert to LVEA again (when did you come back??)

22:03 Lockloss (Robert claimed it wasn't him)/ LLO called -- they're ready to come back up.

22:16 Robert out

22:48 Back to Observe

23:59 Out of Observing to let Robert go turn off a computer in the LVEA

23:03 Back to Observe

We will have another commissioning window on Thursday coincident with LLO.

The main task will be either laser vibrometer measurement of the baffles (again) or air flow test in the PSL room.

There are lower prioritiy tasks that I don't list here.

Betsy, Gerardo

Today, I assisted Gerardo in his supurb silicate bonding of ear #182 to the S4 flat of spare ITM test mass ITM06. No bubbles and placement on flat within spec with alot of headroom.  The second ear is scheduled for bonding next week.

J. Kissel

I attempted to repeat Evan Hall's study (LHO aLOG 27675) in which he was able to manipulate the detuning of the DARM response with a SRCL offset, but was unsuccessful.
   (1) I was able only to inject an offset of +/-100 [ct] in H1:LSC-SRCL1_OFFSET and have the IFO stable (I tried offsets of +/-200 like Evan had done, and then +/-150, but both cause a lock-loss)
   (2) With a +/-100 [ct] SRCL offset, the new SRC detuning parameter tracking did not show any signs of spring frequency change.

Offset ramping times were 120 [sec]. When at +/-150 [ct], there was visible excess noise in SRCL, which then propagated through standard coupling to DARM (see attachement for comparison between no offset and -150 ct gathered just before lock loss).

I did not have time to take sweeps as Evan did.

Recall that at Evan's study was done at with an O1, 10 W IFO. Perhaps the calibration of the offset (he suggests 0.1 [ct/pm]) changes with input power; he doesn't give enough detail about his SRCL budget to re-derive the calibration. Will look into the theory more before attempting this again. It's discouraging that, although the SRC detuning frequency calculation from 7.93 Hz PCALY line appears roughly correct compared to recent sensing function sweeps, the calculation appears to be insensitive to this known thing that manipulates it. 

#backtothedrawingboard

R. Savage, S. Karki, T. Shaffer, J. Kissel

At the request of Rick and Sudarshan, I modified the HIGH_FREQ_LINES guardian to start a new long-duration PCAL X excitation sweep to investigate an apparent systematic error they've found at the 5 kHz data point of the previous sweep (see attachment for current status of model vs. measurement, originally from here; the data from previous iterations of the guardian node code in LHO aLOGs 35532 and 35153). 

The new bounds of the sweep are from 4825 Hz, in 75 Hz increments up to 6 kHz, and the sweep direction is *up* instead of down. 

I've committed the changes to the code to userapps repo here,
/opt/rtcds/userapps/release/cal/h1/guardian/HIGH_FREQ_LINES.py

reloaded the guardian code, changed to the start frequency by hand, and ran the INIT to reset the 24 hr timer.

The next observation stretch (after Apr 19 2017 20:25 UTC) should start the sweep and have the frequency set to 4825 Hz.

Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 1230 seconds. TC B did not register fill. LLCV set back to 21.0% open.
Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 2061 seconds. LLCV set back to 39.0% open.

model restarts logged for Tue 18/Apr/2017
2017_04_18 10:17 h1calcs
2017_04_18 10:23 h1broadcast0
2017_04_18 10:23 h1dc0
2017_04_18 10:23 h1fw0
2017_04_18 10:23 h1fw1
2017_04_18 10:23 h1fw2
2017_04_18 10:23 h1nds0
2017_04_18 10:23 h1nds1
2017_04_18 10:23 h1tw1

Maintenance day. h1calcs model change, new H1EDCU_RACCESS.ini, DAQ restart to support these.

model restarts logged for Mon 17/Apr/2017 - Wed 12/Apr/2017 No restarts reported

WP6572 h1calcs model change

Jeff K, Dave:

new code was installed for h1calcs.

h1hwsex Recovery

Nutsinee, Dave:

The HWS code was recovered on h1hwsex after the frame grabber card was returned last week.

DMT Calibration code reversion

Greg:

The new calibration code (which was installed on 4/11) was reverted back to the old version, but this failed due to channel list changes. The new code was left in place.

Remote access channel lists updated

Jonathan, Dave:

The RACCESS channels lists in both the autoBurt.req and H1EDCU_RACCESS.ini files were updated.

DAQ restart

Dave:

DAQ was restarted to cover h1calcs and H1EDCU_RACCESS config changes

HWS code was writing HWSY data overnight. Stopped at 16:18:15 UTC

Swapped camera fiber cable 16:19 UTC

Code restarted 16:20 UTC, now writing HWSX data.

See alog35628 for details

16:00-16:07 UTC

entered LVEA to de-energize three turbo stations (levitated bearing in turbo dropped)

TITLE: 04/19 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY:

Other than a lockloss, mostly uneventful night mostly in OBSERVING.
LOG:

• 7:39-8:21 Lockloss
• 13:27-14:27 GRB Stand Down Time (confirmed notification with Jeremy at LLO)

In order to see if a couple of optics for HWSY could be identified, the illuminator cover on the
A1F4 viewport of HAM4 was removed.

Conclusion The optic in the HWSY DCBS1 lens mount is most likely to be a dichroic beamsplitter
rather than a lens.

  The orientation of the HWSY VacLens mount is such that the retaining ring is facing the HWS table.
Clearly seen are the two holes of the retaining ring as Betsy illuminated the chamber from A1F4.  The
holes are not clearly visible when one looks from the A1F4 flange side, which is consistent with them
being partly blocked by the lens mount.

  The 2" Siskiyou lens mount is 0.50" thick but has a 0.41" deep recess to accommodate an optic.  The
retaining ring for the mount is 0.13" thick.  If the optic in the mount is the dichroic beamsplitter
(D1200214) which is 0.375" thick.  Since the stack up
of the retaining ring and a 3/8" thick optic is thicker than the mount, the mount is a custom
modification to the standard part.  More importantly since the retaining ring appears to be almost
flush with the surface of the lens mount, the optic held is more likely to be the dichroic beamsplitter
rather than a lens.  The data sheet for a PLCX-50.8-360.6 lens says it is 6.4 mm thick - a concave lens
would be similar.  If the optic in the mount were a lens, the retaining ring would sit deeper in the mount.









Betsy / Peter

If I recall correctly this image (attached) is normally dark in NLN?

Evan G., Robert S.

Looking back at Keith R.'s aLOGs documenting a changes happening on March 14 (see 35146, 35274, and 35328), we found that one cause seems to be the shuttering of the OpLev lasers on March 14. Right around this time, 17:00 UTC on March 14 at EY and 16:07 UTC at EX, there is an increase in line activity.

The correlated cause is Travis' visit to the end station to take images of the Pcal spot positions. The images are taken using the Pcal camera system and needs the OpLevs to be shuttered so that a clean image can be taken without the light contamination. We spoke with Travis and he explained that he disconnected the USB interface between the DSLR and the ethernet adapter, and used a laptop to directly take images. Around this time, the lines seem to get worse in the magnetometer channels (see, for example, the plots attached to Keith's aLOG 35328).

After establishing this connection, we went to the end stations to turn off the ethernet adapters for the Pcal cameras (the cameras are blocked anyway, so this active connection is not needed). I made some magnetometer spectra before and after this change (see attached). This shows that a number of lines in the magnetometers are reduced or are now down in the noise.

Hopefully this will mitigate some of the recent reports of combs in h(t). 

We also performed a short test turning off another ethernet adapter for the H1 illuminator and PD. This was turned off at 20:05:16 18/04/2014 UTC and turned back on at 20:09:56 UTC. I'll post another aLOG with this investigation as well.