Displaying reports 61201-61220 of 86134.Go to page Start 3057 3058 3059 3060 3061 3062 3063 3064 3065 End
Reports until 23:50, Wednesday 17 February 2016
LHO FMCS
corey.gray@LIGO.ORG - posted 23:50, Wednesday 17 February 2016 - last comment - 18:51, Thursday 18 February 2016(25607)
LVEA Temperature Increase of 0.8 degF

Received an FMCS Air Handler HIGH RED alarm.  This evening.  I've acknowledged it, and it will probably stay in the RED state until addressed (if this is a new running state, we should update the alarm handler).

This might be correlated with John turning off heaters on Tuesday, but not sure.

Will send an email to John/Bubba.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 23:58, Wednesday 17 February 2016 (25608)

Hmmm.  I note that this seems to roughly correspond in time with our locking (and esp. alignment) troubles of the last 2 days. 

john.worden@LIGO.ORG - 08:29, Thursday 18 February 2016 (25614)

A better representation of LVEA temperature is this signal:

H0:FMC-LVEA_CONTROL_AVTEMP_DEGF

 

see plot for the last 4 days.

Images attached to this comment
keita.kawabe@LIGO.ORG - 18:51, Thursday 18 February 2016 (25631)

Keita, Sheila

While the average temperature in the LVEA has been stable, the temperature has changed by about 1 degree C in several zones.  Here is a plot of PR3 PIT (oplev and osem) as the temperature changes.  These sensors could both be sensitive to temperature, but the optic could also have really moved with the temperature change. 

It still seems plausible that our alignment difficulties of the last few days are related to temperature.

Images attached to this comment
H1 AOS
sheila.dwyer@LIGO.ORG - posted 20:37, Wednesday 17 February 2016 (25605)
OMC length loop gain reduced

I reduced the gain of the OMC length locking loop by a factor of 3, the UGF has gone from 10 Hz to 3 Hz, and added a 30 Hz low pass.  The new open loop is attached, as well as a spectrum of the drive signal before and after this change.  There are low passes in the PZT driver that mean this is not as dramatic a change in the OMC length RMS as it seems.  

Noise projections coming soon.  

Images attached to this report
H1 ISC
denis.martynov@LIGO.ORG - posted 17:56, Wednesday 17 February 2016 - last comment - 23:33, Wednesday 17 February 2016(25602)
drmi tunings
Sheila, Den

We have tuned DRMI servos to reduce the acquisition time. First of all, we noticed that MICH servo saturates the BS actuator during the flash. In order to solve this issue we have copied control filters from LLO. Attached plot shows comparison of LLO and old LHO MICH servos. Next we have changed locking threshold for SRCL and changed ramping time for PRCL and SRCL boosts.

New changes are in the guardian's "NEW_DRMI_SETTINGS" state. We tested these filters (~10 times) and concluded that there is an improvement in lock acquisition time. Average DRMI wait time is 1 minute.
Non-image files attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 23:33, Wednesday 17 February 2016 (25606)

The main change to the MICH loop is that we are no longer using the invPlant filter, and are now using a simpler compensator, and that we use more aggressive low pass filtering for acquisition.  Attached is a (not great) measurement of the new loop compared the the old one (in blue), and uncalibrated spectra of the error signals showing that things are fairly similar in the end. 

We have now made these new settings the default guardian settings, and there are no longer two alternative DRMI paths in the guardian.  

This means that our MICH loop is a little different in low noise, and that we will have to adjust our MICH FF to compensate.  We have put the new compensation filter in the MICH FF bank, and den found that a gain of -15.9 gave the best subtraction at 30 Hz, and that the coherence was low.  We can check with braodband excitations but have had trouble getting back to low noise since we did this.  

We also made these changes to the MICH loop that is used in initial alignment to lock the dark michelson. 

Images attached to this comment
H1 TCS (SUS)
huy-tuong.cao@LIGO.ORG - posted 17:27, Wednesday 17 February 2016 - last comment - 08:24, Thursday 18 February 2016(25600)
Scanning SR3

[Cao, Ellie, Dave O, Aidan]

To whoever will be around in the control room last after commisioning, here are the steps for SR3 scanning to align Y arm HWS:

1- Turn off SR3 Cage Servo , Make sure that all mirrors are in ALIGNED state.

