Displaying reports 72901-72920 of 82999.Go to page Start 3642 3643 3644 3645 3646 3647 3648 3649 3650 End
Reports until 08:20, Friday 28 February 2014
H1 PSL (PSL)
thomas.vo@LIGO.ORG - posted 08:20, Friday 28 February 2014 (10403)
2014-02-28 PSL Check
At 16:20:23 UTC

PSL-Status:
- Laser is on
- Output Power = 28.8 W
- Watchdog is good.
- System Status is good

PMC:
- Locked for 2 days 20 hours
- PowerRefl = 1.1  W
- PowerTran = 10.8 W

FSS:
- Locked for 1 h 12 m, relatively unstable yesterday afternoon
- Resonant Threshold = 0.7 Volts

ISS:
- Diffracted Power = 6.134%
- Last saturation event was 1h 14 mins ago.
H1 IOO
yuta.michimura@LIGO.ORG - posted 07:31, Friday 28 February 2014 (10402)
MC WFS has gone crazy over night

Stefan, Kiwamu, Yuta  (Yes! I have ligo.org account now!)

Last night, MC could not acquire lock after the guardian update for HAM2 and HAM3. So, Evan and I turned off the MC WFS loop and tweeked MC2 alignment offsets to lock MC. After that, we turned on the MC WFS loop and it seemed OK. H1:IMC-MC2_TRANS_SUM_OUT was ~635 and H1:IMC-IM4_TRANS_SUM_OUT was ~1600.

However, the WFS loop for MC2 was actually not turned on because the switch in the filter bank H1:SUS-MC2_M1_LOCK_(P|Y) was turned off. This was actually the cause of MC2 misalignment. Also, MC input PZTs were turned off (H1:IMC-PZT_(PIT|YAW)). So, MC WFS went crazy over night.

So this morning, we relieved the feedback for MC2 (H1:IMC-MC2_PIT|YAW) to be zero. This MC WFS relief should be added to MC guardian.

H1 SEI
kiwamu.izumi@LIGO.ORG - posted 06:18, Friday 28 February 2014 (10401)
engaged HEPI and ISI for ITMX and ITMY

Stefan, Kiwamu

We noticed that HEPI and ISI for ITMX and ITMY had been down. So we brought them back up. We didn't investigate why they had been down.

Also, engaging the ITMX ISI was rather difficult -- we had to take out the offsets in the T240 signals by manually changing the bias targets.

H1 SUS
kiwamu.izumi@LIGO.ORG - posted 05:32, Friday 28 February 2014 - last comment - 08:54, Friday 28 February 2014(10400)
save misaligned command doesn't work

Help us, Arnaud. crying

The "save misalgined" command in IFO_OVERVIEW screen doesn't work for ITMX. I didn't check other suspensions. Please have a look when you have a chance.

Comments related to this report
arnaud.pele@LIGO.ORG - 08:54, Friday 28 February 2014 (10405)

The script align_save script running behind medm seems to work ONLY when the sitemap is opened from the terminal.

H1 SEI (SEI)
fabrice.matichard@LIGO.ORG - posted 01:47, Friday 28 February 2014 (10397)
SEI Status

I am summarizing here recent progress on SEI units, and providing guidelines regarding what needs to be done next week.

