Displaying reports 75181-75200 of 84537.Go to page Start 3756 3757 3758 3759 3760 3761 3762 3763 3764 End
Reports until 02:06, Thursday 30 January 2014
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 02:06, Thursday 30 January 2014 - last comment - 02:12, Thursday 30 January 2014(9644)
Infrared laser locked to X arm for studying the green beat noise

Stefan, Kiwamu

As a part of the beat noise study, we locked the main infrared laser to the X arm cavity by feeding the reflection signal back to the MC length.

Although we succeeded in locking the IR,  the beatnote tonight was not great at all. It was roughly 500 Hz / sqrtHz in a band from 1 to 900 Hz when the infrared was locked. Plus, the mode hopping was so frequent that I was not able to integrate the spectrum lower than 1 Hz.


IR locking to the X arm:

Because the green light tonight was not stable enough for us to do the CARM hand off, we instead started locking the IR to the X arm. This is the first time for us to directly lock the infrared main laser to an arm cavity without an aid of the ALS technique. We started this from estimating the PDH optical gain of REFLAIR_RF9 by simply looking at the free swinging wave form. According to Alxea's math (alog 7054), we got ~ 1.21 counts/Hz for the optical gain. Also the MC2 M3 stage was approximated to be 18.2 / f^2  Hz / counts. Using these two information, we set the LSC gain to be 0.46 as an initial guess. Note that we cranked up the whitening gain of REFLAIR9 to its maximum. The demod phase was also adjusted to maximized the PDH signal in in-phase. We then fed it back to MC2.

A good servo gain was then empirically found to be about -0.2. Even though we didn't have a transmitted DC or reflected DC signal, we could tell if we grabbed a sideband resonance or carrier resonance by looking at the size of the Q-signal. This allowed us to detemie the right control sign.

