Displaying reports 66681-66700 of 83069.Go to page Start 3331 3332 3333 3334 3335 3336 3337 3338 3339 End
Reports until 04:58, Saturday 21 February 2015
H1 CAL (ISC, SUS)
kiwamu.izumi@LIGO.ORG - posted 04:58, Saturday 21 February 2015 - last comment - 10:00, Wednesday 04 March 2015(16843)
DARM calibration finally updated (crossfinger !)

I am concluding that the scale factor in the original calibration (alog 16698) was underestimated by a factor of about 2.4 in 2 - 20 Hz frequency band (meaning, the DARM spectra we had collected were too good). This was due to my inaccurate estimation of the ESD actuation response.

For the frequency region above 20 Hz, it has been underestimated by a factor of 3.2 when the PSL power stayed at 2.8 W and the same DARM offset was used. This was due to the inaccuracy in the ESD propagating into the sensing factor and also inaccuracy in the UGF location. I did not try to track how the sensing calibration should have been compensated as a function of the PSL power or the DARM offset (alog 16726).

I have updated the CAL-CS online calibration coefficients accordingly in both the sensing and actuation paths.

Pcal_Y seems to still indicate that the DARM spectrum is consistently too good by 40-65 %.



(ETMX response agreed the sus model by 40 %)

The day before yesterday, I had a chance to repeat the calibration of the ESD response of ETMX by locking the X arm with the IR laser. Comparison with ITMX at 13 Hz gave me an ESD response of 6.32 x 10-16 m/cnts in ETMX at 13 Hz. This is 1.4 times larger than the expected than the suspension model. Since I used alpha of 2.0 x10-10 N/V2 in the model, the measured response corresponds to a slightly larger alpha of 2.8x10-10 N/V2. With the right force coefficient of -124518.4 cnts applied on ETMX, I tested both the linearized actuation and non-linearized. They showed almost same strength in a frequency band of 10 - 59 Hz as expected but with the linearized version somewhat stronger by 3-ish % (see the attached) presumably due to the charge on the test mass.

Since the change between the linearized and non-linerized actuations is so small, I neglected this effect and kept using the transfer coefficient of the non-linarized version at 13 Hz.

(Estimation of the DARM optical gain)

Using the measured data taken by Alexa (alog 16805), I estimated the optical gain of the DC read out to be 9.09x10-7 cnts/m. To get this number, I first extrapolated the ESD response to some frequencies at around 20 Hz. Since the loop shape is already known, fitting of the open loop gives me the optical gain. I did eye-fitting this time. The UGF was at around 23 Hz in this particular data.

Since I was able to lock the interferometer at 2.8 W with the DC read out tonight, I cross-checked the DARM open loop. Running a swept sine, I confirmed that it sill kept the same UGF (see the attached below). Good.

(Comparison with Pcal)

First of all, one thing I have to mention is that, in an alog (alog 16781) describing the comparison between LSC-DARM_IN1 and PCAL is not a fair comparison because we know that LSC_DARM_IN1 was not well-calibrated. I checked the CAL-DELTAL_EXTERNAL_DQ at this particular time, but unfortunately the spectrum did not look reasonable probably because I was in the middle of changing some parameters in the CAL-CS. Instead, I looked into a different lock stretch at Feb-02, 5:13:11 UTC with the same IMC incident power of 2.8 W. The Pcal reported greater displacement by a factor of approximately 4.6 (see the attached below).

If I applied the new accurate sensing calibration, the discrepancy would have been a factor of 1.45 or 45% with the Pcal higher than the DARM spectrum.

To double check it, I checked the Pcal again during one of today's lock stretches at Feb-21, 10:04:05 UTC. One thing we have to pay attention is that the Pcal excitation frequency is now shifted to 540.7 Hz (alog 16815). I used the Pcal calibration formula that Sudartian posted in alog 16718 to get the displacement. The ratio between the Pcal and DARM spectrum was about 1.65 or 65% with the Pcal greater than the DARM spectrum. Even though the ratio is slightly different from 8 days ago or so, it still indicates that the DARM calibration is too good by several 10%.

