Displaying report 1-1 of 1.
Reports until 08:08, Friday 08 May 2015
H1 General (DetChar)
nairwita.mazumder@LIGO.ORG - posted 08:08, Friday 08 May 2015 - last comment - 13:08, Friday 08 May 2015(18322)
DQ shift summary for 2nd May (LHO Mini run)
Sift wiki page

Lock times: (ODC-MASTER_OBS_INTENT & DMT-DC_READOUT_LOCKED)

1114582937 1114624965 (42028s)
1114629970 1114639925 (9955s)
1114643198 1114646416 (3218s)

There were three locks on 2nd May for ~10.5hrs , ~2 hrs and 3hrs (continued to 3rd May) respectively.

The first lock loss happen after turning on 504.8 Hz Violin mode damping loop (alog). Not sure about the second one (Nutsinee was guessing that the initial alignment was not done for the full day so may be the optics started drifting), but the third lock was lost because PSL tripped (alog).

The first lock had stable inspiral range of ~8MPC while the second had slightly better range ~10MPC.

Three dips in the inspiral range of the first lock were caused by three loud glitches. (Glitch follow up).

OAF and GDS h(t) calibration still differ between 20Hz and 110Hz (and a bit above 2kHz).

There were few interesting glitch bands: 10 to 40Hz starting from 12:30UTC. , 80-300Hz through out the locks. Most of the loud glitches were seen around this frequency band.

Both UPV and Hveto have found H1:ASC-AS_A_RF45_Q_PIT_OUT_DQ to be the most effective veto channel.

10-40Hz glitches might be related to angular sensing and control channels and output mode cleaner angular channels.  STAMP-PEM has shown that OMC-ASC_QPD_B_PIT_OUT, OMC-ASC_ANG_Y_OUT, ASC-AS_{A,B}_RF45_Q_PIT_OUT channels have high coherence with DARM in 10-40Hz frequency band which started after 12p.m. Might be the cause of excess low frequency glitches starting from 12:30p.m.

Daily CBC result has an interesting vertical band of glitches around 12 to 12:30UTC. It looks like a messy PSD estimation, but the timing is not  convincing that it's involved with the noise floor jump  which seems to be closer to 12:50 UTC.
Comments related to this report
jeffrey.kissel@LIGO.ORG - 08:42, Friday 08 May 2015 (18323)CAL, DetChar, ISC
J. Kissel, for the Calibration Team

We'd discussed the CAL-CS vs. GDS discrepancy on the CAL team call yesterday. We believe the discrepancy arises because the GDS pipeline had not accounted for the (currently) four 16 [kHz] clock cycle delay between the actuation path and the (inverse) sensing path. The delay causes the amplitude discrepancy in the sum of the two paths around the DARM unity gain frequency at ~40-50 [Hz].
nutsinee.kijbunchoo@LIGO.ORG - 13:08, Friday 08 May 2015 (18328)

The second lock of May 2nd happened around 3pm PDT. Jim was on duty so my speculation about why the interferometer lost lock at that time was irrelevent. Sorry I thought the second lock loss happened while I was on shift and optics drift came to mind, which was not even true (it was the PSL tripped). There were no reason stated about this lock loss https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=18183

 

Forgive my scrumbled memory....

Displaying report 1-1 of 1.