Displaying reports 77841-77860 of 87662.Go to page Start 3889 3890 3891 3892 3893 3894 3895 3896 3897 End
Reports until 22:08, Monday 17 February 2014
H1 SUS
brett.shapiro@LIGO.ORG - posted 22:08, Monday 17 February 2014 (10124)
SR2 model fit results
Last week with Andres's help I measured resonance frequencies on SR2 in the double and single hang cases (top locked on stops and middle locked on stops respectively). This log reports the results of fitting the hsts model to that data. The adjusted parameters are listed below with the estimated error bars. Typically I allow d1 (top mass spring tip height) to move. Interestingly, the model had better results when the height of the bottom mass prism was allowed to move instead. Floating d1 did allow the resonances to line up with similar precision, however d1 and I1y  would drift very far from their nominal positions to do this, about 5 mm on d1 and 50% on I1y.

The attachment H1SR2_ModelFit_17Feb2014.pdf shows the measured transfer functions against the nominal model and the model fit. The measured L-P/P-L and T-R/R-T TFs do not show good symmetry, so those comparisons should be taken with a grain of salt. Likely the OSEM balancing is poor as poor balancing will cause errors in the measured zero locations. Similarly, the 1.5 Hzish zero on the measured Roll to Roll TF is probably slightly off from reality. It does not correspond exactly to the measured double hang Roll resonance as it should, and it is also somewhat off from other HSTS suspensions.

The attachment H1L1SR2comparison_17Feb2014.pdf shows the same results but against L1SR2. The new model also fits L1SR2 better, though there are some minor differences.

The new parameter file is on the svn at ...sus/trunk/Common/MatlabTools/TripleModel_Production/hstsopt_H1SR2fit.m

The model fitting code for H1SR2 is on the svn at ...sus/trunk/Common/MatlabTools/TripleModel_Fit/TripPend_GaussNewton_fit_v5_H1SR2.m


Change in parameters from original model with the estimated minimum errors
---------------------------------------
d4: -1.6798 +- 0.094782 mm
I1x: -6.3844 +- 1.2588 %
I2x: -5.2885 +- 11.4653 %
I3x: -3.706 +- 12.1017 %
I1y: 8.8773 +- 0.61371 %
I2y: -5.583 +- 0.5374 %
I3y: -4.6949 +- 0.36401 %
I1z: -5.7573 +- 0.9752 %
I2z: 1.2902 +- 1.0012 %
I3z: -3.2293 +- 0.30808 %
l1: 5.5655 +- 3.3226 mm
l2: 4.2327 +- 0.52961 mm
l3: 1.4169 +- 0.40356 mm
kc1: -1.2835 +- 1.2589 %
kc2: 2.4943 +- 0.4258 %
---------------------------------------
Non-image files attached to this report
H1 SUS
mark.barton@LIGO.ORG - posted 15:29, Monday 17 February 2014 (10123)
New TMTS models
 
I created new versions of the first article and production TMTS Mathematica/Matlab models using data from Eddie Sanchez' D0902773-v8 of 12/25/13:
 
/ligo/svncommon/SusSVN/sus/trunk/TMTS/Common/MatlabTools/tmtsopt_firstarticle.m r6273
/ligo/svncommon/SusSVN/sus/trunk/Common/MathematicaModels/DualLite2DBLateral/20131224TMTS_FirstArticle
20131224TMTS_FirstArticle
 
/ligo/svncommon/SusSVN/sus/trunk/TMTS/Common/MatlabTools/tmtsopt_production.m r6273
/ligo/svncommon/SusSVN/sus/trunk/Common/MathematicaModels/DualLite2DBLateral/20131224TMTS_Production
20131224TMTS_Production
 
Formerly we had been using tmtsopt_firstarticle.m r4580 for both the first article (LHO TMSy) and production builds. It mostly used numbers read from the EASM file of D0900419-v2, plus mass parameters supplied by Ken Mailand. It had required quite a large tweak of +4.3 mm to d1 to match modeR1 at 0.679 Hz, but otherwise matched both builds reasonably well. A matching production parameter set was created, but lacked updated dimensions values for the production telescope and was not used.
 
