Displaying reports 69161-69180 of 85060.Go to page Start 3455 3456 3457 3458 3459 3460 3461 3462 3463 End
Reports until 11:12, Thursday 29 January 2015
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 11:12, Thursday 29 January 2015 - last comment - 11:26, Thursday 29 January 2015(16340)
some maintenance in initial alignment

Ed and Kiwamu,

In the morning of today and yesterday, we went through all the initial aligment steps. In the course of the process, we found that there were a few settings that were hidden and not set correctly. So we made a couplle of modifications on the guardians and filter in order to automate them:

The attached screenshot shows the current good settings in order to go through the alignment sequence. This configuration should be automatically achieved by the guardians.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 11:26, Thursday 29 January 2015 (16341)

Some additional notes:

We found two failure modes which we did not get a chance to fix the guardians. I will have a close look at them tomorrow morning or next week.

  • ISC_DRMI for some reason did not set the PSL power back to the nominal of 10 W even though we requested the DOWN state.
  • When locking PRX, LSC_CONFIGS got stuck in LOCKING_PRX even though ASAIR_A_LF exceeded the threshould value.
H1 ISC
sheila.dwyer@LIGO.ORG - posted 01:47, Thursday 29 January 2015 - last comment - 09:08, Friday 30 January 2015(16335)
CARM at ~30 pm

Kiwamu, Elli, Alexa, Evan, Rana, Daniel, Sheila

Today we were able to reach CARM offsets around 30 pm.  

We transitioned DARM to AS45Q, at a CARM offset where sqrt(TRX+TRY) was -7, we then normalized the signal by sqrt(TRX) (with a factor of 0.23).  One important step in getting there was to implement the ezca servo that adjusts the ALS DIFF offset to bring AS45Q into the linear range.  We are now using that both at a CARM offset of 1 (in SQRT TRX+TRY), and after we transition to the QPDs.  We then change the DARM loww pass filter from a 33Hz low pass to a 80 Hz low pass, to get better phase margin since we are no longer saturating the ESD with ALS noise.  We did this transition several times sucessfully.  As Rana mentioned in alog 16334, we installed an ND1 filter on ASAIR A.  Since this we haven't transitioned to RF DARM again (for reasons that seem to be unrelated to the ND filter), so we will need to check the gain before we transition again. 

