I guess that you get an ellipse when the transfer functions to I and Q have a different phase. One mechanism could be that when driving MICH we make some residual PRCL and this couples with a different transfer function to both I and Q. However, I would expect no phase lag in the PRMI configuration, since there is no enough optical delay in the system to give significant dephasing at few hundreds Hz. This effect might come from mechanical resonances.

It is worth measuring the optical transfer functions from both PRCL and MICH to REFL signals at all frequencies, to see if we have strange features in the TFs.

Last week, while I had the PRMI locked on REFL33, I did some poking around with mirror excitation to RFPD quadrature transfer functions. I got some indication of weird things with sensing MICH with the 3F REFL signals, but it should be explored more before taken as a real thing. I just figured I would show what I saw. 

With that disclaimer out of the way, here's what I did:

• Locked PRMI on PRCL:REFL33_I and MICH:REFL33_Q, as detailed in my earlier ELOG
• Created PRCL and MICH excitations at two different frequencies, notched said frequencies out of the control filters
• Took transfer functions from mirror LSC output signals to 33 I, 33 Q, 165 I, 165 Q in DTT
• For each DOF, look at the measured transfer functions only at the excitation frequency. (Assuming good coherence, which was there)

The basic idea was, some PRCL motion (for instance), has a transfer function to both the I and Q quadratures at a given PD. As the PRCL excitation sine wave goes through one cycle, the REFL signals at the excitation frequency go through some coherent cycle. Thus, the excitation traces out some trajectory in the I vs. Q plane. I believe this is analogous to the typical "radar plot" that we make for sensing matrix elements. 

However, the straight line that we normally plot in the radar plots assumes a certain phase relationship between the DOF-> I and DOF->Q transfer functions that results in a straight line. Here are the trajectories I actually measured, normalized by the excitation amplitudes.

The plotted traces are (x,y) = (H_prcl->I * prcl, H_prcl->Q * prcl) and  (x,y) = (H_mich->I * mich, H_mich->Q * mich) where H_prcl->I is the measured complex transfer function from prcl to REFL I, for instance, and prcl and mich are the excitation signals, normalized to unit amplitude.

PRCL looks like a nice straight line in both of these, and pretty well phased, but not only is MICH not very orthogonal to PRCL, there is quite a bit of ellipticity present, which means we can't fully decouple the two DOFs, even if they were nominally orthogonal. 

I'm not sure what may cause this. To back up this measurement/interpretation, I tried to take measurements of these transfer functions across different excitation frequencies via swept sine DTT, but seismic activity kept me from staying locked long enough...

I have included Yarm CESAR to the LSC model. It was just a copy paste of the Xarm CESAR. Since we are now meditating about implementing CCESAR and DCESAR, I did not run or install the model as yet.

 Guilty!!

POP path

The POP PD was showing only ~200 counts which was very low compared to what we recollect from earlier PRMI locks (~400 counts). Also, the POP ASC QPD was also not well-aligned.
While holding PRMI lock on REFL55, I aligned POP path  to its PD (maximize POP DC counts) and QPD (centered in pitch and yaw).

X and Y green

The X green totally lost its pointing because of the misaligned PZTs from last week's power failure. This was recovered.
Y arm green alignment was also recovered.

 MC2_TRANS path in WFS servo turned OFF.

Local earthquake activity is up. Our suspensions are holding well.    ETMX and ETMY sus damping restored.

FB: /etc/ntp.conf was updated as below such that it refers nodus and also caltech server when nodus is not available

server 192.168.113.200
server 131.215.239.14

ntpd was restarted and

diskless RT machines: they are booted from /diskless/root on fb.
Therefore /diskless/root/etc/ntp.conf was updated in the same way as above.
When the machines are rebooted, this setting will be active.

control machines:

now they are referring nodus and other external servers too.

[Koji Rana]

We are looking at NTP settings. I looked at nodus.

- xntpd is running

- We decided to start over the configuration file /etc/inet/ntp.conf

    - The old configuration was moved to ntp.conf.bak

    - The server configuration file was copied from ntp.server to ntp.conf

    - Caltech NTP servers 131.215.239.14 and 131.215.220.22 were selected as the servers we are reffering

    - Commented out the lines for "fudge" and "broadcast"