The locking procedure is as follows:

  1. Lock IMC
  2. Remove all the notches and aggressive filters in MC2 M3 ISCINF_L.
  3. Turn on only FM3 and FM6 in MC2 M3 LOCK_L to have a large phase margin from 40  to 500 Hz.
  4. Run the beatnote tracking servo using ezcaservo (see Daniel's instruction in alog 9559).
  5. Decouple the MCL at DC by enabling FM1 of LSC_MC
  6. Make sure that the input matrix is set right so that REFLAIR_RF9_I will be used.
  7. Engage the reflection PDH servo which is currently in LSC-SRCL filter. Use  FM2 FM3 and FM4 with a gain of -0.2.
  8. Once the PDH signal becomes quitter, stop the ecaservo and also cut the LSC-MC path by enabling FM7.

One major difficulty we had during the IR lock was that a mechanical resonant mode at 41 Hz (bounce? roll? of MC2) rang up so much that we could not keep locking the IR. We often let the IMC alone to allow it to settle down for a while and this helped a lot. Also Stefan could introduce the additive offset path on top of the MC length control. He had to crank up the input gain of both common mode board and IMC board to the maximum of 31 dB. It seems that we could still go higher although we didn't quantitatively evaluate it yet. This additive offset technique should serve as a good mitigation for this 41 Hz mode issue while maintaining a high control bandwidth.

The attached is a screen shot of the IR locking configuration.

 

Noise of the green beatnote was far from good:

The noise performance of the green beatnote was not great. Something must be wrong. The smallest noise floor I could get was approximately 500 Hz/sqrtHz in a band from 1 Hz to 900 Hz.  I tried not include a mode hop during the spectrum integration. Even so, as you can see in the attached spectrum, it was suspiciously  flat. I used H1:ALS-C_COMM_PLL_CTRL for measuring the beat noise. The calibration was done by injecting a known RF frequency into the PLL and measuring the ADC counts. It was measured to be 7.916 Hz/counts. Also I added a z40/p1.6 filter to cancel the VCO response.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 02:12, Thursday 30 January 2014 (9645)

Additional Note:

PRM is currently in its parking position to avoid a power-recycling fringe at the reflection port.

H1 AOS (IOO)
paul.fulda@LIGO.ORG - posted 20:41, Wednesday 29 January 2014 (9643)
IM4trans whitening gain adjusted

I noticed that IM4trans S1 and S2 channels were saturated, probably after the power increase (similar to the case for IMC WFS noted in entry 9094).

I adjusted the whitening gain down from 45dB to 36dB, which brought segments S1 and S2 down from the rails. IM4trans signal looks better now.

H1 CDS
david.barker@LIGO.ORG - posted 18:01, Wednesday 29 January 2014 (9639)
MSR doors open and fan is running
following the failure of one of the three cooling units in the MSR, as a precaution against a second failure we are keeping the hallway doors open and a fan running overnight.
H1 PSL
kiwamu.izumi@LIGO.ORG - posted 16:19, Wednesday 29 January 2014 (9637)
ISS PD offset jumped

Stefan, Kiwamu

We found that the ISS diffracted light had been high at 24%. According to the trend, it looks that both PD_A and PD_B suddenly got an offset of about 0.5-ish volt and it pushed the diffraction ratio to the high value. The jump happened at around 9:41 local in this morning. Neither Keita nor Yuta was at around the ISC/PSL rack at this specific time. At this point it is unclear what happened or what might have triggered it. The attached is the trend showing the funny jump which also decreased the carrier power everywhere.

For now, we changed the reference offset to bring it to approximately 9%. The new reference offset is:

H1:PSL-ISS_REFSIGNAL           -2.31548

A further investigation is needed.

Images attached to this report
H1 ISC
keita.kawabe@LIGO.ORG - posted 16:03, Wednesday 29 January 2014 (9631)
COMM PLL good to go (Jax, Yuta, Keita)
After confirming that the readout path output of COMM PLL (for CM board) has a large offset (about 4.8V) regardless of the PLL board setting while the output for VCO path was seemingly OK, we pulled out the chassis.

It was U37 (AD829 for z1.6Hz:p40Hz) that was busted. 

Jax tested the board, replaced the broken chip and tested again. She also found that the VCO path output was only routed to the external connector on the back panel, so she connected the internal VCO path SMA cable.

The fixed unit was put in place, the offset was not crazy (about 430mV when input was off, 13dB gain, two common filters on, went down to 13mV when both of the common filters were turned off), we cabled it up. 
H1 General
andres.ramirez@LIGO.ORG - posted 16:00, Wednesday 29 January 2014 - last comment - 07:52, Thursday 30 January 2014(9636)
Ops Shift Summary
8:30–9:00 Going into the LVEA to work on dust monitor – Patrick
9:01      PSL Check List done (noticed the ISS Diffracted Power was                     
          Close to 24% - It should be 5-15%)
9:00–10:30 Water Ground staff on site for water sampling – Hanford
9:27–10:03 Back in the LVEA to swap dust monitor power supply–Patrick                      
9:36-      Starting Initial Alignment of Ham 4 optical table- Hugh
9:41       PSL Check List done (noticed the ISS Diffracted Power was                       
           close to 24% - It should be 5-15%)
9:49–12:06  Working on ACB in LVEA West Bay – Mitchell/Scott
13:05-13:59 Back to work on ACB in LVEA West Bay – Mitchell/Scott
13:10-15:14 Periscope assembly on H2 PSL – Joe
13:46-14:48 Installing Tablecloth bracket on SR2 (LVEA) – Jeff B.
13:50-15:14 Joining Joe for periscope assembly on H2 PSL – Craig/Sam
15:00       Safety Meeting 
Comments related to this report
hugh.radkins@LIGO.ORG - 07:52, Thursday 30 January 2014 (9646)

Left LVEA ~1745

H1 IOO (IOO, ISC)
paul.fulda@LIGO.ORG - posted 15:02, Wednesday 29 January 2014 - last comment - 18:04, Wednesday 29 January 2014(9633)
ISCT1 beam size measurement preparation

This afternoon I went to ISCT1 to begin setting up for the beam size measurements that we hope to use to diagnose the PRC mode matching situation (see LIGO-T1400013).

I took the beam analyzer cart from the optics lab out to ISCT1 and left it set up there. I measured beam powers in two locations just after the REFL periscope: one in reflection of the pick off window directly after the lower periscope mirror, and one after. Since we aim to measure two beams in the REFL path with powers differing by a factor ~4000 it's useful to have low and high attenuation locations. The window is not AR coated so there are two beams visible in reflection. I measured the power of one to be 890uW, and the other to be 800uW, with the low-power head on the VEGA power meter. The beam in transmission of the window was measured to be 123mW. I left the table with the window reflected beam dumped, and the photon inc. beam analyzer behind the dump.The window transmitted beam is still dumped on the shutter.

Comments related to this report
paul.fulda@LIGO.ORG - 18:04, Wednesday 29 January 2014 (9640)

I just looked for the beam in the same locations with PRM misaligned (sending direct PRM reflection to the parking dump). This should be the beam transmitted through PRM, reflected off ITMX, transmitted through PRM again and sent on to ISCT1. The good news is, the beam was still nice and visible on the IR card after the pick-off window yes

I tried to measure the power at that location with the same power meter as before, expect with the filter out. Due to the X-arm work going on, the beam was finging quite a bit in the IR, so I couldn't get a very solid reading. It looked like around 50uW on average, with a peak value of ~80uW. Comparing this with the PRM aligned value it seems a little high. The PRM misaligned beam should be roughly T_PRM^2 * T_BS^2 = 2.25e-4 times the PRM aligned beam. This means I would have expected 123mW*2.25e-4 = 28uW. Maybe some of the green light was leaking in, or maybe the X-arm flashes were confusing the power meter... it will be easier to get a good measurement here with ETMX and ITMY misaligned later. I can't take beam profile measurements until then anyway.

H1 SUS
arnaud.pele@LIGO.ORG - posted 14:50, Wednesday 29 January 2014 (9632)
ETMX snapshot

I took a new safe snapshot of ETMX after correcting the gain of 10 spotted yesterday in the L1 sensalign matrix, and engaging the "norm" R0 damping filters.

H1 CDS
daniel.sigg@LIGO.ORG - posted 13:09, Wednesday 29 January 2014 - last comment - 18:16, Wednesday 29 January 2014(9629)
DAQ/dataviewer limitation?

We are trying to record the frequency of the ifr, but there is a 4Hz offset between the EPICS readback and the value reported by dataviewer and/or saved by the DAQ.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 17:45, Wednesday 29 January 2014 (9638)

Looks like a dataviewer/xmgr problem. When plotting this data using diaggui we get the correct value.

Images attached to this comment
david.barker@LIGO.ORG - 18:16, Wednesday 29 January 2014 (9641)
the eagle eyed amongst you will have noticed the root plot Y-axis doesn't look correct. The data line is 2256 but the Y-range is actually 2260 to 2270 suggesting the data is 2260 (as xmgr showed it). Jim ran command line nds client on this channel and confirmed the DAQ is recording the correct frequency of 24992256Hz. Unfortunately both xmgr and root seem to have plotting problems with static numbers of this magnitude.
H1 ISC
daniel.sigg@LIGO.ORG - posted 11:59, Wednesday 29 January 2014 - last comment - 16:06, Wednesday 29 January 2014(9626)
The way of the beast

(Alexa Daniel)

We went to EX to try to make a more precise measurement of the cavity length. For this measurement we use the fact that in reflection of a locked cavity a phase-modulated RF sideband will not convert into AM, if it is exactly on a free-spectral-range even in the presence of length locking offset. The setup is as follows:

At first glance the accuracy of this method seems to be about 5 Hz, maybe even 2 Hz. We will repeat the measurement in the afternoon to see how repeatable it is.

Comments related to this report
alexan.staley@LIGO.ORG - 12:50, Wednesday 29 January 2014 (9627)

To measure the arm cavity length we measured transfer functions while adusting the IFR frequency. The data includes the magnitude and phase at 1.3kHz for the several frequencies. The ArmCavityLength.m script computes the projection of these TFs at the various frequencies to determine the zero crossing.

The ZeroCrossing.pdf is a plot of the result. The x-axis is the frequency scaled by 24.992271MHz. Notably, the IFR frequency has an offset of 12Hz which has been adjusted for in this plot. Clearly, the zero crossing is at 24.9922709MHz, which gives an arm cavity length of L = 3994.4704m /pm .3mm assuming a zero crossing accuracy of 2Hz.

Non-image files attached to this comment
daniel.sigg@LIGO.ORG - 15:58, Wednesday 29 January 2014 (9634)

As built numbers can be found in alog 9385.
A previous measurement with less accuracy can be found in alog 9386.

alexan.staley@LIGO.ORG - 16:06, Wednesday 29 January 2014 (9635)

We repeated the measurement again this afternoon. I have attached the data, graph, and new matlab script. Again we find that the zero crossing is at 24.992271 MHz /pm 2Hz. This gives an arm cavity length of L = 3994.4704 m /pm .3mm. 

Note: the 12 Hz offset between the IFR and timing comparator was consistent.

Non-image files attached to this comment
LHO General (PEM)
patrick.thomas@LIGO.ORG - posted 10:54, Wednesday 29 January 2014 (9625)
Swapped power supply for Comtrol used for H1 PSL Lighthouse dust monitors
This is the Comtrol Ethernet to serial converter in the H1 PSL electronics racks being used for testing the Lighthouse dust monitors in the enclosure. The connection between the power supply and the box was flaky and had failed. I swapped power supply S/N 00089 for S/N 01411. It appears that it is just a bad sizing tolerance mismatch between the two.

From the alarm log, the power appears to have failed at 10:19 on January 24, 2014. The last data point before today was recorded around 15:56 on January 24, 2014.
H1 CDS
cyrus.reed@LIGO.ORG - posted 09:20, Wednesday 29 January 2014 (9624)
MSR A/C Failure

One of the air conditioning units in the MSR failed last night prior to 3:48 AM (at which point it had reached 88 deg F).  The error code reported on the thermostat control panel was 'E6'.  I have engaged the standby unit, and opened the door and started a fan to return the room to it's desired temperature.

H1 SEI (INS, ISC, SUS)
jeffrey.kissel@LIGO.ORG - posted 18:04, Tuesday 28 January 2014 - last comment - 06:41, Wednesday 29 January 2014(9612)
H1 ISI ITMX 0.5 [Hz] Comb: The Whole Answer and History
[A. Pele, S. Biscans, J. Warner, H. Radkins, F. Clara, R. McCarthy, K. Kawabe, J. Kissel]

We've been chasing the source of an exactly-0.5 [Hz] oscillation (and subsequent higher-order harmonics) in the H1 ISI ITMX, that was first identified in LHO aLOG 9494. After testing the ISI in many different configurations (See LHO aLOGs 9546, 9951, 9585, and 9605), and ruling out capacitive position sensors -- already been shown to have *other* oscillations and frequency combs because an unrelated problem with beating oscillator sync frequencies, see LLO aLOG 10629 -- we narrowed down the source of the problem to the Y3 channel of the Corner 3 T240 on Stage 1. With a single channel to attack, we launched Filiberto on the problem. He identified and fixed the problem (as indicated in 9607). I attach some visual aides to describe the problem; see H1ISIITMX_CableProblem.pdf, and further details below. I also attach a comparison of the performance using the same metrics as in the original discovery, with the ISI in the same control system configuration, but now with all combs absent. We get an RMS of 70 [nrad] in Pitch, which appears to be "pretty good" for the green team. Nice work, gents!

The path forward (for this chamber): This ISI still does not have sensor correction running, LLO's really-low-frequency blend filters, nor has it had any attention paid to optimizing the rotational DOFs to minimize sensor-noise, tilt-horizontal-coupling. All of these things can improve the stage 1 performance between ~0.1 [Hz] and 1 [Hz]. Further, we can probably add more gain to the QUAD damping loop filters at 0.56 [Hz] (the remaining peak corresponding the first "pitch" mode). There is some resonant gain already present, but I can check if we can add more -- the filters were designed for a Monolithic QUAD, where ITMX is a Wire-Hang QUAD and they have different first pitch mode frequencies. Further, we have done any coil balancing or frequency-dependent alignment decoupling which may also help.

Note that we still have to solve the CPS Oscillator Beat Frequency Combs resulting from other chambers, but that's another problem for another day (Rich Mittleman lands tomorrow, and that's one of his primary tasks).

