Displaying reports 43761-43780 of 84094.Go to page Start 2185 2186 2187 2188 2189 2190 2191 2192 2193 End
Reports until 21:16, Tuesday 17 April 2018
H1 ISC (ISC, SYS)
craig.cahillane@LIGO.ORG - posted 21:16, Tuesday 17 April 2018 - last comment - 18:10, Wednesday 18 April 2018(41483)
Further Electric Field Meter Prototype Characterization and Rough Displacement Noise Estimate
Craig, Niko, Georgia

Today Georgia, Niko, and I went down to Xend to take more careful measurements of the Electric Field Meter (EFM) Prototype built by Rich, Calum, and Luis.  

We drove the ISI to check if we could see the electric fields above our EFM noise floor.  We drove the ISI both vertically and horizontally until the watchdog tripped, but never saw a signal in the EFM.  This is surprising, since Rai's prototype was sensitive to ISI driving in the Y chamber.

We measured a calibration TF for both the positive X EFM sensor plate and negative X EFM sensor plate (Plot 1),
the common mode rejection from the X sensor plates (Plot 2),
and an ambient electric field ASD in the X-end chamber (Plot 3).  

Finally, I roughly estimated the ETMX displacement noise we might expect from ambient electric fields given our usual ESD setup. (Plot 4)  
The details of the calculation made to get plots 3 and 4 are in a jupyter notebook on git.ligo.org.

At 100 Hz I estimate around 10^{-22} m/rtHz displacement noise, far below our noise floor.  However, I'm getting a stronger frequency dependence than we perhaps anticipated: our measured electric field falls like f^{-1.5}, until it runs into what is probably the EFM circuit noise floor at 200 Hz.  This gives an overall displacement frequency dependence of f^{-3.5}.

Pictures are courtesy of Niko and Georgia who did all the in-chamber work today.  

Things to do:
1) Get capacitance measurement between calibration plates for a better volts to electric field TF.
2) Understand and create a noise model of the EFM circuitry.  This will probably help explain the strong frequency dependence we're seeing with some low frequency pole.
Images attached to this report
Comments related to this report
rich.abbott@LIGO.ORG - 16:59, Tuesday 17 April 2018 (41498)SYS
I ran a noise simulation of the ungrounded-plate noise spectra.  The attached image shows what would be expected from the 10^12 ohm resistance filtered by the approximately 20pF capacitance of the sense plate to the body (including amplifier input capacity).  The results at 100Hz confirm the ~200nV/rtHz associated with the asymptote of the intrinsic electronics noise of the device as seen when the sense plates are grounded.
Non-image files attached to this comment
georgia.mansell@LIGO.ORG - 19:39, Tuesday 17 April 2018 (41506)

Conclusion: we're fairly confident we are not actually driving the ISI at end-X, and this is why we don't see the associated electric fields.

As a sanity check, Craig brought the previous electric field meter (EFM) out to end-x and placed it in the chamber under the current EFM (see first two photos). We have previously detected the electric field generated by driving the ISI with this EFM (lho alog 40878).

We tried driving the locked ISI again, with increasing amplitude, at 353 Hz, and saw nothing in either EFM. We looked at the GS13 and CPS sensors, both now (first screenshot, with drive signal in the left column) and back in time, when we were driving the ISI back in March (second screenshot, again with drive signals in the left column). We see no signal associated with the drive now (right colum), while in March the drive was present in both these signals.

We checked the watchdogs, and reset the hardware watchdogs just in case, checked the ISI racks for unplugged cables, and the power supplies and are still unsure why we are not driving the ISI.

We took the old EFM out of the chamber for the night.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 09:26, Wednesday 18 April 2018 (41516)

I don't think that we can estimate the contribution to DARM from this data, since we don't have a good estimate of charge on the optic or the coupling from the EFM to the fields at the test mass.

