Displaying reports 52881-52900 of 86398.Go to page Start 2641 2642 2643 2644 2645 2646 2647 2648 2649 End
Reports until 05:42, Wednesday 01 March 2017
H1 SEI
jeffrey.bartlett@LIGO.ORG - posted 05:42, Wednesday 01 March 2017 - last comment - 16:44, Wednesday 01 March 2017(34484)
HAM2 SDF Diss 
   After relocking there was a SDF difference with the HPI-HAM2_IPS_HP_SETPOINT_NOW. Accepted the difference and went into Observing.
Images attached to this report
Comments related to this report
hugh.radkins@LIGO.ORG - 09:00, Wednesday 01 March 2017 (34487)
Link

Thanks for the log Jeff.  This reminds (smacks in the face) me now that I've removed the HEPI Pringles from the Restore Target DOF list, these will all have to be put into the Not Monitored list.  These are the DC positions that the Isolation loops drive to.  When the loops first start, we load the current free hanging position into the "SETPOINT_NOW" channel so the loop starts with no DC load.  After the loop is on and is stable, we load the "Target Position" to move too.  All HEPI loops were driving to Targets but the Pringle loops are AC coupled so loading a DC Target position just was wasted effort that got the loop nowhere in the end.  So this Setpoint Now channel will be different every time there is a platform trip and re-isolation. 

What I don't understand is why there isn't a VP difference too and why this HP difference is so small.

For the ISIs, all HAMs load all DOF Targets, for the BSCs, none of the Targets are loaded; hence, the Not Monitored Lists.

I probably could do this while Observing but I'm reluctant in case the fussing around sets an SDF flag; I'll get it during commissioning later.

Addendum: Checked the SVN, someone must have saved the OBSERVE.snap earlier in the day, to clear the diffs after the HAM2 HPI trip during maintenance; I remember Jim mentioning the trip in the morning.  Then the old e-11 diff popped up; not sure why that happens.  Regardless, I'll get these into the Not Monitored list and it will be a thing of the past.

thomas.shaffer@LIGO.ORG - 16:44, Wednesday 01 March 2017 (34508)
Link

I didn't put the updated script in ISC_LOCK that will switch the SDF reference files since I was worried that I would leave and then something would go wrong. This should hopefully fix this SDF diff in the future. I've tested it a few different ways and it all seems good, but I will do it this shift if I get the opportunity.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 04:29, Wednesday 01 March 2017 (34483)
Ops Owl Mid-Shift Summary 
   Locked and Observing until 11:50 (03:50). Wind and microseism have been building all shift. Base winds in the mid 20s with gusts up into the mid-30s. Lock broke about the time of gusts at the CS into the Mid-40s. 

   Winds over the past 20 minutes appear to be laying down. Will do IA if cannot relock.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 00:30, Wednesday 01 March 2017 (34482)
Ops Owl Shift Transition
Ops Shift Transition: 03/01/2017, Owl Shift 00:08 – 16:00 (00:00 - 08:00) - UTC (PT)
State of H1: IFO locked at NLN, at 30.8W and 64.7 Mpc  
Intent Bit: Observing
Weather: Wind is up to a Moderate Breeze, Clear, lower 40s  
Primary 0.03 – 0.1Hz: Y & Z at 0.02um/s, X a bit above 0.1um/s
Secondary 0.1 – 0.3Hz:  At 0.2um/s 
Quick Summary: Observing for 8.0 hours. The A2L script has a problem.  The A2L Pitch and Yaw signals are somewhat rung up at this time. Guardian is reporting two seismic differences with HAM2, which will clear with the next restart of the Guardian code. 
Outgoing Operator: TJ
LHO General
thomas.shaffer@LIGO.ORG - posted 00:00, Wednesday 01 March 2017 (34479)
Ops Eve Shift Summary

TITLE: 03/01 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Locked my whole shift, I had an error with a2l so I could not run it. I also accidentally knocked us out of Observing for about 40sec.
LOG:

H1 ISC
thomas.shaffer@LIGO.ORG - posted 23:23, Tuesday 28 February 2017 (34481)
Out of Observing to attempt run a2l

Out of Observing from 07:12 - 07:19. Tried to run a2l but there was an error, I'm guessing related to some changes today.

 