Details:
-------- 
The Problem (w/ visual aides):
- PG1: A screenshot of the BSC-ISI Wiring Diagram (D0901301-v10, pg 10), showing the big-picture of the T240 signal chain, from the actual sensor inside the pod, inside the ISI, inside the BSC chamber to the cable going from the T240 Interface Chassis to the Anti-Aliasing chassis. The problem was inside the cable-side of the connection at the T240 Interface chassis, on the rack side of the long cable run from the chamber flange to the rack, which I've circled in red.
- PG2: A zoomed in screenshot of the chassis. The busted pin, Pin 2, which carries the positive leg of either the Y / V DOF had been broken inside the backshell of the cable. I've again circled the problem in red. Fil originally identified the flaw by testing the continuity of the cable and found the dead short on that pin. Fil conjectures that the pin failed because, again inside the backshell, the male pin had been over-crimped and/or not seated well, such that repeated normal use of the connector and bending of the cable caused the connection to snap.
- PG3: An example of a male DB25 connector, looking at the side which would be enclosed inside the backshell, and an associated pin. The pin is crimped to the signal cable, and press-fit in the connector hole.
- PG4: An example of a male DB25 connector, looking at the external connection side. I've only pushed the pin half-way in, but one can see how the pin might be mistaken for functional, but still not be fully seated.

