Displaying reports 50201-50220 of 85244.Go to page Start 2507 2508 2509 2510 2511 2512 2513 2514 2515 End
Reports until 00:14, Saturday 06 May 2017
H1 General
jim.warner@LIGO.ORG - posted 00:14, Saturday 06 May 2017 (36060)
Shift Summary

TITLE: 05/06 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
LOG: 

23:30 Apollo on site to work on MSR cooling, I never saw when he left

23:30 Lockloss and MikeL in CR with a tour

6:50 ITMY TCS guardian takes us out of OBSERVE for 20minutes, no other obvious effect on the IFO
 

H1 TCS (GRD)
jim.warner@LIGO.ORG - posted 00:07, Saturday 06 May 2017 (36059)
TCS_ITMY_CO2 guardian just knocked us out of OBSERVE, again

A TCS guardian just knocked us out of observe again.It has knocked us out of OBSERVE for about ten minutes, while it fiddles with some PZT offsets. I also couldn't find the link to the SDF screen for the ITMY guardian to see what the differences are. It looks like the guardian is having a hard time staying locked.

2017-05-06T07:03:50.60179 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_PZT_SET_POINT_OFFSET => 45.5
2017-05-06T07:03:50.60248 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] = 3
2017-05-06T07:03:53.60372 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] done
2017-05-06T07:03:53.72259 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_PZT_SET_POINT_OFFSET => 49.0
2017-05-06T07:03:53.72295 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] = 3
2017-05-06T07:03:56.72339 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] done
2017-05-06T07:03:56.85062 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_PZT_SET_POINT_OFFSET => 52.5
2017-05-06T07:03:56.85110 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] = 3
2017-05-06T07:03:59.86033 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] done
2017-05-06T07:03:59.95678 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_PZT_SET_POINT_OFFSET => 56.0
2017-05-06T07:03:59.95728 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] = 3
2017-05-06T07:04:02.95752 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] done
2017-05-06T07:04:03.08470 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_PZT_SET_POINT_OFFSET => 59.5
2017-05-06T07:04:03.08496 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] = 3
2017-05-06T07:04:06.08646 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] done
2017-05-06T07:04:06.19308 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_PZT_SET_POINT_OFFSET => 63.0
2017-05-06T07:04:06.19765 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] = 3
2017-05-06T07:04:09.19820 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] done
2017-05-06T07:04:09.30854 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_PZT_SET_POINT_OFFSET => 66.5
2017-05-06T07:04:09.30885 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] = 3
2017-05-06T07:04:12.31090 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] done
2017-05-06T07:04:12.41767 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_PZT_SET_POINT_OFFSET => 70.0
2017-05-06T07:04:12.42090 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] = 3
2017-05-06T07:04:15.42433 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['wait'] done
2017-05-06T07:04:15.51860 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] 3.5, 7.0, 10.5, 14.0, 17.5, 21.0, 24.5, 28.0, 31.5, 35.0, 38.5, 42.0, 45.5, 49.0, 52.5, 56.0, 59.5, 63.0, 66.5, 70.0
2017-05-06T07:04:15.51863 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] 54.8988848698, 54.8350498672, 54.891019514, 55.1177868928, 55.3451070593, 55.5405800837, 55.7137985201, 55.8408840514, 55.6183281204, 55.3447073749, 55.1125390519, 55.0134612237, 55.0977940265, 55.192294462, 55.2613368151, 55.3127282154, 55.3339794561, 55.3309874091, 55.3280875704, 55.2947084872
2017-05-06T07:04:15.61037 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] slopecheckfail 0
2017-05-06T07:04:15.61039 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] slope [-0.01823857  0.01599133  0.06479068  0.06494862  0.05584944  0.04949098
2017-05-06T07:04:15.61040   0.03631015 -0.06358741 -0.07817736 -0.06633381 -0.02830795  0.02409509
2017-05-06T07:04:15.61041   0.02700012  0.01972639  0.01468326  0.00607178 -0.00085487 -0.00082853
2017-05-06T07:04:15.61041  -0.00953688]
2017-05-06T07:04:15.61042 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] gain setting for servo is -54.8288534565
2017-05-06T07:04:15.61042 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] 0
2017-05-06T07:04:15.61043 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] 3.5
2017-05-06T07:04:15.61043 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] 54.8988848698
2017-05-06T07:04:15.61044 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] current chiller setpoint 20.9
2017-05-06T07:04:15.62412 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_CHILLER_SET_POINT_OFFSET => 21.0
2017-05-06T07:04:15.62907 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] ezca: H1:TCS-ITMY_CO2_CHILLER_TSTEP => 1178089473.0
2017-05-06T07:04:15.62921 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] new chiller setpoint 21.0
2017-05-06T07:04:15.63284 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] timer['chillerstep'] = 240
2017-05-06T07:04:15.63295 TCS_ITMY_CO2 [FIND_LOCK_POINT.run] no setpoint found:stepping chiller temp