- xntpd was restarted

    - sudo /etc/init.d/xntpd stop
    - sudo /etc/init.d/xntpd start

- check how the daemon is running
      tail -50 /var/adm/messages

   Mar 28 23:00:49 nodus xntpd[27800]: [ID 702911 daemon.notice] xntpd 3-5.93e Mon Sep 20 15:47:11 PDT 1999 (1)
   Mar 28 23:00:49 nodus xntpd[27800]: [ID 301315 daemon.notice] tickadj = 5, tick = 10000, tvu_maxslew = 495, est. hz = 100
   Mar 28 23:00:49 nodus xntpd[27800]: [ID 798731 daemon.notice] using kernel phase-lock loop 0041
   Mar 28 23:00:49 nodus last message repeated 1 time
   Mar 28 23:00:49 nodus xntpd[27800]: [ID 132455 daemon.error] trusted key 0 unlikely
   Mar 28 23:00:49 nodus xntpd[27800]: [ID 581490 daemon.error] 0 makes a poor request keyid

- check the syncing staus by ntpq -p

        remote           refid      st t when poll reach   delay   offset    disp
   ==============================================================================
   *ntp-02.caltech. .CDMA.           1 u   37   64  377     0.56    3.010    0.08
   +ntp-03.caltech. ntp1.symmetrico  2 u   36   64  377     0.52    2.727    0.12
      this * means nodus is synced to ntp-02. "+" means it is stand by as a valid secondary server.  "when" increases every second.
      When "when" reaches "poll" the clock is synced to the server. These marks are not set at the beginning.
      It was necessary to wait for sometime to get synced to the server.

- Once nodus became a synced server, the realtime systems starts syncing to nodus automatically.

   controls@c1sus ~ 0$ cat /var/log/ntpd
   25 Mar 01:41:00 ntpd[4443]: logging to file /var/log/ntpd
   (...)
   28 Mar 23:13:46 ntpd[4983]: synchronized to 192.168.113.200, stratum 2
   28 Mar 23:14:25 ntpd[4983]: time reset +39.298455 s
   28 Mar 23:14:25 ntpd[4983]: kernel time sync status change 2001
   28 Mar 23:25:19 ntpd[4983]: synchronized to 192.168.113.200, stratum 2
   controls@c1sus ~ 0$ ntpq -p
        remote           refid      st t when poll reach   delay   offset  jitter
   ==============================================================================
   *nodus.martian   131.215.239.14   2 u   42   64  377    0.140   42.222  11.373


* EQ Southeast of LA around 45 minutes ago. Callum and I felt it.

* Koji and I came in to recover. MC suspensions had been mis-aligned. ETMs both tripped their watchdogs.

* As before, the ETMX was stuck in its cage and the UR & LR OSEMs were reading zero V.

* We moved the MC sus back to their OSEM values from 2 hours ago. Koji aligned everything else by just using his chee.

* To shake the ETMX loose, I tried a different tactic than the "Great Balls of Fire". I started giving it 20k steps through the ASCYAW filterbank (with ramping OFF). I used the green light in the X arm video to look at the swinging. Using this as a readback I pumped the OFFSET button on ASCYAW to resonantly swing up the yaw motion. I had to turn the watchdog thresh up to 2000 temporarily. After a couple minutes the ETMX was free.

* We then used the bias sliders to steer it back onto the OL center (which Q nicely lined up for us recently) and then X arm locked in green right away.

Fri Mar 28 22:38:04 2014:  We've just ridden through the 5th aftershock. None of the aftershocks have tripped the watchdogs  but they break the IMC lock.

I aligned MC2 suspension by 0.01 in pit and yaw to align the MC better to the PSL beam. Then I turned the WFS back on. The beams are not centered on the WFS heads.

Nic and Gabriele ought to send their SURF some example code (in April) for how to start redesigning the WFS telescopes so that we can order some optics in early June.

I've also turned on the MC2 TRANS path to gather some data over the weekend on how well or bad it works. Please turn it off on Monday.