2- Run arbitrary waveform generator for H1:  SUS-SR3_M1_OPTICALIGN_P_EXC.

             Frequency has been set to 41.7 mHz

            Amplitude has been set to 750 urad

3- Run arbitrary waveform generator for H1:  SUS-SR3_M1_OPTICALIGN_Y_EXC immediately after step 2

            Frequency has been set to 10.3 mHz

            Amplitude has been set to 1550 urad

Let it run over night

All relevant windows have been left open on computer operator1 10.20.0.81

Comments related to this report
evan.hall@LIGO.ORG - 08:24, Thursday 18 February 2016 (25613)

Started ca 08:33:00 Z.

Stopped ca 16:23:00 Z.

H1 SUS
filiberto.clara@LIGO.ORG - posted 16:44, Wednesday 17 February 2016 (25599)
TMSX SAT AMP Units Replaced (EX).
This afternoon, we replaced the Sat Amp units for TMSX. New units have the same modifications as the SR3/OMC units. Two decoupling capacitors were placed on the input of the negative regulator (U503), as implemented at LLO. 

C602 0.1uf
C601 10uf

New Unit S1100098 Old Unit S1100168
New Unit S1000292 Old Unit S1100066
LHO General
thomas.shaffer@LIGO.ORG - posted 16:02, Wednesday 17 February 2016 (25593)
Ops Day Shift Summary
H1 DAQ (DAQ)
david.barker@LIGO.ORG - posted 15:07, Wednesday 17 February 2016 (25596)
DAQ data concentrator kernel panic and freeze, computer was reset

at 14:11 PST h1dc0 froze up with a kernel panic. We reset the computer by pressing the front panel RESET button, but it did not come back cleanly.

When h1dc0's daqd process first was restarted, it ran for only a short period and then died. It was logging GPS timing jumps of one to many seconds.

Monit restarted it and it is now running correctly. The other DAQ systems restarted at this time correctly, except h1broadcast0 took a long time to get going.

Frame gap due to this problem is

1139782208 to 1139782912

Feb 17 2016 22:09:51 UTC to Feb 17 2016 22:21:35 UTC

H1 TCS (TCS)
aidan.brooks@LIGO.ORG - posted 14:42, Wednesday 17 February 2016 - last comment - 15:24, Wednesday 17 February 2016(25587)
TCS online-simulation coefficients and transfer functions

The TCS simulation model to estimate the lenses and ROC of the optics is now running. The following lists gives the nominal values and the transfer functions used for all the filters:

ITMX/ITMY:

ETMX/ETMY:

Images attached to this report
Comments related to this report
aidan.brooks@LIGO.ORG - 15:02, Wednesday 17 February 2016 (25595)

This screen is accessible from the TCS_MASTER > SIMULATION button.

aidan.brooks@LIGO.ORG - 15:24, Wednesday 17 February 2016 (25597)

The static lenses from the ITMs have been added also (see T1400602)

  • ITMX static = 1/(-80213): H1:TCS-ITMX_SIM_SUB_DEFOCUS_STATIC = -1.2467E-5
  • ITMY static = 1/(+572117): H1:TCS-ITMY_SIM_SUB_DEFOCUS_STATIC = 1.7479E-6
H1 SEI
jim.warner@LIGO.ORG - posted 12:18, Wednesday 17 February 2016 (25592)
ETMX HEPI tripped again

This morning while TJ was trying to relock, ETMX HEPI tripped again. Kiwamu, Sheila and I all poked around at this a bit and can't find an obvious culprit yet. It's definitely something to do with the X HEPI position (tidal or something else). First attached plot is the ETMX actuators time series at the trip. The little shark tooth just before the trip seems to be caused by something in tidal (a reaction to HEPI walking off, maybe? Or something causing the IMC to do something weird?). When I looked a the cartesian signals, the movement seems to be all in X. The second plot is the time series over the same 32 second window of a few other signals, but none of them are particularly enlightening. The dark blue trace on the middle left is the HEPI X location, which goes on some 30 micron excursion, which ultimately causes the lock loss. But the motion seems to be chickens/eggs. Did tidal get some other input that drove HEPI or did HEPI go crazy and drive off tidal? I don't know.

