Displaying reports 61261-61280 of 86521.Go to page Start 3060 3061 3062 3063 3064 3065 3066 3067 3068 End
Reports until 18:59, Tuesday 08 March 2016
LHO VE
kyle.ryan@LIGO.ORG - posted 18:59, Tuesday 08 March 2016 - last comment - 17:05, Wednesday 09 March 2016(25947)
YBM/XBM/Diagonal vent/pump prepardness activities
Kyle. Gerardo, Chandra 

Gerardo -> Installed 12" CFF at HAM10 D8 and gauge pair isolation valve on BSC4 

Chandra -> R&R LVEA Turbo levitation batteries 

Kyle -> Drilled and tapped holes, mounted scroll pump local to Diagonal Turbo and upgraded gauge controller on Diagonal Turbo 

Kyle, Chandra -> Ran QDP80s, YBM, XBM and Diagoanl Turbos and vent/purge air supply (KOBELCO).  The KOBELCO displayed a "HIGH LUBE OIL TEMP" Warning after having run for a while.  Chandra noticed that the chilled water booster pump was off and that the output pressure once on was only 60psi (this may be the result of a reduced frequency running of the chilled water circulating pump - nominally this would be 90 psi - we need to investigate)  The measured dewpoint after > 1 hour of run time was <-30C.  Gerardo noticed that the Diagonal volume was still left connected to the purge air header from when it had last been purged, the isolation valve was then closed.

NOTE: The XBM Turbo spun up to full RPM but tripped off during the braking phase.  This Turbo has a history of high vibration - typically during the accelerating phase.  

Comments related to this report
kyle.ryan@LIGO.ORG - 19:52, Tuesday 08 March 2016 (25949)
The Turbo pump controllers are being left energized overnight in the LVEA to allow the Turbo rotors to come to a full stop
chandra.romel@LIGO.ORG - 17:05, Wednesday 09 March 2016 (25968)
No FRS required. Lower than expected pressure in output from booster pump in chilled water system is likely due to difference in building chilled water pressure (variable speed pumps). 
H1 General (DetChar)
soren.schlassa@LIGO.ORG - posted 16:55, Tuesday 08 March 2016 - last comment - 17:10, Tuesday 08 March 2016(25944)
Line at 47.683Hz in stochastic O1 analysis
A line at 47.683 Hz has appeared in the output of the stochastic O1 (time shifted) analysis. We have used the coherence tool to search for look for the source of this line in H1 and L1.

The line at 47.683 Hz appears very clearly in H1 in the h(t) coherence with H1:PEM-EY_MAG_EBAY_SEIRACK_X_DQ (week 13 example attached) and H1:PEM-EY_MAG_EBAY_SEIRACK_Y_DQ, in weeks 12, 13, 14, 16.

It also appears clearly in the L1 h(t) coherence, apparently associated with some other lines (eg, 47.42Hz) in weeks 5-10, 14, and 16 in these channels:

L1:SUS-ETMX_L1_WIT_P_DQ (week 5 example attached)
L1:SUS-ETMX_L1_WIT_L_DQ
L1:SUS-ETMX_L1_WIT_Y_DQ
L1:PEM-EX_MAINSMON_EBAY_3_DQ (week 5 example attached)
L1:PEM-EX_MAINSMON_EBAY_QUAD_SUM_DQ
L1:PEM-EY_MAG_EBAY_SUSRACK_X_DQ 
Images attached to this report
Comments related to this report
keith.riles@LIGO.ORG - 17:10, Tuesday 08 March 2016 (25945)DetChar
These lines are also visible in the run-averaged spectra for H1 and L1.
See attached figures (ignore the S6 labels in the legend, corresponding
to traces that are off-scale). 

Can anyone think of a device, common to both observatories, that 
produces such a frequency, e.g., a flat-screen monitor?
Images attached to this comment
H1 SEI
filiberto.clara@LIGO.ORG - posted 16:44, Tuesday 08 March 2016 (25943)
Capacitive Position Sensor Timing Fanout Installation

