40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 306 of 341  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  3031   Wed Jun 2 03:50:03 2010 KojiUpdateIOOmode measurement of new input optics

Just note that MMT1 has RoC of -5m (negative!). This means that it is a lens with f=-2.5 m,

 

  3043   Thu Jun 3 13:14:27 2010 kiwamuUpdateIOOmode measurement of new input optics

I corrected the sketch of the new IOO. 

The sketch in the last entry was also replaced by the new one. 

http://nodus.ligo.caltech.edu:8080/40m/3029 

Quote:

Just note that MMT1 has RoC of -5m (negative!). This means that it is a lens with f=-2.5 m,

Attachment 1: inside_vac_2.png
inside_vac_2.png
  3044   Thu Jun 3 14:01:51 2010 kiwamuUpdateIOOmode measurement of new input optics

I checked the measured data of the mode profile which was taken on the last Tuesday.

For the vertical profile,

the plot shows a good agreement between the expected radius which is computed from the past measurement, and that measured on the last Tuesday.

However for the horizontal profile,

it looks like being overestimated. This disagreement may come from the interference imposed on the Gaussian spot as we've been worried. 

So I guess we should solve this issue before restarting this mode matching work.

 - The next step we should do are;

checking the effect of MMT1 on the shape of the beam spot by using a spare of MMT1

 

NOTE:

The expected curve in the attached figure were computed by using the fitted parameter listed on the entry 2984 .

In the calculation the MMT1 is placed at 1911mm away from MC3 as we measured.

And the focal length of MMT1 is set to be f=-2500mm.

Attachment 1: check_measurement_edit.png
check_measurement_edit.png
  3045   Thu Jun 3 14:13:20 2010 JenneUpdateIOOmode measurement of new input optics

Quote:

I checked the measured data of the mode profile which was taken on the last Tuesday.

For the vertical profile,

the plot shows a good agreement between the expected radius which is computed from the past measurement, and that measured on the last Tuesday.

However for the horizontal profile,

it looks like being overestimated. This disagreement may come from the interference imposed on the Gaussian spot as we've been worried. 

So we should solve this issue before restarting this mode matching work.

 - The next step we should do are;

checking the effect of MMT1 on the shape of the beam spot by using spare MMT1

 

NOTE:

The expected curve in the attached figure were computed by using the fitted parameter listed on the entry 2984 .

In the calculation the MMT1 is placed at 1911mm away from MC3 as we measured.

And the focal length of MMT1 is set to be f=-2500mm.

 When / if you use the other MMT1 mirror, make sure to take note whether or not it says "SPARE" on it in pencil.  I don't remember if it's the other MMT1, or if it's one of the MMT2's that says this.  The mirror was baked, so it's okay to use in the vacuum, however it's the one which was dropped on the floor (just prior to baking), so any discrepancies measured using that optic may not be useful.  I don't know how strong the CVI coatings are to scratches resulting in being dropped from a ~1m height.  Bob and I didn't see any obvious big scratches that day, but that doesn't necessarily give it a clean bill of health. 

The optic labeled "SPARE" should NOT be used as the final one in the IFO.

  3046   Thu Jun 3 14:40:28 2010 Alberto, KiwamuUpdateIOOmode measurement of new input optics

Quote:

inside_vac_2.png

 

For the record, we wanted to check whether the fringes on the beam spot were caused by SM2 (see diagram above). We tried two different mirrors for SM2,

The first was one of the flat, 45 degree ones that were already on the BS table. The last, which is the one currently in place, was inside the plastic box with the clean optics that Jenne left us .

The fringes were present in both cases.

  2959   Thu May 20 13:29:40 2010 kiwamuUpdateGreen Lockingmode profile at PPKTP crystal

 I measured again the mode profile of the beam going through the PPKTP crystal by using the beam scan.

The aimed beam waist is 50 um (as described in entry 2735),

and the measured profile had pretty good waist of wx=51.36 +/- 0.0999 um and wy=49.5 +/- 0.146 um 

The next things I have to do are - (1). re-optimization of the temperature of the crystal (2). measurement of the conversion efficiency

The attached figure is the result of the measurement. 

Attachment 1: PPKTPmode.png
PPKTPmode.png
  2960   Thu May 20 14:18:59 2010 kiwamuUpdateGreen Lockingmode profile of 40m cavity

The mode profile of the green beam going through 40m cavity was measured.

According to the fitting the coupling efficiency to the cavity is 98.46%, but still the beam looks loosely focused.