Images attached to this report
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 11:28, Wednesday 17 February 2016 (25591)
CDS model and DAQ restart report, Wednesday-Tuesday 10th-16th February 2016

model restarts logged for Tue 16/Feb/2016
2016_02_16 13:58 h1tcscs
2016_02_16 14:27 h1isietmy

2016_02_16 14:29 h1dc0
2016_02_16 14:31 h1broadcast0
2016_02_16 14:31 h1nds0
2016_02_16 14:31 h1nds1
2016_02_16 14:31 h1tw1

Maintenance day. TCS and ISI-ETMY model changes. H0EDCU_VE.ini change. Related DAQ restart.

Wed 10/Feb/2016 - Mon 15/Feb/2016 No restarts reported.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 11:23, Wednesday 17 February 2016 (25590)
CDS maintenance summary, Tuesday 16th February

TCS model change. WP5732

Dave, Aidan:

Aidan made model changes to h1tcscs.mdl 

Buried EY Seismometer added to h1isietmy model. WP5733

Jeff, Robert, Dave:

h1isietmy was modifed to read the external seismometer, these channels were added to the science frame.

Adding all Vacuum Controls channels to the DAQ. WP5731

Dave:

All the vacuum controls channels were added to the DAQ. Increased the number of channels from 280 to 1777

DAQ restart

Jim, Dave:

DAQ was restarted to support all the above changes. After several hours h1fw1 became unsynchronized to h1fw0 (we had not seen this before). Restarting h1fw1 fixed this.

GLIBC patching

Dave:

Patched and restarted critical servers and about half of the control room workstations.

H1 PSL (OpsInfo)
cheryl.vorvick@LIGO.ORG - posted 11:06, Wednesday 17 February 2016 - last comment - 13:22, Thursday 18 February 2016(25589)
Diode Chiller filled with 350ml of water

I filled the PSL diode chiller with 350ml of water.  Attached is a 30 day plot showing where the diode chilller was filled on Feb 4th, and then the alarm level increasing starting around Feb 13th.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 18:16, Wednesday 17 February 2016 (25603)

How does this alarm?  Is it on Verbal?  Audible alarm out in the Diode Room?  Or is the red light the only way to tell if it's low.  In general, the Crystal Chiller is the one which requires action every week.  For the Diode Chiller all we have is the red LED to warn us of low levels (I've never seen it).  We (operators) just need to remember to also keep checking the Diode Chiller when performing this task.

Conceivably, we check this every Thursday.  If the alarm goes off on Friday, is it OK for this chiller to be in alarm until it's checked the next Thursday?

I wonder if we should include trending the alarm level on the FAMIS procedure for this as Cheryl did.

jason.oberling@LIGO.ORG - 13:22, Thursday 18 February 2016 (25619)

Unfortunately the red LED on the face of the diode chiller is the only alarm we have and checking this LED is part of the FAMIS procedure.  Additionally, especially with Peter and I in Germany until mid-March, if anyone is in the diode room for any reason and sees this red LED lit, fill the diode chiller immediately until the light goes out and post in the alog that water was added and how much.  If the water level gets too low, the chiller will shut off, which also shuts off the entire PSL.  We need a better alarm (especially in the hypothetical situation Corey brings up, this could result in a laser shut down if not caught before the next scheduled check), but this is what we have for now.

LHO VE
john.worden@LIGO.ORG - posted 09:11, Wednesday 17 February 2016 - last comment - 04:22, Thursday 18 February 2016(25586)
CP3 liquid level control

I have increased the LLCV valve setting to 18% (from 15%) to try and compensate for changing conditions.

Factors that are changing are:

The supply pressure is falling as the liquid level in the storage dewar falls.

Heat leak to the liquid transfer line is increasing with outdoor temperature. This results in more vapor in the line and less liquid to the pump.

Radiation from the beam tube as the beam tube warms.

The attached plot shows 100 days of the control valve setting. The flat line at 15% is due to the failure of the differential pressure sensing- we have had to resort to manual setting of this valve.

Images attached to this report
Comments related to this report
john.worden@LIGO.ORG - 10:26, Wednesday 17 February 2016 (25588)

For reference the liquid capacity of the pump reservoir is ~77 gallons when full.

john.worden@LIGO.ORG - 14:28, Wednesday 17 February 2016 (25594)