The new parameter sets use all as-built numbers from D0902773-v8, with one exception: the new first article needs a smaller but still significant tweak of +2.7 mm to d1 to match modeR1=0.679 Hz. The new production parameter set needs no tweaks to match modeR1=0.65 Hz.
 
Plots of the new first article model against H1 TMSy data and the new production model against L1 and H1 TMSx data are attached. The mode frequencies are as per the table below. Note that modeP1 and modeV1 have leap-frogged.
 
	tmtsopt_firstarticle    tmtsopt_firstarticle    tmtsopt_production
r4580                   r6273                   r6273
--------------------------------------------------------------------
modeY1      0.355864    modeY1      0.357487    modeY1      0.356438
modeT1      0.447407    modeT1      0.44897     modeT1      0.44903
modeL1      0.473763    modeL1      0.474697    modeL1      0.474545
modeR1      0.678918    modeR1      0.679192    modeR1      0.650001
modeP1      0.713869    modeV1      0.73404     modeP1      0.729786
modeV1      0.729389    modeP1      0.754609    modeV1      0.750216
modeT2      1.38385     modeT2      1.36581     modeT2      1.37346
modeL2      1.72689     modeL2      1.72179     modeL2      1.73388
modeV2      2.40587     modeV2      2.40182     modeV2      2.40454
modeP2      2.44574     modeP2      2.44429     modeP2      2.56147
modeY2      2.59116     modeY2      2.58853     modeY2      2.71571
modeR2      4.27789     modeR2      4.14866     modeR2      4.31193

   tmtsopt_firstarticle    tmtsopt_production
r4580                   r6273                   r6273
--------------------------------------------------------------------
modeY1      0.356438    modeY1      0.357487    modeY1      0.356438
modeT1      0.44903     modeT1      0.44897     modeT1      0.44903
modeL1      0.474545    modeL1      0.474697    modeL1      0.474545
modeR1      0.650001    modeR1      0.679192    modeR1      0.650001
modeP1      0.729786    modeV1      0.73404     modeP1      0.729786
modeV1      0.750216    modeP1      0.754609    modeV1      0.750216
modeT2      1.37346     modeT2      1.36581     modeT2      1.37346
modeL2      1.73388     modeL2      1.72179     modeL2      1.73388
modeV2      2.40454     modeV2      2.40182     modeV2      2.40454
modeP2      2.56147     modeP2      2.44429     modeP2      2.56147
modeY2      2.71571     modeY2      2.58853     modeY2      2.71571
modeR2      4.31193     modeR2      4.14866     modeR2      4.31193
 
Non-image files attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 11:25, Monday 17 February 2014 (10122)
SEI Status mid morning Monday--All on sans BS-ISI

All the SEIs are operating as left Friday evening except the BS.

The BS ISI is tripped with a GS13 trip at 1076474647 followed by an Actuator limit trip 44 seconds later.  So this ISI only lasted for a few hours (til 2043 pst Friday evening.)  The watchdog plotting tools are not functional at this time, and its a holiday.

Taking the ISI back up, I see the current location and target for Rx is a mear 900nrads but this is too much tilt to start with the Trilliums in the loop.

Can a ISC/PRMI Commissioner confirm that we must servo to this value?  Certainly would make getting the IS back on easier if we could reset these targets.

So going up with the 250mHz blends ( with the T240 watchdog trigger level increased the second time.)  Have moved the Stage1 to nominal blends (T250 everywhere with the T100.44NO for X & Y)  Stage2 is also on with the 250mHz blends.  I notice the signal for Z is large on stage2 so I've turned off the Z boost.  It still has some pretty large swings though...  Seems to be some large low frequency oscillation comes and goes.  Will still likely trip I'm thinking.  If it doesn't hold maybe the blend shold be moved back to 750s.  I know Jim is still working on the loops here.