Besides Guardian work on HAM-ISI (see Jamie's reports),  most of the work has been focused on BSC-ISI units:

 

Blend Filters for the BSC-ISI

We have started to standardize the blend configurations. There are three sets of blend filters that we selected as useful for commissioning and/or operations. They are:

- A set of blend filters called "Start". This filter has a 750 mHz blend frequencies in all degrees of freedoms. It doesn't include the T240. It will be used to turn on the BSC-ISI units. Unlike other "750 mHz" blend filters used in the past, this one provide adequate CPS low pass filtering to not short cut passive isolation.

- A set of blend filters called "T750 mHz". It is based on the same set of complementary filters as "Start", but includes the T240s.

- A set of blend filters called "Tcrappy". This set of blend filters is based on Ryan's noise analysis and filter design work. It has been slightly degenerated to fit into one filter bank and therefore be compatible with our "turn on scripts". Rich  named it "TCrappy"  to emphaisze that it still needs to be refined.

All other sets of blend filters previously tried at LHO can't provide adequate isolation. We are in the process of removing them from all BSC-ISI units filter banks (see status chamber per chamber below).

 

BSC-ISI Conrtrol configs

We currently have two pretty good configurations that we are populating in all chambers:

Config 1:  TCrappy on Stage 1 and Stage 2

Config 2:  TCrappy on Stage 1, T750 mHZ on Stage 2, and sensor correction form Stage 1 to Stage 2.

See ETMX for an example of results comparison.

 

ETMX

- The three standard set of blend filters have been loaded in FM0, FM1 and FM2 respectively. All other blend filters have been removed.

- The sensor correction from Stage 1 to Stage 2 has been installed. Preliminary gain matching has been done. I found a gain of 1.15. A 15% calibration is a bit surprising. To be checked. It gives good results anyhow.

The top left plot of "ETMX.png"  shows Stage 2 motion measured by the GS13s  in the X direction.

The bottom left plot attached shows optical lever pitch motion, amplitude spectrale density.

The bottom right plot attached shows optical lever pitch motion, RMS.

The red curves are references with damping only.

The brown curves show the motion with the "config 1" (Tcrappy everywhere). It reduces the optical lever RMS motion from 600 nrads to 40 nrads.

The magenta curve shows the motion with the "config 2" (Tcrappy, T750 and Sens Cor). It reduces the optical lever motion from 600 nrads to 30 nrads.

It is interesting to note that the two configs offer very different compromise as seen by the GS13s. TCrappy provides better isolation at the Quad's pitch frequencies (~0.45Hz), but the sensor correction config provides a slithly lower RMS. It makes me think we have room to improve the compromise between the feedback and feedborward controls parameters.

No big winds in the past few days, so we'll have to wait to find out wether config 2 behaves well under high wind conditions.

To be done next on this unit :

- tilt decoupling on Stage 2. I have made a template in data/transfer_functions/Isolated. It uses filtered white noise designed to increase the SNR at frequencies of interest and speed up the measurement.

- gain matching optimization for the sensor correction

- Control levels 3

 

ITMX

The blend filters have been written into the filter file tonight. However, the filters have not been loaded yet to not disrupt ongoing decoupling measurements on the quad.

To be done next on this unit :

- loading the blend filters and  test them

- Stage 2 tilt decoupling

- Sensor correction gain matching

 

BS Status

- The three standard sets of blend filters have been loaded in FM0, FM1 and FM2 respectively. All other blend filters have been removed..

- The sensor correction from Stage 1 to Stage 2 has been installed, but no gain matching has been done yet.

- The "BS.png" plot shows Stage 2 motion measured by the GS13s  in the X direction. The red curves show the motions with both stages damped. The blue curve shows all the badness that was induced by the old set of blend filters. The green curve shows what we have with the new set of "Start" filters. The brown curve shows the motion in the "Tcrappy" configuration. The pink curve shows the motion with the "Sensor Correction".

- We have studied the BSC-ISI saturations occuring during the lock acuisition process. It has been reduced for the level 1 controller. We have good insight as for making further improvements.

To be done:

- tilt decoupling on Stage 2

- gain matching for the sensor correction

- Control levels status -> to be checked with Jim and Hugh

 

ITMY

Sheila encourages us to work on this unit as soon as possible, before it gets extensively used for IFO activities. It should be one of the top priorities for next week.

 

Control Scripts:

I have made V4 folders for BS, ITMX and ETMX

Made and commited modifications to routine 6.

 

A general comment I am posting here for the records:

We need indicators at the top level screens showing whether electronigs are in the good gain and whitening states. I got caught several time in the past days.

 

Hugh and/or Jim, Jeff, Arnaud would know details I may not have captured here. Sebastien will be there to help next week.

Images attached to this report
H1 SUS
arnaud.pele@LIGO.ORG - posted 23:30, Thursday 27 February 2014 - last comment - 05:14, Friday 28 February 2014(10396)
ETMX and ITMX TF

Top length to test mass pitch/yaw measurements for L2P and L2Y decoupling on ETMX and ITMX were (re)started and will run overnight. The cavity is curently locked on green with ITMX and ETMX BSC-ISI running with ST1 Isolated in level 3. ITMX measurement is running in the background (with the diag -f command) on opsws1, and ETMX is running on opsws6 with DTT open.

RED TEAM : ITMX measurement should be done before 5am tomorrow. If ETMX is still running PLEASE PAUSE THE EXCITATION before misaligning it

Thanks to Alexa's instructions, locking the cavity with the green laser was fairly easy. Although few things to notice in the process :

- IMC guardian should handle turning on MC2 M2 and M3 length feedback switches. They were off when Evan and Yuta tried to lock the mode cleaner.

- Since the green beam was nicely centered when the ITMX BSC-ISI was damped, the ST1 CPS offsets were reset and stored as targets. (Otherwise it would ring up the T240 when isolating, and trip the WD).

Comments related to this report
kiwamu.izumi@LIGO.ORG - 04:59, Friday 28 February 2014 (10398)

ETMX TF measurement is done -- I don't see any excitation in the MEDM screen and there is no active diag process running on opsws6.

So I misaglined it by the guardian.

 

ITMX TF is still running. Note that opsws1 crashed but the process is still running. You can see it runing by sshing to the workstation.

kiwamu.izumi@LIGO.ORG - 05:14, Friday 28 February 2014 (10399)

We found that the excitation at ITMX was still at 10 Hz which means the measurement didn't progress over the past hours at all. We determined that diag was not a healthy state and therefore we killed the process.

H1 SEI (SYS)
jameson.rollins@LIGO.ORG - posted 22:31, Thursday 27 February 2014 (10394)
HAM2/3 ISI work summary: HAM ISIs now under guardian control

[Jamie, Fabrice]

HAM2/3 ISIs now under guardian control

After much initial headaches, we now have guardian nodes running for HAM2 and HAM3 ISIs (node names ISI_HAM2 and ISI_HAM3 respectively):

The above control screens are accessible from the guardian overview screen (blue "GRD" button on the site map).

The guardians are holding the ISIs in the HIGH_ISOLATED state (corresponding to "isolation level 3" in the old parlance).  The guardians are watching for watchdog trips, and will automatically bring the ISIs back to the requested state (HIGH_ISOLATED in this case) after the operator resets the watchdog.  State graph of the ISI_HAMX module that the nodes are executing is attached.

Things to note about operations of the HAM ISIs

The current configuration (high GS13 gain, lower blend filter cross over frequency) is not able to survive (de)isolation from/to very large bias offsets.  Fabrice and I tweaked the isolation gain ramps such that turning on and off the isolation loops (and the corresponding biases) survives offsets that correspond to an overestimate of the expected extrema of the platform drift (more detailed report to follow).  Given that we don't routinely hold large offsets on the HAMs we don't expect this to be too big of a problem.  And too be clear, the previous configuration wouldn't survive large offsets either, so we're definitely better off than we were.  After testing, we reset the CART_BIAS targets to the equilibrium position ("Reset CPS offsets" && "Store target offsets").

In any event, it's possible that over time the equilibrium position will drift far enough away from the current target that an attempt to move the isolation biases back will cause a WD trip.  This would likely happen after a WD trip caused by something else.  Resetting the target to the new equilibrium value should make the problem go away.

I'll be posting a more detailed report on the current HAM ISI configuration tomorrow.

Images attached to this report
H1 AOS
douglas.cook@LIGO.ORG - posted 16:11, Thursday 27 February 2014 - last comment - 10:54, Friday 28 February 2014(10393)
IAS euipment ready for the first look at ETMy
Jason and I are ready for the lateral and longitudinal ETMy position measurements in the AM. We won't know whether we will need to tweak the ACB position for any line of sight issues until the first look. Thanks Betsy and Travis for setting the ACB for us (temporary setup). We will not release the optic suspension for the fine positioning until we are satisfied that no large moves are needed.
Comments related to this report
travis.sadecki@LIGO.ORG - 08:52, Friday 28 February 2014 (10404)

Credit where credit is due: Mitch and Jim "installed" the ACB.  Betsy and I just uncovered the SUS and mounted the corner cube.

betsy.weaver@LIGO.ORG - 10:54, Friday 28 February 2014 (10407)

For posterity - the ACB is sitting on the ACB "table" in the tube section between the chamber and the spool.  This is to enable the IAS sighting of the ETMy optic without the ACB blocking the view while it is parked in the tube before install.  We chose not to install the ACB on Stage 0 because it blocks access to the 3rd blocked side of the QUAD making alignment and sensor tuning extremely difficult.  The ACB will be installed on Stage 0 after a few rounds of this is complete.

LHO General
gerardo.moreno@LIGO.ORG - posted 16:02, Thursday 27 February 2014 (10392)
Operation Summary

8:50 am, Arnaud running transfer functions @ ITMY.
8:55 am, Andres to LVEA, to work on or around the test stands, West bay area.
9:04 am, Hugh to LVEA, work at HAM5.
9:10 am, Jim B and Cyrus R working at Mid-Y.
9:27 am, Rick S, Craig C, and Chirs S to the LVEA, work inside the H2 PSL enclosure.
10:22 am, Kyle R, to LVEA, crane RGA equipment over Y-arm tube, he finished craning at 10:48 am.
10:30 am, Dave B, reboots and restarts for h1seih23.
11:49 am, Hugh, to LVEA, pick up tools from around HAM5.
1:35 pm, Kyle R, to LVEA, working with the 1.5" valve at gauge pair 124.
2:19 pm, Cyrus R and Jim B picking up hardware from Mid-Y, to retrive to EE shop.

H1 SUS
betsy.weaver@LIGO.ORG - posted 15:45, Thursday 27 February 2014 (10390)
PUM glass processing continued

Gerardo, Betsy

After having one failed ear bond early in the week on PUM ITM03, Gerardo sucessfully bonded both ears.

 

We also loaded PUM ETM06 (destimed for ITMx PUM replacement soon) onto the table and glued it's flag mounts and first of 2 prisms.  We'll get to the 2nd prism tomorrow hopefully.

H1 SUS
betsy.weaver@LIGO.ORG - posted 15:42, Thursday 27 February 2014 - last comment - 10:07, Friday 28 February 2014(10389)
WBSC10 ETMy SUS cables

While in the chamber, we also connected the 5 SUS and 1 ring heater cables to the feedthru and confirmed signal throughput on the 5 sus.  We pulled the C3 covers from both of the ETMy and TMSy suspensions before installing the corner cube. 

 

Jason and Doug should have a clear shot of the corner cube (and probably the edges of the optic) through the ACB from the spool.  We await X,Y,Z measurements.

Comments related to this report
betsy.weaver@LIGO.ORG - 10:07, Friday 28 February 2014 (10391)

In-vacuum ETMy SUS cable serial numbers:

 

Floor 1 of CB  D1000225-S1104879 to D1000234-88"- 941

Floor 2 of CB  D1000225-S1l04881 to D1000234-88" - 942

Floor 3 of CB  D1000225-S1104882 to D1000234-88" - 940

FLoor 4 of CB  D1000225-S1104880 to D1002522 - 924

 

Floor 1 of CB  D1000225-S1104883 to RH cable

Floor 2 of CB  D1000225-S1104878 to D1002522 - ? (ETMy L2 stage)

 

All are plugged into feedthrus on the F3 port of the chamber as per the WBSC10 D1200111 cable routing doc.

H1 SEI (INS)
hugh.radkins@LIGO.ORG - posted 14:59, Thursday 27 February 2014 (10387)
WBSC10 ETMY SEI Activities and Status

JimW & MitchellR

We payloaded the ISI Keel with the 600 lbs per D1002266-v1 (v1 really?); each 150lb stack sitting on 8 in2 of 1/4" thick viton.  See photo.

With that completed we unlocked HEPI and floated the platform (~15000lbs) on the HEPI DSCW Springs.  Next we shot level/elevation of the Optical Table.  See attachment for log notes.

The table actually started out pretty good, I thought we had disturbed it more during float.  The level had about 0.5mm runout and the elevationi was low 1.3 mm--all within spec.  We adjusted anyway to be 0.3mm runout and 0.2mm high.

Mitchell then joined Jim in chamber and moved the ACB deep into the Spool.  I then helped Betsy put the lift table into the chamber.  Jim & Mitchell moved the Table into the Spool and set the ACB atop the table.  Betsy & Travis were working to install the retroreflector for the IAS Y shot while Jason & Doug were getting their equipment readied,

Images attached to this report
Non-image files attached to this report
H1 ISC
jaclyn.sanders@LIGO.ORG - posted 13:07, Thursday 27 February 2014 - last comment - 10:19, Friday 28 February 2014(10382)
COMM PLL repairs

(Alexa, Jax, Stefan)

Alexa was trying to hunt down a missing gain factor for her model and instead found a busted COMM PLL board (serial number S1200564). The op-amp for the VCO compensation stage (U37) was blown. I recalled replacing the same op-amp on the DIFF PLL about a month ago, suggesting that there's something that makes this particular op-amp vulnerable. After discussing with Richard McCarthy, we opted to change resistor R96 from 0 to 2k ohms to protect the poor thing. Lab tests show that it's in good shape, and it'll be back to the ISC rack as soon as we're done with the ISC meeting.

Comments related to this report
peter.fritschel@LIGO.ORG - 13:51, Thursday 27 February 2014 (10384)

Should this resistor change be propagated to all PLL boards?

jaclyn.sanders@LIGO.ORG - 13:56, Thursday 27 February 2014 (10385)

No, we're still thinking about it. It's going in as modified and if it keeps having problems, we'll burn that bridge when we get to it.

jeffrey.kissel@LIGO.ORG - 10:19, Friday 28 February 2014 (10406)
This smells of an ISC integration issue so we don't forget...
H1 CDS (SEI)
david.barker@LIGO.ORG - posted 11:35, Thursday 27 February 2014 - last comment - 18:50, Thursday 27 February 2014(10379)
all models on h1seih23 restarted to clear frozen DAC outputs

Fabrice, Jamie, Jim, Dave

I restarted all the models on h1seih23 to clear the no-DAC-output problem.

Sequence was: stop user models, restart IOP model, start user models

models are h1isiham2,3 h1hpiham2,3 h1iopseih23

Fabrice then put ISI ham 2,3,4,5,6 into a safe state, and I updated the safe.snap files in SVN and committed them.

Comments related to this report
keith.thorne@LIGO.ORG - 18:50, Thursday 27 February 2014 (10395)
Has the /etc/startWorld.sh script been installed on H1 front-ends?  That is what is used at L1 for these restarts.
H1 ISC (ISC)
evan.hall@LIGO.ORG - posted 09:56, Wednesday 26 February 2014 - last comment - 16:43, Friday 28 February 2014(10345)
Setting up PRC length measurement with auxiliary laser

[Ed, Evan]

We are preparing to make a measurement of the length of the PRC using the phase-locked auxiliary laser technique described by Chris Mueller (T1400047). Previously, this has been used to measure the Livingston IMC length (LLO alog 9599).

We set down a 520 mW Lightwave NPRO on the IOT2R table, along with a Faraday isolator and steering mirrors. We will inject this beam into the PRM_refl side of the IOT2R periscope. The beam will hit the back of IM4, and a small fraction (2400 ppm) will be transmitted toward the PRM. This gives 1.2 mW of auxiliary power on the PRM, compared to 9 mW of 45MHz PSL single-sideband power on the PRM.

Most of the auxiliary power should reflect from the back of IM4 and return to the IOT2R table via the IO_forward side of the periscope. For mode-matching, we hope that we can simply send part of the IO_forward beam onto a New Focus 1611 and maximize the observed beat. Currently, there is 3 mW of power in the IO_forward beam.

Using this beat, or otherwise, we will phase-lock the auxiliary laser to the PSL carrier beam. Then with PRMI locked on the PSL sideband, we will sweep the offset to the auxiliary PLL and monitor the RF coming out of POPAIR_B. We should see the strength of the RF reach a maximum whenever the auxiliary beam is coresonant with the the PSL sideband. By tracing out the Lorentzian profile of the RF amplitude across successive resonances of the PRC, we can extract the FSR of the PRC. Given a design length of 57.6557 m, we expect an FSR of 2 599 850 Hz. If we can measure the FSR to within 100 Hz, we can get the PRC length to within 2 mm.

Comments related to this report
evan.hall@LIGO.ORG - 15:47, Thursday 27 February 2014 (10388)

Yesterday we got the NanoScan back from EX and Ed used it to measure the beam parameter coming out of the Faraday isolator. The waist is about 100 µm and located more or less in the middle of the isolator. The size is maybe a bit smaller than we want, but we appear to be able to get more than 90% of the power through, with a reasonably Gaussian mode.

After the FI, we placed a HWP to set the beam to be s-polarized. After this, we placed a New Focus 5104 as a first steering mirror. As a second steering mirror, we use IO_PRMR_BS1.

We removed a lens from between IO_PRMR_M3 and IO_PRMR_BS1. It was unlabeled, and anyway there is nothing after that lens except beamsplitters and dumps.

We did an ALM optimization to mode match to the PRM. Joe Gleason's IOT2R layout (D0902284) gives the distance from the bottom of the IOT2R periscope to the PRM as 3.6 m. The spot size is 2.24 mm, with a ROC of 11 m (T0900407, p 5). ALM told us to put an f = 500 mm lens about 3 inches before IO_PRMR_M3 ("before" meaning "closer to the FI").

We put down two irises in order to constrain the pointing of the PRM_Refl beam. We then blocked this beam and steered the auxiliary beam through the irises. With a little tweaking, we were able to see our beam coming out on the IO_Forward part of the periscope. We measured the power of this beam and found that it was only about 5% of what we were putting in. This initially confused us, until we realized that our path in HAM2 has to go through a 90% reflector which is intended for the ISS. Given that IO_PRMR_BS1 is a 90% reflector and ROM LH1 (in HAM2) is also a 90% reflector, we in fact only expect 90% × 90% × 10% = 8% of the power to come back onto the IOT2R table.

evan.hall@LIGO.ORG - 16:43, Friday 28 February 2014 (10432)

Yesterday, we put down the New Focus 1811, aligned the PSL and auxiliary beams from IO_forward onto the PD. We found a beat with the auxiliary laser temperature around 37.7 °C. By tweaking the auxiliary input pointing, we were able to get -4 dBm of RF beat out of the 1811 with about 1 mW of DC power from each beam in front of the PD (so 2 mW total).

We were then able to implement a PLL using an HP function generator and the LB1005 servo box. We set the function generator to ~30 MHz and +7 dBm, and used it to drive the LO of a mixer. We took the beat and put it into the mixer RF. The IF was terminated, filtered at 1.9 MHz, and then fed into the LB1005. The output of the LB1005 was then fed into the fast input of the laser. We were able to catch lock by turning the laser's temperature control knob to push the beat toward 30 MHz. The lock would hold for about 1 minute before the controller saturated. To maintain sanity, I suspect it will be necessary to implement a slow temperature loop to relieve the fast controller.

Displaying reports 72901-72920 of 82999.Go to page Start 3642 3643 3644 3645 3646 3647 3648 3649 3650 End