I forgot about the heat into the pump due to radiation from the surrounding vacuum chamber in the mid station. Here is a plot of recent VEA temperatures at MID Y. 

Images attached to this comment
michael.zucker@LIGO.ORG - 04:22, Thursday 18 February 2016 (25611)

That is illuminating, thanks. We take feedback controls for granted around here; don't miss it till it's gone. Hope this sophisticated PIL* control algorithm will tide us over until we can regen & fix the level sensor.

 

 

 

 

 

 

*Primate In Loop

H1 General (CAL, ISC, SUS)
kiwamu.izumi@LIGO.ORG - posted 16:54, Tuesday 16 February 2016 - last comment - 20:35, Wednesday 17 February 2016(25575)
ESD bias voltage sign-flipped on ETMX and ETMY

Jeff, Darkhand, Kiwamu,

We have been meaning to do this, but kept missing a chance to do. Today we have fliiped the sign of the ESD bias voltage both on ETMX and ETMY.

This alog only describes what we did on the digital front end models. We will perform a set of confirmation measurement and verify the H1 DARM model later.


See alog 22135 for a concise summary of the bias flip.

[Bias flip on ETMY ]

[Bias flip on ETMX]

Comments related to this report
kiwamu.izumi@LIGO.ORG - 11:41, Wednesday 17 February 2016 (25584)

We took open loop and Pcal sweep measurements in nominal low noise after the biases were flipped. They reside at:

  • /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/DARMOLGTFs/2016-02-16_H1_DARM_OLGTF_7to1200Hz.xml
  • /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/PCAL/2016-02-16_PCALY2DARMTF_7to1200Hz.xml

Darkhan will process the data later.

P.S.

I have updated the SDF accordingly for SUS-ETMX and ETMY and CAL-CS when the interferometer was in nominal low noise.

darkhan.tuyenbayev@LIGO.ORG - 20:35, Wednesday 17 February 2016 (25604)CAL

Kiwamu, Darkhan,

Summary

Our analysis of a DARM OLG TF and a PCALY  to DARM TF measurements taken after the ESD bias sign flip on Feb 16, 2016 showed that:

  • the gain of the sensing function has reduced by about 4 % since it was measured on Jan 7, 2016 (see attachment 4); it looks like the change is mostly non frequency dependent;
  • the actuation function measurement over the O1 actuation model show a frequency dependent residual(see attachment 5), we believe that this discrepancy is coming from a new LVLN ESD driver electronics TF being different from a previous one;
  • new measurements of the ESD driver electonics have to be taken to account for the hardware updates in the front end filters (SUSETMX/Y) and the Matlab DARM model.

Disscussion (actuation function)

The ETM ESD drivers' electronics and front-end FOTON filters associated with the ESD responses were recently updated, see LHO alogs 25468, 25485. Since the front end filter's do not perfectly cancel the ESD response, in the Matlab parameter files we used a better approximated ZPK responses that are based on the old ESD electronics measurements. Since currently we do not have TF measurements for the new ESD driver electronics, we have removed all of the compensations (for the non-perfect front-end filters) from the Matlab analysis of the DARM and PCALY to DARM TF measurements.

Measurement files, scripts

DARM OLG TF and PCALY to DARM TF measurements have been committed to CalSVN:

Runs/PostO1/H1/Measurements/DARMOLGTFs/2016-02-16_H1_DARM_OLGTF_*.txt
Runs/PostO1/H1/Measurements/PCAL/2016-02-16_PCALY2DARMTF_*.txt

Up to date filter files have been copied to

Common/H1CalFilterArchive/h1omc/H1OMC_1125881488.txt
Common/H1CalFilterArchive/h1susetmy/H1SUSETMY_1126240802.txt

DARM parameter file and comparison script have been committed to

Runs/PostO1/H1/Scripts/DARMOLGTFs/CompareDARMOLGTFs_O1andPostO1.m
Runs/PostO1/H1/Scripts/DARMOLGTFs/H1DARMparams_1139722878.m

Results (plots) are in

Runs/PostO1/H1/Results/DARMOLGTFs/2016-02-16_*.pdf

Non-image files attached to this comment
Displaying reports 61201-61220 of 86134.Go to page Start 3057 3058 3059 3060 3061 3062 3063 3064 3065 End