After making this transition, Elli, Kiwamu and Rana worked on the DHARD WFS, which we turned on to reduce the fuctuations in AS DC.  This allowed us to go to CARM offsets -25 in sqrt(TRX+TRY), which is about half of the total power we expect in the arms.  If you assume that the recyling gain is 30 (we don't really know) it is something like 30 pm.  In Refl DC we saw the power drop by about 20%.  We saw that the linearized REFL 9 I signal had turned over, and that without linearization the signal had reached the peak.  We made a few attempts to transition, and we were able to turn down the gain of the TR CARM signal to 50% of the nominal and turn the REFL 9 signal to what we think the nominal gain should be (-100 in the input matrix).  We lost the lock when we turned off the TR CARM signal.  Our next plan was to leave the TR CARM engaged with reduced gain, and keep reducing the CARM offset.  

However, we have been having a hard time locking in the last few hours.  We think that it might help to try transitioning to DARM to RF a little sooner, so that we could use WFS.  

The sequence that was working earlier this afternoon is in guardian up to the RF DARM transition, although this might need to be re-worked.  We have added but not tested a state for the DHARD WFS. 

Attached is a screenshot of our striptool durring the sequence, which was all handled by the guardian this time.  

Images attached to this report
Comments related to this report
alexan.staley@LIGO.ORG - 02:06, Thursday 29 January 2015 (16336)

As we were about to leave we had a nice stable lock. We were able to transition to RF DARM again at -7.0 cts CARM offset after having adjusted for the ND filters. We now have a +20dB filter in ASAIR_RF45Q, and the input matrix is now 25. We turned on FM4(z4^2:p1^2) in DARM loop which significantly helped the DARM noise. We then proceeded to adjust the CARM offset to -20 cnts. At this point we transitioned TR_RELF9 to 100% with TR CARM at 50%. We were able to reduce the CARM offset to zero, but this only lasted for about a second or so. We never fully turned off TR CARM,  but we think it has a zero slope here since we are at zero offset. More tomorrow when we are awake ....  

 

Lock loss time: 09:58:40 UTC Jan 29th

gabriela.gonzalez@LIGO.ORG - 05:28, Thursday 29 January 2015 (16337)
Great work!
lisa.barsotti@LIGO.ORG - 10:59, Thursday 29 January 2015 (16338)ISC
Assuming I am looking at the right lock attempt, (data attached starting at 09:48:00 UTC) it seems that REFL DC is only ~30% less than at the beginning of the sequence when you transition to RF. There should be room to get closer. 

P.S: For comparison, trend of powers with "lossy" arms is here. The build up in the arms for same relative REFL DC power was about a factor of 3 lower (by eye numbers).
Non-image files attached to this comment
evan.hall@LIGO.ORG - 18:50, Thursday 29 January 2015 (16344)

Daniel and Rana have mentioned that optical torques may become significant as we come in to resonance.

Summary

For 10 mm of miscentering and 46 kW of circulating arm power (at 0 pm of CARM offset), we get a torque of 3×10−6 N m. I estimate the stiffness constants of each pendulum to be 4.9 N m for pitch and 6.5 N m for yaw (a better estimate could be made using the actual suspension models). This means that the static misalignments induced by the radiation torque could be as large as 1 μrad. The attached code computes the torsional stiffnesses of the pendula.

Details

  • For 8 W incident on the IFO with the PRM misaligned, we expect 0.12 W incident on each arm. Assuming an arm gain of 283 W/W, that gives 34 W of circulating power.
  • From LHO#15390, with the IFO locked we expect a buildup of 1350 W/W compared to the PRM-misaligned single-arm case. That gives 46 kW of optical power.
  • The torsional stiffness of the pendulum can be found by computing the moment of inertia of the test mass for pitch and yaw rotations. Combined with modeled torsional frequencies, the stiffness is given approximately by κ = ω2 I.

As a next step, we might also consider the stiffness of the optical springs using, e.g., eqs. 31 in the paper by Sidles and Sigg. At 46 kW of circulating power, we get 15 N m for the major mode and −0.6 N m for the minor mode.

[Edit: Also, Kiwamu has pointed out an error in the expression for the moment of inertia for the test masses. This has been fixed in this entry and in the attached code.]

Non-image files attached to this comment
evan.hall@LIGO.ORG - 14:37, Thursday 29 January 2015 (16352)

Here are some oplev trends from last night's final lock attempt.

The drop in the buildup of POP18 seems correlated with a drift in ETMX pitch (0.3 μrad), and to a lesser extent BS pitch (0.2 μrad), SR3 pitch (0.4 μrad) and ITMY pitch (0.2 μrad). There may also be some drift in PR3 yaw and pitch (≈0.1 μrad). All of these drifts happen on time scales much slower than the change in TRX buildup, which supports the idea that these are thermal drifts induced, e.g., by wire heating.

Non-image files attached to this comment
eleanor.king@LIGO.ORG - 14:25, Thursday 29 January 2015 (16351)

For the record here are some lock loss times from last night:

 

Early in the evening we were trying to transition DARM from ALS_DIFF to ASAIR_A_RF45_Q and the lock dropped at the following times:

Jan 28 20:46:40 UTC, Jan 28 21:06:32 UTC, Jan 28 21:06:17 UTC, Jan 28 22:55:00 UTC.

Speculating from the lock loss plots, we think that DARM noise causes a big spike in light leaking out of the AS port.  This causes the power on the  LSC-TR_X/Y_QPDs controlling CARM to fluctatue enough that CARM drops lock.  Running the ASAIR centering servo should help minimise big spikes at ASAIR_A_LF.  Once we were able to transition DARM to RF this type of lock loss stopped happening.

-----------------------

Here are some lock losses from after the transition DARM to RF.  The cause of these lock losses remained unclear.  MICH, PRCL and SRCL were ringing up signals at various frequencies (4Hz-20Hz) but this changed from lock loss to lock loss.  Again there are big spikes in ASAIR_A_LF right before the lock loss.  ETMy alignment needed frequent touching up.

Jan 29 00:28:31 UTC, Jan 29 00:49:41 UTC, Jan 29 05:34:23 UTC. 


--------------------

Later in the evening we were having  a hard time locking.  Again we were loosing lock before DARM transition to RF.  Again there are big spikes in ASAIR_A_LF, probably caused by DARM motion.

Jan 29 07:35:25 UTC, Jan 29 07:35:25 UTC, Jan 29 08:24:26 UTC, Jan 29 08:40:40 UTC

sheila.dwyer@LIGO.ORG - 14:51, Thursday 29 January 2015 (16354)

Here is a screen shot of the CARM offset reduction from earlier in the evening, when the alingment must hve been slightly better.  Although we didn't reduce the CARM offset, and were locked on TR CARM, we had a recylcing gain of about 10.2.  Also, some of the signal from POP18 and POP90 is rotated into the Q phase as CARM offset is reduced.  

Images attached to this comment
lisa.barsotti@LIGO.ORG - 09:08, Friday 30 January 2015 (16366)ISC
Peter, Matt, Lisa

For the records, we had this theory that if the f_1 was tuned such as to make the 2f_1 resonant in the arms, the beat between the 2f_1 and the carrier in the recycling cavity could be responsible for the decay in POP18. 
Looking in the L1/H1 logs and MEDM screens, we arrived at the conclusion that in H1, given the arm length of 3994.4704 m and f_1  = 9.100230 MHz, the offset from resonance for the 2f_1 should be 380 Hz.  
In L1 the offset for the 2f_1 from resonance is 500 Hz (reported here), as nominal.
H1 AOS
rana.adhikari@LIGO.ORG - posted 00:24, Thursday 29 January 2015 (16334)
ASAIR saturation: ND 1.0 installed

Alexa, Rana, Ellie

We noticed that one of our locklosses during the CARM offset reduction (after we're transitioned onto AS45 -> DARM) seems to be due to ADC sauration in ASAIR 45 so we put in an ND1.0 screwed onto ASAIR_A.

In the attached plot you see that ASAIR_A_45 goes to 0.0003. Since we have a -160 dB digital filter between the ADC and this point, this corresponds to ~32000 counts at the ADC.

OTOH, REFL9 seems to be pretty puny (~500 counts with half of the full buildup), so we're turning up the gain on there by ~10 and turning on the Whitening filter to see if it helps the CARM noise be low.

Images attached to this report
H1 General (CDS)
rana.adhikari@LIGO.ORG - posted 17:56, Wednesday 28 January 2015 - last comment - 13:23, Thursday 29 January 2015(16333)
Auto-Scale for Big plots with Dataviewer: CDS Bug #377

To get bigger plots in dataviewer (i.e. getting the plot window to auto-scale) for both playback and 'real-time' plots, you can now just set up an option in your GRACE environment:

1) In your user directory make a directory called .grace:      mkdir .grace

2) Change to that directory:                                   cd .grace