craig.cahillane@LIGO.ORG - 18:10, Wednesday 18 April 2018 (41531)
In my estimate, I assumed that charge on the test mass is zero and the ambient electric fields at the EFM are the same as those at the test mass.
My concern is that we are just looking at EFM sensor noise and not really ambient electric fields.  It seems like we are seeing ambient electric fields below 200 Hz with a frequency dependence of f^{-1.5}.  
Many assumptions went into the estimated displacement noise, I wouldn't trust it to better than an order of magnitude.
H1 ISC (AWC)
terra.hardwick@LIGO.ORG - posted 16:36, Tuesday 17 April 2018 - last comment - 09:24, Thursday 19 April 2018(41490)
Output beam study, clipping?

Aidan, Daniel V-H., TVo, Dan B., Terra

This is the initial analysis of the HAM6 output beam scan we did last weekAttached is the overall picture, in the style of LLO's beam study.

Measurements are done in HAM6 during single bounce configuration (no TCS) either directly in beam or using pickoff. Data is then fit by varying input beam parameters and, to some degree, OM optical/path length parameters. These are compared against the original output beam design. (There is a caveats to this, see below.) Since there was large astigmatism, what I show is beam fit prioritized to fit vertical measurements. [R,w] directly after SRM for design and vertical fits shown in plot. X-axis distances are in meters from SRM.

Main points:

Caveat/to do: the design beam includes a 50km ITM lens, so I need to subtract that for more meaningful comparison; in the works.

For reference, the parameters used are:

 

Images attached to this report
Comments related to this report
terra.hardwick@LIGO.ORG - 10:20, Wednesday 18 April 2018 (41517)

Adding screen shot of raw data from beam scanner: horizontal data on top, vertical on bottom. A one-sided pedestal on the right side of top plot can be seen. This measurement was taken ~10 inches from the edge of the ISI table closest to the septum window in the beam path as it enters HAM6 from SRM to OM1.

Images attached to this comment
aidan.brooks@LIGO.ORG - 09:24, Thursday 19 April 2018 (41541)

I enhanced the bottom image [vertical cross-section of beam] and rescaled it to the same horizontal and vertical scale as the top image [horizontal cross-section of beam], then I pasted this over the top image. Horizontal cross section = thin white line. Vertical cross-section = thick black line. 

This highlights the excess power in the right hand side of the horizontal cross-section.

Images attached to this comment
H1 General
cheryl.vorvick@LIGO.ORG - posted 16:28, Tuesday 17 April 2018 (41497)
Day Summary:

Summary:

Details:

 

H1 TCS (TCS)
cheryl.vorvick@LIGO.ORG - posted 14:59, Tuesday 17 April 2018 (41496)
TCS chillers flow: 2 old channels, 2 new channels, and current state of glitching

Attached are plots of the flow rates from the flow meters (old channels) and from the TCS chillers (new channels, through RS232).  Breakdown of performance is:

Images attached to this report
LHO VE (CDS, VE)
patrick.thomas@LIGO.ORG - posted 13:46, Tuesday 17 April 2018 (41494)
Added new Inficon gauge to end Y (Y7 PT428)
WP 7491

Patrick, Richard, Dave

Everything except the DAQ has been updated and restarted. I ran into difficulty because it turned out that the new gauge required an updated version (1.3.0.0) of the ESI file. This had to be downloaded here: "https://products.inficon.com/en-us/nav-products/product/detail/bpg402-s/" (under the Downloads tab, the last item listed). Once it was downloaded I copied it to C:/TwinCAT/3.1/Config/Io/EtherCAT on h0vacey and renamed it from "ESI" to "Inficon_BPG402_V1_3_0_0.xml". For some reason this seemed to freeze TwinCAT and I had to log out and back in. It then turned out that the new version changed the names of the fields in the system manager, so I had to update my scripts to match these. This was the cause of the multiple restarts. I changed the settings of the gauge to read in Torr. I burtrestored to 11:00 am local. CP7 is recovering. Dave will restart the DAQ at the next opportunity.
H1 CDS (PSL)
david.barker@LIGO.ORG - posted 13:29, Tuesday 17 April 2018 - last comment - 14:02, Tuesday 17 April 2018(41493)
h1psliss model restarted, waiting on DAQ restart

WP7476 Fix binary IO to second-loop chassis

Keita:

h1psliss was restarted to fix binary I/O to the production second-loop chassis.