While I'm looking at the PRM ASC servo model, I tried to use the current servo filters for the ASC
as Manasa aligned the POP PDs and QPD yesterday. (BTW, I don't find any elog about it)

I found no issue for locking PRMIsb with the REFL165I&Q signals if the PRM ASC is employed.
See this entry for the IFO settings.

It is just stable. The IFO is ready for the arm scanning.

=== ASC setting ===

PRCL_PITCH: FM1/3/9 x-0.004
PRCL_YAW: FM1/3/9 x-0.001

The PRM OPLEV has to be off when the PRM ASC is engaged. Actually, it turned out that we don't need OPLEV for locking.

ETMX ASC output was turned off for whatever reason. Switched it on, ASS is fine.

The following that went unnoticed from yesterday were recovered today:

1. ETMX and ETMY 'misalign' scripts weren't running. Troubleshooting showed slow machines c1auxex and c1auxey weren't responding. The machines were reset.

2. PRM oplev gains were zero. Gain values were set looking back at the burt files.

3. X end PZT power supplies were turned ON and set to 100V.

4. X end doubler temperature was reset to the last optimal value on elog (36.35 deg).

Some hitches that should be looked into:

1. Check: ASS for X arm seems not quite doing its job. ETMX has to be moved using sliders to obtain maximum TRX and the arm alignment was seen to be drifting.

2. Check: Status of other slow machines and burt restore whichever needs one.

Incidentally, while messing around with transfer functions and sensing matrix elements this evening, I was able to sideband lock straight onto REFL33 I&Q.  The settings were all identical to Koji's ELOG, with the following differences:

Input ports:
REFL33   WHTN: 30dB demod phase +125.5deg (tweaked from 135.5 to minimize MICH in I)

Input matrix:

REFL33I x +1.0 -> PRCL
REFL33Q x +3.0 -> MICH

Servo:
MICH OFS 0 / Gain 1/ Limitter ON (Oscillations occurred at 1.3)
PRCL OFS 0 / Gain -0.04 / Limitter ON

Output matrix:

MICH ITMX -1.0 / ITMY 1.0
PRCL PRM 1.0

[Manasa, Eric, Koji]

PRMIsb was locked with REFL165I&Q.

- Aligned the arms with ASS. The misaligned ETMX and ETMY

- Configured PRMIsb with IFO_Configure screen

- Immediately PRMIsb was locked with REFL55I&Q

- Checked the REFL165 phase in terms of the REFL165Q vs PRCL. It was already well adjusted at -82.5deg. We tuned the phase a bit more and got -83.5deg.

- With DTT, relative gain between REFL55I and REFL165I was measured. REFL165I is about x10 higher than REFL55I and has the same sign.

- The transition of PRCL with the input matrix was just easy.

- With DTT, relative gain between REFL55Q and REFL165Q was measured. REFL165Q is about x3 higher than REFL55Q and has the same sign.

- The transition of MICH was flakey, but after careful adjustment of the PRM alignment, ~10s lock was achieved. It seemed that the PRM alignment fluctuation
  was bug enough to unlock the interferometer.

- Eric went into the lab and aligned all of the oplevs except for the SRM's one.

- Now the lock with REFL55 and also with REFL165 became more robust. Less MICH offset and darker AS port.

Input ports:
REFL55   WHTN: 45dB demod phase +45.0deg
REFL165 WHTN: 45dB demod phase -83.5deg

Input matrix: for acquisition:
REFL55I x 1.0 -> PRCL
REFL55Q x 1.0 -> MICH

Input matrix: PRCL Transition:
REFL55I x 1.0 + REFL165I x 0.0 -> x0.5 + x0.0 -> x0.5 + x0.05 -> x0.3 + x0.05 -> x0.2 + x0.05 -> x0.1 + x0.05 -> x0.0 + x0.05

Input matrix: MICH Transition:
REFL55Q x 1.0 + REFL165Q x 0.0 -> x0.5 + x0.0 -> x0.5 + x0.3 -> x0.3 + x0.3 -> x0.2 + x0.3 -> x0.1 + x0.3 -> x0.0 + x0.3

Triggers:
MICH POP110I 100up/10down / FM Trig FM2/3/9 35up 2down 5sec delay
PRCL POP110I 100up/10down / FM Trig FM2/3/6/9 35up 2down 0.5sec delay

Servo:
MICH OFS 0 / Gain 1.3 / Limitter ON
PRCL OFS 0 / Gain -0.04 / Limitter ON

Output matrix:
MICH PRM -0.2625 / BS 0.5
PRCL PRM 1.0

Recovery work: now arms are locking as usual

- FB is failing very frequently. Everytime I see red signals in the CDS summary, I have to run "sudo ntpdate -b -s -u pool.ntp.org"

- PMC was aligned

- The main Marconi returned to initial state. Changed the frequency and amplitude to the nominal value labeled on the unit

- The SHG oven temp controllers were disabled. I visited all three units and pushed "enable" buttons.

- Y arm was immediately locked. It was aligned using ASS.

- X arm did not show any flash. I found that the scx model was not successfully burtrestored yesterday.
  The setting was restored using Mar 22 snapshot.

- After a little tweak of the ETMX alignment, a decent flash was achieved. But still it could not be locked.

- Run s/LSC/LSCoffset.py. This immediately made the X arm locked.

- Checked the green alignment. The X arm green is beating with the PSL at  ~100MHz but is misaligned beyond the PZT range.
  The Y arm green is locked on TEM00 and is beating with the PSL at ~100MHz.

Extending the previous model, I've closed a rudimentary CESAR loop in simulink. Error signals with varying noise levels are combined to bring a "cavity" to lock.  

There are many things that are flat out arbitrary at this point, but it qualitatively works. The main components of this model are:

• The "Plant": A pendulum with f0 = 2Hz, Q = 10
• Some white force noise, low passed at 1Hz before input to the plant.
• The Controller: A very rough servo design that is stable...
• ALS signal: Infinite range Linear signal, with a bunch of noise
• Transmission and PDH signals are computed with some compiled C code containing analytic functions (which can be a total pain to get working), have less noise than ALS
• Some logic for computing linearized PDH and SqrtInv signals
• A C code block for doing the CESAR mixing, and feeding to the servo

And it can lock! 

Right now, all of the functions and noise levels are similar to the previous simulation, and therefore don't tell us anything about anything real...

However, at this point, I can tune the parameters and noise levels to make it more like our interferometer, and thus maybe actually useful. 

As far as I know the system is running as usual. I had the IMC locked and one of the arm flashing.
But the other arm had no flash and none of the arms were locked before kunch time.

This morning Steve and I went around the lab to turn on the realtime machines.

Also we took the advantage of this opportunity to shutdown linux1 and nodus
to replace the extension cables for their AC power.

I also installed a 3TB hard disk on linux1. This was to provide a local daily copy of our
working are. But I could not make the disk recognized by the OS.
It seems that there is a "2TB" barrier that the disk bigger than 2.2TB can't be recognized
by the older machines. I'll wait for the upgrade of the machine.

Rebooting the realtime machines did not help FB to talk with them. I fixed them.
Basically what I did was:

- Stop all of the realtime codes by running rtcds kill all on c1lsc, c1ioo, c1sus, c1iscex, c1iscey

- run sudo ntpdate -b -s -u pool.ntp.org on c1lsc, c1ioo, c1sus, c1iscex, c1iscey, and fb

- restart realtime codes one by one. I checked which code makes FB unhappy. But in reality
  FB was happy with all of them running.

Then slow machines except for c1vac1 and c1vac2 were burtrestored.

-------

Zach reported that svn was down. I went to the 40m wiki and searched "apache".
There is an instruction how to restart apache.

 Out gassing plus leak rate   0.15  mTorr / hour

 The pressure rose to 2.5 mTorr in 17 hours

 V1 was opened at 1:56pm

 VM2 opened at 2:10 so the RGA region is back to 1e-5 torr

 9:11pm closed PSL shutter, turned Innolight 2W laser on,

         turned 3 IFO air cond on,

        CC1 5.1e-5 torr, V1 is closed, Maglev has failed, valve configuration is " Vacuum Normal "  with V1 & VM1 closed, RGA not running,   c1vac1 and c1vac2   were saved by UPS,

        (Maglev is not connected to the UPS because it is running on 220V)

        reset & started Maglev.........I can not open V1 without the 40mars running...........

        Rossa is the only computer running in the control room,

        Nodus and Linux1 was saved by UPS,

        turned on IR lasers at the ends, green shutters are closed

It is safe to leave the lab as is.

I'm checking the status from home.

P1 is 8e-4 torr

nodus did not feel the power outage (is it APS supported?)

linux1 booted automatically

c1ioo booted automatically.

c1sus, c1lsc, c1iscex, c1iscey need manual power button push.

 The 40m experienced a building-wide power failure for ~30 seconds at ~7:38 pm today.

Thought that might be important...

 We should make screens like this for the LSC signals, errors, ALS, etc.

Please take a look at the table top with the flashlight before removing it. If it is dusty, wipe it down with dry lint free cloth in the box.

There is one box with flash light and wiper at AP, ETMY & ETMX  optical tables.

 I've been getting a simulation going with the eventual goal of simulating CESAR-type signals for CARM. So for I've only been using MIST, though I'm still thinking about what to do for a fully time domain approach. (For example, maybe a mixture of simulink and analytical equations? We'll see how painful that gets...)