The other excitation at 36.7 Hz (alog 16815) did not have signal-to-noise ratio more than 2 in the DARM spectrum due to high noise in this frequency region and therefore I did not use it this time. Nevertheless, the Pcal at this frequency was also greater as well. So the relation between Pcal and DARM spectrum is qualitatively consistent.

Images attached to this report
Non-image files attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 15:47, Friday 27 February 2015 (16982)CAL, ISC

Here is a fresh DARM spectrum (from 2015-02-26 10:21:50 UTC) compared with the GWINC prediction. Between 1 and 3 kHz (where the spectrum looks reasonably clean and has the right shape for shot noise), the agreement looks good.

GWINC reports 9 Mpc from this measurement.

Images attached to this comment
Non-image files attached to this comment
kiwamu.izumi@LIGO.ORG - 10:00, Wednesday 04 March 2015 (17069)

This is another detail point of this calibration log (for my self-justification).

In the ISC call last Friday, people pointed out that the first Pcal plot (link to the plot ) seemed greater by a factor of 10-ish than the calibrated DARM. Here, I explain that they don't differ by a factor of 10 but a factor of 4.6 as I declared in the original alog.

  • Pcal line at 104.75 Hz = 2.07566 x 10-16 m/sqrtHz
  • DARM spectrum at 104.75 Hz = 4.49421 x 10-17 m/sqrtHz

To be celar, I attach a zoomed version of the previous plot. See below.

Taking the ratio of Pcal/DARM, I again confrimed that the ratio is 4.6185. This is the number I quoted in the original alog. Here, I repeat a conclusion I said in the original alog: since we now know that the DARM calibration was off by a factor of 3.18 on Feb 12th, if we apply this correction the descrepancy between Pcal and DARM would have been a factor of 1.45 or 45 % with the Pcal greater.

Images attached to this comment
H1 AOS
sheila.dwyer@LIGO.ORG - posted 23:38, Friday 20 February 2015 - last comment - 20:12, Saturday 21 February 2015(16841)
spectrum tonight

Alexa, Sheila, Dan, Evan, Kiwamu

Tonight we have had good locking.  The take home message tonight was that our noise changes with aligment, and so we think that we need to spend some time getting some ASC going (or at least a reproducible alingment)  before we can make much progress on noise hunting.  (see alog 16839)

 We moved SR2, the difference between the noise spectrum before and after can probably be explained by the alignment depent noise rather than by reducing the rubbing (see alogs 16831 and 16811).  The new positions are shown in the attahed screen shot.  The SR3 OPLEV is not alinged any more.     If someone wants to use the OpLev over the weekend, you will have to go back to the old alingment of SR2+3. 

Turning on the OMC dither alingment improved the spectrum from 20-70 Hz in a way that is reproducble.  The main improvement in the noise tonight came from alinging IM4, which resulted in the best spectrum we have had so far around 100 Hz.  Note, the attached spectra are not calibrated!

Images attached to this report
Comments related to this report
daniel.hoak@LIGO.ORG - 23:47, Friday 20 February 2015 (16842)

To add to the expanding ecology of H1 noise curves, here is a progression of our 2.8W locks for the past week and a half.

Also tonight Sheila has added the ETMY bounce mode damping to the Guardian with gain of -100.  This has been working very well, the bounce mode is the lowest it's ever been.

Images attached to this comment
evan.hall@LIGO.ORG - 20:12, Saturday 21 February 2015 (16849)

Just out of curiosity, here is a rough estimate of the calibrated DARM spectrum for the 2.8 W lock. This was done assuming the spectrum is shot-noise limited above 1 kHz (except for the bump).

Non-image files attached to this comment
H1 ISC
evan.hall@LIGO.ORG - posted 23:10, Friday 20 February 2015 (16839)
Some ASC work during full lock

Sheila, Alexa, Dan, Evan

Summary

Tonight on dc readout, we started to reduce the coupling of alignment fluctuations into DARM by closing some more ASC loops. We focused mainly on the input and power-recycling optics.

During this work, the lowest value of REFL_A_LF observed was 0.4 ct (compared with 21 ct on resonance), meaning the interferometer visibility is 98%. The highest arm power observed was 1150× single-arm buildup, meaning the interferometer recycling gain is 34 W/W.

Details

List of loops, and things tried:

H1 ISC
alexan.staley@LIGO.ORG - posted 23:02, Friday 20 February 2015 - last comment - 05:30, Saturday 21 February 2015(16840)
An attempt at DARM with more phase

Alexa, Sheila, Evan, Dan

Peter had noted that our suspension compenstation for the LSC DARM filter was different than the one used at LLO. In his plot LHO#16728 he had actually missed a Lead filter at 200 Hz (FM9) that we turn on once we are on RF DARM. See new sus compenstation comparison plot. Even with this lead filer on, we still do not have as much phase as Livingston.

Today, I loaded LLO's suspension compenstation filter into FM1 of LSC DARM. We tried enaging this for ALS DIFF but immediately saturared L3. Our next plan in attempt to acquire more phase margin is to develop a filter which can be engaged along with the lead filter (FM9) once we are on RF DARM with our original sus compensation filter (FM8), and see if this causes saturation. TBD.

Images attached to this report
Comments related to this report
peter.fritschel@LIGO.ORG - 05:30, Saturday 21 February 2015 (16844)

Did you include the stopband (notch) filter for the violin mode fundamentals? If not, perhaps these were saturating L3?

H1 CDS
sheila.dwyer@LIGO.ORG - posted 20:51, Friday 20 February 2015 - last comment - 13:46, Saturday 21 February 2015(16838)
what happened to z audio?

Before tuesday, we had been listening to IFO channels through the computer speakers using z audio.  It seems like z audio has disapeared. 

Comments related to this report
jameson.rollins@LIGO.ORG - 13:39, Saturday 21 February 2015 (16845)

Can you be more specific?  What's the error message?

jameson.rollins@LIGO.ORG - 13:46, Saturday 21 February 2015 (16846)

Fixed.  Somehow the command was acceidentally removed in some recent command parsing restructuring.  It should be back to working now.

H1 SUS (ISC, SUS)
sheila.dwyer@LIGO.ORG - posted 17:40, Friday 20 February 2015 (16831)
SRC alignment, rubbing vs clipping

Since Betsy found out that SR2 is rubbing at its nominal alignment, (alog 16811), I've tried to investigate if we can move SR2 so that it is not rubbing without introducing clipping.  This was done by moving SR2 pitch, then adjusting SR3 to center on AS_C.  The attached plot shows the power on each of the PDs we have at the AS port, each PD is normalized to the mean powers at different alingments so they can be displayed on the same plot.  While we get some clipping on AS_C and AS_A when we are in the non rubbing zone, happily the best location for the OMC QPDs are in the middle of the SR2 alingments where betsy says there should not be clipping. 

Keita had previoulsy set the alingment of the SRC cavity and the pios to AS_C (alog 15145 ).

Images attached to this report
H1 ISC
eleanor.king@LIGO.ORG - posted 17:01, Friday 20 February 2015 (16837)
Preparations for SRC length measurement

Dave O, Evan, Elli

This morning we prepared for a measurement of the SRC length we plan to take tomorrow.  We were working on IOT2R.  We realigned the Auxiliary laser beam going into HAM1 so that in follows the reflection of the carrier from the PRM onto IOT2R.  This realigned the Aux laser beam returning frm HAM1 onto the 1611 photodiode on IOT2R.  The beat note of the Aux laser and carrier is -34dBm, the same as what we saw in December.  We tried locking the beat note to the spectrum analyser but ran out of LVEA time, so this is a job for tomorrow the settings were the same as used in December.

H1 SEI
hugh.radkins@LIGO.ORG - posted 16:13, Friday 20 February 2015 (16836)
HEPI Pump Servo Alarm Levels tightened up--Please respond

While we had been playing with things, I kept the alarm levels a little sloppy but now that we'll likely leave this alone for a time, I've closed down the range of operating pressures.

The alarm handler will alarm (as it has for some time) at differential pressures outside of +-2PSI.  The servo should have no problems keeping the pressure within that range.  Further it will alarm MAJOR at +- 5 psi.  If the minor alarm goes off and stays out of major alarm, it is likely the servo has frozen or someone left it in manual mode.  Please address asap and feel free to seek realtime help from me.  There is an OPS wiki too.  If the alarm is ignored, an avoidable HEPI trip will likely be the result.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 15:57, Friday 20 February 2015 (16835)
Ops Day Shift Summary
LVEA: Laser Hazard
Observation Bit: Commissioning  