H1 CDS
david.barker@LIGO.ORG - posted 16:57, Friday 05 May 2017 - last comment - 08:08, Saturday 06 May 2017(36057)
scipy version 0.19 is now the default
Comments related to this report
thomas.shaffer@LIGO.ORG - 08:08, Saturday 06 May 2017 (36061)

This seems to be what has been causing some troubles with time machine and a2l. This version of scipy does not have the "special" attribute that these scripts use.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 16:55, Friday 05 May 2017 (36056)
CDS O2 restart report: Tuesday 2nd - Thursday 4th May

model restarts logged for Thu 04/May/2017

Many restarts due to site power glitches from lightening storm and recovery thereof. Full report attached as text file.

model restarts logged for Wed 03/May/2017 No restarts reported

model restarts logged for Tue 02/May/2017
2017_05_02 11:50 h1dc0
2017_05_02 11:55 h1broadcast0
2017_05_02 11:55 h1dc0
2017_05_02 11:55 h1fw0
2017_05_02 11:55 h1fw1
2017_05_02 11:55 h1fw2
2017_05_02 11:55 h1nds0
2017_05_02 11:55 h1nds1
2017_05_02 11:55 h1tw1
2017_05_02 11:57 h1broadcast0
2017_05_02 11:57 h1dc0
2017_05_02 11:57 h1fw0
2017_05_02 11:57 h1fw1
2017_05_02 11:57 h1fw2
2017_05_02 11:57 h1nds0
2017_05_02 11:57 h1nds1
2017_05_02 11:57 h1tw1

Maintenance day. Reboot of h1dc0 for day208bug, added fire pump chans to DAQ. Required several restarts (duplicate fmcs chans).

Non-image files attached to this report
H1 General
travis.sadecki@LIGO.ORG - posted 16:03, Friday 05 May 2017 - last comment - 18:06, Friday 05 May 2017(36055)
Ops Day Shift Summary

TITLE: 05/05 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:  Locked for the entire shift and for ~13 hours total so far.  No issues to report.
LOG: 

Hugh requests that the HAM2 and 3 GS13 gains be set to correct values at the next Out of Observe opportunity.  Contact Hugh for more info.

Jason requests that the ISS diffracted power be lowered to ~3% at the next Out of Observe opportunity.

Both of these items are on the Operator white board.

 

Comments related to this report
jim.warner@LIGO.ORG - 18:06, Friday 05 May 2017 (36058)PSL, SEI

We had a mystery lockloss just as LLO came back up, so I took the opportunity to address both the ISS diffracted power and the HAM2&3 gains (again). This time, to fix the gains, Dave reminded me the h1fescript0 is still running ubuntu, so I ssh'ed onto that machine and went to userapps/isi/common/scripts and did a ./sensor_hilo HAM2 GS13 hi and a ./sensor_hilo HAM3 GS13 hi. Much easier than last time. The ISS adjustment was straightforward, but we were already at 4%, before I tweaked the voltage down.

H1 General
travis.sadecki@LIGO.ORG - posted 12:57, Friday 05 May 2017 (36052)
Ops Day Mid-shift Summary

Locked for 9.5 hours.  LLO is still down due to weather which seems to be both site's biggest issue lately.

LHO VE
logbook/robot/script0.cds.ligo-wa.caltech.edu@LIGO.ORG - posted 12:10, Friday 05 May 2017 - last comment - 14:06, Friday 05 May 2017(36050)
CP3, CP4 Autofill 2017_05_05
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 2896 seconds. TC B did not register fill. LLCV set back to 18.0% open.
Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill not completed after 3600 seconds. LLCV set back to 42.0% open.
Images attached to this report
Comments related to this report
chandra.romel@LIGO.ORG - 14:06, Friday 05 May 2017 (36053)

20:52 UTC

Raised CP3 to 20% open.

Manually filled CP4 - took 13 min. to overfill (set to 70% for 11 min. and then to 100% for 2 min). Left at 44% open.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 11:24, Friday 05 May 2017 - last comment - 12:44, Friday 05 May 2017(36047)
Details of last night's storm related CDS restarts

MSR UPS reports going onto battery power three times during the storm:

5/4 20:44:09 On Batt
5/4 20:44:10 On Line
5/4 20:45:41 On Batt
5/4 20:45:42 On Line
5/4 21:49:46 On Batt
5/4 21:49:47 On Line

Both BRS machines at the end stations did not reboot or require code restarts.

The corner station Beckhoff computer (h1ecatc1) did not reboot (on ups power), the units at the end stations did reboot around 20:48. h1ecatx1 required a manual reboot at 22:25 to complete its code startup.