3) Copy my gracerc file into your directory:                   cp /ligo/home/rana.adhikari/.grace/gracerc.user .

Now, when you restart dataviewer, you will have autoscaling.

BTW, this is described somewhat in CDS Bugzilla #377 from Tobin Fricke, Jim Batch, & Keith Thorne.

Comments related to this report
james.batch@LIGO.ORG - 12:56, Thursday 29 January 2015 (16346)
Note that the Realtime display suffers a bit when the "PAGE LAYOUT FREE" option is used to autoscale the plot windows.  As the attached screen shot shows, you no longer get the full plot in the window.  It takes some inconvenient fiddling to get the full plot displayed.
Images attached to this comment
rana.adhikari@LIGO.ORG - 13:23, Thursday 29 January 2015 (16348)

true enough - this is usually fixed by hitting stop and then start after first resizing the window. It usually undoes the cutoff plots, but sometimes it just leaves it bad...

H1 SEI
hugh.radkins@LIGO.ORG - posted 17:06, Wednesday 28 January 2015 (16332)
H1 SEI BSC-ISI under RCG SDF Monitoring

Completed the BSC file modifications today like the HAM-ISI yesterday and HEPIs last Thursday.  Now all SEIs are monitored by SDF with Guardian doing the rest.  There remain red issues (5 platforms) I did not clear to remind us of ongoing questions & issues to address.

