Displaying reports 57841-57860 of 83004.Go to page Start 2889 2890 2891 2892 2893 2894 2895 2896 2897 End
Reports until 18:28, Wednesday 02 March 2016
H1 ISC (ISC)
matthew.evans@LIGO.ORG - posted 18:28, Wednesday 02 March 2016 - last comment - 10:27, Monday 07 March 2016(25847)
DARM noise fluctuation vs. LVEA Temperature

Plotting the cross-correlated DARM noise (band 5) and LEVA temperature on the same plot doesn't show any obvious relationship.  The .fig is included in case someone has a good idea of how to use this data.

Images attached to this report
Non-image files attached to this report
Comments related to this report
lisa.barsotti@LIGO.ORG - 19:23, Wednesday 02 March 2016 (25848)
This analysis has been inspired by the recent investigations on the  L1 noise , that shows some correlation of DARM variations vs LVEA temperature.

By superimposing the current best L1 curve and the best H1 curve from O1 (see plot), one can see that the noise in the L1 bucket seems to have more "scattering looking" peaks (which can be modulated by temperature-induced alignment variations), while the H1 noise less so. 

The noise at high frequency is notably lower in L1, mostly due to the higher cavity pole frequency. 

Non-image files attached to this comment
kiwamu.izumi@LIGO.ORG - 14:50, Friday 04 March 2016 (25882)DetChar

I have extended Matt's previous analysis to the entire O1. In addition, I added another interesting channel, the vertical sensor of the top stage of ITMY. Here is the result.

I went through trend of some interesting channels where I was looking for signals showing similar variation to the band limited rms of the cross spectra. I came across ITMs' top stage vertical monitors and found them showing two relatively big bumps (actually dips in the raw signals) which seemingly match the ones in the band limited rms on Dec 2nd and Dec 29th. However, even through they look like showing a good agreement in the last half of the O1 period, the first half does not show an obvious correlation. Does this mean that the modulation mechanism of the noise level changed in the middle of the run and somehow noise level became sensitive to vertical displacement of ITMs or in-chamber temperature ?

Images attached to this comment
Non-image files attached to this comment
kiwamu.izumi@LIGO.ORG - 10:27, Monday 07 March 2016 (25910)

For completeness, I have looked at other vertical monitors. Here is the result. They all show qualitatively the same behavior more or less. The fig file can be found on a server.


 

Images attached to this comment
H1 CDS
david.barker@LIGO.ORG - posted 17:18, Wednesday 02 March 2016 (25845)
/ligo file system filled this morning

Carlos, Dave:

The /ligo file system filled up  this morning. Carlos did an emergency move of /ligo/backups/alog over to the ops-home disk. Later we built a file system on a spare 2TB disk Carlos had installed on cdsfs0 and we moved the Guardian log files backup directory over to it. This freed up 112GB of disk space. Along with other cleanup work /ligo currently has 143GB of disk available. We hope this carries us through to the install of the new cdsfs0 NFS server scheduled for Tuesday 8th.

H1 General
cheryl.vorvick@LIGO.ORG - posted 16:17, Wednesday 02 March 2016 - last comment - 08:20, Thursday 03 March 2016(25843)
Ops Day Summary:

Day Shift 16:00-23:59UTC (08:00-16:00PT)

State of H1: DRMI lock for Jenne

Shift Summary:

Site Activities:

- 19:30 Kyle - LVEA to survey for upgrade

- 19:45 Kyle - out of LVEA

- 21:27 Corey - optics lab

- 21:15 Ed - LVEA to reset PSL watchdog

- 21:25 Ed - out of PSL

 

Locking / Initial Alignment:

- locking X arm in red was very fast, and had good power

- ITMY needed more of an offset during SRC alignment

- PRMI needed to adjust BS for DRMI

- DRMI is well aligned and relocking quickly for the last 2-3 hours of the shift

 

Control Room:

- Video0 froze, now fixed after a reboot

- Video4 had the wrong striptool displayed, now fixed

Comments related to this report
cheryl.vorvick@LIGO.ORG - 16:40, Wednesday 02 March 2016 (25844)

ITMY mis-alignment issue tracked down to offset, now fixed.