Current Configuration of the ISI in this measurement:
- ISI-ITMY and ISI-BS CPS OFF
- HPI-ITMX running Level 1 Isolation Filters, with a position sensor only blend filters on all DOFs.
- ISI-ITMX running Level 1 Isolation Filters, with "T100mHz_N0.44" blends on ST1 XY and "750mHz" on ST1 ZRXRYRX and all of ST2. Note with out the extra 0.5 [Hz] notch that was the temporary temporary solution from a few days ago.
- SUS-ITMX running Level 2.1 damping loops.

The History:
Jim recalled having problems with this exact channel just after the cartridge install in mid-November 2013: though they were able to find a configuration in which their spectra passed acceptance testing (see E1100848), they spent a few days trying to fix a low-gain issue with this same channel (exactly a factor of two). Though we could not find any associated aLOGs, or saved raw data, Jim did managed to find a few saved .pdfs of the problem, one of which I attach here (see ITMX_ASD_after_filter_reload_2013_11_15.pdf). At the time, Jim and Seb were focused on solving the fact that the channel had a factor-of-two lower gain that the other 8 T240 DOFs, and in the rush that was ITMX they didn't notice the minor bump at 0.5 [Hz]. Further, he and Sebastian spent several days on it, because the fact-of-two problem was intermittent, and found that jostling the cable at the flange (not at the rack) was the most effective way to mitigate it. It went further unnoticed until we began *using* the T240s in the ST1 isolation loops. In summary -- this cable problem has been present ever since its install, but due to the usual chaos of a chamber install, plus the holidays, plus the rotating door of seismic commissioners with higher priorities, it was missed. HOWEVER, I really don't put anyone nor any testing procedure at fault; this is a 1 and 1000, perfect storm of problems that we will continue to have for the next few years as we begin to push the aLIGO systems to their designed performance levels.
Non-image files attached to this report
Comments related to this report
peter.fritschel@LIGO.ORG - 06:41, Wednesday 29 January 2014 (9623)SYS

Plug for Integration Issue Tracker:

I don't disagree with Jeff's conclusions at the end of his entry. However, I did want to suggest that the flaky behavior observed in November could have been put into the Integration Issue Tracker, and had it been, we probably would have zeroed in on the cabling much sooner when the 0.5 Hz issue arose. This isn't just a '20-20 hindsight' comment -- as Jeff says, we will continue to have to deal with this kind of issue, so let's take this as a lesson to use the Issue Tracker as another tool to help us debug and improve the instrument.

Displaying reports 75181-75200 of 84537.Go to page Start 3756 3757 3758 3759 3760 3761 3762 3763 3764 End