Finished the wiring and installation of the electronics for the new CPS timing distribution at EX, EY, and LVEA. CPS interface units need to be modified before switching to the new timing distribution.

H1 SUS
betsy.weaver@LIGO.ORG - posted 16:32, Tuesday 08 March 2016 (25942)
Weekly ETM charge measurements

I was only able to take the ETMY charge measurements today.  I've processed the results, and the last 2 weeks of data that others have taken.

Plots pending...

H1 SYS
betsy.weaver@LIGO.ORG - posted 15:56, Tuesday 08 March 2016 (25940)
Resonance wiki updated

At Keita's request, I've added the summarized table info of modeled optic body modes from alog 20513 to the Resonance wiki.

 

Recall, the RESONANCE WIKI is here.
 

LHO VE (FMP, SYS, VE)
richard.mccarthy@LIGO.ORG - posted 15:37, Tuesday 08 March 2016 (25938)
Installed New Vacuum control system at EX
Per workpermit 5758 installed the new Beckhoff based vacuum control chassis and computer.  There were a couple of hardware issues.  First was the polarity of the 4-20ma inputs.  One set of 4 for the fan vibration monitors were fine but we had to swap the 3 for vacuum LN2 gauges.  Also plugged the Watchdog shorting connector in backwards which prevented the LN2 control valve from operating.  Once we fixed those issues the hardware and Beckhoff software worked fine.  The next problem was the gateway computer.  Some files needed to be modified to allow the channels to pass. I will let other comment on this.

For now the system is running and screens are being modified so the users will not see much difference.
H1 SEI (OpsInfo)
thomas.shaffer@LIGO.ORG - posted 15:14, Tuesday 08 March 2016 (25936)
Script to turn the SEI Sensor Correction on or off for STS Recentering

I wrote a quick script that will change all of the gains in the appropriate degrees of freedom for the SEI Corner Station sensor correction. The gains should be 0 or OFF when recentering the STS, and then turned back ON after (assuming the chambers are up). I imagine there will be more guidence for operators to do this in the future.

The script can be found in (userapps)/isi/h1/scripts/Toggle_CS_Sensor_Correction.py

 

 

thomas.shaffer@opsws10:/opt/rtcds/userapps/release/isi/h1/scripts$ ./Toggle_CS_Sensor_Correction.py -h
usage: Toggle_CS_Sensor_Correction.py [-h] ON_or_OFF

positional arguments:
  ON_or_OFF   1 or 0 to turn the gain ON or OFF respectively

optional arguments:
  -h, --help  show this help message and exit
 

 



			
			
H1 SEI (SUS)
hugh.radkins@LIGO.ORG - posted 14:14, Tuesday 08 March 2016 (25934)
LHO BSC ISI Models Updated--Channel Data Rate Change**

WP 5765 See T1600062  SEI log 897

Changed data storage rate for BSC:

1) ISI-optic_STi_MASTER_H(V)j_DRIVE & ST2_BLND_dof_GS13_CUR_IN1

This change means that for the next week or so, inquiries of these channels for times from ~5 days ago to before the restart will need to be via nds2.  And, one must avoid selecting a request or data that spans the change.  Middle of a maintenance day...maybe that should just be avoided anyway.

2) Increased allowable saturations on L4Cs, GS13s & ACTs to reduce unwarranted tripping.

3) Replaced some utility channels with lower case characters with upper case.

4) Replaced a momentary  with LONG_PULSE for STS2 mass centering function.

5) Added SUS Point calculation blocks (detailed in 25913.) ISI will take the overhead of calculating this to ease the load of the SUS model.

6) Added Stage2 senscorr DQ channels for T240 & CPS.

LHO General
bubba.gateley@LIGO.ORG - posted 11:44, Tuesday 08 March 2016 (25933)
LVEA Main Crane Rail Shimming
The LVEA main crane rail shimming as suggested by the survey crew from Duane Hartman & Associates Inc. has been completed. A copy of the shim changes will be entered in the DCC soon.
H1 TCS (TCS)
aidan.brooks@LIGO.ORG - posted 10:14, Tuesday 08 March 2016 - last comment - 18:56, Tuesday 08 March 2016(25932)
Nominal TCS power levels for O2 - ITM substrate lens only