I was starting to see the Epics readouts for the output filters get into the 1000s for the horizontals (already doing the vertical s for a while,) so I switched Stage2 to the 750mHz blends.  This certainly reduced these readback's magnitude right away.  I've reenabled the Z boost now as a result.

I'll leave the ISI at this for the moment: Stage2 Lvl2 with 750mHz blend, Stage1 is Lvl2 with T100mHzNO.44 blends on X & Y and T250mHz elsewhere.  Sadly, the BLRMS needs a lot more green.

H1 PEM
jameson.rollins@LIGO.ORG - posted 09:50, Monday 17 February 2014 (10121)
alarm fugue

Given that it's a holiday, there are no operators on site to silence the alarm chorus.  There are some CDS alarms that I can't quite identify the source of, but the CDS system looks ok on the whole, so I'm just silencing them temporarily.

There does seem to be a persistent alarm from the EY dust monitor.  I ACK'd it once when I came in, but it was back again a couple minutes later.

H1 ISC (ISC)
evan.hall@LIGO.ORG - posted 21:26, Sunday 16 February 2014 - last comment - 10:57, Tuesday 18 February 2014(10120)
ALS-X BBPD has gone dark

The ALS-X BBPD appears to have gone dark around 2:30 PST on Friday.  The EX laser IR PD and fiber monitor PDs appear to have been disturbed around the same time, but they have recovered.

Possibly this is related to Friday's work on installing WFS on the ISCTEX table, or the related editing of the X-end simulink models.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 10:57, Tuesday 18 February 2014 (10139)

The +-18V PD power supply cable for the table was unplugged at the power strip on the field rack. All DC diodes connected to the DC diode interface were down.

Should work now.  

Don't know why it was unplugged, it's hard to accidentally plug it off. 

H1 DAQ (CDS)
david.barker@LIGO.ORG - posted 09:19, Sunday 16 February 2014 (10119)
DAQ Status

Over the weekend both frame writers have restarted in the early hours. fw1 just after midnight Sat morning (00:01) and fw0 this morning at 01:00. They had both been very stable over the past week.

H1 ISC
daniel.sigg@LIGO.ORG - posted 23:13, Friday 14 February 2014 - last comment - 08:25, Tuesday 18 February 2014(10118)
ALS WFS in EX

(Blue Team)

Short progress report:

More details to follow.

Comments related to this report
keita.kawabe@LIGO.ORG - 08:25, Tuesday 18 February 2014 (10129)
  • "50:50 splitter" turns out to be more like 20:80.  Due to this, WFSA interface was set to high DC gain mode while WFSB is low.
  • Things were put in place based on Jax's calculation, without measuring the beam. Beam profile was measured at some places but it was so ugly I don't think it makes much sense to make an analysis.
  • The first attachment is the beam profile right after the beam is picked off of the REFL diode path. Ugly.
  • The second is the profile of the beam going into the chamber upstream of the 1" lens (between L6 and M9). One side is clipped off. I don't post all pictures but the beam is reasonable after the first Faraday, not terrible after EO, bad after the second Faraday.
  • A part of the problem seems to be in the input beam. Didn't try to "fix" it, as the past attempts to do so with existing components failed multiple times in OAT. I really believe that we need to put Faraday on an adjustable mount.
  • DC path is working, so are the picos.
  • RF path is yet to be checked.
Images attached to this comment
H1 ISC
stefan.ballmer@LIGO.ORG - posted 20:09, Friday 14 February 2014 (10117)
ODC master for the rest of E5
I set up the H1 ODC master channel: H1:ODC-MASTER_CHANNEL_OUT_DQ

The "H1 Interferometer Summary" bit (bit0) now includes the following bits:
Bit4:  PSL Summary (EPICS timing only)
Bit5:  IMC Summary
Bit 21:ADC overflow (for PSL, EPICS timing only)
Bit 22:DAC overflow (for PSL, EPICS timing only)
Bit 23:EXC on       (for PSL, EPICS timing only)
Bit 28:Guardian Observation Ready
Bit 29:Operator Science Mode Button