Traceback (most recent call last):
  File "./a2l_min_LHO.py", line 107, in <module>
    matrix.asc_ads_input[dof,sensor]=0
AttributeError: 'module' object has no attribute 'asc_ads_input'

H1 General
thomas.shaffer@LIGO.ORG - posted 20:34, Tuesday 28 February 2017 (34480)
Ops Mid shift report

Locked for 4.5hrs with a range of 65Mpc.

We were out of observing for about 40sec when I ran a test that imported the wrong file and caused one SDF diff. I rectified it immediately.

H1 AOS
thomas.shaffer@LIGO.ORG - posted 16:08, Tuesday 28 February 2017 - last comment - 16:20, Tuesday 28 February 2017(34476)
Ops Eve Shift Transition

TITLE: 03/01 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 17mph Gusts, 13mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY: ASC troubles from some maintenance day efforts. Up to low noise now but still diagnosing.

 

Comments related to this report
thomas.shaffer@LIGO.ORG - 16:20, Tuesday 28 February 2017 (34477)
Link

Observing 00:19UTC at ~64Mpc.

There are a few SPM diffs on HAM2 SEI that we will have to clear another time.

H1 SUS (COC)
betsy.weaver@LIGO.ORG - posted 16:01, Tuesday 28 February 2017 (34474)
ETM13 ear bonding

After many aborted attempts to bond ears to this test mass since Dec, we were finally successful today.  Gerardo and I placed a near perfect ear bond of ear 65 to ETM13 S4 flat - no bubbles and placed within spec with very small error.  This test mass is designated to be the new ETMX for LHO eventually.

Images attached to this report
H1 General
travis.sadecki@LIGO.ORG - posted 16:00, Tuesday 28 February 2017 (34475)
Ops Day Shift Summary

TITLE: 02/28 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  First half of the shift was dedicated to Maintenance Day activities, the second half has been relocking and troubleshooting ASC issues. 
LOG:  See attached text file for full log.

 

Non-image files attached to this report
log2017-02-28.txt
LHO General
vernon.sandberg@LIGO.ORG - posted 14:44, Tuesday 28 February 2017 (34472)
Work Permit Summary for 2017 February 28
Work Permit Date Description alog/status
6508.html 02/28/17 11:10 AM Bug fix to get correct signal from LSC to ASC. Should be POPDC, but is accidentally REFLDC. 34461 & 34470
6507.html 02/28/17 10:00 AM Update default version of GDS code to gds-2.17.9-2 to fix an issue with foton (FRS ticket 7447, Bugzilla 1075) and an issue with the NDS2 interface for diaggui to collect reduced data set channel names along with raw names (Bugzilla 1072). 34457 & 34470
6506.html 02/27/17 04:02 PM Change the model to map what are used to be ASC-AS_D channels to PSL-DIAG_BULLSEYE channels. Add four 2k channels from the bulls eye to the frame. https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=7515 https://dcc.ligo.org/E1700074-v1 34460
6505.html 02/27/17 02:56 PM Pull ADS block from LLO so that both sites have all the functionality they need, but we can both be using the same model again (they'll pull our full version after I finish). Model will be installed on maint. day, along with bullseye work permit work. 34470
6504.html 02/27/17 02:02 PM With IFO unlocked (during maintenance) try to identify sources of lines in power monitors which are coherent with lines in DARM. If we identify them, repeat test with locked IFO later.  
6503.html 02/27/17 01:50 PM Re-terminate HV Ion pump connector (Y2-8). Cable will be tested with the HiPOT tester to 5kV. Work will require access into End Y mechanical room. See alog 34385. 34466
6502.html 02/27/17 01:46 PM Add RACCESS numeric EPICS records to DAQ for trending (DAQ restart required). Create new target h1raccess and add all EPICS channels to autoBurt.req for hourly autoburt backup. 34470
6501.html 02/27/17 09:52 AM Regular PSL Maintenance: 1) Temperature tune HPO pump diodes after 2-25-2017 pump diode current increase. 2) Tweak beam alignment into PMC. For these activities the IFO needs to be DOWN and the ISS needs to be OFF. 34456
6500.html 02/24/17 12:56 PM Widen bandwidth of filter in OAF BLRMS. No change in SDF. The new filter will be loaded while we are not in observing mode.  
6499.html 02/24/17 10:09 AM Suspect another short in ion pump HV cable. Marc will test cable. 34466
6498.html 02/23/17 10:39 PM Measure beam spot positions on IMC mirrors. Intended target of time to do this measurement is during PEM measurements at LLO, expected to take place 24 Feb 2017.  
6497.html 02/23/17 04:43 PM I will perform a coherence test by taking coherence between the bullseye sensor and DARM as a function of PR3 spot position by intentionally misaligning interferometer mirrors. This will be done during the commissioning window tomorrow (Feb.24).  
6496.html 02/23/17 01:22 PM Run new fiber from server room to valve room, part of wireless upgrade. Work will involve removing ceiling tiles along main hallway in OSB.  
6495.html 02/23/17 01:11 PM Inventory OneStop cables on all front end computers, MSR, EX, EY, MX, MY, H2-building. Taking photos, non-invasive.  
6494.html 02/22/17 10:48 AM Deploy T240 Seismometer near BRS for staging to install in BRS Thermal Housing next Maintenance Day 34462 & 34463
       