ITMY drivealign_P2L_gain change from 1.05 to 0.6 accepted after the OK by Sheila, had been 0.6 for at least 10 days.

Images attached to this comment
edmond.merilh@LIGO.ORG - 08:20, Thursday 03 March 2016 (25854)

The Front End watchdog reset takes place in the LASER Diode Room, not in the LVEA/PSL enclosure. :)

H1 SEI (ISC)
jim.warner@LIGO.ORG - posted 14:34, Wednesday 02 March 2016 - last comment - 09:44, Friday 04 March 2016(25842)
Plans for wind fence testing at LHO

I've been slowly trying to get stuff figured out for testing a wind fence set up at LHO, and am getting ready to try to set something up. I'll summarize where I think things are here.

Currently, I want to try a small, cheap wind fence at EX, mostly to explore how effective screens are at slowing wind, effects on ground motion and tumbleweed build up. The fence would be a couple of 4x4-ish 12-15 foot posts and some fine polymer netting like that used around tennis courts, gardens and the like. It may be necessary to add guy lines, as well.  In addition to the fence, Richard has said he will help me get an STS buried at EX, similar to Robert's set up at EY, and we are ordering 3 anemometers with stand alone data collection so no changes need to be made to CDS for this. I think this set up will allow me to look at a few of the concerns that people have brought up. So far the concerns I've heard are:

1. Increased ground motion. Fences slow wind by applying a force to the airstream, this is transmitted to the ground and produces increased tilt and other high frequency motion. I think the tilt can be addressed by placing the fence some few tens of meters from the building, per Robert's measurements of building tilt. Higher frequency motion can hopefully be addressed by design of the fence support structure, but we'll have to see how bad the motion is.

2. Similarly, the fence could make airflow more turbulent. I suspect that airflow at the building level is probably turbulent anyway. Hopefully, a well designed fence push turbulent flows around the building, while slowing most of the air makes it through.

3. Tumbleweed build up. Anything that blocks the wind will gather tumbleweeds around here, which could make a fence a fire hazard and maintenance issue.  This  could be addressed by leaving a gap at the bottom. The airflow below a few feet probably isn't a significant source of problems for us, but I don't know how big this gap would need to be. I also plan on using a mesh fine enough that tumbleweeds won't stick to the fence very easily. Industrial fences are flame resistant, and won't ignite on their own.

4. Wind damage. We have seen winds above 100 mph during a storm, this would create very high loads on any fence. I haven't been able to figure out how to calculate wind loads on a permeable wall yet, but Civil Engineers have building codes dealing with this. For my test, I'm trying to get some idea of the loads involved with moderatewind, and just making the fence so that the mesh will tear free in a way that won't damage the EX building if the wind gets too bad. Industrial fences are designed to stand similar wind loads, and their screens are held in place with replaceable break-away clips to prevent damage.

5. Cost/size. BrianL talked to a company that makes industrial fences a few months ago. The ball park figure for a 40 x 200 foot fence was about $250,000. That was a first pass at a price and the company had some suggestions at how to cut down on the cost. This price also needs to be weighed against the 10-15 % of down time we have due to wind. Something of that size would also probably have to be approved by the DOE. It's also unclear if we would have to completely surround each endstation, or if we could get away with less coverage. Probably, we don't need to "protect" EY along the X-axis, or EX along the Y-axis.

Comments, criticism, praise are all welcome.

Comments related to this report
john.worden@LIGO.ORG - 08:29, Thursday 03 March 2016 (25855)

Comments;

Any break away components will need to be constrained so the EPA doesn't come after us for polluting the desert. I suggest that even a temporary test fence be built to withstand any expected wind/snow/tumbleweed loads.

Be aware that any wind speed and direction measurements are likely influenced by ground effects until you are well above the ground and nearby obstructions - say 25- 50 feet???

brian.lantz@LIGO.ORG - 09:44, Friday 04 March 2016 (25879)FMP
Thanks John. 
The ones I saw advertised had a cable top and bottom which suspended the wind fabric. The top attachments from the fabric to the cable were "permanent" and the attachments to the lower cable were the break-away. This should allow it to yield to the wind load, but to keep it from blowing away and causing more trouble.
H1 ISC (ISC)
matthew.evans@LIGO.ORG - posted 14:12, Wednesday 02 March 2016 (25841)
DARM noise fluctuation

