Displaying reports 64281-64300 of 83294.Go to page Start 3211 3212 3213 3214 3215 3216 3217 3218 3219 End
Reports until 07:58, Thursday 09 July 2015
LHO General
richard.oram@LIGO.ORG - posted 07:58, Thursday 09 July 2015 (19515)
L1 PSL lock-out is now released

FYI:

The lock-out on the L1 PSL is now released.

All conditions in the original memo have been met. 

The release memo is here: https://dcc.ligo.org/M1500231

H1 ISC
stefan.ballmer@LIGO.ORG - posted 00:37, Thursday 09 July 2015 - last comment - 13:01, Thursday 09 July 2015(19512)
More full locking work
Kiwamu, Stefan

We noticed that in full lock (before power up) we again have questionable WFS. Indeed it seems to again be SRCL1 YAW that runs away - slowly at low power, but rapidly at high power. This is all a deja-vu, see elogs 18442, 18923, 18931.

More investigation suggested that it is actually the QPD loops that pull us into a regime where the other loops are not stable. So for now we changed the QPD loop offsets at low power to just keep us at the same location:
  New values: H1:ASC-X_TR_A_PIT_OFFSET H1:ASC-X_TR_B_PIT_OFFSET H1:ASC-X_TR_A_YAW_OFFSET H1:ASC-X_TR_B_YAW_OFFSET
   -0.084
   -0.212
   -0.023
    0.006
  Old values: H1:ASC-X_TR_A_PIT_OFFSET H1:ASC-X_TR_B_PIT_OFFSET H1:ASC-X_TR_A_YAW_OFFSET H1:ASC-X_TR_B_YAW_OFFSET
   -0.029
   -0.158
   -0.007
    0.105

However we still lost it on POWER UP. More work needed here.


We also reverted the changes from earlier today (alog 19511): ETMX ISCINF gain back to 1, and the L1 gain back to 0.28. This now gave us a lower peak-peak ESD drive and - unlike earlier today - ALS DIFF engaged just fine... (no idea why it acted up earlier...)


Comments related to this report
kiwamu.izumi@LIGO.ORG - 00:36, Thursday 09 July 2015 (19513)
old offsets
H1:ASC-Y_TR_A_PIT_OFFSET = 0.101
H1:ASC-Y_TR_A_YAW_OFFSET = -0.127
H1:ASC-Y_TR_B_PIT_OFFSET = -0.056
H1:ASC-Y_TR_B_YAW_OFFSET = 0.055
H1:ASC-X_TR_A_PIT_OFFSET = -0.0841
H1:ASC-X_TR_A_YAW_OFFSET = -0.023
H1:ASC-X_TR_B_PIT_OFFSET = -0.212
H1:ASC-X_TR_B_YAW_OFFSET = 0.006
 
 
new (temporary) offsets
H1:ASC-Y_TR_A_PIT_OFFSET = -0.192
H1:ASC-Y_TR_A_YAW_OFFSET = -0.365
H1:ASC-Y_TR_B_PIT_OFFSET = -0.32
H1:ASC-Y_TR_B_YAW_OFFSET = -0.237
H1:ASC-X_TR_A_PIT_OFFSET = -0.084
H1:ASC-X_TR_A_YAW_OFFSET = -0.023
H1:ASC-X_TR_B_PIT_OFFSET = -0.212
H1:ASC-X_TR_B_YAW_OFFSET = 0.006OLD
H1:ASC-Y_TR_A_PIT_OFFSET = 0.101
H1:ASC-Y_TR_A_YAW_OFFSET = -0.127
H1:ASC-Y_TR_B_PIT_OFFSET = -0.056
H1:ASC-Y_TR_B_YAW_OFFSET = 0.055
H1:ASC-X_TR_A_PIT_OFFSET = -0.0841
H1:ASC-X_TR_A_YAW_OFFSET = -0.023
H1:ASC-X_TR_B_PIT_OFFSET = -0.212
H1:ASC-X_TR_B_YAW_OFFSET = 0.006
 
 
H1:ASC-Y_TR_A_PIT_OFFSET = -0.192
H1:ASC-Y_TR_A_YAW_OFFSET = -0.365
H1:ASC-Y_TR_B_PIT_OFFSET = -0.32
H1:ASC-Y_TR_B_YAW_OFFSET = -0.237
H1:ASC-X_TR_A_PIT_OFFSET = -0.084
H1:ASC-X_TR_A_YAW_OFFSET = -0.023
H1:ASC-X_TR_B_PIT_OFFSET = -0.212
H1:ASC-X_TR_B_YAW_OFFSET = 0.006OLD
H1:ASC-Y_TR_A_PIT_OFFSET = 0.101
H1:ASC-Y_TR_A_YAW_OFFSET = -0.127
H1:ASC-Y_TR_B_PIT_OFFSET = -0.056
H1:ASC-Y_TR_B_YAW_OFFSET = 0.055
H1:ASC-X_TR_A_PIT_OFFSET = -0.0841
H1:ASC-X_TR_A_YAW_OFFSET = -0.023
H1:ASC-X_TR_B_PIT_OFFSET = -0.212
H1:ASC-X_TR_B_YAW_OFFSET = 0.006
 
 
H1:ASC-Y_TR_A_PIT_OFFSET = -0.192
H1:ASC-Y_TR_A_YAW_OFFSET = -0.365
H1:ASC-Y_TR_B_PIT_OFFSET = -0.32
H1:ASC-Y_TR_B_YAW_OFFSET = -0.237
H1:ASC-X_TR_A_PIT_OFFSET = -0.084
H1:ASC-X_TR_A_YAW_OFFSET = -0.023
H1:ASC-X_TR_B_PIT_OFFSET = -0.212
H1:ASC-X_TR_B_YAW_OFFSET = 0.006
H1 ISC
sheila.dwyer@LIGO.ORG - posted 18:42, Wednesday 08 July 2015 (19511)
recovering locking