Previous W.P.s      
6492.html 2017-02-17 17:25 Removed beam dump from the FLIR camera path (both CO2X and Y). This will be the new nominal configuration. 34459
6472.html 2017-02-09 16:29 De-energize LLCV electric actuators, remove electric actuator housing domes, lift 4-20mA and 24VDC wires from actuator and remove 1/2" flexible conduit from housings, tighten 1/2 conduit elbows to ensure good contact with their sealing o-rings, reconnect conduit to elbows, re-land wires, re-install housing dome and re-energize actuators 34133, 34151, & 34468
6457.html 2017-01-26 13:43 Remove Coil Driver BIO Connections to WD: Modify & Compile models; DeIsolate Platform; Restart model; Isolate ISI; DAQ ReStart required. 33776, 33799, & 34470
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 14:18, Tuesday 28 February 2017 (34470)
CDS maintenance summary, Tuesday 28th February 2017

WP6457 Removal of coil driver binary in ISI watchdog, h1isiham2 restarted

Hugh, Jim W, Dave:

h1isiham2 was restarted with new code.

WP6505 ASC code upgrade

Jenne, Kiwamu, Keita, Sheila, Dave

h1asc model was modified and restarted. In the DAQ: 1050 slow channels were added, 150 slow channels were remove, 4 fast channels (2048Hz) were added (list below):

+: fast channel H1:PSL-DIAG_BULLSEYE_PIT_OUT_DQ added to the DAQ
+: fast channel H1:PSL-DIAG_BULLSEYE_SUM_OUT_DQ added to the DAQ
+: fast channel H1:PSL-DIAG_BULLSEYE_WID_OUT_DQ added to the DAQ
+: fast channel H1:PSL-DIAG_BULLSEYE_YAW_OUT_DQ added to the DAQ

WP6502 Add RACCESS slow channels to DAQ and autoburt

Dave:

A new H1EDCU_RACCESS.ini file as added to the DAQ dataconcentrator master file. Also a new target h1raccess was created along with its autoBurt.req file for hourly snapshots of remote users.

DAQ Restart:

Dave:

DAQ was restarted to incorporate the above changes to models and EDCU.

WP6507 GDS software upgrade

Jim:

GDS software upgraded to version 2.17.9-2

Guardian DIAG_MAIN restart

Travis, Dave:

The DIAG_MAIN guardian node was stopped and started to free up the memory it was using. The available memory on h1guardian0 went from 35.5GB to 43.7 as a result.

CDS computer labeling

Dave:

In both the EX and EY CDS computer racks all computers are labeled both front and back.

WAP power up notification

Richard, Carlos:

WAP power up notifications were tested. System needs some more investigation. WAPS are now all OFF.

WP6508 h1lsc model change, REFLDC being sent to ASC, should be POPDC.

Jenne, Keita, Dave:

h1lsc mode was modified and restarted. No DAQ restart was necessary.

h1brsex found to have RED error LED on front panel, machine was rebooted and code restarted

Jim, Dave, Carlos:

During my EX visit I noticed that the front panel red led was ON. This had been seen on h1brsey late 2016. h1brsex was rebooted and the code restarted.

 