The guardian that will be serving bit 28 is not running yet.


Images attached to this report
H1 IOO (IOO, ISC, SYS)
stefan.ballmer@LIGO.ORG - posted 19:04, Friday 14 February 2014 (10116)
Iss saturation
I noticed from the ODC summary that the ISS was running out of range again. I  changed the set point (ISS_REFSIGNAL) from -1.93 to -1.88.

I also verified  that this was not due to a noise eater oscillation (ODC didn't indicate it as such, and toggling it didn't change it.)

H1 SEI (ISC, SEI)
hugo.paris@LIGO.ORG - posted 17:40, Friday 14 February 2014 (10114)
SEI Platform Status

Foton files were cleaned up for every SEI platform (ISI + HEPI). Details about the cleanup process can be found in SEI aLog #370

Every SEI platform was turned off, had its filter coefficient reloaded, and turned back on exepted ETMX ISI and HEPI, which ISC commissioners needed. ETMX's platforms will get their filters reloaded at the next window of opportunity.

Work started at 4:50PM and just finished. It was performed under WP #4435 which is now closed.

 

SEI crew (Jim, Hugh, Hugo) left its platforms in the following state:

H1 SEI (INS)
jim.warner@LIGO.ORG - posted 17:27, Friday 14 February 2014 (10115)
Good install progress on ETMY ISI today, but more to go

Hugh and I mostly finished cabling ETMY ISI today, but were held up by an issue with the CPS's and some broken test feed thru components. After we powered up the CPS's, we were systematically disconnecting sensors to verify routing and we noticed that the corners 2 and 3 were acting weird. After rounds of calling Richard, plugging and unplugging various cables, we figured out that the ribbon cable that carries the sync signal from the satellite rack chassis to it's power/distribution board was plugged in backwards. The other racks have keyed cables to prevent this, but this rack had an unkeyed cable. After fixing this we found that we also have a dead sensor, further debugging has that narrowed down to a broken probe. We don't have time today to finish balancing, so we'll continue on Tuesday.

H1 DAQ (CDS)
david.barker@LIGO.ORG - posted 17:15, Friday 14 February 2014 (10113)
DAQ Restart

Late entry, DAQ restart performed at 15:59PST.

Restarted the DAQ for three reasons:

The frame broadcaster had the following channels added

+[H1:PEM-EX_SEIS_VEA_FLOOR_X_DQ]
+[H1:PEM-EX_SEIS_VEA_FLOOR_Y_DQ]
+[H1:PEM-EX_SEIS_VEA_FLOOR_Z_DQ]
+[H1:PEM-EY_SEIS_VEA_FLOOR_X_DQ]
+[H1:PEM-EY_SEIS_VEA_FLOOR_Y_DQ]
+[H1:PEM-EY_SEIS_VEA_FLOOR_Z_DQ]+[H1:PEM-EX_SEIS_VEA_FLOOR_X_DQ]
+[H1:PEM-EX_SEIS_VEA_FLOOR_Y_DQ]
+[H1:PEM-EX_SEIS_VEA_FLOOR_Z_DQ]
+[H1:PEM-EY_SEIS_VEA_FLOOR_X_DQ]
+[H1:PEM-EY_SEIS_VEA_FLOOR_Y_DQ]
+[H1:PEM-EY_SEIS_VEA_FLOOR_Z_DQ]
 