Anyways, with the parameters I have for the 40m, I've set up a simulation, where I can do things like a "static" CARM scan.

(i.e. PRMI perfectly locked. Ask what different PDs see if the arms were just statically sitting at some CARM offset)

PDH signals are there in the REFL diodes. The coupled line width here looks smaller than the ~40pm number I've heard before, so I should check my parameters. (Likely culprit, I'm using nominal R and T for the arm cavities)

I've also done the slightly more sophisticated thing of looking at the transfer function from CARM motion to different PDs, at different CARM offsets. For TRX and REFLDC, these seem to match up qualitatively to some plots that Kiwamu has done for aLIGO, with frequencies shifted by the relative arm length factor of 100. (Q's left, K's right, Y-axis on mine are W/m with 1W input the IFO)

We can also look at the PDH diodes (revised from my initial post. Had an error in my code): 

That's where I've gotten so far!

[ Manasa, Ericq and Steve ]

 Vivitek D952HD with 186 hours installed.

I tried to repeat Koji's PRMI lock using REFL165I/Q. I was not able to lock PRMI stably. All I could get was momentary PRMI sb locks (few seconds) using AS55Q for MICH and REFL165Q for PRMI. I tried to transition MICH locks from AS55Q to REFL165I/Q and this did not work well; I lost even the momentary locks.