H1 ISC
keita.kawabe@LIGO.ORG - posted 16:21, Wednesday 28 January 2015 (16218)
Another baffle PD health check

Summary:

QE and transimpedance combined for Baffle PD1 and PD4 on all ITMs and ETMs agree with each other within 10%. In the table below, QE/transimpedance combined for each PD is normalized such that the average of all diodes becomes 1.

  X Y
PD1 PD4 PD1 PD4
ETM 1.01 1.00 1.09 1.03
ITM 0.94 0.98 1.00 0.95

I haven't done any error analysis, but the biggest error should be the systematic in ITM-ETM comparison that was introduced by an assumption that IR mode matching is perfect.

PD1-PD4 comparison on the same baffle (e.g. ETMX PD1 and PD4) should be quite good.

Details:

This is yet another baffle health check.

The other day I used some short time available to misalign TMS and steer MMT3 to point IR beam on ETM baffle PD4, first on  ETMX and then on ETMY. This could be used to make ETMX(PD4)/ETMY(PD4) comparison, assuming that the IR straight shot beam size is the same on ETMX and ETMY.

Then I proceeded to align MMT3, align ETMs to point the beam to PD4 on ITM baffles. Since ETM reflectivity is basically 1, and since the mode matching cannot be as bad as green, we can use these measurements combined with nominal IR beam size to make ETM(PD4)/ITM(PD4) comparison.

Also, when people do initial alignment they are basically doing PD1/PD4 comparison on a single baffle using green beam. (You cannot make comparison across different baffles using green because of the beam size difference described in my previous alog.)

So, stitching all these together, if we believe that the QE variation of diodes for green is the same as that for IR, we can map out the QE/transimpedance combined for all baffle diodes.

In the table below of the raw data, photo current in mA for straight shot measurements of green on PD1 and PD4 as well as IR on PD4 on all arm cavity baffles are shown.

 

  PD1 green PD4 green PD4 IR
EX 0.0453 0.0448 0.0127
EY 0.0111 0.0104 0.0130
IX 0.123 0.129 0.0176
IY 0.0243 0.0230 0.0170

Green data can be used to make PD1/PD4 ratio on each of the optics.

IR ETM data is used to make PD4 ETMX/ETMY ratio.

IR ITM data, combined with the nominal IR beam radius on ITM and ETM (53.4 and 63.5 mm, respectively), is used to make PD4 ETMX/ITMX and ETMY/ITMY ratio.

After some math we get the table at the top of this entry.

H1 General
edmond.merilh@LIGO.ORG - posted 15:58, Wednesday 28 January 2015 (16319)
Daily Ops Summary

06:45 Karen into the LVEA

07:00 Cris into the LVEA

08:00 set OIB to 'Commissioning'

08:05 unlocked DRMI to start practicing locking Green light to arms (ALS) No luck. Later learned the proper way to unlock DRMI. Thanks Kiwamu

08:30 Morning meeting

08:45 Started working with Kiwamu on getting my first arm locks. SUCCESS!

09:09 Betsy and Mitch to W bay

09:22 Jeff B to LVEA

09:29 Mike L into LVEA

09:30 Jeff B out of LVEA

09:49 Mike L out of LVEA

09:52 McCarthy to EX

10:54 Betsy and MItch out of LVEA

10:55 Caterers on site

11:03 McCarthy back from EX

11:07 Fil to MY

11:43 Fill back from MY

12:15 Vanessa to MY

12:24 S&K Electricians to EY