The attached plot (and script) shows the nominal TCS power levels required for O2 to correct for just the ITM substrate lenses.

The following values are assumed:

The bottom line is that we will cease to need central heating around 45W on ITMX and 30W on ITMY and will need to start using the RHs to compensate for the thermal lenses. No consideration is yet given to HOM correction with annular CO2 heating.

 
Subject: Re: RC as-built design
Date: May 14, 2015 at 7:54:37 PM EDT

Hi All,

The value of the thermal lens that was always used when adjusting the cavities is 50 km.  

The issue which caused all of the confusion last summer was one of definition; i.e. what does it mean to have a 50 km thermal lens.  The plots Muzammil put together, on which the decision to include the thermal lens was based, modeled the thermal lens as being inside the ITM.  The model we used to adjust the optic positions had the 50 km thermal lens immediately in front of the ITM.  The effective focal length in the two cases differs by a factor of n (the index of refraction), with it being stronger in the model which was used to calculate the positions.  Because of this the positions were tuned to have a slightly stronger thermal lens than was originally decided on based on Muzammil's plots.  

Fortunately, Lisa and I discovered that this is essentially a non-issue since the length changes needed to tune for the two different thermal lenses are less than the length changes needed to compensate for tolerances in the measured radii of curvature of the optics.  
 
Images attached to this report
Non-image files attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 18:56, Tuesday 08 March 2016 (25946)

Thank you Aidan for working on this.

Speaking of the thermal lensing, we (the LHO crews) have been discussing a possible TCS pre-loading strategy. Here are some summary points of our (future) strategy:

  • We dial the ITMY ring heater to the value that is optimized for 50 W PSL power. According to your plot, a ring heater power of 1.3 W seems the optimum.
    • We let it stay there all the time regardless of whether the interferometer is locked or not.
    • We do this because the ring heater can be too slow to keep up with the interferometer's thermal state
  • On the other hand, we do not heat up the ITMX ring heater (at least at the beginning of the test).
    • Perhaps we will perform a fine adjustment later with the fully locked interferometer with 50 W input.
  • Before the interferometer is locked, we engage both CO2 lasers to pre-heat the interferometer.
    • CO2X will be at 0.5 W according to your plot
    • CO2Y will be at 0.3 W according to your plot
  • Once the interferometer is locked and starts powering up, we turn off the CO2 lasers.
    • For the early phase, we are thinking of a simple power down with a step function.
    • As a next step, we will attempt transient compensation by applying pre-calculated CO2 requested power.
    • Cao has already looked into this transient compensation issue and had a matlab code ready to calculate various configurations.
  • We can play with the ETM ring heaters to see if we can maneuver away from the parametric instabilities.
    • I have not done any calculation for this yet.
  • As soon as the interferometer is unlocked, we set the CO2 back to the pre-heat settings in order not to cool down the interferometer.

Any comments/questions are welcome.

H1 SEI
thomas.shaffer@LIGO.ORG - posted 09:33, Tuesday 08 March 2016 (25931)
T240 Centering FAMIS #4366 and Bonus STS

All T240s prrof masses that within healthy range (< 0.3 [V]). Great!