Along the same lines of earlier investigations into DARM noise fluctuations, I checked the "high frequency" (1-100mHz) spectrum of the DARM RMS in 2 bands between 80 and 100Hz.  The fluctuations in these BLRMSs are fairly featureless, though there appear to be small peaks at 30 and 70mHz (see plot).

The code used to generate these plots is:

gwd = GWData;
data7 = gwd.fetch('26 Dec 2015 8:00:00', 3*60*60, 'H1:SUS-ETMX_L2_DAMP_MODE7_RMSLP_OUT16', 'mDV');
dd7 = GWFilt.detrend(data7.data);
fs = data7.rate; tfft = 256;
[p7, ff] = pwelch(dd7, hann(fs * tfft), [], fs * tfft, fs);

data8 = gwd.fetch('26 Dec 2015 8:00:00', 3*60*60, 'H1:SUS-ETMX_L2_DAMP_MODE8_RMSLP_OUT16', 'mDV');
dd8 = GWFilt.detrend(data7.data);
[p8, ff] = pwelch(dd8, hann(fs * tfft), [], fs * tfft, fs);

loglog(ff, [p7, p8]); axis([0.005, 0.2, 1e-4 1e-2]); grid on
title('Flucutations in DARM noise (Boxing Day 2015)')
legend('80-100Hz band', '100-120Hz band')
xlabel('frequency [Hz]')
ylabel('Power spectrum of variations')

Images attached to this report
H1 General (PSL)
edmond.merilh@LIGO.ORG - posted 13:56, Wednesday 02 March 2016 (25839)
Reset PSL FE Watchdog

The watchdog was reset at 13:22PST as per FAMIS http:// https://ligo-wa.accruent.net/LB_Request_Update.asp?RequestID=3587

H1 GRD
thomas.shaffer@LIGO.ORG - posted 10:53, Wednesday 02 March 2016 - last comment - 12:52, Wednesday 02 March 2016(25837)
Testing PSL Guardian Node

I took advantage of the the earthquake and the higher winds this morning and went to test out a new PSL node. Much of the code was taken from LLO's PSL guardian, but I tweaked it for our uses and added a few things that they didn't have. After I created the node, I could not get "guardctrl medm" to pop up a medm for the node.  (shot of the error attached) In the interest in time, I continued just using the the log and other guardctrl commands. This is much more awkward that I expected and slowed me down quite a bit. After sorting through the few syntax errors, bringing the power up and down, and searching for home, I have some notes and will work on a few issues I found. Overall, it went well and it should, hopefully, be usable very soon.

I stoped and destroyed the node when I was done, I will recreate it next chance I get to test it (whenever that may be).

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 12:52, Wednesday 02 March 2016 (25838)

Completely spaced and did not use "guardmedm". This would have worked for what I needed.

H1 General (VE)
cheryl.vorvick@LIGO.ORG - posted 09:36, Wednesday 02 March 2016 - last comment - 10:02, Wednesday 02 March 2016(25835)
Site activities - H1 Update: at 17:35UTC (9:35PT)

Site activities:

- 17:16UTC Kyle and Gerardo - at EX and door X2-8 to work on cable for annulus ion pump

 

H1 Update:

- 17:53UTC all ISI platforms returned to nominal isolation

Comments related to this report
cheryl.vorvick@LIGO.ORG - 10:02, Wednesday 02 March 2016 (25836)

Ex work on hold until the road is cleared of tumbleweeds.

H1 General
cheryl.vorvick@LIGO.ORG - posted 08:38, Wednesday 02 March 2016 (25833)
Ops Morning Update:

Earthquake:

Time: Wed Mar 02 12:49:47 UTC 2016

Location: Southwest of Sumatra, Indonesia; LAT: -4.9, LON: 94.3

Magnitude: 7.8

- HEPIs that tripped: HAM1, ETMX (BSC9)

- ISIs that tripped: all ISIs