More will be added during next Tuesday's maintenance.
H1 General
andres.ramirez@LIGO.ORG - posted 16:00, Friday 14 February 2014 - last comment - 16:02, Friday 14 February 2014(10111)
Ops Shift Summary
8:50      PSL Check ok. NOTE: ISS Diffracted Power is low (1.4%) and unstable with peaks over 20%. It should be 5-15%)
9:00-12:00 Going to End X to do cabling – Luis/Filiberto
10:00-12:00 Baffle work (disassembling contaminated scrapple baffle, searching for parts for arm cavity installation, and general cleanup) in LVEA West bay – Mitchell
11:01-11:03 DAQ restart – Dave
11:10-11:45 heading into the LVEA to get parts – Gerardo
12:12-12:15 Change h1iopsusey model to remove the DC OSEM component from the software watchdog – Dave 
14:15-15:51 PCAL assembly on H2 PSL – Joe
14:22-   Taking some parts to End Y – Corey
15:02-15:50 Back into the LVEA West bay (Searching and organizing Baffle parts – Mitchell
15:59   DAQ restart - Dave

NOTE: I noticed that the ISS Diffracted Power has been unstable today. It was about 1.4% in the morning with high peaks over 20% during the day (is this normal?). Based on one of the PSL trainings it should be 5-15%. I have added some pics from today and one from the last 5 days.
Comments related to this report
andres.ramirez@LIGO.ORG - 16:02, Friday 14 February 2014 (10112)


		
		
Images attached to this comment
H1 SEI (SEI, SYS)
hugo.paris@LIGO.ORG - posted 15:45, Friday 14 February 2014 (10109)
HAM4-IS - 100% ready for Guardian testing

We could not close the ISO loops on HAM4-ISI yesterday, even thought those are Level 1 generic loops. We ran transfer functions overnight, which allowed me to tweak the symmetrization filters. I also corrected a few minor typos in the unit-specific scripts. 

ISO Lv1 loops are now stable with any of the 4x blend filters installed:

I duplicated ISO Lv1 into the filter modules reserved to Lv2 and Lv3. Those use more that one filter bank. I filled the extra filter banks with gains of one. Same goes for the Boost filters. Those only use 1x filter module though.

Here is what is loaded in the ISO filter banks:

I tried turning on different combination of ISO and DAMP with the control scripts. They all worked. HAM4-ISI good to go as far as starting Guardian testing goes! yes

Images attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 15:13, Friday 14 February 2014 (10108)
~1330 hrs. local -> Stopped pumping CP8 dewar's vacuum jacket @ X-end
Will resume on Tuesday
H1 AOS
mitchell.robinson@LIGO.ORG - posted 13:28, Friday 14 February 2014 (10107)
SC2 Scrapper baffle for HAM4
The SR2 Scrapper Baffle (D1200922) was found to have been contaminated sometime during storage. This was discovered while staging for install on HAM 4. The baffle has been dis-assembled and taken to clean and bake to be re-classed. 
H1 CDS (SEI, SUS)
david.barker@LIGO.ORG - posted 13:00, Friday 14 February 2014 (10106)
new h1iopsusey model, removed DC component from the Software Watchdog
WP#4447
Created new h1iopsusey model to remove the DC components of the ETMY software watchdog. At the same time I did the same for TMSY though this is not used in the WD trigger circuit. Related changes to the safe.snap and the MEDM screen were made. at 12:17 local time the h1susey models were stopped to install the new IOP model. I tested the WD using the PANIC button on the SUS DACKILL. I then restarted the h1susetmy and h1sustmsy models, burt restoring to 11am today.
A DAQ restart is needed for the IOP model, can wait till later.
H1 CDS (CDS, SEI)
sheila.dwyer@LIGO.ORG - posted 12:06, Friday 14 February 2014 (10105)
SEI scripts don't work on the end station workstations

ETMX hepi tripped, there was activity in the end station electronics rack when the trip happened.  

The scripts for plotting the trip, the command scripts for HEPI and the ISI and the buttons to switch the blend filters don't work on the Imac's at the end station.  Alexa is working on bringing ETMX back up from the control room.  

H1 SEI
hugh.radkins@LIGO.ORG - posted 11:23, Friday 14 February 2014 (10104)
ETMY Late Morning Update--Sensors emulated

Jim and I emulated the Sensors and they look correct so we are go for complete sensor plug in.  We are still rigging up the CPS and some of the coil driver feedthrus need replacing.  It might be optimistic that we'll run transfer functions tonight but maybe.  We should be floated and balanced for sure though by the end of the day.

Displaying reports 77841-77860 of 87662.Go to page Start 3889 3890 3891 3892 3893 3894 3895 3896 3897 End