07:15 Cris & Karen – Cleaning in the LVEA
07:15 Jodi – In the LVEA
07:52 Corey – Working in the Squeezer Bay
08:05 Elli & Dave – Working on IOT2R 
08:20 Jim – Running TFs on HAM4
10:00 Corey – Out of the Squeezer Bay
11:00 Kyle – Going to HAM5 area to get bolts for HAM1
11:14 Kyle – Out of the LVEA
11:17 Keita – Going into the LVEA to look for 3IFO parts
11:21 - Adjusted the ISS diffracted power from 5.2% to 8.1%
11:35 Keita – Out of the LVEA
12:13 Elli & Dave – Out of the LVEA
12:49 Ed – Retrieving totes from Mid-Y
13:21 John, Bubba, & Kyle – Going to Mid stations and end stations to check the weather stations
13:42 Dan & UM Students – Going to LVEA roof. 
13:54 Ed – Opening high-bay roll-up door to bring in totes. 
14:10 Ed – Going back to Mid-Y
14:30 Ed – Back from Mid-Y
15:05 John, Bubba, & Kyle – Back from mid and end stations
LHO VE
kyle.ryan@LIGO.ORG - posted 15:52, Friday 20 February 2015 (16834)
~1330 -1500 hrs. local -> entered exited VEAs
Looking for missing VE chamber door bolts! -> Also, noticed X-end turbo pump controller still energized from most recent pump down (fan has been running unnecessarily) -> Turned off controller and brushed up against OPLEV pier accidentally in the process
LHO VE
kyle.ryan@LIGO.ORG - posted 15:44, Friday 20 February 2015 (16833)
~0900 - 1000 -> Climbed on and around HAM1
Finished bolting HAM1 East door -> Noticed West door also missing half of its bolts -> Will need to bolt West door Monday morning for anticipated pump of HAM1 on Tuesday
LHO General (PEM)
dale.ingram@LIGO.ORG - posted 15:22, Friday 20 February 2015 - last comment - 14:05, Saturday 21 February 2015(16832)
Hanford site seismic
Several commissioners feel that our new seismic defenses leave H1 insensitive enough to truck traffic that our Hanford site contacts no longer need to email me weekly with reports of their levels of activity.  A quick glance at the 1-3Hz seismic trace in the control room will always settle the question of whether the trucks are hauling or not.    

We've built up a good bank of contacts related to site operations.  Feel free to email me any time if you have questions about the possibility of earth-shaking things occurring near LHO.  
Comments related to this report
jeffrey.kissel@LIGO.ORG - 14:05, Saturday 21 February 2015 (16847)DetChar, PEM, SEI
Dale -- is this a suggestion for a study? D'you have the past ~6 months worth of weekly reports from these contacts? If so, we can corroborate their reports against our seismic data to better quantify that when they say they're doing "X" on site in a given week, then we see "Y" amount of noise in the BLRMS channels (or "Z" amplitude in spectra) at these times of day.

This would be a fun DetChar exercise, and prove the point once and for all with a systematic study...

I ask because doing the opposite, namely, finding that the IFO is noisey, (asking / being able to prove) whether its because of the ground motion, and then remembering to ask you for "what's going on this week at the Hanford reservation?" is pretty tough.

(Unfortunately or thankfully, we don't have LLO's pleasure of proving that loggers surrounding the corner station to our "powerful new seismic defenses," are like mosquitoes are to a brick wall: see LLO aLOG 15797 or LLO aLOG 15634).
H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 11:21, Friday 20 February 2015 (16830)
Adjust ISS Power
Adjusted ISS diffracted power from ~ 5% to ~ 8%.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 11:12, Friday 20 February 2015 (16829)
08:30 Meeting Minutes
  Estimates are at least 10 working days needed to complete the 3IFO tasks before the end of March. To reach this goal, Tuesday’s and Thursday’s will be open access to LVEA and VEAs and noisy work (craning, forklifts, etc.) will be permitted between 08:00 and 16:00. During this time, the LVEA and VEAs can be transitioned to Laser Safe as needed. Always check in with the operator before starting a task.
  