Comments related to this report
david.barker@LIGO.ORG - 14:02, Tuesday 17 April 2018 (41495)

DAQ restarted for PSL-ISS and VAC-EY work.

H1 CDS
david.barker@LIGO.ORG - posted 12:51, Tuesday 17 April 2018 - last comment - 13:27, Tuesday 17 April 2018(41491)
cell phone alarms temporarily turned off while h0veey is being rebooted
Comments related to this report
david.barker@LIGO.ORG - 13:27, Tuesday 17 April 2018 (41492)

started it again

H1 SUS (DetChar, ISC, SUS)
jeffrey.kissel@LIGO.ORG - posted 12:47, Tuesday 17 April 2018 (41488)
H1 SUS ETMY: Highest Vertical and Roll Modes after BRD Install -- Good enough? Unique Roll Mode Results...
J. Kissel

Using (at first) ring-down fitting techniques described in LHO aLOG 40098 and LLO aLOG 28503, I have attempted to characterize and assess the performance of H1 SUS ETMY's recently installed "Bounce" and Roll mode Dampers (BRDs, D1500228) which aim to reduce the Q of the highest vertical and roll modes (V4 and R4). 

While I was able to easily identify a single V4 mode and characterize its Q to be rather high, the roll mode was very evasive, and I believe has split into two, very low Q modes. 

Remember, the goal for these BRDs was to reduce the Q of the V4 and R4 modes from ~10^6 to "one to several thousand" (see pg 6 of G1600371, and thermal noise impact discussion in T1500271). 
Unclear if either BRD results are within spec: the V4 mode has a Q of 7300 (arguably higher than "several thousand"), and the R4 mode, split into two modes, have Qs of 600 and 440 (arguably lower than "one thousand," and probably undesirable to be overdamped enough to split the mode in two). 

H1 SUS ETMY's BRD manual tuning results can be found in LHO aLOG 40541.

Further Details below.

%%% V4 "Bounce" Mode Characterization %%%

I was able to clearly identify and characterize the V4 mode:

                                ETMY 

    V4 Frequency / Hz           9.726  (0.001)

    V4 Q / dimensionless        7302  (8)

(The uncertainties quoted for the Q are the 68% C.I., 1-sigma [sqrt of the] weighted sample variance resulting from 3 measurement trials on each mode; the value reported is the weighted mean of the three trails. See more details below. The uncertainty on the frequency is simply the requested binwidth of the ASD used after finding the mode frequency.)

Attachments Key for V4 / "Bounce" Mode:
    - 2018-04-12_H1SUSETMY_L3_V_BBEXC_awgsettings.png AWGGUI settings for broadband V4 search before I knew the frequency
    - 2018-04-12_H1SUSETMY_L3_V_SineInj_awgsettings.png AWGGUI setings once the frequency was found, and during ring-down measurements
    - H1SUSETMY_L2_Q_bounce_ASD.pdf Collection of post-processed ASDs of L2_WIT_L_DQ channel used for each ring-down trial
    - H1SUSETMY_L2_Q_bounce_Time_Series.pdf Collection of RMS time-series of L2_WIT_L_DQ channel and fit results for each ring-down trial
    - 2018-04-12_H1SUSETMY_V4R4_Characterization_PostBRDInstall.pdf (PG 1) Trial results plotted against weighted mean and variance.

%%% R4 "Roll" Mode Characterization %%%

I was *not* able find the highest roll mode frequency using the standard search method -- iterating through driving the top mass (M0) in Roll with small ~0.2 Hz band passes over a 13.5 and 14.2 Hz range. I tried searching by driving in vertical at the top mass as well, still was not able to ring anything up. I was finally able to see something ring up by driving the penultimate mass (L2) in pitch, but I was not convinced I wasn't just seeing my broadband excitation in my witness sensors (L2 OSEMs in L, P, or Y, and L3 optical levers in P or Y), because the sensor signals would die off very quickly (and it was tough to tell how quickly, because I need at least a 0.005 Hz BW running ASD to see what I'm doing).

So, finally, I took an excessively long swept sign measurement through the band, driving at L2 in P. These revealed *two* features, with quite low Q, clearly visible in optical lever Y, and barely visible in optical lever P. 

