Displaying reports 65581-65600 of 85629.Go to page Start 3276 3277 3278 3279 3280 3281 3282 3283 3284 End
Reports until 08:09, Monday 17 August 2015
LHO FMCS
bubba.gateley@LIGO.ORG - posted 08:09, Monday 17 August 2015 (20590)
Faulty compressor
Late last week we had one of the two compressors quit on the AAON unit at the staging building. See FRS 3455. This unit is designed to supplement the original 12 T Carrier chiller which also has one of the two condenser fan motors beginning to show signs of failure. See FRS 3451.

The failed compressor has been disconnected and the AAON is operating at 50% capacity which should be enough to assist the main unit enough to keep the staging building cool especially during the somewhat cooler temperatures.

The faulty parts have now been ordered and hopefully arrive before any additional triple digit temperatures.

 
H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:07, Monday 17 August 2015 (20592)
Owl Shift Summary
LVEA: Laser Hazard
IFO: UnLocked
Observation Bit: Commissioning  

All Times in UTC
07:00 Take over from Ed M.
07:00 Commissioners working on IFO
09:11 Locked at Nominal_Low_Noise – Commissioning on going 
11:09 Lock Loss – Commissioning activities
11:30 Dust counts at End-Y high
12:01 Locked at Nominal_Low_Noise – Commissioning on going 
15:00 Turn over to Travis
15:04 Lockloss - 
H1 SEI (DetChar)
nairwita.mazumder@LIGO.ORG - posted 07:43, Monday 17 August 2015 - last comment - 07:35, Friday 04 September 2015(20589)
Seismic Noise Budget Model performance for ITMY
The attached pdf contains current Stage-1 and Stage-2 NB model performance of ITMY chamber for X,Y,Z and RZ dof. 

Fig 1- ST1 ITMY X
Low frequency near microseism model performance is limited by the ground blend filter (HEPI L4C+IPS)
1-5Hz frequency band is limited by GND-STS passing through the sensor correction path
5Hz and above (upto 10Hz say) is limited by Stage-2 back reaction
Below microseism model does not match with actual performance.       (May be because of some tilt coupling??  But it looks like actual measurement is limited by the sensor noises (T240/CPS) via isolation filter. - Not sure about it)

Fig 2- ST2 ITMY X
Instead of T240 BLND OUT,  I have used T240 BLND IN as the input (stage-1 displacement) to the ST-2 model.
Though the model and measured GS13 are in agreement above blend frequency (250mHz), the shape between 1-3Hz are not same. The model output looks more like the input signal T240 BLND IN.  May be a better input noise model will work better. 
Since the stage-2 model performance above ~1Hz is highly dependent on stage-1 displacement, we can san say that the Stage-2 back reaction on stage-1 can have effect on the final performance of the model. 
Fig 3 - ST1 ITMY Y

Most of the features and model performance are same as X dof.

Fig 4 - ST2 ITMY Y

Though this one is same as ST2 ITMY X only thing I have noticed here is the actual IFO ST1 performance is better than ST2  between ~ 300-500 mHz. 

Fig 5- ST1 ITMY Z

ST-1 model performance matches the actual measurement at almost all the frequency range of interest.  
The conclusions derived for ground model and Stage-2 back reaction hold here too.   

Fig 6- ST2 ITMY Z

Unlike X and Y dof, the model performance between 60 to 250 mHz is quite good (I am still trying to figure out why this sort of discrepancy exists between these dofs ???)
At the same time the mismatch between model and actual performance above 5Hz is noticeable. Model is over estimating the actual performance here (though the model has already included stage-2 back reaction in Stage-1)
Fig 7- ST1 ITMY RZ

Apart from the limitations of the model due to ground noise at low frequencies, the performance of this stage is mostly limited by CPS sensor noise via BLEND+ISO  path.

Fig 8- ST1 ITMY RZ
   