LHO General (DCS)
bubba.gateley@LIGO.ORG - posted 15:46, Wednesday 28 January 2015 (16330)
DCS Construction Progress
The temporary barrier originally installed for the DCS construction has been removed. Mechanical is 98% complete with remaining items being plenum grills and dampers, start up of the HVAC system by a factory rep, installation of cable trays and some touch up painting. Electrical is on the order of 70% complete. 
Images attached to this report
H1 SUS (ISC)
brett.shapiro@LIGO.ORG - posted 14:55, Wednesday 28 January 2015 (16329)
You can now make damped triple and double Matlab models from the foton file

Like the quad model scripts (LHO 16126), I updated the generate_Triple_Model_Production.m and generate_Double_Model_Production.m functions so that you can specify a foton filter for the top mass damping loops.

The generate scripts is in

.../SusSVN/sus/trunk/Common/MatlabTools/TripleModel_Production

and

.../SusSVN/sus/trunk/Common/MatlabTools/TripleModel_Production

If youhaven't done so in the past week, you will also need to svn up

.../SusSVN/sus/trunk/Common/MatlabTools

since this is where the foton file reading functions are located (imported from the SeiSVN)

You can still specify the usual .mat struct file as before. The generate script looks for the .txt extension to determine if you are sending it a foton file.

 

Here is an example of how to make a model with damping filters read from foton:

hsts_model = generate_Triple_Model_Production(frequency_vector_for_plots, 'hstsopt_metal', [], 0, 1, '/opt/rtcds/lho/h1/chans/H1SUSMC1.txt')

IMPORTANT: The foton file does not know which filter modules are engaged. This information is coded into the function with a variable called medm_engaged_modules, which must be updated at the time of running the script. The script will output to the command line which modules are being used for each filter, and where to change in case you forget. For a variety of reasons I thought it more convenient from a user-point-of-view to have this coded into the function rather than as another input to the function, however this could be modified. This is the same in the quad script.

 

These functions have more instructions commented into their headers.

Just have the single sus scripts to go.

H1 AOS
keita.kawabe@LIGO.ORG - posted 13:35, Wednesday 28 January 2015 (16328)
green beam size on ITMs and baffle PDs

Summary:

Green straight shot beam size on ITMX is a factor of 0.87 of nominal (i.e. too small) while ITMY a factor of 1.2 too large.

The beam radius ratio is (X/Y)=0.72, which makes the ITMX baffle PD output current to be a factor of 2 larger than that of Y when you hit these PDs using a straight shot beam.

There used to be a factor of 2 to 2.5 unexplained difference between the photocurrent in ITMX and ITMY baffle diodes during initial green alignment, but the beam size explains a factor of 2, so the remaining factor is about 1.2 or so, which I don't care for now.

Background:

This is one of those health check type stuff. Baffle PDs could be used for scattering measurement but the health of some of those PDs were in question.