Once identifying these two modes at 13.766 Hz and 13.856 Hz in the L2 P drive to L2 Y OSEM response, I then used the lower of the two frequencies to conduct the standard set of trials, hoping to identify the Q that way. I used that lower mode -- 13.766 Hz -- because while both modes were visible in optical lever Y, the lower frequency feature was *more* visible in the optical lever P transfer function so I had greater confidence it was the roll mode. The results are attached, and give a Q of ~200, but again, I couldn't find a set of FFT and RMS parameters that showed a clear ring down that had no "noise bounces." These results claim a Q of ~200.

Finally, as a last ditch effort to be really confident that these 13.766 Hz and 13.856 Hz modes were real, I went from an excessively to ridiculously long TF from M0 R to each of the lower stage sensors (again, L2 L, P, and Y OSEMs, L3 P and Y optical levers), taking it over night. This transfer function also showed these same features, so I'm now confident that the roll mode has been split into two low Q modes:

                                ETMY 
                                Mode R4.1           Mode R4.2
    R4 Pole Frequencies / Hz    13.788 (0.001)      13.883 (0.001)
    R4 Zero Frequency / Hz                 13.851 (0.001)

    R4 Pole Qs / dimensionless  600  (10)           440 (10)
    R4 Zero Frequency / Hz                 240 (10)

where I've determined these frequencies and Qs from using foton to create a crude, by-hand/by-eye fit and the uncertainties are estimated from me changing the frequency and Qs by the quoted values and seeing that the fit is not good enough. The fit is 
     zpk([2.5;2.5],[],1,"n")*                                    (two out-of-measurement-band zeros, to start that phase and slope off right)
     zpk([],[0.01149+i*13.788;0.01149-i*13.788],1,"n")*          (a complex pair of poles at 13.788 Hz with a Q of 600)
     zpk([0.0288562+i*13.851;0.0288562-i*13.851],[],1,"n")*      (a complex pair of zeros at 13.851 Hz with a Q of 240)
     zpk([],[0.0157761+i*13.883;0.0157761-i*13.883],1,"n")*      (a complex pair of poles at 13.883 Hz with a Q of 440)
     gain(1.5e-10)                                               (arbitrary gain to match the magnitude scale of the data)

   
Attachments Key for R4 / "Roll" Mode:
    - 2018-04-12_H1SUSETMY_L2P_L3_R_SineInj_awgsettings.png AWGGUI settings during the unconvincing ring-down trials
    - H1SUSETMY_L2_Q_roll_ASD.pdf ASD of L2_WIT_L_DQ (OSEMs) during unconvincing ring-down trials
    - H1SUSETMY_L2_Q_roll_Time_Series.pdf RMS time series of L2_WIT_L_DQ (OSEMs) during unconvincing ring-down trials
    - 2018-04-12_H1SUSETMY_L2_L3_R4_ModeSearch_SSinj.png  Excessively long swept sine measurement showing L2 Pitch drive to L2 P & Y OSEM response
    - 2018-04-12_H1SUSETMY_M0R_L3_R4_ModeSearch_SSinj.png Ridiculously long swept sine measurement showing M0 Roll drive to L2 P & Y OSEM response
    - 2018-04-12_H1SUSETMY_M0R_L2Y_FotonFit.png Foton Fit of ridiculously long M0 R to L2 Y swept sine measurement
Images attached to this report
Non-image files attached to this report
H1 PEM
jeffrey.bartlett@LIGO.ORG - posted 11:17, Tuesday 17 April 2018 (41489)
Monthly Dust Monitor Vacuum Pump Checks
   Checked vacuum pumps on both end stations and at the corner station. All pumps are operating normally. Temps and pressures are in their proper ranges. Made a slight adjustment in the vacuum pressure for End-X pump. Closing FAMIS task #7524
H1 CDS (CDS, GRD)
cheryl.vorvick@LIGO.ORG - posted 09:32, Tuesday 17 April 2018 - last comment - 09:26, Thursday 19 April 2018(41487)
SDF snapshots taken Monday Morning between 8:20AM and 8:40AM Pacific Time (15:20-15:40UTC)