- oprics that tripped: BS, PR2 (full trip), SR2 (only upper two stages), and MC1(only upper two stages)

- Hugh and Jim were here early, and have ISIs in Damped, and HEPIs in Robust_Damped

- 0.03-0.1Hz ground motion is typically around 0.05um/s, and is currently 0.5um/s

- useism (0.1-0.3Hz ground motion) is at 0.5um/s

Current H1 Status:

- guardian issues being worked on

- too much ground motion to lock 

H1 CDS
patrick.thomas@LIGO.ORG - posted 00:30, Wednesday 02 March 2016 (25831)
Conlog test
I'm leaving conlog-test-master running and connected to the same channels as h1conlog1-master.
LHO General
patrick.thomas@LIGO.ORG - posted 00:24, Wednesday 02 March 2016 (25830)
Ops Evening Shift Summary
0:25 UTC Kyle to end X to get something forgotten outside of LVEA
0:42 UTC Kyle back

After TCS work was done for the day Sheila and I attempted to lock the X and Y arms on green. I was able to lock the X arm fairly quickly, but the Y arm took a long time to realign. Further attempts were abandoned for the night with winds over 40 mph.
H1 SUS (ISC)
brett.shapiro@LIGO.ORG - posted 22:54, Tuesday 01 March 2016 - last comment - 11:29, Friday 04 March 2016(25829)
Quad Matlab model updates

svn up at .../SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/

Updates:

1) Added an option for optical lever damping that actuates at the PUM (L2) stage. Like top mass damping, this can be imported from the sites, or added in locally.

2) Added options for violin modes at all stages. Previously this was only available for the fibers. You can choose how many modes you want at each stage, doesn't have to be the same number.

3) Added an option to load damping from a variable in the matlab workspace. Previously this could only be done from a saved file or imported from the sites.

 

Detailed instructions fpr generate_QUAD_Model_Production.m are commented into the header. See G1401132 for a summary of the features, and some basic instructions on running the model.

I am tagging this to the svn now as

quadmodelproduction-rev7995_ssmake4pv2eMB5f_fiber-rev3601_h1etmy-rev7915_released-2016-03-01.mat

...the file is large (386 MB) so it is slow to upload.

The tagged model includes 25 violin modes for the fibers, 20 for the uim-pum wire, 15 for the top-uim wire, and 10 for the top-most wire. For the 25 fiber violin modes, the first 8 are based on measured frequencies from h1etmy, the remainder are modeled frequencies. All metal wire modes are modeled values. The oplev filters are turned off in this model as well (I imported the filters from LHO, and they were turned off at the time).

 

For reference, this is a summary of the history of model revisions in the svn:

generate_QUAD_Model_Production.m

rev 7359: now reads foton files for main chain and reaction damping

rev 7436: Changed hard coded DAMP gains to get the correct values for LHO ETMX specifically.

rev 7508: Restored damping filter choice for P to level 2.1 filters as opposed to Keita's modification. Cleaned up error checking code on foton filter files, and allowed handling of filter archive files and files with the full path.

rev 7639: renaming lho etmy parameter file

rev 7642: Adding custom parameter file for each quad. Each one is a copy of h1etmy at this point, since that one has the most available data.

rev 7646: added ability to read live filters from sites, and ability to load custom parameter files for each suspension

rev 7652: updated to allow damping filters from sites from a specific gps time (in addition to the live reading option)

planned future revision - seismic noise will progate through the damping filters as in real life. i.e the OSEMs are relative sensors and measure the displacement between the cage and the suspension.

rev 7920: big update - added sus point reaction forces, top OSEMs act between cage and sus, replaced append/connect command with simulink files

rev 7995: added oplev damping with actuation at the PUM (L2); added options for violin modes at all stages, rather than just for the fibers; added option to load damping from a variable in the workspace, in addition to the existing features of loading damping from a previously saved or importing from sites.

ssmake4pv2eMB5f_fiber.m

no recent (at least 4 years) functional changes have been made to this file.

* quadopt_fiber.m

- rev 2731: name of file changed to quadopt_fiber.m, removing the date to avoid confusion with Mark Barton's Mathametica files.

- rev 6374: updated based on H1ETM fit in 10089.