The demod phases for both AS55 and REFL165 were also very different. 

Input ports:
AS55       WHTN: 21dB  demod phase -78.7deg
REFL165 WHTN: 45dB demod phase -80.7deg

Input matrix:
AS55Q x1.00 MICH

REL165Q x+0.14

Triggers:
MICH POP110I 100up/10down / FM Trig FM2/3/6/7/9 35up 2down 5sec delay
PRCL POP110I 100up/10down / FM Trig FM2/3/6/9 35up 2down 0.5sec delay

Servo:
MICH OFS 0.0 / Gain -10 / Limiter ON
PRCL OFS 0 / Gain -0.023 / Limiter ON

Output matrix:
MICH ITMX -1.0 / ITMY +1.0
PRCL PRM 1.0

MC spot sposition script was ran

/opt/rtcds/caltech/c1/scripts/ASS/MC/mcassMCdecenter

Found no notable beam position change before and after the earthquake

  UR osem IR shield glass is pushed back. It came out of its clip holder. The magnet is free.

  Atm2,  UL & LL magnets  centered poorly. Almost hinging on opposite sides.

              UR & LR centered well.  There have plenty of room to move in an earth quake.

 This recovery proceeder deserves a pattern

Note: IR shield glass position variations,  Atm4

 I am really, really happy to hear that it was just a sticking situation.  Really happy. 

It was little bit surprising to me but Rana's professorial rock'n roll excitation released its sticking on the unconfirmed thing by unconfirmed reason.

I aligned the Xarm manually and via ASS.