The 08:00 to 10:00 noise windows are suspended while the extended Tuesday and Thursday noise hours are in effect.
 
Summary: No commissioning and noisy work on Tuesday and Thursday between 08:00 and 16:00. Commissioning during all other hours. These times can be altered due to special requirements, with agreement of the commissioners.
 
Fred brought up the need to review and refine the alarms, alarm handlers, and system monitoring. Fred asked that that the staff think about how these systems can be improved. This will be the subject of the next Science Team meeting.    

Tuesday 02/24 - GV5 and GV7 will be closed to support the pump down of HAM1.
Kyle – will be installing the remaining bolts on the HAM1 doors. 
Filiberto – Will be shutting down the Test Stand in the West Bay area to prep for rack removal.
Jim – running TFs on HAM4
    
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 07:53, Friday 20 February 2015 (16827)
CDS model and DAQ restart report, Thursday 19th February 2015

model restarts logged for Thu 19/Feb/2015
2015_02_19 07:56 h1fw0
2015_02_19 16:34 h1nds1

Two unexpected restarts, nds1 most probably due to request overload. Conlog frequently changing channels report attached.

Non-image files attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 00:59, Friday 20 February 2015 - last comment - 09:43, Friday 20 February 2015(16825)
IR find is better, guardian and tidal locklosses, alingment work

Dan, Sheila, Evan, Jeff, Alexa

Tonight locked many times (on RF) but didn't stay locked verry long.  We found two new lockloss causes that were relatively easy to solve:

During one of our short locks early in he evening ,  we made an attempt to align the green to the arm cavities after the DHARD WFS had come on. For the X arm the only thing we needed to do to get a good build up was move the TMS, we saw the spot move on the ITMX green camera and updated the spot positions for the green WFS (248.3 for PITCH, and 354.8 for YAW).  For the Y arm we saw that moving TMS was not good enough, we needed to also adjust QPD offsets.  We lost the lock in the middle of this process.  Note: the recycling gain tonight was low, around 25, but we think that having the green co-alinged even for this low build up would be better than our original situation.

During the earth quake we have spent some time on the new COMM IR search state that evan wrote.  We modified it, it is now 100% successful, but it can take a couple of minutes (generally under 5).  This is still faster on average than having a human do it, and we can think about something else while this is working now.  

Images attached to this report
Comments related to this report
daniel.hoak@LIGO.ORG - 01:04, Friday 20 February 2015 (16826)

Here are the plots that tell the tidal story.  The offset to the {X,Y}_COMM_ERR filter banks is supposed to be updated by the TIDAL_HACK Guardian; this provides the error signal which is controlled through the SUS and ultimately offloaded to HEPI.  This offset was turned off for the X-end on Tuesday, which is why the X_COMM_ERR output is zero.  At the same time the HACK Guardian, which takes the DC component of IMC_F and writes this to the COMM_ERR offsets, was turned off, which is why the output of Y_COMM_ERR is a nonzero constant.  The Y_COMM_CTRL filter bank was happily integrating this constant off to infinity whenever the arms were locked.  HEPI was still getting some input from the SUS drives but it was, as you might expect, not helpful.

First plot is today, we lost lock because IMC_F (lower left corner) was railing at the limit of the VCO, something like >2000 counts (calibrated to kHz, so that's the 2MHz VCO range).

Second plot is the 2-hour lock from last week, when the IMC_F output was small and steady.  The low-frequency signal was being offloaded to HEPI, the COMM_ERR outputs were nonzero.

Images attached to this comment
jameson.rollins@LIGO.ORG - 09:43, Friday 20 February 2015 (16828)

It looks like the TIDAL_HACK guardian module does not define an initial request, meaning that it will come up with REQUEST = NONE, and the system won't leave the INIT state.  This is why the TIDAL_HACK node wasn't doing anything after the recent guardian restarts.

I suggest setting:

request = 'COPY_AND_PASTE'

in that module, so that when the node restarts it always goes back into the appropriate state.

Displaying reports 66681-66700 of 83069.Go to page Start 3331 3332 3333 3334 3335 3336 3337 3338 3339 End