- rev 7392: updated pend.ln to provide as-built CM heights according to T1500046

- rev 7912: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit.  Same as h1etmy.m.

* h1etmy.m

- rev 7640: created the H1ETMY parameter file based on the fit discussed in 10089.

- rev 7911: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit. Same as quadopt_fiber.m.

Comments related to this report
brett.shapiro@LIGO.ORG - 11:29, Friday 04 March 2016 (25881)

I added more comments to the header of the model file, generate_QUAD_Model_Production.m, explaining how to run the model with measured violin modes and Qs. I also clarified the comments on including custom damping. I updated the feature summary doc G1401132 with the same information.

H1 ISC
lisa.barsotti@LIGO.ORG - posted 22:21, Tuesday 01 March 2016 (25828)
Current SRM vs SRM 20% vs no SRM
As a curiosity, here are some projections comparing the current H1 noise with SRM T = 20% (nominal aLIGO design) and no SRM (power recycling only). The SRM T=20% and no SRM curves are obtained simply by replacing the modeled H1 quantum noise in the present configuration (SRM T equivalent = 39%) with the quantum noise calculated for these alternative configurations, assuming the rest of the noise the same.

We would have detected GW150914 no matter what; the SNR could have been 30% worse. 


GWINC output for corresponding theoretical curves:

Current H1

BNS Inspiral Range:      159.65 Mpc
BBH Inspiral Range:        3.04 Gpc (z = 1.0)

SRM T = 20%

BNS Inspiral Range:      131.75 Mpc
BBH Inspiral Range:        2.35 Gpc (z = 0.8)

NO SRM

BNS Inspiral Range:      155.89 Mpc
BBH Inspiral Range:        2.95 Gpc (z = 1.0)
Non-image files attached to this report
LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 15:55, Tuesday 01 March 2016 - last comment - 14:12, Wednesday 02 March 2016(25816)
X-End Neg Regeneration

(Chandra, Gerardo and Kyle)

Regenerated NEG pump with the aid of an aux cart.

Valved out NEG pump from X-End, then started regeneration of NEG pump ~19:00 utc.
2 hours later heating was complete, waited for temperature to drop down, valved in NEG pump to X-End volume at 21:45 utc and @ 92 deg C.

Comments related to this report
john.worden@LIGO.ORG - 14:12, Wednesday 02 March 2016 (25840)

Pressure plots attached.

-Chandra

Images attached to this comment
H1 SUS (SUS, SYS)
richard.mccarthy@LIGO.ORG - posted 15:02, Tuesday 01 March 2016 - last comment - 09:34, Wednesday 02 March 2016(25812)
Suspension Sat Amp Mods
Finished adding Caps to the Negative regulator per latest dwg. Today we completed the ITMx,ITMy,BS, and all of Ham5 and Ham6 Suspensions.  Also verified and corrected were needed Ham2 optics.
This should stem any oscillations caused by the long cables from the SAT amp side.
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:34, Wednesday 02 March 2016 (25834)DetChar
I've verified with Richard that this concludes the H1 SatAmp upgrade as per Integration Issue 1129, DCN E1100767, and G1100856. 

Nice work gents!

Stay tuned for a systematic check of how-and-if it has improved the high frequency oscillations this upgrade was intended to fix.
H1 IOO (IOO)
cheryl.vorvick@LIGO.ORG - posted 11:18, Monday 29 February 2016 - last comment - 08:31, Wednesday 02 March 2016(25781)
IM2 (PMMT1) oscillating after Satellite module fix

IM2 position is now oscillating by 5urad in pitch and yaw after satellite module fix on Feb. 23.

Three plots attached:

Images attached to this report
Comments related to this report
edmond.merilh@LIGO.ORG - 11:33, Monday 29 February 2016 (25784)

That Sat amp doesn't qualify as fixed at this point. The modification is not currently installed. See Richard McCarthy for details.

edmond.merilh@LIGO.ORG - 08:31, Wednesday 02 March 2016 (25832)

3/1/2016 The modification has been added.

Displaying reports 57841-57860 of 83004.Go to page Start 2889 2890 2891 2892 2893 2894 2895 2896 2897 End