One of the suspicions came from the fact that, when looking at green straight shot beam during full initial alignment, PD current from X arm baffle is much larger than Y arm. A part of it comes from the laser power (there's about a factor of 2 or so difference) but the baffle PD current is a factor of 4 to 5-ish different, so there always was a factor of 2 to 2.5 unexplained.

Details:

I first used dither align script to point the TMS beam to PD1 and then PD4 of the ITM baffle. Since the horizontal distance between PD1 and PD4 is 11.3", the script allows us to calibrate TMS alignment slider.

Immediately after the script finished, I pointed the beam to PD4 center, move TMS in YAW in one direction by more than the beam radius,  and ran another script to move TMS in YAW, wait and measure PD4 current.

Attached is the YAW scan data (circles and crosses) as well as the fit to Gaussian profile assuming the same radius in PIT and YAW:

current = ofst+ A * 2/pi/w^2 * exp(-2*(X-X0)^2/w^2)

where w is the beam radius and A is an overall factor.

  beam radius [m] A [mA m^2] QPD_SUM
IX PD4 0.033 (0.038 nominal) 3.8E-7 46180
IY PD4 0.046 (0.038 nominal) 2.7E-7 26124
X/Y 0.715 1.4 1.77

The last column in the above table shows QPDA_SUM+QPDB_SUM. If everything makes sense, and if the beam was at the same height as the PD center during the scan, QPD_SUM ratio should agree with A ratio, but apparently it doesn't at 20%-ish level. This is good enough because the suspicion was that there was something grossly wrong about the baffle PDs.

BTW we can do the same thing for IR beam, scanning MMT3, to assess the IR matching to the arms if we want to (or better yet, do the spiral scan to see both PIT and YAW).

Images attached to this report
H1 ISC
jim.warner@LIGO.ORG - posted 13:27, Wednesday 28 January 2015 - last comment - 13:39, Thursday 29 January 2015(16327)
Pop 18 trend showing window for last nights lock

Looks like lock was from about 9:14 UTC to 16:09 UTC. For posterity.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 13:39, Thursday 29 January 2015 (16349)DetChar, ISC, SEI, SUS
Also for posterity:
- This is a DRMI lock stretch.
- IMC WFS DOF4 is OFF
- No corner station WFS engaged. 
- ISS second loop is *OFF*. 
- 10 [W] input reqested. 
- SEI was in the most recent nominal configuration -- 
    HPI Pump Servo ON, 
    Sensor Correction to ISI XY and HEPI Z, 
    (no ST0-1 Feed Forward yet), 
    Using 01_28 blends on the HAM ISIs, 
    "45 [mHz]" X&Y, LLO blends on BSC ISIs.

Great for offline, data-mining studies of
- Gain Problems with STS2B
- HAM3 0.6 [Hz] feature
- Coherence with HPI Pump Pressure.
- DAC major-carry transition glitches.
- Cavity performance with respect to SEI performance.
- Lock Loss statistics

Among other things...
H1 SEI (ISC, SEI)
evan.hall@LIGO.ORG - posted 13:22, Wednesday 28 January 2015 (16326)
M5.7 earthquake 40 km SW of Ferndale, CA

http://earthquake.usgs.gov/earthquakes/eventpage/nc72387946

Ground velocity exceeds 20 μm/s from 0.03 Hz to 0.1 Hz. IMC MC2 transmission is noticeably wobbly.

H1 CDS
patrick.thomas@LIGO.ORG - posted 11:47, Wednesday 28 January 2015 (16324)
Updated conlog channel list
Added 2 channels and removed 788.
H1 General
edmond.merilh@LIGO.ORG - posted 11:01, Wednesday 28 January 2015 (16320)
Morning Meeting Summary

Work Permit review.

SEI - continuing work on SDF system for BSC ISI. HEPI pump servo is ongoing tinvestigation. Maybe Jeff will run some TFs looking at 1Hz to 10Hz at some point today.

SUS - no big news. Thomas will ressurect the Drift Monitor this week sometime.

ISC/Commish - taking small steps in the positivedirection. Had a rather lengthy DRMI lock last night beginning ~01:30.

3IFO - no activities in LVEA. All activities across the street.

Facilities - Beam Tube cleaning is ongoing. Gutter work is don at LSB. Crew has moved to VPW.

CDS - variac installation at End station for Heater. Work in HAM6 area on Fast Shutter. R Abbott will be coming to work with this.

Gary will be moving ISS arrays and using the large airlock door in the LVEA

H1 ISC
alexan.staley@LIGO.ORG - posted 00:54, Wednesday 28 January 2015 - last comment - 10:58, Wednesday 28 January 2015(16315)
CARM offset to ~100pm

Sheila, Evan, Rana, Eli, Kiwamu, Alexa

Today we were able to reduce the CARM offset from 800pm to 100pm. We made three major changes to acheive such an offset.

  1. We noticed that the sqrt(TRX+TRY) counts into the CM board was only about 100 pk-pk. We increased this to about 800pk-pk by reallocating some gain. We decreased the LSC-REFL_SERVO_IN1_GAIN from 0dB to -16dB, and increased the LSC-REFLBIAS_GAIN from 8 to 50.4.
  2. We added a z20:p40 to REFLBIAS in order to get more phase and push the UGF of TR CARM from 200 Hz to 150 Hz. This filter is only engaged after we have already turned off ALS COMM, at which point we do not need to compensate for the COMM PLL VCO.
  3.  We noticed that ASAIR_RF45_Q was rather noisy as we were reducing the CARM offset. We added an integrator FM2 (z2:p0) to ALS DIFF to reduce low frequency noise. This helped make TR CARM more stable.

Transition Process from 800 pm to 400pm

To start,

With some TR buildup (approximately 1ct on LSC-X/Y_TR_A_LF_OUT),

With CARM on sqrt(TRX+TRY),

Transition Process from 400pm to 100pm

With all the settings as above, we bring the CARM offset to -3.2 (or ~150pm). At this point we transitioned the in-air TR PDs to the IR TR QPD_Bs.  For reference, ASC-X/Y_TR_B_POW_NORM =1,1  and LSC-TR_X/Y_QPD_B_SUM_GAIN = 0.222, 0.175 respectively. Also, the QPD NSUM was about 400cts here. We continued to reduce the CARM offset to -4.5 cts (or ~80pm). At first,t the ASAIR_RF45_Q looked like a decent signal and responded well to a DIFF offset change. We turned on a servo for about 1.5min to ensure ASAIR was around zero (z servo -r LSC-ASAIR_A_RF45_Q_NORM_MON -g -11111 ALS-C_DIFF_PLL_CTRL_OFFSET).  We measured ASAIR_RF45_Q/DARM_IN1 = 3e7 (at this point DARM_IN1 is just ALS DIFF signal). Note: we added a -160dB FM10 filter in LSC-ASAIR_A_RF45. Then the PD_DOF_MATRIX for ASAIR_RF45_Q is 3.3. So far, we were able to transition from ALS DIFF to RF DARM 50% of the way, and then we broke the lock. We started to reconsider whether we were actually in the linear range for RF DARM. Maybe we should be using AS45Q/SQRT(TRX) at this point? This requires a model change; however, this is already impleneted in the l1lsc.mdl that is in the SVN, so we could just copy that.

A little more ...

The farthest CARM offset we reached was -7 cts or ~60pm on sqrt(TRX+TRY) with the QPDs controlling CARM and ALS DIFF for DARM. Here we had 26 x single arm power, and REFL DC dropped from 80mW to ~75mW.

Comments related to this report
eleanor.king@LIGO.ORG - 01:00, Wednesday 28 January 2015 (16316)

Some lock loss times for today:

Lock losses while transitioning DARM from ALS-DIFF to AS_AIR_45_Q:

06:01:40 UTC (28jan)

06:33:34

07:53:45

stefan.ballmer@LIGO.ORG - 10:58, Wednesday 28 January 2015 (16323)
Almost there!
H1 SUS
rana.adhikari@LIGO.ORG - posted 19:51, Tuesday 27 January 2015 - last comment - 12:31, Wednesday 28 January 2015(16313)
ETMX Bounce Mode ringup trend

The stopband filter we put in the ETMX OL servo yesterday seems to have done the job of preventing the ringups:

In the attached trend of the OLPIT 3-10 Hz BLRMS, you can see the ringup start around 6AM local time this Sunday, the 25th.

Around noon on Monday (1800 UTC), Evan and Alexa start damping the mode using the bandpass filter in the OL PIT servo. They stop around 2100 UTC when the mode is small. It then rings up for the next 7 hours until we turn the stopband filter on.

Then it rings down with a 1/e time of ~4 hours (which implies a bounce mode Q of ~440,000 if nothing else is driving it).

We should make sure to install these on all of the test mass OL servos.

Images attached to this report
Comments related to this report
rana.adhikari@LIGO.ORG - 12:31, Wednesday 28 January 2015 (16325)

Added the Bounce + Roll bandstop filter to all the ETM/ITM OLDAMP filter banks. In some cases, I have overwritten existing 'notch' filters there for this purpose. Its not a good idea to use 'notch' for these mechanical modes which drift in frequency.

I made the Roll bandstop wider since there's no phase hit from this higher frequency filter. The vertical lines in the plot show the expected bounce frequency (9.775 Hz) and the roll frequency (13.81 Hz) which has some small natural spread between the optics, but I figure this should catch them all, even when the VEA temperatures drift.

Non-image files attached to this comment
Displaying reports 69161-69180 of 85060.Go to page Start 3455 3456 3457 3458 3459 3460 3461 3462 3463 End