Please DO NOT go through this figure. Still need to sort out the problems.

   
Same sort of features can be seen in almost all the BSC chambers except BS where the stage-2 controllers are not in use. 
Non-image files attached to this report
Comments related to this report
nairwita.mazumder@LIGO.ORG - 07:35, Friday 04 September 2015 (21204)SEI
T240 and GS13 sensor noise floors are added to the seismic noise budget plots.
Non-image files attached to this comment
H1 General
jeffrey.bartlett@LIGO.ORG - posted 05:18, Monday 17 August 2015 (20587)
High Dust Counts at End-Y
Have been seeing high dust counts at End-Y during evening ops shift. The counts are not that far off the normal values for End-Y, but there is no apparent cause for the spikes. Will continue to monitor.  
Images attached to this report
H1 ISC
evan.hall@LIGO.ORG - posted 04:50, Monday 17 August 2015 - last comment - 16:08, Monday 17 August 2015(20585)
DARM loop with more phase

Darkhan, Jenne, Stefan, Evan

Upon revisiting the shape of the DARM loop, we found that we had 4 dB of gain peaking from 10 Hz to 50 Hz.

That seems a bit too strong for our taste, so we took a look at the DARM suscomp filter that we've been using for the past few months. Aside from the low-frequency (<2 Hz) suspension resonance compensation and the high-frequency (>900 Hz) inversion rolloff, there is a single pole at 200 Hz.

This serves us well when locking DIFF, but in full, low-noise lock it costs us phase (not least because we also have the effect of the 350 Hz RSE pole).

Anyway, there is now a filter installed in EY L3 lock with a zero at 200 Hz and a pole at 1000 Hz in order to push this pole up to higher frequency. This gives us a modest improvement in phase margin at the DARM ugf (34° to 46°). The DARM ugf is 40 Hz or so (more or less the same as before). The EY ESD has about 16000 ct rms, mostly accumulated around 1 kHz (magenta/orange in the attached spectra show the before/after).