Now we are back in the normal state.

I tried to take the photos of the magnets from outside. So far most suspicious was LL.
Otherwise, the magnets are OK.
(The SD magnet is the one with most reasonable response.)
Steve will try to take much more zoomed photo with Olympus. But the LL coil already showed some response in my observation in the morning.

Off again. Restarted ntp on fb.

I confirmed that we need to vent the chambers.

All of the mirrors have been aligned except for ETMX.

ETMX does not respond to the excitation by the UR and LR coils. Likely that the magnets are knocked off, or stuck in the coil.

PRM/SRM oplevs are too much off and can't be turned on. Need realignment of the beams on the QPDs.

- FB was down. FB restarted ("telnet fb 8087", then type shutdown)

- Aligned the MC mirrors.

- Aligned PRM. Look at the REFL. It was slightly mislisligned.

- AS has no beam. The Y arm was resonating with the green. So I determined that the TTs were the misaligned guys.

- Touched TT2 pitch with an increment of 0.1. Immediately the AS beam spot for ITMY was found. And the arm was resonating.

- The RM was further aligned. The bias sliders were saved and then the PRM was misaligned.

- Yarm was locked on TEM01. The ASS maximized the transmission for TEM01, and then the arm was locked on TEM00.
  The ASS aligned the arm and TTs. These values were saved.

- Yarm was aligned and I can see the AS spot. So I believe the BS is still well aligned.

- Aligned the PRM to reduce the ghost beams.

- Moved the ITMX to have Michelson fringes properly.

- Also aligned the SRM.

- Now ETMX was checked. Played with the alignment biases to see if the mirror was sticking on the coils. The mirror can rock a little, but it did not come back.

- Then, checked each magnets. 0.8Hz 1000cnt signals were injected to each coils (cf. C1:SUS-PRM_**COIL_EXC) to see how the mirror could react.
  The OSEM output and green spot on the ETMX cage were observed.

- Saw some response by actuating the UL, LL, SD coils.

- Saw no response from the UR and LR coils. They show the OSEM output of zero. Does this mean the magnets fell in the coils?

//Manasa// MC spot positions measured and they look alright with not much change from before the earthquake (attach)

 KroneCrane Fred inspected and certified the 3 40m cranes for 2014. The vertex crane crane was load tested at fully extended position.

 It looks like that ETMX have  2 sticky magnets.

Asymptotic cooling of the mirror motion with CESAR was tested.

With ALS and the full control bandwidth (UGF 80-100Hz), the actuator amplitude of 8000cnt_pp is required.

Varying control bandwidth depending on the noise level of the signal, the arm was brought to the final configuration with the actuator amplitude of 800cnt_pp.

 Ha!

 Annual crane inspection is scheduled for 8-11am Monday, March 17, 2014

The control room Smart UPS has two red extension cords that has to be removed: Nodus and Linux1

[Jenne, EricQ]

As Koji suggested in his email this afternoon, we looked at how much actuator range is required for various forms of arm locking:  (1) "regular" PDH lock aquisition, (2) ALS lock acquisition, (3) CESAR cooling.

To start, I looked at the spectra and time series data of the control signal (XARM_OUT) for several locking situations.  Happily, when the arm is at the half fringe, where we expect the 1/sqrt(TRX) signal to be the most sensitive (versus the same signal at other arm powers), we see that it is in fact more quiet than even the PDH signal.  Of course, we can't ever use this signal once the arm is at resonance, so we haven't discovered anything new here.

EricQ then made some violin plots with the time series data from these situations, and we determined that a limit of ~400 counts encompasses most of the steady-state peak-to-peak output from locking on the PDH signal.