H1 CDS
patrick.thomas@LIGO.ORG - posted 14:05, Tuesday 28 February 2017 (34469)
Updated conlog channel list 
Channel list attached.
Non-image files attached to this report
all.txt
LHO VE
kyle.ryan@LIGO.ORG - posted 13:51, Tuesday 28 February 2017 (34468)
Modified CP7 liquid level control valve (LLCV) housing @ Y-end 
This completes WP #6472

As with the others, this unit had standing water within the housing and should benefit from the drain installed as part of this modification.
H1 CDS
david.barker@LIGO.ORG - posted 13:43, Tuesday 28 February 2017 (34467)
investigating nds2 client error

Jeff is seeing a matlab nds2 client error, Jonathan thinks it may be related to maintenance. I am able to get a channel list from the caltech nds2 server using diaggui, but matlab reports the error:

>> nds2.connection('nds.ligo.caltech.edu')
Java exception occurred:
java.lang.RuntimeException: Error occurred trying to write to socket
    at nds2.nds2JNI.new_connection__SWIG_2(Native Method)
    at nds2.connection.<init>(connection.java:51)
 

LHO VE
kyle.ryan@LIGO.ORG - posted 13:39, Tuesday 28 February 2017 - last comment - 15:37, Tuesday 28 February 2017(34466)
Y2-8 BT ion pump back on line 
Richard M., Filiberto C.

I energized the Y2-8 BT ion pump after the CDS guys repaired the shorted pump-end connector.  As the attached pressure plot indicates, the pump is obviously working.  Curiously, however, the indicated pressure and current on the controller read zeros.  I wonder if the current sensing components were damaged during the arcing/shorting bursts leading up to the final short?  Regardless, these two values are local only and are not "seen" by CDS.
Non-image files attached to this report
Y28_pressure.pdf
Comments related to this report
filiberto.clara@LIGO.ORG - 15:37, Tuesday 28 February 2017 (34473)
Link

Work was done under WP 34466. Cable was tested with HiPOT tester (5kV).

H1 SEI
jim.warner@LIGO.ORG - posted 12:52, Tuesday 28 February 2017 - last comment - 14:24, Tuesday 28 February 2017(34465)
BRSX computer restarted

Dave noticed that there was an error light on at the BRSX Beckhoff box. Looking the the event logs with Carlos, we found some software errors that we suspect are responsible for this, shown in the attached screenshot. This seems to happen frequently with BRSX (I haven't checked BRSY yet, but we found the light on at the chassis at EY some time in December(?) as well). We cleared this by restarting the BRSX machine, but we aren't sure what the cause is or why the chassis light came on because of a software issue.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 14:24, Tuesday 28 February 2017 (34471)
Link

TWINCAT error codes reports the following for error 0x4225:

Drive not ready during axis start

During an axis start it is ascertained that the drive is not ready. The following are possible causes: - the drive is in failure state (hardware fault) - the drive is in the starting-up stage (e.g. following an axis reset preceded by a hardware fault) - the drive has not been enabled

Remark: The time required for "booting" a drive after a hardware fault can amount to several seconds.

H1 ISC
jenne.driggers@LIGO.ORG - posted 11:09, Tuesday 28 February 2017 - last comment - 12:09, Tuesday 28 February 2017(34461)
Bug in LSC model, for signal sent to ASC model

While checking the new ADS matrix, I discovered a bug in the LSC model.  The ASC and ADS get length and power buildup signals from the LSC model.  These are then used as error signals for the ADS, and the buildups as potential dynamic power normalization options for ASC error signals.

However, what is supposed to be POPAIR_B_LF (POP DC) from the LSC model is actually currently REFLAIR_B_LF. The attached image is a tiny portion of the LSC model, showing that what goes up a level is actually coming from a REFL tag, not a POP tag.  (I'll try to remember to put more screenshots showing the signal flow later, but want to get this fixed since it's maint. day).

At LHO, we are not actually using this signal to run the IFO.  We just occasionally look at it if we're demodulating things trying to find new error signals, during commissioning time.  I'll call LLO to check if they use it, because if they do (I don't think they do), they'll need to check on things.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 12:09, Tuesday 28 February 2017 (34464)
Link

This has now been fixed (WP 6508).  LLO is also not using this signal during normal IFO operation, so them fixing it will not cause any problems.  Adam is aware, and will look at it.

Displaying reports 52881-52900 of 86398.Go to page Start 2641 2642 2643 2644 2645 2646 2647 2648 2649 End