Evan, Nic, Stefan, Elli, Sheila

After spending some time to recover alignment, fiber polarization, turn TCS back on, ect, we have started to attempt locking. 

The first problem we ran into was that ALS DIFF was not locking, the first problem we found was that the linearization was off.  In addition, it seems that the ESD gain has been reduced by a factor of 2 after the vent and discharging.  The attached screenshots show the OLG and crossover measurements with a factor of 2 added in drivealign, they match the references well this way.  The green reference in the OLG measurement shows the gain when we managed to lock with the nominal settings from before the vent.  

We have edited the guardian to add a factor of 2 gain in ETMX ISCINF, and reduced the L1 gain from 0.28 to 0.14 to keep the crossover around 1 Hz.  The drives with DIFF locked are attached.  

We were able to lock on DC readout, but Evan found that the DARM gain was 4dB too high, so he reduced the gain in the DARM filter bank to 900 from 1200.  We made it to DC readout and lost lock durring the power up.  

Images attached to this report
H1 SUS
leonid.prokhorov@LIGO.ORG - posted 16:30, Wednesday 08 July 2015 (19510)
OPLEV Charge measurements
More charge measurements on ETMs. Plots are attached.
Still no charges.
Images attached to this report
H1 SEI (CDS)
jim.warner@LIGO.ORG - posted 16:23, Wednesday 08 July 2015 - last comment - 10:10, Friday 17 July 2015(19509)
Quacking matlab filters and foton filter glitching