Here's a list of how they're doing just in case you care:
ETMX T240 1 DOF X/U = 0.077 [V]
ETMX T240 1 DOF Y/V = 0.094 [V]
ETMX T240 1 DOF Z/W = 0.119 [V]
ETMX T240 2 DOF X/U = -0.199 [V]
ETMX T240 2 DOF Y/V = -0.246 [V]
ETMX T240 2 DOF Z/W = -0.094 [V]
ETMX T240 3 DOF X/U = 0.093 [V]
ETMX T240 3 DOF Y/V = -0.087 [V]
ETMX T240 3 DOF Z/W = 0.06 [V]
ETMY T240 1 DOF X/U = 0.03 [V]
ETMY T240 1 DOF Y/V = -0.042 [V]
ETMY T240 1 DOF Z/W = 0.005 [V]
ETMY T240 2 DOF X/U = -0.168 [V]
ETMY T240 2 DOF Y/V = 0.029 [V]
ETMY T240 2 DOF Z/W = 0.132 [V]
ETMY T240 3 DOF X/U = -0.001 [V]
ETMY T240 3 DOF Y/V = -0.003 [V]
ETMY T240 3 DOF Z/W = 0.1 [V]
ITMX T240 1 DOF X/U = -0.023 [V]
ITMX T240 1 DOF Y/V = 0.275 [V]
ITMX T240 1 DOF Z/W = 0.202 [V]
ITMX T240 2 DOF X/U = 0.24 [V]
ITMX T240 2 DOF Y/V = 0.262 [V]
ITMX T240 2 DOF Z/W = 0.296 [V]
ITMX T240 3 DOF X/U = 0.064 [V]
ITMX T240 3 DOF Y/V = 0.247 [V]
ITMX T240 3 DOF Z/W = 0.239 [V]
ITMY T240 1 DOF X/U = 0.192 [V]
ITMY T240 1 DOF Y/V = 0.068 [V]
ITMY T240 1 DOF Z/W = 0.116 [V]
ITMY T240 2 DOF X/U = 0.196 [V]
ITMY T240 2 DOF Y/V = 0.266 [V]
ITMY T240 2 DOF Z/W = 0.214 [V]
ITMY T240 3 DOF X/U = 0.121 [V]
ITMY T240 3 DOF Y/V = 0.214 [V]
ITMY T240 3 DOF Z/W = -0.149 [V]
BS T240 1 DOF X/U = 0.054 [V]
BS T240 1 DOF Y/V = 0.091 [V]
BS T240 1 DOF Z/W = 0.22 [V]
BS T240 2 DOF X/U = 0.162 [V]
BS T240 2 DOF Y/V = 0.237 [V]
BS T240 2 DOF Z/W = 0.231 [V]
BS T240 3 DOF X/U = 0.134 [V]
BS T240 3 DOF Y/V = 0.087 [V]
BS T240 3 DOF Z/W = 0.024 [V]
 

 


 

Jim W suggested that I run the script for the STS's as well while I'm here.

There are 1 STS proof masses out of range ( > 2.0 [V] )!
STS C DOF Z/W = 3.155 [V]


All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = -0.947 [V]
STS A DOF Y/V = 0.13 [V]
STS A DOF Z/W = -0.068 [V]
STS B DOF X/U = 0.886 [V]
STS B DOF Y/V = 0.62 [V]
STS B DOF Z/W = 0.563 [V]
STS C DOF X/U = -1.536 [V]
STS C DOF Y/V = -0.929 [V]
STS EX DOF X/U = 0.516 [V]
STS EX DOF Y/V = -1.076 [V]
STS EX DOF Z/W = 0.387 [V]
STS EY DOF X/U = 0.518 [V]
STS EY DOF Y/V = 0.683 [V]
STS EY DOF Z/W = -0.266 [V]

 


 

FAMIS #4366  closed
 

LHO FMCS (CDS)
carlos.perez@LIGO.ORG - posted 06:28, Tuesday 08 March 2016 (25930)
New File Servers Deployment
As part as Tuesday maintenance today March 8, 2016 CDS system admins will be deploying a new file system ( /Ligo ) the switch over will limit the ability to use any workstation or server that mounts /Ligo until the work is completed; Once the switch over on the MSR has been done, every workstation must be updated and restarted.
H1 General
lisa.barsotti@LIGO.ORG - posted 02:57, Tuesday 08 March 2016 - last comment - 14:53, Tuesday 08 March 2016(25929)
Quick summary of today's work
Sheila, Jenne, Matt, Rob, Evan, Lisa