None of the three HEPI pump controller computers rebooted or needed code restarts.

MY weather station stopped operating 21:34 PDT, was restarted this morning.

All Front End Computers rebooted around 20:46, some multiple times. Report generated from h1fs0's NFS mount requests for /opt/rtcds:

20:45:11    h1pemmy
20:45:12    h1pemmx
20:45:15    h1sush2b
20:45:18    h1lsc0
20:45:20    h1oaf0
20:45:22    h1seib3
20:46:42    h1pemmy
20:46:44    h1seiey
20:46:44    h1seiex
20:46:45    h1susauxey
20:46:46    h1pemmx
20:46:46    h1iscex
20:46:46    h1sush2b
20:46:47    h1iscey
20:46:48    h1seib1
20:46:49    h1susauxex
20:46:49    h1seih23
20:46:50    h1susauxh56
20:46:50    h1lsc0
20:46:51    h1susb123
20:46:51    h1susauxh2
20:46:52    h1susauxh34
20:46:52    h1asc0
20:46:52    h1susauxb123
20:46:52    h1oaf0
20:46:53    h1seib3
20:46:53    h1seih16
20:46:53    h1seib2
20:46:54    h1psl0
20:46:54    h1sush56
20:46:55    h1seih45
20:46:57    h1sush34
20:46:57    h1sush2a
20:47:07    h1susex
20:47:09    h1susey
 

Comments related to this report
david.barker@LIGO.ORG - 11:33, Friday 05 May 2017 (36048)

Because h1psl0 and h1oaf0 were rebooted last night, we don't need to reboot these next week during the vent to clear their '208 days running' issue.

david.barker@LIGO.ORG - 11:34, Friday 05 May 2017 (36049)

No systems on UPS power saw any issues last night, this includes NFS file servers, networking, DAQ, GDS.

david.barker@LIGO.ORG - 12:44, Friday 05 May 2017 (36051)

from cdsfs0's NFS mount request logs, the following computers rebooted:

20:46:58    h1digivideo2.cds.ligo-wa.caltech.edu.
20:47:02    h1auxscript0.cds.ligo-wa.caltech.edu.
20:47:13    h1digivideo0.cds.ligo-wa.caltech.edu.
20:47:14    h1digivideo1.cds.ligo-wa.caltech.edu.
21:50:59    h1auxscript0.cds.ligo-wa.caltech.edu.
21:51:05    h1digivideo2.cds.ligo-wa.caltech.edu.
21:51:19    h1digivideo0.cds.ligo-wa.caltech.edu.
21:51:23    h1digivideo1.cds.ligo-wa.caltech.edu.

This agrees with these machines not on ups power. Looks like no control room workstations/FOM machines rebooted.

 

H1 CDS (CDS, PEM)
patrick.thomas@LIGO.ORG - posted 11:08, Friday 05 May 2017 (36046)
restarted IOC for mid Y weather station
18:01 - 18:04 UTC Restarted IOC on h0epics and burtrestored to 6:10 AM local time.
H1 General
travis.sadecki@LIGO.ORG - posted 08:04, Friday 05 May 2017 (36044)
Ops Day Shift Transition

TITLE: 05/5 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing
OUTGOING OPERATOR: Cheryl
QUICK SUMMARY:  No issues were handed off.  Lock is 4.5 hours old.

H1 General
cheryl.vorvick@LIGO.ORG - posted 08:02, Friday 05 May 2017 (36043)
Ops Owl Summary:
LHO FMCS
john.worden@LIGO.ORG - posted 06:05, Friday 05 May 2017 - last comment - 14:21, Friday 05 May 2017(36041)
FMCS no connection to LSB

It looks like the storm brought down part of the new FMCS - possibly communications to the LSB? All other buildings appear to be working fine with both the old and new systems.

Comments related to this report
richard.mccarthy@LIGO.ORG - 14:21, Friday 05 May 2017 (36054)
The fiber to network converter must have hit a power level threshold and lost the ability to communicate.  This has been replaced and we are back on line.
H1 General (IOO)
cheryl.vorvick@LIGO.ORG - posted 04:54, Friday 05 May 2017 - last comment - 11:08, Friday 05 May 2017(36039)
Opw Owl Transition:
Comments related to this report
cheryl.vorvick@LIGO.ORG - 05:01, Friday 05 May 2017 (36040)

SDF files:

Images attached to this comment
jim.warner@LIGO.ORG - 11:08, Friday 05 May 2017 (36045)

The SDF diffs indicate that, again, HAMs 2&3 are in the wrong state.

Displaying reports 50201-50220 of 85244.Go to page Start 2507 2508 2509 2510 2511 2512 2513 2514 2515 End