Earlier today, I wrote a couple out of loop feedforward filters to the BS ISI foton file using Foton. When I hit the load coefficients button (while the ISI was isolated, the ff paths were off, so it shouldn't have done anything), the ISI tripped, hard. It rang up the T240's pretty bad and I couldn't isolate the ISI for several minutes after. Worried I had inadvertantly written some other filter I ran a diff on the most recent archived file and the file created yesterday when Jeff restarted the models. This showed a whole bunch of filter coefficient differences, which shouldn't have been there (as reported by a diff of the two archive files, I don't know exactly what changed, see attached). Talking to Jim, Dave and Jeff, it sounds like the glitch was probably caused by my having used Quack recently (June 22nd) to load some blend filters. Jeff's model restart (and even a prior model restart on June 30) simply inherited that quack-written file. Today was the first time the BS's foton file was opened and saved in Foton. Quack can apparently load coefficients with higher precision than Foton will accept, so when you open and save a "too high" precision filter with Foton, it rounds the coefficients off. Sudden change in precision of SOS coefficients in the blend filters = bad for isolation loops = bad trip.

We've seen this Foton vs. Quack Rounding problem before -- see e.g. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=3553 -- and it's still biting us.

This sounds like a relatively easy thing to control for, I can think of two ways:

- getting Quack to check and do the rounding on it's own before writing to the Foton file.

- have the post-build script run a "foton -c" on all filter files before the model gets restarted.

Is there someone in the CDS group who can fix this? Maybe it has been? There are several versions of Quack running around, June was my first attempt with it, maybe I used the wrong one.

I used /ligo/svncommon/SeiSVN/seismic/Common/MatlabTools/autoquack.m

 https://svn.ligo.caltech.edu/svn/seismic/Common/MatlabTools/autoquack.m

Last Changed Author: brian.lantz@LIGO.ORG
Last Changed Rev: 7939
Last Changed Date: 2014-02-14 15:38:15 -0800 (Fri, 14 Feb 2014)
Text Last Updated: 2014-02-14 15:48:16 -0800 (Fri, 14 Feb 2014)

Non-image files attached to this report
Comments related to this report
richard.mittleman@LIGO.ORG - 07:02, Thursday 09 July 2015 (19514)

we should use the readfoton script to read and plot the installed filter, i can do that

brian.lantz@LIGO.ORG - 13:57, Monday 13 July 2015 (19591)
I suspect that the problem appears because a change (however small) in the filter coefficients causes the filters to reset (clear history, start over) and reset of the filter history = glitch in the output. It is easy to image this glitch being quite large for a ISI loop which is holding a static offset. 

I am working on an update to autoquack which will have it automatically call foton -c so that the filter updates happen in a deterministic way, and there is a log file telling you which filters have been touched.
 
brian.lantz@LIGO.ORG - 10:10, Friday 17 July 2015 (19704)
filed ECR 
https://services.ligo-wa.caltech.edu/integrationissues/show_bug.cgi?id=1077

testing of possible solution, see 
https://alog.ligo-la.caltech.edu/SEI/index.php?callRep=789
-Brian
LHO General
thomas.shaffer@LIGO.ORG - posted 16:01, Wednesday 08 July 2015 (19508)
Ops Day Shift Summery

0712 - Joe Gleason to EY

0715 - J Gleason out

0858 - Jim W finished with BSC measurements

0859 - Leonid starting charge measurements EX/EY

0900 - Fil to EX for ALS fiber conduit install

0923 - Richard to EX to help Fil

0924 - Jordan, Vincent to EX for PEM cabling

0934 - Gerardo to EX prep for gate opening

0953 - Richard back

1000 - Kyle to EX

1114 - Nutsinee to EY for PCal measurments

1115 - Vincent to CER

1121 - Vincent out but then to LVEA for PEM cables

1125 - Bubba at EX (according to card reader)

1127 - Kyle, Gerardo back from EX and goin intot the LVEA to HAM6

1138 - Ed to EX to adjust OpLev

1139 - Nutsinee back

1155 - Kyle, Gerardo out

1232 - Fil to MY

1323 - Gerardo, John, Bubba at EX

1408 - HEPI alarm. Pump pressure was "Not Okay" Hugh was contacted(see alog)

1410 - Hugh to EY to investigate

1445 - Kyle to EY

1506 - Kyle back

1550 - Elli, Sheila to LVEA to turn ON CO2X laser

1558 - Elli, Shelia out of LVEA and now going to the Ends to turn ON the ring heaters

H1 GRD
thomas.shaffer@LIGO.ORG - posted 15:40, Wednesday 08 July 2015 (19496)
New decorator added to IMC_LOCK Guardian

This morning when Jim B. restarted H1IOPSEIH23, I forgot to set the IMC_LOCK Guardian to OFFLINE. The IMC kept its lock but the WFS ran away with the HEPI misalignment. To avoid this in the future Jeff, Sheila, and I decided to have IMC_LOCK check that the SEI managers for HAM2/3 are ISOLATED. I added a new decorator to the IMC_LOCK  Guardian (@sei_state_checker) that will make sure HAM2 and HAM3 SEI managers are in the ISOLATED state. If they are not, it will return the MOVE_TO_OFFLINE state. OFFLINE is now a protected state(redirect = False) and has a run condition that will not allow the Guardian to move on unless the SEI managers are ISOLATED (Thank you, Jamie). The idea behind this is to allow the the node to "wait" in OFFLINE until the SEI managers are where they should nominally be.

I reloaded the Guardian with the new code and committed it to the SVN.

**EDITED Wed July 8, 2015  15:36 PST**

H1 SEI
hugh.radkins@LIGO.ORG - posted 15:28, Wednesday 08 July 2015 (19507)
WBSC9 EndX SEI HEPI Pump Pressure Alarm values widened

We are sliding backwards in our efforts to quiet the pressures at EndX.  EE's latest test in the grounding has increased the noise on the pressure signals.  As a result, I've opened up the no-alarm region of the differential pressure to +-6 psi.  Remember, a momentary pressure glitch is pretty harmless and meaningless; but, an alarm that is sustained must be addressed asap.

LHO VE
kyle.ryan@LIGO.ORG - posted 15:12, Wednesday 08 July 2015 (19506)
Increased vapor pressure of CP7's dewar
~1500 hrs. local -> Adjusted boil-off pressure regulator 1 full turn clockwise
H1 CDS
david.barker@LIGO.ORG - posted 15:11, Wednesday 08 July 2015 (19504)
Camera Copy script extended to X-arm, new MEDM created

My script which reads the digital video ITM green image's X,Y,SUM and writes them as EPICS values to the ALS end station model (as YAW,PIT,SUM) has been extended to run on the X-arm as well as the Y-arm.

I have created an MEDM screen (H1CDS_CAMERA_COPY.adl, see attachment) which is accessible from the SITEMAP via the CDS pull down (last item on list).

The script runs within a screen environment on h1fescript0 as user controls

Images attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 15:07, Wednesday 08 July 2015 - last comment - 15:11, Wednesday 08 July 2015(19503)
WBSC10 EndY ETMY SEI HEPI Pump Station Shutdown--OV3 Error on VFD

The last time the OverVoltage while running at SetPoint occurred was 14 July 2014.  Restarted normally per procedure in WIKI.  The system was down for about 40 minutes.  FRS 3289.

Comments related to this report
thomas.shaffer@LIGO.ORG - 15:11, Wednesday 08 July 2015 (19505)

Wiki located here: https://lhocds.ligo-wa.caltech.edu/wiki/SEI

LHO VE
john.worden@LIGO.ORG - posted 14:37, Wednesday 08 July 2015 - last comment - 16:28, Friday 10 July 2015(19501)
NEG Pump at END X

END X has been transitioned to the NEG pump. The main turbo is isolated but still spinning.

Pressure has remained at ~2.2e-8 torr.

Comments related to this report
gerardo.moreno@LIGO.ORG - 16:28, Friday 10 July 2015 (19557)

Installed Pump

Images attached to this comment
LHO VE
kyle.ryan@LIGO.ORG - posted 14:25, Wednesday 08 July 2015 (19500)
CP7 liquid level control valve (LLCV) is creeping up towards 100% open
The dewar level for CP7 is relatively low and the LLCV % open is nearly maxed out -> The vapor head pressure is 20 < pressure < 25 psi which should be more than adequate -> Delivery isn't for 6 more days -> At this rate we will have to do something or CP7 will have to be filled manually 
LHO VE
kyle.ryan@LIGO.ORG - posted 14:18, Wednesday 08 July 2015 (19499)
IP3 controller partial failure
IP3 lost 1 of 2 channels shortly after replacing IP1 controller -> Both of these two units are the original (circa 1997) Varian MultiVac models of which we only have one or two left now on the site -> The failure is "Over Temperature" which is the typical failure mode -> I am unsure what is left for spares but will replace this unit as I am able
LHO VE
kyle.ryan@LIGO.ORG - posted 14:10, Wednesday 08 July 2015 (19498)
Replaced IP1 controller
~1330 hrs. local -> Installed Gamma LPC unit (No CDS signal interface to this Make/model yet.  Indicated CDS values are bogus until otherwise specified)  

LHO VE
kyle.ryan@LIGO.ORG - posted 14:07, Wednesday 08 July 2015 (19497)
Opened GV20
Kyle, Gerardo 

Dumped unpumped gate annulus volume into pump cart -> Decoupled cart from GV20 -> Opened GV20
H1 DetChar (DetChar)
keith.riles@LIGO.ORG - posted 21:22, Thursday 04 June 2015 - last comment - 08:39, Thursday 09 July 2015(18879)
Narrow lines in early ER7 data
Following up this earlier report on pre-ER7 narrow lines in H1 DARM, attached is a corresponding
list of early ER7 lines and some spectra for 30.5 hours of data from May 31 through June 4 at 13:00 UTC, based
on FScans SFTs generated as of Thursday morning. 

Figure 1 shows the 0-2000 Hz spectrum for the early ER7 data with line labels according to the same scheme as before.

Figure 2 shows the mid-May and early ER7 spectra overlain without line label clutter.

Attachment 1 is the early ER7 line list (nearly identical in line frequencies but not strengths to that of mid-May)

Attachment 2 is a zipped tar file of 27 sub-band spectra for early ER7 with lines labeled.

Attachment 3 is a zipped tar file of 27 sub-band spectra comparing mid-May to early ER7 without labels.

I haven't yet digested all of the changes from mid-May to the early ER7A data (what I call ER7A here), but here are things that are immediately apparent::
  • Bounce and roll modes are greatly reduced in this ER7 sample
  • Quad violin modes are less excited in this ER7 sample
  • The previous comb with a fundamental of 36.9733 Hz (54 harmonics visible) has shifted slightly to a fundamental of 36.9725 Hz (50 harmonics visible).
  • The broad structures seen in the 280-440 Hz band are worse in early ER7 than in mid-May (due to PSL jitter, if I understood Robert correctly)
  • The nefarious OMC alignment dithers and their upconversion have reappeared in what the CW group considers to be an astrophysically interesting band (anything below 2 kHz) at frequencies of 1675.1, 1700.1, 1725.1 and 1750.1 Hz
  • Whatever dithers there were previously at 81.0000 and 310.0000 Hz have disappeared.
Images attached to this report
Non-image files attached to this report
Comments related to this report
nelson.christensen@LIGO.ORG - 08:39, Thursday 09 July 2015 (19516)DetChar, PEM
We used the coherence tool to try and see if there was a coherence between h(t) and other channels for this 36.9725 Hz noise line and its harmonics.

There is a coherence between the h(t) channel and ...
H1:PEM-CS_MAG_EBAY_SUSRACK_Z_DQ
at
36.9725 Hz * 2 =  73.9450 Hz (definitely)
36.9725 Hz * 3 = 110.9175 Hz (barely above background)
36.9725 Hz * 4 = 147.89 Hz (definitely)
36.9725 Hz * 5 =  184.8625 Hz (above background)
36.9725 Hz * 6 = 221.8350 Hz (definitely)
...
For whatever reason the even harmonics are stronger.
The mat file for the coherence is here:
https://ldas-jobs.ligo-wa.caltech.edu/~eric.coughlin/ER7/LineSearch/H1_COH_1116633616_1118275216_SHORT_1_webpage/data/H1:PEM-CS_MAG_EBAY_SUSRACK_Z_DQ_data.mat

For H1:PEM-CS_MAG_EBAY_SUSRACK_X_DQ there is a coherence with h(t) at
36.9725 Hz * 4 = 147.89 Hz (barely about background)
See
https://ldas-jobs.ligo-wa.caltech.edu/~eric.coughlin/ER7/LineSearch/H1_COH_1116633616_1118275216_SHORT_1_webpage/data/H1:PEM-CS_MAG_EBAY_SUSRACK_X_DQ_data.mat

For For H1:PEM-CS_MAG_EBAY_SUSRACK_Y_DQ there is a coherence with h(t) at
36.9725 Hz * 2 = 73.9450 Hz (barely above background)
36.9725 Hz * 4 = 147.89 Hz (above background)
36.9725 Hz * 5 =  184.8625 Hz (barely above background)
36.9725 Hz * 6 = 221.8350 Hz (above background)
...
See
https://ldas-jobs.ligo-wa.caltech.edu/~eric.coughlin/ER7/LineSearch/H1_COH_1116633616_1118275216_SHORT_1_webpage/data/H1:PEM-CS_MAG_EBAY_SUSRACK_Y_DQ_data.mat
 
Nothing in the other magnetometers.

Nelson, Eric Coughlin, Michael Coughlin
Displaying reports 64281-64300 of 83294.Go to page Start 3211 3212 3213 3214 3215 3216 3217 3218 3219 End