I took snapshots of every SDF screen that had diffs when I arrived Monday, in response to Dave's alog that said a number of our front end computers might freeze at any time.  I've renamed the snapshots to have the format (screen/system name)_SDF, and if I included more than one screen/system in the snapshot then the name is in the format (screen/system name)_(screen/system name)_(screen/system name)_SDF.  This morning, in preparation for reboots on Thursday,  JeffK is accepting some values, for example TRAMP times that have changed, and TVo is looking at some SDF screens to accept changes that reflect commissioning modifications that should be kept.  At this time, Tuesday at 9:20PT, we have 56 SDF screens that show diffs.

Images attached to this report
Comments related to this report
cheryl.vorvick@LIGO.ORG - 09:26, Thursday 19 April 2018 (41542)
Images attached to this comment
H1 General
cheryl.vorvick@LIGO.ORG - posted 08:28, Tuesday 17 April 2018 (41486)
Morning Update:

As Of 15:26UTC (8:26PT):

H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 08:18, Tuesday 17 April 2018 (41485)
Post 70W Install PSL Cooling
   Posted below are the plots for the various PSL pressure, flow, and cooling signals post 70W and new shutter install. This should represent the final configuration of the reworked cooling system necessary to accommodate the new amp. Most changes reflected in the plots are as expected and should assist with final tuning and balancing the water flows. The goals of the tuning will be to (1) reduce pressures as much as possible while retaining enough flow to ensure proper cooling. (2) to shift pressure manipulations from within the PSL enclosure to the chiller room, and (3) to reduce water flow table noise to a minimum.     
   
Images attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 20:43, Monday 16 April 2018 (41481)
TE203 alarms
I lowered the temperature set point from 130C to 127C on the CP4 heater controller this evening.  The recent TE203 ROC alarms are the result.  The remotely displayed controller screen has been, seemingly, unchanging now for days? weeks? so I perturbed it to verify that the displayed temperatures would react/change.
 
I am monitoring periodically.  
LHO VE
chandra.romel@LIGO.ORG - posted 18:18, Monday 16 April 2018 - last comment - 05:54, Tuesday 17 April 2018(41478)
mysterious air leak around IP4

Kyle and I independently leak checked IP4 gate valve on the beam tube side and found a very delayed He signal (many seconds to minutes). I bagged the flange joint with party store balloon mylar and found minutes delay from a vertex background signal of 4.8e-9 Torr-L/s to a leak rate of 8.5e-9 Torr-L/s, using UL1000 leak checker. It's still unclear if this flange joint is leaking or if He is migrating to the actual leak. Need N2 to flush out the He. After the leak rate crept up to 8.5e-9 Torr-L/s very slowly, I finally removed the bag and then it crept down even slower while I blew on the flanges.

Note that the flanges were somewhat gappy after installation (top and bottom of valve) a few months back. Gerardo torqued them metal to metal and found that the pressure improved on the IP4 pump side (its GV is closed), from April 13th.

IP4 was leak checked after it was installed last year with a small leak noted from 8" CFF:  https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=40339

Comments related to this report
chandra.romel@LIGO.ORG - 18:22, Monday 16 April 2018 (41479)

The background of the vertex volume is 4.8e-9 Torr-L/s of He, with UL1000 leak checker backing the main turbo and the vertex pressure at 1.9e-6 Torr (after recent vent). When leak checker+turbo are isolated from main volume, the background drops to 1.2e-9 Torr-L/s and when isolated from turbo drops to >>1e-9 Torr-L/s.

chandra.romel@LIGO.ORG - 18:22, Monday 16 April 2018 (41480)

IP4 is 20-30 ft from main turbo+leak checker.

john.worden@LIGO.ORG - 21:33, Monday 16 April 2018 (41482)

Bag the bonnet?

chandra.romel@LIGO.ORG - 05:54, Tuesday 17 April 2018 (41484)

I can try that. I sprayed it and didn't see an immediate response.

Displaying reports 43761-43780 of 84094.Go to page Start 2185 2186 2187 2188 2189 2190 2191 2192 2193 End