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

The signal observed by the coarse frequency discriminator was actually dominated by the ADC noise above 30 Hz.

It means that once increasing the UGF more than 30 Hz the servo will feed the ADC noise to the test mass and shake it unnecessarily.

I guess this could be one of the reasons of the unstable behavior in the Y end PDH lock (#6071).

(But still it doesn't fully explain the instability).

 To improve the situation I am going to do the following actions:

   (1) Installation of a whitening filter (probably use of SR560s)

   (2) Redesign of the servo filter

Here is a brief noise budget of the coarse sensor.

Gray curve: free running noise when no servo is applied

Green curve : in-loop noise when the ALS loop is closed with the coarse frequency-discriminator. The UGF was at 30 Hz.

Red curve : ADC noise of the coarse discriminator

Eventually the instability in the Y end PDH servo turned out to be some kind of an alignment issue.

After carefully realigning the green beam to the Y arm, the UGF of the ALS loop became able to be at more than 50 Hz.

With this UGF it became able to suppress the arm motion to the ADC noise level (few 100 pm in rms).

Now I am scanning the arm length to look for a TEM00 resonance.

(the Story)

I have noticed that the spatial fringe pattern of the reflected green light was very sensitive to the pitch motion of ETMY when the green light was locked to the Y arm.

So I realigned the last two launching mirrors to minimize the reflected light. Indeed the misalignment was mainly in the pitch direction.

I basically translated the beam upward by a couple of mm or so.

The amount of the DC reflection is about 2.4 V when it is unlocked and it is now 0.77 mV when the green light is locked.

(Some details)

The picture below is a screen shot of the LSC real time model, zoomed in the new LOCKIN part.

The LOCKIN module consists of three big components:

1. A Master oscillator
   • This shakes a desired DOF through the LSC output matrix and provides each demodulator with sine and cosine local oscillator signals.
   • This part is shown in the upper side of the screen shot.
   • The sine and cosine local oscillator signals appear as red and blue tags respectively in the screen shot.
2. An input matrix
   • To allow us to select the signals that we want to demodulate.
   • This is shown in the left hand side of the screen shot.
3. Demodulators
   • These demodulators demodulate the LSC sensor signals by the sine and cosine signals provided from the master oscillator.
   • With the input matrix fully diagonalized, one can demodulate all the LSC signals at once.
   • The number of demodulators is 27, which corresponds to that of available LSC error signals (e.g. AS55_I, AS55_Q, and etc.).
   • This part is shown in the middle of the screen shot.

      An example              

      How to set the thresholds         

1. Open the trigger matrix window, which is accessible from the C1LSC overview screen as usual.
2. Then type the desired upper and lower thresholds into the column.

The below is a screenshot of the trigger matrix screen. The thresholds column is pointed by a big white arrow.

 

Of course, DO NOT set the upper threshold value to be smaller than that of the lower threshold. Otherwise it won't correctly work.

Also if you want to have the usual trigger rather than the Schmitt trigger, simply put the upper and lower thresholds at the same values.

      Details         

Some new screens have been made for the new multiple-LOCKIN system running on the LSC realtime controller.

The medm screens are not so pretty because I didn't spend so long time for it, but it is fine for doing some actual measurements with those new screens.

So the basic works for installing the multiple-LOCKIN are done.

 The attached figure is a screen shot of the LOCKIN overview window.

As usual most of the components shown in the screen are clickable and one can go to deeper levels by clicking them. 

Now a power normalization is doable for the LSC error signals.

It is working fine, but at some point we may want to have some kind of a saturation filter or limiter to avoid dividing a signal by a small number.

 (How to set the normalization)

•   Click a small matrix panel on the LSC OVERVIEW window (shown in the attached screen shot below).
  •     This will give you a pop-up-window, which shows a matrix to route the normalization signals

•   Choose a numerator channel, which you want to divide, and choose denominator channels, which you want to use as a power normalization factor.
•   Put some number in the corresponding matrix elements.
•   Once you put a non-zero element in the matrix, the corresponding numerator channel will be divided by the specified denominator channels.
  •     Otherwise the static normalization factors (e.g. C1:LSC-AS55_POW_NORM, etc.,) will be used for the denominator.

It turned out that the power normalization need a modification.

I will work on it tomorrow and it will take approximately 2 hours to finish the modification.

     Concept of Power Normalization         

1.  Static power normalization, which should be placed before the input matrix.
2.  Dynamic power normalization, which should be placed after the input matrix.

       Locking plan            

Here is a plan in my mind and these are basically the details of the gantt chart (#6143):

• (1 day task) Measurement of the recycling gains of the RF sidebands with the PRMI and DRMI configuration, using POP22/110 RFPD.
  • I need to have confidence that I am really locking the DRMI with SRC resonating to 55 MHz.
  • Also those values will enable us to estimate losses and mode matching again (maybe ?).
• (3-4 days task) Measurement of the sensing matrix using the multiple-LOCKIN system.
  • Write a script to automatically measure the sensing matrix. This must be easy.
    • The results will enable us to diagonalize the input matrix and therefore it eventually gives more solid lock of the DRMI
    • Also it will give us the optical gains of 3f signals. So this is actually a step toward the 3f signal check.
• (3-4 days task) Noise budgeting on the 3f signals
  • This is a very important part of the DRMI characterization because the results will tell us whether we can hold the DRMI lock with a sufficient SNR or not.
  • If it turns out that they don't have good SNRs, we then have to come up with some ideas to improve the SNRs.
• (Extra fun task depending on schedule) 3f DRMI lock + Y arm ALS
  • If the beat-box electronics are not available by the time when the work above are completed, I will do this fun task.
  • Probably it is better to start preparing the common mode servo electronics because it will be needed anyway.

The dynamic power normalization system has been modified such that the normalization happen after the LSC input matrix.

[John / Kiwamu]

 We tried to figure out what is causing spikes in the REFL33 signal, which is used to lock PRCL.

No useful information was obtained tonight and it is still under investigation.

(Background)

 One thing preventing us from doing smooth measurements of the noise budget and the sensing matrix is some sharp spikes in the LSC error signals.

For example when we lock PRMI with REFL33 and AS55 fedback to PRCL and MICH respectively, both the REFL33 and AS55 signals show some spikes in time series.

Those spikes then bring the noise spectra higher than how they should be.

So for the reason, taking the noise budget doesn't give us much information about the interferometer rather than there are spikes.

Also the sensing matrix measurement has been suffered from those spikes, which excite the impulse responses of the low pass filters in the LOCKIN detection systems a lot.

(What we did)

 We looked into the actual analog signals to see if there are indeed spikes or not before they are acquired to the ADCs.

But we didn't find any corresponding spikes in the signals that are after the mixers.

It maybe because the signals we looked into didn't have high enough SNR because they were coming out from the monitor lemo outputs on the demod boards.

 Then we thought the spikes are from the whitening circuits, due to some kind of saturation.

We decreased the gain of the whitening filters by a factor of 10, but it didn't help and the spikes were still there.

[John / Valera / Kiwamu]

 We installed a new weapon, an optical spectrum analyzer in the AS port.

Like we used to do in the old days, two BNC cables were newly laid down and they bring the output of the OSA to the control room to monitor the spectrum with an oscilloscope.

(Some notes)

The photo diode of the OSA was replaced by a Thorlab PDA100A to amplify the signals.

The carrier peak is at about 6.9 V and the f1 and f2 sidebands peaks are at about 40 mV when the beam is in straight shot (everything is misaligned except ITMY and BS).

According to a rough calculation, those numbers correspond to a modulation depth of about 0.16 or so.

The depth agree with what Mirko measured before (#5519)

A very strange thing is going on.

The REFL11 and REFL55 demod signals show high frequency noise depending on how big signals go to the POS actuator of PRM.

This noise shows up even when the beam is single-bounced back from PRM ( the rest of the suspensions are misaligned) and it's very repeatable.

Any idea ?? Am I crazy ?? Is PRM making some fringes with some other optics ??

(background)

(Glitch is related to the PRM POS actuation)

(Possible scenario)

I did a quick test to check a hypothesis that PRM is interfering with some other optics in the single bounce configuration.

I shook all the suspensions (except the MC mirrors) at 3 Hz in POS, PIT and YAW with an amplitude of 1000 counts.

No effects were found in the REFL demod signals.

So it is NOT a fringe effect caused by the other suspended mirrors.

 Last night I found that there were many dust particles on the second steering mirror in the REFL path on the AS table.

Looking at it through an IR viewer, I saw the REFL beam hitting one of the biggest dust particles on that mirror.

This dust particle maybe causing the glitches or maybe not.

Anyway because it's always better to have clean mirrors, I will wipe the steering mirror in this evening and check the presence of the glitches again.

 Another possibility is that there is some beam clipping of the REFL beam before it gets to the PD. Then there could be a partial reflection from that creating a spurious interference. Then it would only show the fringe wrapping if you excite the scatterer or the PRM.

I wiped both surfaces of the REFL second steering mirror.

However no improvements. The glitches still remain.

(Pic.1 before wiping, Pic.2 after wiping)

Assuming that PRM is interfering with some other optics, I have estimated the optical distance between PRM and an object that interferes with PRM.

The optical distance is estimated to be 9.5 +/- 0.5 m.

If we believe this number the object is most likely outside of the vacuum chambers.

 (The measurement)

1.  Preparation : calibration of the MC2 actuator as a frequency actuator (for more details, see the next section)
2.  Set the interferometer to the single-bounce configuration such that the beam directly is reflected back from PRM
3.  Take spectra of REFL11_I without driving any optics. This spectra tells us how quiet the noise normally is.
4.  Drive MC2_POS at 10 Hz with an amplitude of 10000 counts so that we can see the high frequency up conversion noise
   • The frequency was chosen such that the excitation is out of the local damping bands
   • The amplitude was chosen to be as big as possible until the MC unlocked
   • With this drive, the laser frequency should change by 20 MHz peak-peak at 10 Hz.
5.  Record the noisy spectrum when the MC2_POS was driven.
6.  Drive PRM instead of MC2 at 10 Hz.
   • Adjust the amplitude of the excitation such that the cut-off frequency of the up conversion noise matches with that of the MC2 driven case.
   • The amplitude was found to be 1700 - 2000 counts, this uncertainty is currently limiting the precision of the optical distance estimation.
   • With this amount of the drive, PRM moves by 0.8 um peak-peak at 10Hz.
7. Estimate the optical length based on the amount of the drives for PRM and MC2.
   • Estimate the FSR using the following relation df/FSR = dx/ (lambda/2). => FSR = 17 MHz
   • Since FSR = c/ (2L),  L = c/(2 FSR) = 9.5 m or so

(Calibration of the MC2 actuator)

I searched for a scattering body in the REFL path.

According to the result the REFL path on the AS table is innocent.

The idea of the search method is given as follows:

•   Put a 1/10 ND attenuator at the origin of the REFL path on the AS table.
•   Of course this reduces the signal level by the same factor of 10 in the REFL11_I demod signal.
•   If the scattering body is in the REFL path the up conversion noise will be smaller by a factor of 100 because the scattered light go across the attenuator twice.

Indeed the glitches show up in the analog demodulated signals. So it is not an issue of the digital processing.

With an oscilloscope I looked at the I/Q monitor outputs of the LSC demodulators, including REFL11, REFL33, REFL55, POY11, AS55 while keep locking the carrier-resonant PRMI.

I saw some glitches in REFL11, REFL55 and AS55. But I didn't see any obvious glitches in REFL33 and PO11 because the SNR of those signals weren't good enough.

(some example glitches)

The attached plot below is an example shot of the actual signals when the carrier resonant PRMI was locked.

The first upper row is the spectrogram of REFL11_I, REFL55_I, REFL33_I and AS55_Q in linear-linear scale.

The second row shows the actual time series of those data in unit of counts.

The bottom row is for some DC signals, including REFLDC, ASDC and POYDC.

You can see that there are so many glitches in the actual time series of the demod signals (actually I picked up the worst time chunk).

It seems that  most of the glitches in REFL11, REFL33 and AS55  coincide.

The typical time scale of the glitches was about 20 msec or so.

Note that the PRMI was locked by REFL33 and AS55 as usual.

I went through various IFO configurations to see if there are glitches or not.

Here is a summary table of the glitch investigation tonight. Some of the cells in the table are still not yet checked and they are just left blank.

        Low finesse PRMI      

The low finesse PRMI configuration is a power-recycled MIchelson with an intentional offset in MICH to let some of the cavity power go through MICH to the dark port.

To lock this configuration I used ASDC plus an offset for MICH and REFL33 for PRCL.

The MICH offset was chosen so that the ASDC power becomes the half of the maximum.

In this configuration NO glitches ( a high speed signal with an amplitude of more than 4 or 5 sigma) were found when it was locked.

Is it because I didn't use AS55 ?? or because the finesse is low ??

Also, as we have already known, the up conversion noise (#6212) showed up -- the level of the high frequency noise are sensitive to the 3 Hz motion.

Here is a hypothetical scenario which could make the glitches in the LSC error signals. It can be considered as a 4 step phenomenon.

        (1) up conversion noise due to a large motion at 3 Hz

   => (2) rms level exceeds the line width (a.k.a. linear range) in some LSC sensors

   => (3) unlocks some of the DOFs  in a moment

   => (4) glitches due to the short unlock.

- - plan  - -

 In order to check this hypothesis the low finesse PRMI must serve as a good test configuration.

What I will do is to gradually decrease the offset in MICH such that the finesse of PRMI becomes higher.

And at each different finesse I will check the spectra, glitch rate, and etc.

I have measured the sensing matrix of PRMI.

It seems that the MICH signal in the 3f ports (REFL33 and REFL165) were quite tiny, and because of that it is very tough to use them for the actual MICH control.

The data is coming soon.

I think I have told a lie in the last meeting -- the measured sensing matrix doesn't look similar to what Optickle predicts.

Smells like something is very wrong.

Measured sensing matrix

        Some obvious things:

•  REFL11 : The separation angle between MICH and PRCL is narrow and it is far from the ideal 90 degree. This doesn't agree with the simulation.
•  REFL33:  The MICH and PRCL signals are almost degenerated in their demodulation phase.
•  REFL55 :  It shows non-90 degree separation. This doesn't agree with the simulation.
•  REFL165 : The separation is close to 90 degree, but the signals are small. And I am not sure if the MICH signal is real or just noise.
•  AS55 : Somehow it shows a nice 90 degree separation, but this result doesn't agree with the simulation.

Expected sensing matrix from a simulation

Measurement

•  Locked PRMI with the carrier anti-resonating in PRCL.
•  Adjusted the control gains for both the MICH and PRCL control to have UGFs at ~ 100 Hz.
•  Put a 30 dB notch filter  in each control servo at 283.1 Hz where an excitation signal will be.
•  Excited PRCL and MICH at different time via the realtime lockng in the LSC front end. The amplitude is 1000 counts and the frequency is at 238.1 Hz.
  
  • For the MICH excitation, I have coherently and differentially excited ITMs
•  Used DTT to take a transfer function (transfer coefficients at 283.1 Hz) from the lockin oscillator to each LSC demodulated signal.
  • Including AS55I/Q, REFL11I/Q, REFL33I/Q, REFL55I/Q and REFL165I/Q.
•  Calibrated the obtained transfer functions from unit of counts/counts to V/m using the actuator response (#5637)

I updated the table which I posted some time ago (#6231). The latest table is shown below.

It seems that the glitches show up only when multiple DOFs are locked.

Interesting thing is that when the low finesse PRMI is locked with a big MICH offset (corresponding to a very low finesse) it doesn't show the glitches.

Qualitatively speaking, the glitch rate becomes higher as the finesse increases.

I will try SRMI tomorrow as this is the last one which I haven't checked the presence of the glitches.

I found that the DC monitor of the REFL165 was showing 9 V regardless of how much laser power goes to the diode.

I am worried about whether the RF output is also broken.

It needs to be checked and I will leave this to Suresh as one of his morning tasks.

Sometimes ago I reported that there have been a kind of upconversion noise when PRM was excited (#6211).

This time I found another one, which showed up when BS was excited.

Assuming this is related to some kind of scattering process and also assuming this is from the same scattering body as that for the PRM driven case,

we may be able to localize and perhaps identify the scattering body.

(Measurement Condition)

(Noise spectrum)

So why don't you use AS55I and Q for the control of PRMI???

 Those Radar plots are awesome. Even more awesome would be if they were in units of W/m (so that it can be directly compared with Optickle) and so that the numbers are useful even 1 year from now. Otherwise, we will lose the RF transimpedance information and thereby lose everything.

Also, please post the provenance of the counts->V calibration.

I locked the PRMI with the AS55I and Q combination.

It seems the glitche rate decreased,

but I am not 100 % sure because the rest of the demod signals (i.e. REFL11 and etc) were showing relatively big signals (noise ?), which may cover the glitches.

Also the optical gain of PRCL at AS55I doesn't agree with my expectation based on the obtained sensing matrix (#6283).

It looks too low and lower than the measured sensing matrix by a factor of 50 or so.

I will continue working on this configuration tomorrow and then move on to the SRMI locking as a part of the glitch hunting activity.

I tried the "Yarm + PRMI" configuration to see what happens.
The Y arm was locked at a resonance and held with the ALS technique.
On the other hand, the X arm was freely swinging.

I briefly tried severl demod signals to calm down the central part, but didn't succeed.
Now I feel I really want to have the X arm locked with the ALS technique too.
Give me the beat-box !

The attached screen shot shows the transmitted light of both arms as a function of time.
TRY is always above 1, since it was kept at a resonance.
Sometimes TRY went to 50 or so.

I have installed a proto version of the ALS beatbox delay-line frequency discriminator (DFD, formally known as MFD), in the 1X2 rack in the empty space above the RF generation box.

That empty space above the RF generation box had been intentionally left empty to provide needed ventilation airflow for the RF box, since it tends to get pretty hot.  I left 1U of space between the RF box and the beatbox, and so far the situation seems ok, ie. the RF box is not cooking the beatbox.  This is only a temporary arrangement, though, and we should be able to clean up the rack considerably once the beatbox is fully working.

For power I connected the beatbox to the two unused +/- 18 V Sorensen supplies in the OMC power rack next to the SP table.  I disconnected the OMC cable that was connected to those supplies originally.  Again, this is probably just temporary.

Right now the beatbox isn't fully functioning, but it should be enough to use for lock acquisition studies.  The beatbox is intended to have two multi-channel DFDs, one for each arm, each with coarse and fine outputs.  What's installed only has one DFD, but with both coarse and fine outputs.  It is also intended to have differential DAQ outputs for the mixer IF outputs, which are not installed in this version.

The intended design was also supposed to use a comparator in the initial amplification stages before the delay outputs.  The comparator was removed, though, since it was too slow and was limiting the bandwidth in the coarse channel.  I'll post an updated schematic tomorrow.

I made some initial noise measurements:  with a 21 MHz input, which corrseponds to a zero crossing for a minimal delay, the I output is at ~200 nVrms/\sqrt{Hz} at 5 Hz, falling down to ~30 nVrms about 100 Hz, after which it's mostly flat.  I'll make calibrated plots for all channels tomorrow.

The actual needed delay lines are installed/hooked up either.  Either Kiwamu will hook something up tonight, or I'll do it tomorrow.

I tried SRMI. The glitch rate wasn't as high as that of PRMI but it happened once per 10 sec or so.

Last night I tried the "Y arm + central part" locking again. Three different configuration were investigated :

•  Y arm + DRMI
•  Y arm + PRMI
•  Y arm + MICH

In all the configurations I displaced the Y arm by 20 nm from the resonance.

As for the DRMI and PRMI configurations I wasn't able to acquire the locks.

As for the MICH configuration, the MICH could be locked with AS55. But after bringing the Y arm to the resonance point the lock of MICH was destroyed.

I did a quick calculation to see if the offset of the arm length which I tried last night was reasonable or not.

The conclusion is that the 20 nm offset that i tried could be a bit too close to a resonance of the 55 MHz sidebands.

A reasonable offset can be more like 10 nm or so where the phases of all the laser fields don't get extra phases of more than ~ 5 deg.

The attached plot shows where the resonances are for each sideband as a function of the displacement from the carrier's resonance.

The red solid line represent the carrier, the other solid lines are for the upper sidebands and the dashed lines are for the lower sidebands.

The top plot shows the cavity power and the bottom plot shows how much phase shift the fields get by being reflected by the arm cavity.

Apparently the closest resonances to the the main carrier one are that of the 55 MHz sidebands, and they are at +/- 22 nm.

So if we displace the arm length by 22 nm, either of the 55 MHz sidebands will enter in the arm cavity and screw up the sensing matrix for the 55 MHz family.

I tried the Yarm + PRMI configuration again.

The PRMI part was locked, but it didn't stay locked during the Y arm was brought to the resonance point.

I will post the time series data later.

(locking of the PRMI part)

Tonight I was able lock the PRMI when the arm was off from the resonance by 10 nm (#6306).

This time I used REFL11Q to lock the MICH instead of the usual AS55Q because the MICH didn't stay locked with AS55Q for some reason.

The PRCL was held by REFL33I as usual.

Also I disabled the power normalization for the error signals because it could do something bad during the Y arm is borough to the resonance.

In order to reduce the number of the glitches, PRM was slightly misaligned because I knew that the lower finesse gives fewer glitches.

The figure below shows the time series of the Y arm + PRMI trail.

(Top plot )

  Normalized TRY (intracavity power). It is normalized such that it shows 1 when the arm is locked with the recycling mirrors misaligned.

(Middle plot)

ASDC and REFLDC in arbitrary unit.

(Bottom plot)

The amount of the arm length detuning observed at the fine frequency discriminator.

(Sequence)

At t = 20 sec, the amount of detuning was adjusted so that the cavity power goes to the maximum. At this point the PRM was misaligned.

At t = 30 sec, the cavity length started being slowly detuned to 10 nm. As it is being detuned the intracavity power goes down to almost zero.

At t = 45 sec, the alignment of PRM was restored. Because of that, the REFLDC and ASDC diodes started receiving a large amount of light.

At t = 85 sec, the PRCL and MICH were locked. The REFLDC signal became a high value as the carrier light is mostly reflected. The ASDC goes to a low value as the MICH is kept in the dark condition.

At t = 100 sec, the length started being slowly back to the resonance while the PRMI lock was maintained.

At t = 150 sec, the lock of the PRCL and MICH were destroyed. With the arm fully resonance, I wasn't able to recover the PRMI lock with the same demod signals.

 Isn't the point that the 11 and 55 MHz signals have the carrier effect, but the 3f signals are better?

I calculated how the DC signals should look like in the Y arm PRMI configuration.

The expected signals are overlaid in the same plot as that of shown in #6313.

You can see there are disagreements between the observed and expected signals in the plot below at around the time when the arm is brought to the resonance.

(expected behaviors)

•  TRY: At the end it should be at 1 (remember TRY is normarlized) and should not go more than that, since the power-recycling is in a weird situation and it is not fully recycling the power.
•  ASDC: It should become brighter at the end because the arm cavity flips the sign of the reflected light and hence the dark port must be on a bright fringe.
•  REFLDC: It will decrease a little bit because the arm cavity and MICH try to suck some amount of the power into the interferometer.

I have hooked the ALS beatbox into the c1ioo DAQ.  In the process, I did some rewiring so that the channel mapping corresponds to what is in the c1gcv model.

The Y-arm beat PD is going through the old proto-DFD setup.  The non-existant X-arm beat PD will use the beatbox alpha.

Y coarse I (proto-DFD) --> c1ioo ADC1 14 --> C1:ALS_BEATY_COARSE_I
Y fine   I (proto-DFD) --> c1ioo ADC1 15 --> C1:ALS_BEATY_FINE_I
X coarse I (bbox alpha)--> c1ioo ADC1 02 --> C1:ALS_BEATX_COARSE_I
X fine   I (bbox alpha)--> c1ioo ADC1 03 --> C1:ALS_BEATX_FINE_I

This remapping required coping some filters into the BEATY_{COARSE,FINE} filter bank.  I think I got it all copied over correctly, but I might have messed something up.  BE AWARE.

We still need to run a proper cable from the X-arm beat PD to the beatbox.

I still need to do a full noise/response characterization of the beatbox (hopefully this weekend).

Last night I took a closer look at the LSC analog signals to find which components are making the glitches.

I monitored the RFPD output signals and the demodulated signals at the same time with an oscilloscope when the PRMI was kept locked.

Indeed the RFPD outputs have some corresponding fast signals although I only looked at the RELL11 I and Q signals.

(REFL33 didn't have sufficiently a high SNR to see the glitches with the oscilloscope.)

I will check the rest of channels.

I found that none of the filter banks in the LSC input signals have the precise anti-whitening filters.

I installed the precise filters on REFL11, REFL33, REFL55 and AS55 based on Jenne's measurement (#4955)

After installing them I briefly checked the REFL11 sensing matrix with the PRMI locked, but it didn't change so much from what I got (#6283).

But I felt that the PRMI became more robust after that ... I just felt so ...

(Background)

(What I did)

(Next ?)

• Check  the amount of of the sidebands using the OSA
• Check the amount of the DC light
• Check the sensing matrix to see if the absolute values in watt / meter make sense or not
  • This work needs calibrations on all the demodulated board (this is equivalent to measuring the conversion losses of the mixers in the demod boards).
• Measure the contribution from the RAMs (it must be measurable by some means)

I installed the rest of the precise anti-whitening filters. Now all of the LSC sensors have the right filters.

I briefly ran a Optickle code to see how the PRC macroscopic length screws up the sensing matrix in the PRMI configuration.

Especially I focused on the optimum demodulation phases for the MICH and PRCL signals to see how well they are separated in different PRC length configuration.

It seems that the demod phases for MICH and PRCL are always nicely separated by approximately 90 degree regardless of how long the PRC macroscopic length is.

If this is true, how can we have such a strange sensing matrix ??

(Simulation results)

 Like I said, this is possible if you fail to set up the OSA to look at the sidebands at BOTH the AS and REFL ports at all times. Don't waste your time - set up an OSA permanently!

I am installing an OSA on the AP table and it's ongoing.

I am leaving some stuff scattered on the AP table and I will resume the work after I come back.

I placed the OSA (Optical Spectrum Analyzer) on the AP table and this OSA will monitor the REFL beam.

Tomorrow I will do fine alignment of the OSA.

(some notes)

- a new 90% BS in the REFL path for limiting the REFL beam power

- Squeezed the ABSL (ABSolute length Laser) path

- Modification of the AS OSA path

The OSA for the REFL beam is now fully functional.

The only thing we need is a long BNC cable going from the AP table to the control room so that we can monitor the OSA signal with an oscilloscope.

The attached picture shows how they look like on the AP table. Both AS and REFL OSAs are sitting on the corner region.

Plans:

•  DRMI (PRMI) + one arm test before the LVC meeting
•  Study of the funny sensing matrix and the RAM offset effects before the LVC meeting
•  Glitch hunting

Action items:

• MC beam pointing 
  
  • to make the PZT1 pitch relax
• OSA setup
  •    a long BNC cable for monitoring the signal in the control room
• Power budget on the AP table
  • in order to ensure the laser power on each photo diode

•  POP22/110 sideband monitor
  • installation of an RF amp
  • building a diplexer
  • connect the signals to the demod boards 
•  Calibration of the demod boards
  • calibrate the conversion loss of the mixers to calibrate all the LSC signals to watts / meter
•  (1+G) correction for the glitch time series data
• Simulation study for the RAM offset
  • How much offset do we get due to the RAM ? and how do the offsets screw up the sensing matrix ?
•  A complete set of the MICH characterization
  •   DC power
  •   Sensing matrix
  •   Noise budget
  •   OSA
  •   Estimation of the RAM offset 
  •  Summarize the results in the wiki
•  A complete set of the PRMI/DRMI characterization
  •  The same stuff as the MICH characterization
•  DRMI + one arm test
  •   Monitor the evolution of the sensing matrix during the arm is brought to the resonance