[ericq: What's being plotted here are "kernel density estimates" of the time series data of XARM_OUT when locked on these signals. The extent of the line goes to the furthest outlier, while the dashed and dotted lines indicate the median and quartiles, respectively]

I tried acquiring ALS and transitioning to final PDH signals with different limiters set in the Xarm servo.  I discovered that it's not too hard to do with a limit of 400 counts, but that below ~350 counts, I can't keep the ALS locked for long enough to find the IR resonance.  Here's a plot of acquiring ALS lock, scanning for the resonance, and then using CESAR to transition to PDH, with the limit of 400 counts in place, and then a lockloss at the end.  Even though I'm hitting the rails pretty consistently, until I transition to the more quiet signals, I don't ever lose lock (until, at the end, I started pushing other buttons...).

After that, I tried acquiring lock using our "regular" PDH method, and found that it wasn't too hard to capture lock with a limit of 400, but with limits below that I can't hold the lock through the boosts turning on.

Finally, I took spectra of the XARM_OUT control signal while locked using ALS only, but with different limiter values. Interestingly, I see much higher noise between 30-300 Hz with the limiter engaged, but the high frequency noise goes down.  Since the high frequency is dominating the RMS, we see that the RMS value is actually decreasing a bit (although not much).

We have not made any changes to the LSC model, so there is still no smoothing between the ALS and IR signals.  That is still on the to-do list.  I started modifying things to be compatible with CARM rather than a single arm, but that's more of a daytime-y task, so that version of the c1lsc model is saved under a different name, and the model that is currently compiled and running is reverted as the "c1lsc.mdl" file.

I have modified the IFOconfigure scripts and the corresponding .req files for the X arm and Y arm in burt. I have also added configure scripts to save and restore LSC settings for locking the arms using ALS error signals.

The settings are yet to be saved and the scripts should also be checked if they are working as required.

Q and I have started to use the ALS slow servo for the end aux lasers while locking the arms using ALS. The servo prevents us from hitting the limits of the PZT range for the end lasers and a better PDH locking.

But keeping the servo ON causes the slow output to drift away making it hard to find the beat note everytime the arm loses lock. The extensive beat note search following the unlock can be avoided by clearing history of the slow servo.

Speaking of the whitening board, I had neglected to post details showing the the whitening was at least having a positive effect on the transmon QPD noise. So, here is a spectrum showing the effects that the whitening stages have on a QPD dark noise measurement like I did in ELOG 9660, at a simulated transmission level of 40 counts. 

The first whitening stages gives us a full 20dB of noise reduction, while the second stage brings us down to either the dark noise of the QPD or the noise of the whitening board. We should figure out which it is, and fix up the board if necessary. 

The DTT xml file is attached in a zip, if anyone wants it.

[Nic, Jenne, EricQ, and Koji]

We have used CESAR successfully to bring the Xarm into resonance.  We start with the ALS signal, then as we approach resonance, the error signal is automatically transitioned to 1/sqrt(TRX), and ramped from there to POX, which we use as the PDH signal.

In the first plot, we have several spectra of the CESAR output signal (which is the error signal for the Xarm), at different arm resonance conditions.  Dark blue is the signal when we are locked with the ALS beatnote, far from IR resonance.  Gold is when we are starting to see IR resonance (arm buildup of about 0.03 or more), and we are using the 1/sqrt(TRX) signal for locking.  Cyan is after we have achieved resonance, and are using only the POX PDH signal.  Purple is the same condition as cyan, except that we have also engaged the low frequency boosts (FM 2, 3, 4) in the locking servo.  FM4 is only usable once you are at IR resonance, and locked using the PDH signal.  We see in the plot that our high frequency noise (and total RMS) decreases with each stage of CESAR (ALS, 1/sqrt(TR) and PDH). 

To actually achieve the gold noise level of 1/sqrt(TR), we first had to increase the analog gain by swapping out a resistor on the whitening board. 

The other plots attached are time series data.  For the python plots (last 2), the error signals are calibrated to nanometers, but the dark blue, which is the transmitted power of the cavity, is left in normalized power units (where 1 is full IR resonance). 

In the scan from off resonance to on resonance, around the 58 second mark, we see a glitch when we engage FM4, the strong low frequency boosts.  Around the 75 second mark we turned off any contribution from 1/sqrt(TR), so the noise decreases once we are on pure PDH signal. 

In the scan through the resonance, we see a little more clearly the glitch that happens when we switch from ALS to IR signals, around the 7 and 12 second marks. 

We want to make some changes, so that the transition from ALS to IR signals is more smooth, and not a discrete switch.