Several things happened today, more details will be posted later:
  • we locked several times in low noise (note: ASC in the old configuration with DC (not RF90MHz) centering, see week-end entries for more details): the best range we saw today was about ~70 Mpc, due to some peaks in the spectrum higher than usual -- the 290 Hz was particularly higher than during O1;
  • in low noise Sheila made several ISI shaking tests, Robert did some investigations in parallel as well;
  • we looked at the coupling into the OMC at full power: this measurement needs to be repeated to make sure the conclusion we get is right, as the inferred coupling to the OMC would be significantly lower than what assumed from previous measurements;
  • Jenne took some DHARD open loop transfer functions as function of the DARM offset;
  • some off-line investigations to get hints of the mystery noise happened as well, more details will follow.
Some of these things are not finished as an earthquake hit us around 10pm local time; we waited for two hours for the noise to go down again, but we couldn't really relock robustly afterwards, even when the ground motion seemed back to normal (to be investigated). Some items for our to-do-list that came up tonight (to be merged with what we already have on the control room whiteboard) are:
  • inspired by Kiwamu's analysis, modulate the vertical position of optics and look for changes in the DARM noise;
  • (new entry): look at the DARM rms, and see if there is some loop optimization that can be done to minimize it (in particular, check if rms optimization advocated by Jeff at the last commissioning workshop happened or not);
  • in-depth analysis of frequency noise, in particular look for saturations in the common mode board;
  • close the loop on this OMC coupling, and if it is real, distinguish between mode mismatch vs misalignment - if it turns out that the alignment into the OMC is bad, resurrect deacon alignment (ECR already submitted and approved).
Comments related to this report
keita.kawabe@LIGO.ORG - 14:53, Tuesday 08 March 2016 (25935)

Higher-than-before jitter coupling seems to have made a lot of excess noise peaks. See these high coherence peaks between DARM and various IMC WFS signals (only WFS DC signals are shown).

It doesn't look like the intensity noise caused by the jitter (look at low coherence between DARM and ISS second loop signal, also IM4_TRANS_SUM coherence is low even when IM4_TRANS_PIT coherence is high).

Something seems to be excited on the PSL table (look at the coherence between DARM and PSL table accelerometer).

What happened in the PSL since Feb 26 2016 16:30 UTC when the IFO was in good low noise lock?

Images attached to this comment
H1 ISC
evan.hall@LIGO.ORG - posted 01:16, Tuesday 08 March 2016 - last comment - 15:47, Tuesday 08 March 2016(25928)
DARM-to-OMC coupling at full power

Lisa, Evan

We repeated the DARM-to-OMC coupling test (25852) at full power.

Tentatively, the change in the violin mode heights with the OMC locked and unlocked suggests only a 75 % coupling into the OMC (i.e., a 25 % loss).

We are not sure why the violin mode at 502.8 Hz is fatter with the OMC locked, so we would like to repeat this test with a calibration line.

Images attached to this report
Non-image files attached to this report
Comments related to this report
koji.arai@LIGO.ORG - 15:47, Tuesday 08 March 2016 (25939)

This 502.8Hz mode seems one of the violin mode for ITMX, accoding to the wiki https://awiki.ligo-wa.caltech.edu/aLIGO/H1%20Violin%20Mode

If that's true, just to be sure, you should use one of the ETM violin modes, or ETM cal line as you mentioned.

When I was doing a beacon scan using some of the violin modes, I found that the 45MHz modulation sidebands also had finite response to the violin modes.
Assuming this came from the motion of the ITMs, I learned that I needed to use the ETM motions in order to correctly figure out the signal mode matching.

H1 ISC (ISC)
matthew.evans@LIGO.ORG - posted 23:22, Monday 07 March 2016 (25927)
DARM noise, a simple budget

I made a quick "noise budget" which accounts for most of the H1 noise with just shot noise, coating thermal noise, a 1/f mystery noise, and a 1/f^4 "other noises" curve.  This is a much poorer version of the real noise budget, but it is enough to help with the mystery noise search.

Images attached to this report
Non-image files attached to this report
Displaying reports 61261-61280 of 86521.Go to page Start 3060 3061 3062 3063 3064 3065 3066 3067 3068 End