This measurement has been done by using the oplev legs (entry #2957) to allow the beam to go through the 40m walkway.

With a beam scan set on a movable cabinet, I measured it along the 40m chamber.

Since the plot looks not so nice,  I am going to work on this measurement a little bit more after I improve the mode matching.

 


Here is the parameters from the fitting

target waist [mm] 2.662
measured waist x [mm] 2.839
measured waist x [mm] 3.111
   
target waist position [m] 43.498
measured waist position x [m] 42.579
measured waist position y [m] 38.351

 

I believe the error for the travel length was within 0.5 meter. The length was always measured by a tape measure.

A thing I found was that: spatial jittering of the beam gets bigger as the beam goes further. This is the main source of the error bar for the spot size. 

 

 

Attachment 1: MMT40mcavity.png
MMT40mcavity.png
  6437   Thu Mar 22 17:35:59 2012 kiwamuUpdateLockingmode profiles of the POP and POX beams : not bright enough

I tried to measure the beam profiles at the POP and POX ports as Koji mentioned in his entry (#6421).

However it turned out that the beam powers were too small to be measured with our beam scan at those ports.

So I will move on to measurements at the REFL port as Rana suggested because the laser power is much larger than that of POP and POX.

(If the data of the POP and POX beam profiles turn out to be very necessary, we will do the razor blade technique with a more sensitive photo diode)

Quote from #6421

More precise analysis can be done with quantitative analysis of those two spots with Beamscan. This could happen tomorrow.

 

  6446   Mon Mar 26 18:04:43 2012 kiwamuUpdateIOOmode scan at the REFL port

For those who are interested in the actual data, I attache the actual data in zip file together with a python plot code.

The distance was set such that the 1st steering mirror (the one at the very left in the previous cartoon diagram #6445 ) in the REFL path is positioned at zero.


mode_profile.png

 

- - - Fitting results (chi-square fitting done by gnuplot):

All values are in unit of meter

# PRM (v) (Last tree points are excluded as the beam were clipped at the aperture of the beam scan)

w0          = 0.0015114        +/- 2.192e-05    (1.451%)
z0           = -4.46073         +/- 0.05605      (1.256%)

# PRM (h)

w0           = 0.00212796       +/- 1.287e-05    (0.6049%)
z0           = -2.53079         +/- 0.1688       (6.668%)

# ITM (v) (Last two points are excluded as the beam were clipped at the aperture of the beam scan)

w0           = 0.00190696       +/- 4.964e-05    (2.603%)
z0           = -8.09908         +/- 0.1525       (1.882%)

# ITM (h)

w0           = 0.0032539        +/- 4.602e-05    (1.414%)
z0           = -1.89484         +/- 1.524        (80.42%)

 

Attachment 2: REFLmodescan.zip
  8720   Wed Jun 19 01:12:42 2013 JenneUpdateASCmodel name ASS -> ASC ???

I am proposing a model name change.  Currently, we have an "ASS" model, but we do not have an "ASC" model. 

The ASS is currently using ~17 of 60 available microseconds per cycle.  So, we have some cpu overhead available to put more stuff on that cpu. Like, say, ASC stuff.

So, my proposal is that we change the ASS model name to "ASC", and put all of the ASS-y things in a top_names block, so we retain the current channel names.  The IOO top_names block that is in the current ASS model (which is there to send signals to the LSC DAC for the input tip tilts, even though the names need to be IOO) should obviously stay on the top level, so that things in there retain their names.

Then, I can make a new top_names sub-block for ASC-like things, such as the new POP QPD. 

Inside the ASC block (in the ASC model), I'm currently thinking something simple will do..... QPD inputs, going to a matrix, which outputs to the filter banks in the "length" degree of freedom basis (PRCL, SRCL, etc), then another matrix, going to the ASC suspension paths. 

So, for example, the POP QPD pitch would go to the PRCL_PIT filter bank, and then on to the PRM_ASCPIT path in the SUS screen.

Or, in another example case, IPPOS yaw would go to an input pointing filter bank, then on to TT1's yaw slider.

EDIT:  After a few minutes of thinking, I think I also want triggering, and perhaps filter bank triggering, in the ASC model.  One of the reasons Koji has been pushing for the new automation system is that when the PRC fell out of lock, the ASC path would kick the PRM until Koji ran a down script.  Triggering will fix this issue, and it's the kind of thing that needs to happen quickly, so may not really be appropriate for the Guardian anyway.

  8723   Wed Jun 19 04:56:07 2013 KojiUpdateASCmodel name ASS -> ASC ???

Sounds good.
Or we just stuff any angle control things in to Angular Stabilization System without changing the model name.
The process name itself is not a big deal.

  7038   Thu Jul 26 13:10:51 2012 janoschUpdateLSCmodelled ringdown

We fitted shutter and ringdown functions to the ringdown data. It is not perfectly clear how the power change due to the shutter is handed over to the power change due to ringdown. The fit suggests that the ringdown starts at a later time, but this does not necessarily make sense. It could be that the slow power decrease when the shutter starts clipping the TEM00 beam is followed by the cavity, but then the power decrease becomes too fast when the shutter reaches the optical axis and the ringdown takes over. Also, the next measurement should be taken with adjusted DC offset.

Ringdown.png

  7039   Thu Jul 26 15:43:03 2012 ranaUpdateLSCmodelled ringdown

You cannot use the digital system for this. You hook up a scope to the transmitted light as well as the incoming light (after the MC, perhaps at IP_POS). Then you acquire the data from both places simultaneously using an ethernet equipped scope. The step response of the PDs used for this has to be calibrated separately.

  5711   Thu Oct 20 11:59:21 2011 ZachUpdateComputer Scripts / Programsmodified "dataviewer" on nodus

The "dataviewer" script was still setting the server to fb40m on nodus. I modified it to fb, so that this is the default when you enter "dataviewer" or "dv".

  4949   Wed Jul 6 23:03:57 2011 kiwamuUpdateLSCmodified locking scripts

[Jenne / Kiwamu]

 Last night we modified the locking scripts, that were called from C1IFO_CONFIGURE.adl, to adapt them to the new "PRCL" and "SRCL" convention.

So far they work fine and quitted dumping some error messages about inexistence of these channel names.

  P.S. The locking scripts have been summarized on the 40m wiki

Quote from #4912

- Now the power and signal recycling cavity lengths are named "PRCL" and "SRCL" in stead of three letter names without "L".

We should change the locking script to accomodate these changes.

  9324   Thu Oct 31 21:22:00 2013 rana, kojiSummaryIOOmodulation beat note in MC servo

I hooked up the 4395 to the MC servo board test out (TP2A) and looked at the spectrum using our new SPAG4395.py script. We noticed a huge peak at ~3.8 MHz and correctly guessed that it was due to the beat between the MC modulation frequency 29.5 MHz and 3*f1 (~33 MHz).

So we tuned the Marconi for the main mod. from 11065910 to 11066099 Hz and saw the beat note disappear (to within the 1 Hz tuning precision of our Marconi).

New MC length tuning method! Alert the LA Times!

13031.png13031_200.png13031_200b.png

My conjecture is that this temperature dependent mismatch between the modulation frequency (f1) and the MC length  is what leads sometimes to our nasty saturating PC DRIVE signal. TBD.

  11036   Mon Feb 16 01:45:12 2015 KojiSummaryLSCmodulation depth analysis

Based on the measured modulation profiles, the depth of each modulation was estimated.
Least square sum minimization of the relative error was used for the cost function.
-8th, -12th~-14th, n=>7th are not included in the estimation for the nominal case.
-7th~-9th, -11th~-15th, n=>7th are not included in the estimation for the 3f reduced case.

Nominal modulation

m_f1 = 0.194
m_f2 = 0.234
theta_f1f2 = 41.35deg
m_IMC = 0.00153

3f reduced modulation

m_f1 = 0.191
m_f2 = 0.0579
theta_f1f2 = 180deg
m_IMC = 0.00149

(Sorry! There is no error bars. The data have too few statistics...)

Attachment 1: modulation_nominal.pdf
modulation_nominal.pdf
Attachment 2: modulation_3f_reduced.pdf
modulation_3f_reduced.pdf
  6027   Mon Nov 28 16:51:57 2011 kiwamuUpdateLSCmodulation frequency reset

I reset the modulation frequency to 11065910 Hz (#5530). It had been at 11065399 Hz probably since the power shut down.

  240   Wed Jan 16 14:06:24 2008 robUpdateLSCmonday's locking
rob, tobin, johnnie

We did some locking work monday night, with decent progress. Working in the PRFPMI style, we managed to get through the part of the script that hands off the offset-CARM DOF to the MCL, but were not successful in engaging the AO path.

We also confirmed the problem with tdsread which prevent it from reading from multiple TLS (Three Lettered Subsystems) at the same time. Tobin traced this to a problem with the ezca library which tds uses, but it's not clear how to fix it. For now we just split the tdsread calls so that there are no multiple TLS calls. Tobin will report further on this.
  12667   Tue Dec 6 00:43:41 2016 gautamUpdateIMCmore IMC ringdowns

In an effor to see if I could narrow down the cause of the 100kHz ringing seen in the reflected PD signal, I tried a few things.

  1. Changed the PD - there was a PDA 255 sitting on the PSL table by the RefCav. Since it wasn't being used, I swapped the PD I was using with this. Unfortunately, this did not solve the problem.
  2. Used a different channel on the oscilloscope - ringing persisted
  3. Changed BNC cable running from PD to oscilloscope - ringing persisted
  4. Checked the spectrum of the PD under dark and steady illumination conditions for any features at 100kHz, saw nothing (as expected) 

I was working under the hypothesis that the ringing was due to some impedance mismatch between the PD output and the oscilloscope, and 4 above supports this. However, most documents I can find online, for example this one, recommend connecting the PD output via 50ohm BNC to a scope with input impedance 50ohms to avoid ringing, which is what I have done. But perhaps I am missing something.

Moreover, the ringdown in reflection actually supplies two of the five variables needed to apply the MIT method of loss estimation. I suppose we could fit the parameter "m4" from the ringdown in transmission, and then use this fitted value on the ringdown in reflection to see where the reflected power settles (i.e. the parameter "m3" as per the MIT paper). I will try analyzing the data on this basis.

I also measured the power levels at each of the PDs, these should allow us to calibrate the PD voltage outputs to power in Watts. All readings were taken with the Ophir power meter, with the filter removed, and the IMC locked.

PD Power level
REFL 0.47 mW (measured before 1.0 ND filter)
Trans 203 uW
Incident 1.06 mW

 

  6264   Thu Feb 9 17:11:05 2012 steveUpdateSUSmore OSEM problems

These observations of the OSEMs  were taken while taking transfer functions of oplev YAW at excitation amplitude 0.1

 

 Atm1,  C1:SUS-ETMX_SENSOR_SIDE cross coupling

Atm2,   C1:SUS-ITMX_SENSOR_LL   not excitable

Atm3-4,   BS and PRM  insensitive

 

Good OSEM list: ITMY, ETMY and SRM

 

Attachment 1: ETMXosemEXC0.1ampl.png
ETMXosemEXC0.1ampl.png
Attachment 2: IMTX-YAW0.1.png
IMTX-YAW0.1.png
Attachment 3: BSosemEXC.1ampl.png
BSosemEXC.1ampl.png
Attachment 4: PRMosemEXC.1ampl.png
PRMosemEXC.1ampl.png
  10172   Thu Jul 10 01:02:13 2014 ranaUpdatePSLmore PMC science

Increased gain and SNR in PMC LO monitor circuit.

  1. R20: 499 -> 50k Ohms (increases gain by 100)
  2. Used Marconi to drive the LO input and readout C1:PSL-PMC_LODET
  3. Fit this function and loaded it into the psl.db file. The old Kalmus way used LOGE, but I wanted to use log10, so I did. The sensor is only useful in a narrow band. Since the signal is so low at low levels, I just fit to the highest 4 points because I was too lazy to do proper weighting. Do as I say, not as I do.

Plot with data and fit attached.

** N.B.: in order to update the calibration without rebooting, I used the following command: z write C1:PSL-PMC_LOCALC.CALC "2.235*LOG(B)+12.265". This allows us to update EPICS CALC records without rebooting the IOC.

Attachment 1: PMCloCal.pdf
PMCloCal.pdf
  15849   Sun Feb 28 16:59:39 2021 rana, gautamUpdateLSCmore PRMI checks here: what it is ain't exactly clear

On Friday evening we checked out a few more things, somewhat overlapping with previous tests. All tests done with PRMI on carrier lock (REFL11_I -> PRC, AS55_Q-> MICH):

  • check that PRC drive appropriately minimizes in REFL55_Q. I:Q ratio is ~100:1; good enough.
  • put sine waves around 311 and 333 Hz into PRCL and MICH at the LSC output matrix using awggui and LSC osc. not able to adjust LSC/OSC output matrix to minimize the MICH drive in REFL_I.
  • measured the TF from BS & PRM LSC drive to the REFL55_I/Q outputs. very nearly the same audio frequency phase, so the problem is NOT in the electronics || mechanical transfer functions of the suspensions.

 

Further questions:

  1. is this something pathological in the PRMI carrier lock? we should check by locking on sidebands to REFL55 and REFL165 and repeat tests.
  2. Can it be a severe mode mismatch from IMC output to PRMI mode? the cavity should be stable with the flipped folding mirrors, but maybe something strange happening. How do we measure the mode-matching to the PRC quantitatively?
  3. huge RAM is ruled out by Gautam's test of looking at REFL demod signals: dark offset vs. offset with a single bounce off of PRM (with ITMs mis-aligned)
  4. if there is a large (optical) offset in the AS55_Q lock point, how big would it have to be to mess up the REFL phase so much?
  5. what is going on with the REFL55 whitening/AA electronics?

unrelated note: Donatella the Workstation was ~3 minutes ahead of the FE machines (you can look at the C0:TIM-PACIFIC_STRING on many of the MEDM screens for a rough simulacrum). When the workstation time is so far off, DTT doesn't work right (has errors like test timed out, or other blah blah). I installed NTP on donatella and started the service per SL7 rules. Since we want to migrate all the workstations to Debian (following the party line), lets not futz with this too much.


gautam, 1 Mar 1600: In case I'm being dumb, I attach the screen grab comparing dark offset to the single bounce off PRM, to estimate the RAM contribution. The other signals are there just to show that the ITMs are sufficiently misaligned. The PRCL PDH fringe is usually ~12000 cts in REFL11, ~5000cts in REFL55, and so the RAM offset is <0.1% of the horn-to-horn PDH fringe.

P.S. I know generally PNGs in the elog are frowned upon. But with so many points, the vector PDF export by NDS (i) is several megabytes in size and (ii) excruciatingly slow. I'm proposing a decimation filter for the export function of ndscope - but until then, I claim plotting with "rasterized=True" and saving to PDF and exporting to PNG are equivalent, since both yield a rasterized graphic.

Attachment 1: RAMestimate.png
RAMestimate.png
  15850   Sun Feb 28 22:53:22 2021 gautamUpdateLSCmore PRMI checks here: what it is ain't exactly clear

I looked into this a bit more and crossed off some of the points Rana listed. In order to use REFL 55 as a sensor, I had to fix the frequent saturations seen in the MICH signals, at the nominal (flat) whitening gain of +18 dB. The light level on the REFL55 photodiode (13 mW), its transimpedance (400 ohm), and this +18dB (~ x8) gain, cannot explain signal saturation (0.7A/W * 400 V/A * 8 ~ 2.2kV/W, and the PRCL PDH fringe should be ~1 MW/m, so the PDH fringe across the 4nm linewidth of the PRC should only be a couple of volts). Could be some weird effect of the quad LT1125. Anyway, the fix that has worked in the past, and also this time, is detailed here. Note that the anomalously high noise of the REFL55_Q channel in particular remains a problem. After taking care of that, I did the following:

  1. PRMI (ETMs misaligned) locking with sidebands resonant in the PRC was restored - REFL55_I was used for PRCL sensing and REFL55_Q was used for MICH sensing. The locks are acquired nearly instantaneously if the alignment is good, and they are pretty robust, see Attachment #1 (the lock losses were IMC related and not really any PRC/MICH problem).
  2. Measured the loop OLTFs using the usual IN1/IN2 technique. The PRCL loop looks just fine, but the MICH loop UGF is very low apparently. I can't just raise the loop gain because of the feature at ~600 Hz. Not sure what the origin of this is, it isn't present in the analogous TF measurement when the PRMI is locked with carrier resonant (REFL11_I for PRCL sensing, AS55_Q for MICH sensing). I will post the loop breakdown later. 
  3. Re-confirmed that the MICH-->PRCL coupling couldn't be nulled completely in this config either.
    • The effect is a geometric one - then 1 unit change in MICH causes a 1/sqrt(2) change in PRCL. 
    • The actual matrix element that best nulls a MICH drive in the PRCL error point is -0.34 (this has not changed from the PRMI resonant on carrier locking). Why should it be that we can't null this element, if the mechanical transfer functions (see next point) are okay?
  4. Looked at the mechanical actuator TFs are again (since we forgot to save plots on Friday), by driving the BS and PRM with sine waves (311.1 Hz), one at a time, and looking at the response in REFL55_I and REFL55_Q. Some evidence of some funkiness here already. I can't find any configuration of digital demod phase that gives me a PRCL/MICH sensing ratio of ~100 in REFL55_I, and simultaneously, a MICH/PRCL sensing ratio of ~100 in REFL55_Q. The results are in Attachments #5
  5. Drove single frequency lines in MICH and PRCL at 311.1 and 313.35 Hz respectively, for 5 minutes, and made the radar plots in Attachments #2 and #3. Long story short - even in the "nominal" configuration where the sidebands are resonant in the PRC and the carrier is rejected, there is poor separation in sensing. 
    • Attachments #2 is with the digital REFL55 demod phase set to 35 degrees - I thought this gave the best PRCL sensing in REFL55_I (eyeballed it roughly by looking at ndscope free-swinging PDH fringes).
    • But the test detailed in bullet #4, and Attachments #2 itself, suggested that PRCL was actually being sensed almost entirely in the Q phase signal.
    • So I changed the digital demod phase to -30 degrees (did a more quantitative estimate with free-swinging PDH fringes on ndscope, horn-to-horn voltages etc).
    • The same procedure of sine-wave-driving now yields Attachments #3. Indeed, now PRCL is sensed almost perfectly in REFL55_I, but the MICH signal is also nearly in REFL55_I. How can the lock be so robust if this is really true? 
  6. Attachments #4 shows some relevant time domain signals in the PRMI lock with the sidebands resonant. 
    • REFL11_I hovers around 0 when REFL55_I is used to sense and lock PRCL - good. The m/ct calibration for REFL11_I and REFL55_I are different so this plot doesn't directly tell us how good the PRCL loop is based on the out-of-loop REFL11_I sensor.
    • ASDC is nearly 0, good.
    • POP22_I is ~200cts (and POP22_Q is nearly 0) - I didn't see any peak at the drive frequency when driving PRCL with a sine wave, so no linear coupling of PRCL to the f1 sideband buildup, which would suggest there is no PRCL offset.
    • Couldn't do the analogous test for AS110 as I removed that photodiode for the AS WFS - it is pretty simple to re-install it, but the ASDC level already doesn't suggest anything crazy here.

Rana also suggested checking if the digital demod phase that senses MICH in REFL55_Q changes from free-swinging Michelson (PRM misaligned), to PRMI aligned - we can quantify any macroscopic length mismatch in the PRC length using this measurement. I couldn't see any MICH signal in REFL55_Q with the PRM misaligned and the Michelson fringing. Could be that +18dB is insufficient whitening gain, but I ran out of time this afternoon, so I'll check later. But not sure if the double attenuation by the PRM makes this impossible.

Attachment 1: PRMI_SBres_REFL55.png
PRMI_SBres_REFL55.png
Attachment 2: PRMI1f_noArmssensMat.pdf
PRMI1f_noArmssensMat.pdf
Attachment 3: PRMI1f_noArmssensMat.pdf
PRMI1f_noArmssensMat.pdf
Attachment 4: PRMI_locked.png
PRMI_locked.png
Attachment 5: actTFs.pdf
actTFs.pdf
  7671   Mon Nov 5 19:38:52 2012 jamie, jenne, ayaka, denUpdateAlignmentmore alignment woes

Earlier this morning we thought things were looking pretty good.  IPPOS, IPANG, and the AS and REFL spots looked like they hadn't moved too much over the weekend.  Our plan was to do a quick check of things, check clearances, etc., tweak up the oplevs, and then close up.  This is when I made the ill-fated decisions to check the table levelling.

The BS table was slightly off so I moved one of the thick disk weights off of the other disk weight that it was sitting on, and on to the table next to it.  This seemed to improve things enough so I left it there.  ITMY didn't need any adjustment, and I move a couple smaller weights around on ITMX.  Meanwhile Jenne was adjusting the output PSL power back into it's nominal range (<100mW), and re-tweaking up the mode cleaner.

When we then looked at the vertex situation again it was far off in yaw.  This was clearly evident on PZT2, where the beam was no longer centered on the PZT2 mirror and was near the edge.  This was causing us to clip at the BS aperture.

We took some deep breaths and tried to figure out what we did that could have messed things up.

Jenne noticed that we had moved slightly on the PSL QPDs, so she adjusted the PSL output pointing to re-aquire the previous pointing, and realigned the MC.  This had a very small positive affect, but not nearly enough to compensate for whatever happened.

We spent some more time trying to track down what might have changed, but were unable to come up with anything conclusive.  We then decided to see if we could recover things by just adjusting the PZT input steering mirrors.  We couldn't; recentering at PRM, BS, ITMY, and ETMY was moving us off of PR3.

Jenne suggested we look at the spot positions on the MMT mirrors.  I had checked MMT1 and it looked ok, but we hadn't looked at MMT2.  When we checked MMT2 we noticed that we were also off in yaw.  This made us consider the possibility that the BS table had twisted, most likely when I was securing the moved mass.  Sure enough, when I manually twisted BS table, by grabbing it with my hand, very little force would cause the input beam to walk much of the way across PZT2, more than accounting for the offset.  The effect was also very clearly hysteretic as well; I could twist the table a little and it would stay in the new position.

At this point we had fucked things up enough that we realized that we're basically going to have to walk through the whole alignment procedure again, for the third time this vent.  We were able to recover the PRM retro-reflection a bit, but the tip-tilts have drifted in pitch (likely again because of the table levelling).  So we're going to have to walk through the whole procedure systematically again.

Lessons learned:  Many things are MUCH more sensitive than I had been assuming.  The tip-tilts are of course ridiculous, in that lightly touching the top or bottom of the mirror mount will move it by quite a lot in pitch.  The tables are also much more sensitive than I had realized.  In particular, tightening screws can twist the table hystereticly by milliradians, which can of course completely loose the pointing.  We need to be a lot more careful.

Assuming the table hasn't moved too much we should be able to recover the alignment by just adjusting the PZTs and tweaking the pitch of the tip-tilts.  At least that's the hope.    No more touching the table.  No more leveling.  Hopefully we can get this mostly done tomorrow morning.

  8059   Mon Feb 11 17:17:30 2013 JamieSummaryGeneralmore analysis of half PRC with flipped PR2

Quote:

We need expected finesse and g-factor to compare with mode-scan measurement. Can you give us the g-factor of the half-PRC and what losses did you assumed to calculate the finesse?

This is exactly why I added the higher order mode spacing, so you could calculate the g parameter.  For TEM order N = n + m with spacing f_N, the overall cavity g parameter should be:

g = (cos( (f_N/f_FSR) * (\pi/N) ))^2

The label on the previous plat should really be f_N/FSR, not \omega_{10,01}

BUT, arbcav does not currently handle arbitrary ABCD matrices for the mirrors, so it's going to be slightly less accurate for our more complex flipped mirrors.  The affect would be bigger for a flipped PR3 than for a flipped PR2, because of the larger incidence angle, so arbcav will be a little more correct for our flipped PR2 only case (see below).

Quote:

Also, flipped PR2 should have RoC of - R_HR * n_sub (minus measured RoC of HR surface multiplied by the substrate refractive index) because of the flipping.

This is not correct.  Multiplying the RoC by -N would be a very large change.  For an arbitrary ABCD matrix:

R_eff = -2 / C

When the incident angle in non-zero:

tangential: R_eff = R_eff / cos(\theta)
sagittal:   R_eff = R_eff * cos(\theta)

For flipped PR2, with small 1.5 degree incident angle and RoC of -706 at HR:

M_t = M_s = [1.0000, 0.0131; -0.0028, 1.0000]
R_eff = 705.9

For flipped PR3, with large 41 degree incident angle and RoC of -700 at HR:

M_t = [1.0000, 0; 0.0038, 1.0000]
M_s = [1.0000, 0; 0.0022, 1.0000]
R_eff = 592.4

The affect of the substrate is negligible for flipped PR2 but significant for flipped PR3.

The current half-PRC setup

OK, I have now completely reconciled my alamode and arbcav calculations.  I found a small bug in how I was calculating the ABCD matrix for non-flipped TTs that made a small difference.  I now get the exact same g parameter values with both with identical input parameters.

Quote:

According to Jenne dictionary, HR curvature measured from HR side is;

PRM: -122.1 m
PR2: -706 m
PR3: - 700 m
TM in front of BS: -581 m

Sooooo, I have redone my alamode and arbcav calculations with these updated values.  Here are the resulting g parameters

  arbcav a la mode measurement
g tangential 0.9754 0.9753 0.986 +/- 0.001
g sagital 0.9686 0.9685 0.968 +/- 0.001

So the sagittal values all agree pretty well, but the tangential measurement does not.  Maybe there is an actual astigmatism in one of the optics, not due to angle of incidence?

arbcav HOM plot:

foo.pdf

  9452   Tue Dec 10 10:07:01 2013 SteveUpdateIOOmore beam traps

 New razor beam dump installed to trap reflected beam of the input vacuum window.

 

Attachment 1: InputWindowRefDump.jpg
InputWindowRefDump.jpg
Attachment 2: InpWindowRefDupm.jpg
InpWindowRefDupm.jpg
  2997   Thu May 27 02:22:24 2010 kiwamuUpdateGreen Lockingmore details

 Here are some more plots and pictures about the end PDH locking with the green beam. 

-- DC reflection

 I expected that the fluctuation of the DC reflection had 1% from the resonant state to the anti-resonant state due to its very low finesse.

This values are calculated from the reflectivity of ETM measured by Mott before (see the wiki).

In my measurement I obtained  DC reflection of V_max=1.42 , V_min=1.30  at just after the PD.

These numbers correspond to 7.1% fluctuation. It's bigger than the expectation.

I am not sure about the reason, but it might happen by the angular motion of test masses (?)

 

--- time series

Here is a time series plot. It starts from openloop state (i.e. feedback disconnected).

At t=0 sec I connected a cable which goes to the laser pzt, so now the loop is closed.

You can see the DC reflection slightly decreased and stayed lower after the connection.

The bottom plot represents the feedback signal measured before a sum amp. which directly drives the pzt.

stimes.png

 

 

-- length fluctuation  

One of the important quantities in the green locking scheme is the length fluctuation of the cavity.

It gives us how much the frequency of the green beam can be stabilized by the cavity. And finally it will determine the difficulty of PLL with the PSL.

I measured a spectrum of the pzt driving voltage [V/Hz1/2] and then converted it to a frequency spectrum [Hz/Hz1/2].

I used the actuation efficiency of 1MHz/V for the calibration, this number is based on the past measurement.

spectrum.png

RMS which is integrated down to 1Hz  is 1.6MHz.

This number is almost what I expected assuming the cavity swings with displacement of x ~< 1um.

 

-- flashing

A picture below is a ETMx CCD monitor.

One of the spot red circled in the picture blinks when it's unlocked. And once we get the lock the spot stays bright.

ETMX_small.png

 

  2999   Thu May 27 09:43:50 2010 ranaUpdateGreen Lockingmore details

Quote:

 RMS which is integrated down to 1Hz  is 1.6MHz.

This number is almost what I expected assuming the cavity swings with displacement of x ~< 1um.

 Its OK, but the real number comes from measuring the time series of this in the daytime (not the spectrum). What we care about is the peak-peak value of the PZT feedback signal measured on a scope for ~30 seconds. You can save the scope trace as a PNG.

  308   Mon Feb 11 14:24:19 2008 steveUpdatePEMmore earthquakes
ITMX and ITMY sus damping restored after Baja earthquake 5.1 mag at 10:29 this morning.

The ground preparation for The ITS building is almost finished.
Activity is winding down, however the Baja California_ Mexico earthquake zone
"Guadala Victoria" started acting up on Friday.

http://earthquake.usgs.gov/eqcenter/recenteqsus/Maps/special/California_Nevada_eqs.php
Attachment 1: eqfeb11.jpg
eqfeb11.jpg
  11655   Thu Oct 1 19:49:52 2015 jamieUpdateDAQmore failed attempts at getting new fb working

Summary

I've not really been able to make additional progress with the new 'fb1' DAQ.  It's still flaky as hell.  Therefore we're still using old 'fb'.

Issues

mx_stream

The mx_stream processes on the front ends initially run fine, connecting to the daqd and transferring data, with both DAQ-..._STATUS and FE-..._FB_NET_STATUS indicators green.  Then after about two minutes all the mx_stream processes on all the front ends die.  Monit eventually restarts them all, at which point they come up green for a while until the crash again ~2 minutes later.  This is essentially the same situation as reported previously.

In the daqd logs when the mx_streams die:

Aborted 2 send requests due to remote peer 00:30:48:be:11:5d (c1iscex:0) disconnected
Aborted 2 send requests due to remote peer 00:14:4f:40:64:25 (c1ioo:0) disconnected
Aborted 2 send requests due to remote peer 00:30:48:d6:11:17 (c1iscey:0) disconnected
Aborted 2 send requests due to remote peer 00:25:90:0d:75:bb (c1sus:0) disconnected
Aborted 1 send requests due to remote peer 00:30:48:bf:69:4f (c1lsc:0) disconnected
mx_wait failed in rcvr eid=000, reqn=176; wait did not complete; status code is Remote endpoint is closed
disconnected from the sender on endpoint 000
mx_wait failed in rcvr eid=000, reqn=177; wait did not complete; status code is Connectivity is broken between the source and the destination
disconnected from the sender on endpoint 000
mx_wait failed in rcvr eid=000, reqn=178; wait did not complete; status code is Connectivity is broken between the source and the destination
disconnected from the sender on endpoint 000
mx_wait failed in rcvr eid=000, reqn=179; wait did not complete; status code is Connectivity is broken between the source and the destination
disconnected from the sender on endpoint 000
mx_wait failed in rcvr eid=000, reqn=180; wait did not complete; status code is Connectivity is broken between the source and the destination
disconnected from the sender on endpoint 000
[Thu Oct  1 19:00:09 2015] GPS MISS dcu 39 (PEM); dcu_gps=1127786407 gps=1127786425

[Thu Oct  1 19:00:09 2015] GPS MISS dcu 39 (PEM); dcu_gps=1127786408 gps=1127786426

[Thu Oct  1 19:00:09 2015] GPS MISS dcu 39 (PEM); dcu_gps=1127786408 gps=1127786426

In the mx_stream logs:

controls@c1iscey ~ 0$ /opt/rtcds/caltech/c1/target/fb/mx_stream -r 0 -W 0 -w 0 -s 'c1x05 c1scy c1tst' -d fb1:0
mmapped address is 0x7f0df23a6000
mmapped address is 0x7f0dee3a6000
mmapped address is 0x7f0dea3a6000
send len = 263596
Connection Made
isendxxx failed with status Remote Endpoint Unreachable
disconnected from the sender

daqd

While the mx_stream processes are running daqd seems to write out data just fine.  At least for the full frames.  I manually verified that there is indeed data in the frames that are written.

Eventually, though, daqd itself crashes with the same error that we've been seeing:

main profiler warning: 0 empty blocks in the buffer

I'm not exactly sure what the crashes are coincident with, but it looks like they are also coincident with the writing out of the minute and/or second trend files.  It's unclear how it's related to the mx_stream crashes, if at all.  The mx_stream crashes happen every couple of minutes, whereas the daqd itself crashes much less frequently.

The new daqd can't handle EDCU files.  If an EDCU file is specified (e.g. C0EDCU.ini in our case), the daqd will segfault very soon after startup.  This was an issue with the current daqd on fb, but was "fixed" by moving where the EDCU file was specified in the master file.

Conclusion

There are a number of differences between the fb1 and fb configurations:

  • newer OS (Debian 7 vs. ancient gentoo)
  • newer advLigoRTS (trunk vs. 2.9.4)
  • newer framecpp library installed from LSCSoft Debian repo (2.4.1-1+deb7u0 vs. 1.19.32-p1)

It's possible those differences could account for the problems (/opt/rtapps/epics incompatible with this Debian install, for instance).  Somehow I doubt it.  I wonder if all the weird network issues we've been seeing are somehow involved.  If the NFS mount of chiara is problematic for some reason that would affect everything that mounts it, which includes all the front ends and fb/fb1.

There are two things to try:

  • Fix the weird network problem.  Try remove EVERYTHING from the network except for chiara, fb/fb1, and the front ends and see if that helps.
  • Rebuild fb1 with Ubuntu and daqd as prescribed by Keith Thorne.
  11656   Thu Oct 1 20:24:02 2015 jamieUpdateDAQmore failed attempts at getting new fb working

I just realized that when running fb1, if a single mx_stream dies they all die.

  11664   Sun Oct 4 14:28:03 2015 jamieUpdateDAQmore failed attempts at getting new fb working

I tried to look at fb1 again today, but still haven't made any progress.

The one thing I did notice, though, is that every hour on the hour the fb1 daqd process dies in an identical manor to how the fb daqd dies, with these:

[Sun Oct  4 12:02:56 2015] main profiler warning: 0 empty blocks in the buffer

errors right as/after it tries to write out the minute trend frames.

This makes me think that this new hardware isn't actually going to fix the problem we've been seeing with the fb daqd, even if we do get daqd "working" on fb1 as well as it's currently working on fb.

  5279   Mon Aug 22 21:32:10 2011 kiwamuUpdateGeneralmore in-vac work : AS clipping fixed and OSEM/oplev adjustment

[Keiko / Jenne / Jamie / Kiwamu]

 We did the following things today :

  + fixed the AS clipping issue

  + realigned all the oplevs

  + checked and adjusted the all OSEM DC values, including PRM, SRM, BS, ITMs, ETMs, MC1 and MC3

 

Since we touched the OSEMs the alignment has changed somewhat.

Right now Jenne, Suresh and I are working on the "confirmation alignment".

Once we find the alignment is still good (steerable by the PZTs and the DC coil bias), tomorrow we will do the drag&wipe and door closing.

Quote from #5275

We need to check/fix the AS beam clipping and once it's done we will readjust the OSEM mid range and the oplevs.

 

  5284   Tue Aug 23 06:49:24 2011 AnamariaUpdateGeneralmore in-vac work : AS clipping fixed and OSEM/oplev adjustment

Where was the AS clipping?! Ah, the suspense...

Quote:

  + fixed the AS clipping issue

 

Quote from #5275

We need to check/fix the AS beam clipping and once it's done we will readjust the OSEM mid range and the oplevs.

 

 

 

  4389   Wed Mar 9 04:46:13 2011 kiwamuUpdateGreen Lockingmore intensity noise measurement

 

Here is a diagram for our intensity noise coupling measurement.

intensity_setup.png

 

The below is a plot for the intensity noise on the DCPD. (I forgot to take a spectra of the PD dark noise)

For some reason, the RIN spectrum becomes sometimes noisier and sometimes quieter. Note that after 10 pm it's been in the quiet state for most of the time.

An interesting thing is that the structure below 3 Hz looks like excited by motion of the MC when it's in the louder state.

IntensityNoise.png

Quote: from #4383

A photo diode and an AOM driver have been newly setup on the PSL table to measure the intensity noise coupling to the beat note signal.

We tried taking a transfer function from the PD to the beat, but the SNR wasn't sufficient on the PD. So we didn't get reasonable data.

  1082   Fri Oct 24 11:09:08 2008 steveUpdateSAFETYmore lexan plates under cameras
The MC2, MC3&1 and BSC-SUS cameras were repositioned somewhat in the
process of placing lexan disks under neat them.
MC1&3 will have to be readjusted.

Now all horizontal viewports are protected.
  1728   Thu Jul 9 19:05:32 2009 ClaraUpdatePEMmore mic position changes; mics not picking up high frequencies

Bonnie has been strung up on bungees in the PSL so that her position/orientation can be adjusted however we like. She is now hanging pretty low over the table, rather than being attached to the hanging equipment shelf thing. Butch Cassidy has been hung over the AS table.

Moving Bonnie increased the coherence for the PMC_ERR_F signal, but not the MC_L. Butch Cassidy doesn't have much coherence with either.

I noticed that the coherence would drop off very sharply just after 10 kHz - there would be no further spikes or anything of the sort. I used my computer to play a swept sine wave (sweeping from 20Hz to 10kHz) next to Butch Cassidy to see if the same drop-off occurred in the microphone signal itself. Sure enough, the power spectrum showed a sharp drop around 10kHz. Thinking that the issue was that the voltage dividers had too high impedance, I remade one of them with two 280 Ohm and one 10 Ohm resistor, but that didn't make any difference. So, I'm not sure what's happening exactly. I didn't redo the other voltage divider, so Bonnie is currently not operating.

 

Attachment 1: DSC_0569.JPG
DSC_0569.JPG
Attachment 2: DSC_0570.JPG
DSC_0570.JPG
Attachment 3: bonnie_psl_hi_mcl12.pdf
bonnie_psl_hi_mcl12.pdf
Attachment 4: bonnie_psl_hi_errf12.pdf
bonnie_psl_hi_errf12.pdf
Attachment 5: bc_as_table.pdf
bc_as_table.pdf
Attachment 6: powerspec.pdf
powerspec.pdf
  1729   Thu Jul 9 19:24:50 2009 ranaUpdatePEMmore mic position changes; mics not picking up high frequencies
Might be the insidious 850 Hz AA filters in the black AA box which precedes the ADC.

Dan Busby fixed up the PSL/IOO chassis. WE might need to do the same for the PEM stuff.
  2040   Fri Oct 2 02:55:07 2009 robUpdateLockingmore progress

More progress with locking tonight, with initial acquisition and power ramps working.  The final handoff to RF CARM still needs work.

I found the wireless router was unplugged from the network--just plugging in the cable solved the problem.  For some reason that RJ45 connector doesn't actually latch, so the cable is prone to slipping out of the jack.

 

  2047   Sat Oct 3 14:53:24 2009 robUpdateLockingmore progress

Late last night after the ETMY settled down from the quake I made some more progress in locking, with the handoff to RF CARM succeeding once.  The final reduction of the CARM offset to zero didn't work, however.

  12095   Thu Apr 28 00:41:08 2016 gautamUpdateendtable upgrademore progress - Transmon PD installed

The IR Transmon system is almost completely laid out, only the QPD remains to be installed. Some notes:

  1. The "problem" with excessive green power reflected from the harmonic separator has been resolved. It is just very sensitive to the angle of incidence. In the present configuration, there is ~10uW of green power reflected from either side, which shouldn't be too worrisome. But this light needs to be dumped. Given the tiny amount, I think a black glass + sticky tape solution is best suited, given the space constraints. This does not reach the Transmon PDs because there is a filter in the path that is transmissive to IR only. 
  2. I aligned the transmitted beam onto the Thorlabs PD, and reconnected the signal BNC cable (the existing cable wasn't long enough so I had to use a barrel connector and a short extension cable). I then reverted the LSC trigger for the X arm back to TRX DC and also recompiled c1ass to revert to TRX for the dither alignment. At the moment, both arms are stably locked, although the X arm transmission is saturated at ~0.7 after running the dither alignment. I'm not sure if this is just a normalization issue given the new beam path or if there is something else going on. Further investigations tomorrow.
  3. It remains to dump some of the unwanted green light from the addition of the harmonic separator...
  4. We may want to redesign some (or all) of the Transmon path - the lens currently in use seems to have been chosen arbitrarily. Moreover, it is quite stubbornly dirty, there are some markings which persist after repeated first contact cleaning...

I feel like once the above are resolved, the next step would be to PDH lock the green to the arm and see what sort of transmission we get on the PSL table. It may be the polarization or just alignment, but for some reason, the transmitted green light from the X arm is showing up at GTRY now (up to 0.5, which is the level we are used to when the Y arm has green locked!). So a rough plan of action:

  1. Install transmon QPD
  2. PDH lock green to X arm
  3. Fix the window situation - as Steve mentioned in an earlier elog, the F.C. cleaning seems to have worked well, but a little remains stuck on the window (though away from where any laser radiation is incident). This is resolved easily enough if we apply one more layer of F.C., but the bottle-neck right now is we are out of PEEK which is what we use to remove the F.C. once dried. Steve thinks a fresh stock should be here in the next couple of days...
  4. Once 3 is resolved, we can go ahead and install the Oplev.
  5. Which leaves the lst subsystem, coupling to the fiber and a power monitor for the NPRO. I have resolved to do both these using the 1% transmitted beam after the beamsplitter immediately after the NPRO rather than pick off at the harmonic separator after the doubling oven. I need to do the mode-matching calculation for coupling into the fiber and also adjust the collimating lens...
  6. Clean-up: make sure cables are tied down, strain-relieved and hooked up to whatever they are supposed to be hooked up to...
  2673   Mon Mar 15 09:43:47 2010 steveUpdatePEMmore sandblasting today

Do not open IFO vacuum envelope today! They are sandblasting again at CES

  6959   Wed Jul 11 11:18:21 2012 steveUpdatePEMmore seismic noise next week
 
   The fabricators of the big flume in the CES lab have begun testing the sediment feed system which is the noisiest component and plan to test off and on during the day for the next week.
   Please let me know if you detect the noise or have any issues.
 
 
Brian Fuller

phone: 626-395-2465

  6961   Wed Jul 11 13:45:01 2012 JenneUpdatePEMmore seismic noise next week

Quote:
 
   The fabricators of the big flume in the CES lab have begun testing the sediment feed system which is the noisiest component and plan to test off and on during the day for the next week.
   Please let me know if you detect the noise or have any issues.
 
 
Brian Fuller

phone: 626-395-2465

 Masha and Yaakov - this is an excellent opportunity for you guys to test out your triangulation stuff!  Also, it might give a lot of good data times for the learning algorithms.

Maybe you should also put out the 3 accelerometers that Yaakov isn't using (take them off their cube, so they can be placed separately), then you'll have 6 sensors for vertical motion.  Or you can leave the accelerometers as a cube, and have 4 3-axis sensors (3 seismometers + accelerometer set).

  12794   Fri Feb 3 11:03:06 2017 jamieUpdateCDSmore testing fb1; DAQ DOWN DURING TEST

More testing of fb1 today.  DAQ DOWN UNTIL FURTHER NOTICE.

Testing Wednesday did not resolve anything, but Jonathan Hanks is helping.

  10714   Fri Nov 14 08:25:29 2014 SteveUpdateSUSmorning issues

PRM, SRM and the ENDs are kicking up.  Computers are down.  PMC slider is stuck at low voltage.

Attachment 1: morning.png
morning.png
  9726   Fri Mar 14 09:44:34 2014 SteveUpdateLSCmorning lock
Attachment 1: 2hrsMorningLock.png
2hrsMorningLock.png
  13504   Fri Jan 5 17:50:47 2018 ranaConfigurationComputersmotif on nodus

I had to do 'sudo yum install motif' on nodus so that we could get libXm.so.4 so that we could run MEDM. Works now.

  12582   Thu Oct 27 09:38:32 2016 SteveUpdatePEMmouse

We may have a mouse in the lab.  Do not leave any food scrap in trash ! Traps will be set.

 

Attachment 1: mouse.jpg
mouse.jpg
ELOG V3.1.3-