[In the longer term, we should just roll p/z pair into the suscomp filter, so that it rises like f essentially from 1 Hz to 1 kHz. Then put a 200 Hz pole / 1000 Hz zero pair in EX L3 lock, so as not to disturb the DIFF loop shape. However, I've put what we have so far into the guardian and it works fine.]

Darkhan and I retuned the DARM OLTF template in order to not saturate with this new loop shape. The attachment shows the before (blue) and after (red), along with the closed-loop gain and loop suppression. There's still moderate gain peaking below 20 Hz.

Images attached to this report
Non-image files attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 05:28, Monday 17 August 2015 (20588)

Also attached is new pcal sweep measurement.

Non-image files attached to this comment
betsy.weaver@LIGO.ORG - 16:08, Monday 17 August 2015 (20604)

Attached is a screen snapshot of the ETMy L3 LOCK filter bank and the corresponding CAL-CS_DARM_FE_ETMY_L3 bank, now showing the new filter.  There are still differences between the banks...

Images attached to this comment
H1 ISC (ISC)
stefan.ballmer@LIGO.ORG - posted 02:08, Monday 17 August 2015 - last comment - 08:13, Monday 17 August 2015(20582)
45MHz oscillator phase noise measurement
Evan, Stefan,

Evan will make a more detailed log entry with actual measurements, but here are the highlights:
- We beat the 45Mhz signal from the installed and the spare harmonic generators.
- the first odd thing was that straight out of the harmonic generators, the 45Mhz signals were out of phase by about 170deg, even though the 9MHz inputs were nicely in phase...
- We phased the two signals to be exactly in phase an stuck them into a mixer: 0.415V
- We phased the. To be exactly 90deg apart: no DC signal, and ~ 220nV/rtHz of flat  broadband noise.
- this gives 5.3e-7 rad/rtHz between the two signals.
- Assuming equal and non-coherent contributions, the phase noise of one box is thus: 3.75e-7 rad/rtHz
- If we assume that the oscillator phase noise has the same coupling as the oscillator amplitude noise (9e-2mA/RIN), we would expect 3.4e-8mA/rtHz. Thats's pretty close to what we see on ODC_DCPD_SUM.
Comments related to this report
evan.hall@LIGO.ORG - 08:13, Monday 17 August 2015 (20593)

Data attached: two amplitude noise measurements, two phase noise measurements. One set taken sending equal drive levels into the mixer, and another set taken with the rf attenuated by 5 dB.

Non-image files attached to this comment
H1 ISC
sheila.dwyer@LIGO.ORG - posted 02:03, Monday 17 August 2015 - last comment - 04:48, Monday 17 August 2015(20581)
rephasing refl 45 WFS, refl wfs sensing matrix

We had noticed last week that the refl 45 WFS were phased incorrectly, and tonight Jenne and I rephased them by moving PR3 100 counts in pitch.  This only affects the PRC2 loop.  We've locked and engaged the ASC several times since then, and this seems fine.  

While we did improve the phasing and tuned it to within 5 degrees, I is only about 9 dB higher than Q for PR3 motion.  We will need a different phasing strategy, where we phase 45 to minimize the signal from chard in one quadrature if we want to distinguish between PR3 motion and CHARD.

 C

The first two attached screenshots are the phases before we started, except that for REFL A the phase of the first quadrant was -165 not -145.  The following 2 screenshots were the phases we rephased.  For the time being we have reverted. 

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 04:48, Monday 17 August 2015 (20586)

Earlier tonight, we rephased the REFL 45 WFS to be maximally sensitive to PR3 motion, but I think that instead, we should phase them to be minimally sensitive to CHARD motion.

H1 SYS (CDS, SYS)
sheila.dwyer@LIGO.ORG - posted 01:37, Monday 17 August 2015 (20580)
making SDF greener

Jenne and I spent some time making SDF green before the enigneering run starts in the morning.  

The main things that are still showing diffs are HAM1 HPI, some violin mode damping settings on ITMY, and many diffs in CALCS.  

While we were doing this we noticed a potentially nasty trick that SDF does.  We chose some channels that should be not monitored from the list of DIFFs, and right as I was about to CONFIRM, the IFO lost lock.  A new diff showed up on the top of the list, and the channels I had intended to not mon were moved down the list, but the yellow squares stayed in the same place.  It would have been verry easy to miss this and apply the action to the wrong channels.  Jenne is putting this in bugzilla.  

H1 GRD (ISC)
evan.hall@LIGO.ORG - posted 00:58, Monday 17 August 2015 (20578)
OMC_LOCK states for adding/removing DCPD whitening

The OMC_LOCK guardian now has the states ADD_WHITENING and REMOVE_WHITENING, which do what they say on the tin. If you have one stage of whitening on, running ADD_WHITENING will turn on one more stage, etc.

They are not connected to the rest of the graph at all, so you'll have to run them manually.

They are intended to be compatible with full lock, so they can be run at any time (so long as you don't end up saturating the DCPD ADCs, of course).

H1 General
edmond.merilh@LIGO.ORG - posted 23:55, Sunday 16 August 2015 (20576)
Daily Ops Summary - Evening shift

ALL TIMES IN UTC

 

Arrived to find IFO beginning lock sequence after TJ did some PRMI alignment to help DRMI. It seems previous lock segments were on the average of about half a hour

 

LOCK LOG:

 

Evening Summary:

 


 

H1 AOS
stefan.ballmer@LIGO.ORG - posted 20:53, Sunday 16 August 2015 (20574)
The end of the last long lock
The inspiral range had trended down significantly in the last ~2h of the lock.

- Looking back at the data the spectrum showed a 1/f^2 noise floor between 15 and 150Hz. (plot 1)
- This floor was clearly generated by frequent glitches. Plot 2 shows a filtered time series for the bad time (blue, 2015/08/16 15:05 UTC) and a good time (red, 2015/08/16 13:35 UTC)
  Filter: zpk([0;0;],[1000;1000],1,"n")ellip("BandPass",6,1,80,30,200)

- Sheila noticed that both the M2 and M3 coils of the SRM were hovering around the ominous 65536cts mark, so there is the suspicion that these are SRM glitches. However I couldn't line them up convincingly... Either way, Sheila did the top stage bleed-off today, so we will see...
Images attached to this report
H1 PEM
robert.schofield@LIGO.ORG - posted 20:21, Sunday 16 August 2015 (20573)
A third vibration-sensitive site: HAM2
A third vibration-sensitive site: HAM2
 
Katie and I have shaken most chambers with shakers on cross beams (focusing on coupling through the isolation rather than scattering from the chamber walls). The figure shows that, in addition to the PSL and HAM6, HAM2 is also close to limiting DARM. Shaking by a factor of about 30 over background, measured by the GS13s in the 800-860 portion of the ISI suspension band, produces features over an order of magnitude tall in DARM.
 
Thus it may be useful to damp higher modes of the blade springs and flexures in HAM2 as well as HAM6.

Katie and I have shaken most chambers with shakers on cross beams (focusing on coupling through the isolation rather than scattering from the chamber walls). The figure shows that, in addition to the vibration senstitive PSL and HAM6, vibration at HAM2 is also close to limiting DARM. Shaking by a factor of about 30 over background, measured by the GS13s in the 800-860 portion of the ISI suspension band, produces features over an order of magnitude tall in DARM.

Thus it may be useful to damp higher modes of the blade springs and flexures in HAM2 as well as HAM6.

Katie Banowetz, Robert Schofield

Non-image files attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 18:18, Sunday 16 August 2015 (20572)
SRM offloading to M1

Evan, Sheila, Jenne, Stefan

we have been intending to offload the SRM length control to M1 (instead of M2) for some time now.  This is now done in the guardian, and is basically a copy of what was done in alog 19850.  The only difference is a 50Hz Cheby low pass, which is used as a cut off instead of a 70 Hz elliptic.  This is in the ISC_DRMI guardian now. 

I have turned off the L2P and L2Y decoupling, as I could only use very low gain with them on.  

Update:

Neither the PRM nor SRM had a true integrator in the top stage, now they both have one which we have engaged by hand, and the guardian has been edited to turn these on, which we will test after our next lockloss. 

Last update: We've tested the integrator switching on now, its fine.

H1 ISC
evan.hall@LIGO.ORG - posted 18:18, Sunday 16 August 2015 - last comment - 10:46, Monday 17 August 2015(20571)
SR3 cage servo

Sheila, Evan

Running the dc-coupled oplev servo on SR3 for long periods of time seems to be causing us grief (LHO#20519).

As an alternative, we are trying out a cage servo which feeds the witness sensor in pitch back to M2:

ezcaservo -r H1:SUS-SR3_M3_WIT_PMON -g -300 -s <SR3 M3 P witness setpoint> H1:SUS-SR3_M2_TEST_P_OFFSET

The step response of this loop has a time constant of 30 s or so.

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 01:01, Monday 17 August 2015 (20579)

Jenne and I put this cage servo into a new guardian, called SR3_CAGE_SERVO.  One hick up in this process was the fact that the gain setting that works for ezcaservo is opposite to the one that works for cdsutils.servo 

This guardian is managed by the ISC_DRMI guardian, which doesn't turn it off but does make sure that it is turned on after DRMI locks.  There are states to run the servo, turn it off, and to clear the history (clear offset). We've added this guardian to the list of guardians in IFO guardian. (That is the guardian who checks that the state of other guardians), and set the nominal state to CAGE_SERVO_RUNNING.

We've also added it to the ISC guardian overview screen.   

If misaligning SR3, this servo needs to be off.  The guardian will go to CAGE_SERVO_OFF if SR3 is misaligned. 

jameson.rollins@LIGO.ORG - 10:46, Monday 17 August 2015 (20596)

Did you guys add this new node to the overview screen?  Please let me know when you add new nodes.  All nodes have to be tracked in the infrastructure, so we need to know all nodes that are running and are being depended upon by other nodes.

H1 ISC (CAL, ISC)
stefan.ballmer@LIGO.ORG - posted 23:50, Saturday 15 August 2015 - last comment - 21:46, Sunday 16 August 2015(20560)
Calibration: Suggestion for ESD drive strangth monitoring
I made the suggestion before, but today I actually tried it:

By driving both L2 and L3 at a fixed frequency, but with a gain and phase such that their contribution cancelers in DARM, we can easily monitor (and servo, if we want) the ESD drive strength, which is expected to vary with charging.

This method has the big advantage that there are NO LARGE cal line resulting in DARM.

Here are the settings I tried:
- H1:SUS-ETMY_L2_TEST_L_EXC: drive with 300 cts at 20Hz, phase   0  deg
- H1:SUS-ETMY_L3_TEST_L_EXC: drive with 51.7cts at 20Hz, phase 134.2deg

The resulting line in DARM is only ~0.016 times the size of the line with only 1 drive. I also used the H1:SUS-ETMY_L2_DAMP_MODE7_BL filter bank to monitor the line strength. This suggests we should get on the order of 1% monitoring precision on a few second time scale - all while only producing the tiniest peak in DARM - with no up-conversion feet.

Also - since the biggest variation we see is on the microseism time scale - we should try the ESD linearization..
Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 21:46, Sunday 16 August 2015 (20575)
Attached is a time series plot of the logarithmic line strength at 20Hz. The line stayed below 10^(-1.7) for the whole 9h30min of the lock, suggesting the ESD drive never changed more than 2%.

- The surge in arm power early on was due to a test Evan did.
- The odd drop at the end corresponds to when the data got glitchy - not sure what happened there...
Images attached to this comment
H1 ISC
gabriele.vajente@LIGO.ORG - posted 18:01, Saturday 15 August 2015 - last comment - 09:08, Monday 17 August 2015(20555)
Noise at the PSL periscope peaks due to OMC misalignment

I alrady noticed yesterday that the DARM noise at the periscope peaks (200-400 Hz) was high at the beginning of the lock and then reduced over time.

The first attached plot shows a BLRMS of DARM around those peaks, starting right after reaching the low noise state. There is a clear reduction of the noise over time. The second plot shows that on a similar time scale, the OMC alignment output signal changed, mostly ANG_Y.

This seems to confirm the idea that input beam jitter at the periscope peaks is converted into intensity noise by an OMC misalignment, which changes over time.

To confirm this, I move the OMC angular loops during full lock, adding offsets of few tens of counts to the POS and ANG loops. The third plot shows the steps in the control signals. I was able to reduce the BLRMS by adding an offset of -40 to the ANG_Y loop. The fourth plot compares the DARM spectrum with (red) and without (blue) the ANG_Y offset. I should have increased the offset more. Unfortunately, I noticed that the output was hitting the limit of 300 and I stupidly increased it to 1000: but since the loop was integrating, I broke the lock since I suddenly increased the output from -300 to -1000.

However, the experiment confirms that the noise at the periscope peaks changes in amplitude with the OMC alignment, which is not optimal.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 00:34, Monday 17 August 2015 (20577)

I am not 100% sure what value Gabriele meant to leave, but I have accepted in SDF (Sheila and I are in process of clearing a bunch of diffs in SDF) the value of -30 for ANG_Y for the OMC.  I'll check with Gabriele about what value he meant to leave (his alog seems to indicate -40, but we found it at -30).

daniel.hoak@LIGO.ORG - 03:28, Monday 17 August 2015 (20583)ISC

Since we're using the QPD loops to align the OMC, it's probably better to record any change in the alignment in the QPD offsets.  I forget the channel names at the moment, but these are the offsets in the OMC QPD channels (not the same channels in the ASC models).  If the offsets are stored in the ANG and POS loops, they will have to be turned off if/when we switch to the dither alignment.  If they are recorded in the QPD filter banks it is one less thing to think about.

To summarize the OMC alignment: the QPD offsets have been tuned so the OMC is well-aligned in the low power state.  In this state, the dither error signals should be zero.  We know that as the power is increased, the QPD offsets are no longer a good alignment, especially in pitch -- this is according to the dither error signals.  We suspect the misalignment is due to some junk light that shifts the nominal alignment position on the QPDs.  Unfortunately, the misalignment is large enough that engaging the dither loops in the high power state saturates the drive to the OMC SUS.  This is why we have stuck with the QPD alignment for now...we should find a solution before O1 that allows us to use the dither loops.  The last time the alignment scheme had any attention was in late May.

Needless to say, do remember to check the drives to the OMC SUS OSEMs when changing the alignment settings, they may saturate!

gabriele.vajente@LIGO.ORG - 09:08, Monday 17 August 2015 (20595)

The offsets I left (-30) is better than 0, but not the optimal one yet. It's better to check the OMC alignment again

Displaying reports 65581-65600 of 85629.Go to page Start 3276 3277 3278 3279 3280 3281 3282 3283 3284 End