40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 309 of 344  Not logged in ELOG logo
ID Date Authorup Type Category Subject
  1163   Tue Nov 25 19:29:15 2008 rana, alberto, johnConfigurationEnvironmenttemperature

Quote:
The PSL Room Temperature was alarming because it had gone above 23 C. This set off an unfortunate chain of events:

We found that the PSL HEPA was set low (20%). This is a fine setting for when no one is working in there but it
does raise the temperature since there are heat sources inside the blue box.

We tried to change the office area temperature to compensate and also the westmost sensor inside the lab area by 2 deg F.

The office area one was problematic - there was so much dust in it that the gas valve nipple was clogged. So we've
now blown it all clean with a compressed air can. We're now tuning the calibration screw to make our new
digital sensor agree with the setpoint on the controller.

Expect wild temperature swings of the office area for a couple days while Alberto and I tune the servo.


This morning Bob found 92F in the office area and in the control room of the lab. He turned down the thermostat and when I got in at about 9 I found 65. After a few hours of adjustment of the thermostat's calibration, I could stabilize the room temperature to about 72F. I also turned down the thermostats inside the lab of a couple of degrees F.
  1151   Fri Nov 21 16:11:26 2008 rana, alberto, robUpdatePSLMach Zender alignment
The Mach Zender's dark port DC voltage had gone up too high (~0.5 V)and was turning yellow
on the screen. I re-aligned by touching the knobs on the 166 MHz path. Doing alignment after the
166 EOM had very little effect. The main improvement came from doing yaw on the turning mirror
just ahead of the 166 MHz EOM; this is the one which as no adjustment knobs (duh).

During this procedure, I had the MC off, the ISS off, and the MC autolocker off. After finishing
the alignment, the power on the ISS PDs had railed and the dark port power was ~0.29 V. So we
put in a ND0.2 on the ISS path and now the voltages are OK (~2 V on each PD). We have to remove the
ND filters and change the first ISS turning mirror into a ~10-20% reflector.


So now the MZ alignment seems good; Alberto is on the MC periscope alignment like a cheap suit.
Attachment 1: PB210051-1.JPG
PB210051-1.JPG
  1155   Fri Nov 21 20:29:43 2008 rana, alberto, robUpdatePSLMach Zender alignment

Quote:
So now the MZ alignment seems good; Alberto is on the MC periscope alignment like a cheap suit.


And alignment is now mostly done - MC locks on the TEM00.
                 REFL_DC

Unlocked           4.50  V
Locked noWFS       1.30  V
Locked + WFS       0.42  V
and the 29.5 MHz modulation depth is really small.

We should be able to rerun the Wiener analysis on this weekends MC data.

I don't know what our nominal StochMon numbers now are, but after Alberto tweaks up the alignment he can tell us if the RFAM has gotten any better.
  1973   Tue Sep 8 15:14:26 2009 rana, alexConfigurationDAQRAID update to Framebuilder: directories added + lookback increased

 Alex logged in around 10:30 this morning and, at our request, adjusted the configuration of fb40m to have 20 days of lookback.

I wasn't able to get him to elog, but he did email the procedure to us:


1) create a bunch of new "Data???" directories in /frames/full
2) change the setting in /usr/controls/daqdrc file
       set num_dirs=480;

my guess is that the next step is:

3) telnet fb0 8087

    daqd>  shutdown

I checked and we do, in fact, now have 480 directories in /frames/full and are so far using up 11% of our 13TB capacity. Lets try to remember to check up on this so that it doesn't get overfull and crash the framebuilder.

  4112   Wed Jan 5 16:00:11 2011 rana, alexSummaryDAQFrameBuilder fails in a new way

Email from Alex:

Turned out to be the lack of current year information in the IRIG-B signal
received by the Symmetricom GPS card in the frame builder machine caused
this. I have added a constant in daqdrc to bring the seconds forward:

controls@fb /opt/rtcds/caltech/c1/target/
fb $ grep symm daqdrc
#set symm_gps_offset=-1;
set symm_gps_offset=31536001;

Hopefully we will be upgrading to the newer timing system at the 40M this
year, so this will not happen again next year.


 

Doing an 'ls -lrt' in /frames/full/ now shows that the names are correct:

drwxr-xr-x 2 controls controls 249856 Dec 30 19:06 9777
drwxr-xr-x 2 controls controls 192512 Dec 31 16:00 9778
drwxr-xr-x 2 controls controls 151552 Jan  1 08:53 9463
drwxr-xr-x 2 controls controls 266240 Jan  2 12:39 9464
drwxr-xr-x 2 controls controls 258048 Jan  3 16:26 9465
drwxr-xr-x 2 controls controls 253952 Jan  4 20:13 9466
drwxr-xr-x 2 controls controls 151552 Jan  5 13:54 9467
drwxr-xr-x 2 controls controls  12288 Jan  5 15:57 9783

  1551   Wed May 6 16:56:35 2009 rana, alex, joeConfigurationComputersdaqd log, cront, etc.
While Alex came over, we investigated the log file problems with DAQD and NDS on FB0. There was a lot of
the standard puzzling and mumbling, but eventually we saw that it doesn't create its log file and so it
doesn't write to it. The log file is /usr/controls/main_daqd.log. The other files called daqd.log.DATE
in the logs/ directory are actually not written to. Its awesome.

We also have put in a fix for the overflowing jobs/ directory. It gets a file written to it every time
you make and NDS request and our seisBLRMS has been overloading it. There's now a cron for it in the fb0
crontab which cleans out week-old files at 6:30 AM every day.

We also changed the time of the daily backup from 3:30 AM (when people are still working) to 5:50 AM
(by which time the seismic has ramped up and interferometerists should be asleep). I didn't like the
idea of a bandwidth hog nailing the framebuilder during the peak of interferometer work.

#
# Script to backup via rsync the most recent 40m minute trends and
# any changes to the /cvs/cds filesystem.
#
50 05 * * * /cvs/cds/caltech/scripts/backup/rsync.backup < /dev/null > /cvs/cds/caltech/scripts/\
backup/rsync.backup.log 2>&1

30 06 * * * find /usr/controls/jobs -mtime +7 -exec /bin/rm -f {} \;

seisBLRMS.m restarted on mafalda.
  6049   Wed Nov 30 02:04:26 2011 rana, den, jenne, kiwamu, jzweizigUpdateCDSFiltering Noise issue tracked down ???

 You can read through all of our past tests to see what didn't work in tracking things down. As Den mentions, there was actually a lot of evidence that there was some double->single precision action in the filter calculation causing the noise we saw.

However, it turns out that this is NOT the case.

This afternoon I was so confused that I enlisted JZ to help us out. He came over and I tried to replicate the error. When looking at the time series, we noticed that it wasn't random noise; the signals seem to be getting clipped as they crossed zero. Sort of like a stiction problem. JZ left to go replicate the error on an offline system.

This turned out to be the important clue. As we examine the code we find this inside of fm10Gen.c:

if((new_hist < 1e-20) && (new_hist > -1e-20)) new_hist = new_hist<0 ? -1e-20: 1e-20;

this is line is basically trapping the filter history at 1e-20, to prevent some kind of numerical underflow problem (?). Seems reasonable, except that some filters which have higher order low passing in them actually have an overall scale factor which can be small (even as small as 1e-23, as Den pointed out).

So the reason we saw such weird behavior is that the first filter in SUSPOS is an AC coupling filter. This takes the OSEM signal and remove the large mean value. Then the next filter multiplies it by 1e-23 before doing the filtering and you end up with this noise in the filter history.

I looked and this line is commented out in the new BiQuad code, but as far as I can tell this issue has been around in aLIGO, eLIGO, iLIGO, etc. for a long time and could have been causing many cases of excess noise whenever we ended up a tiny gain factor in an IIR filter. At the 40m, there are easily a hundred such cases.

For now, I suppose we can just change this number to 1e-40 or so. I don't know how to calculate what the right number should be. Not sure why this underflow is not an issue for the BiQuad, however.

  10723   Mon Nov 17 20:40:29 2014 rana, diegoUpdateIOOInvestigating the IMC WFS situation

We've known for years that the IMC WFS sensing chain is pointlessly bad, but until recently, we haven't thought it was worth it to fix.

There are problems in all parts of the chain:

  1. The WFS Photodetectors oscillate ~200 MHz when turned up to full gain. Diego and I confirmed this today by measuring the RF spectrum of the signals going into the WFS demod boards and seeing the oscillation change (not much) with RF gain. I recommend we switch the heads into the full gain mode (turn all of the attenuators OFF). At the moment we are operating with the 2dB and 8dB attenuators ON.
  2. The demod board has some bad gain allocation and noisy opamps.
  3. The whitening board has too much up/down of gain with noise injection along the way. And the range cannot fill up the ADC.
  10803   Tue Dec 16 01:50:27 2014 rana, diegoFrogsLSCMICH filter is nuts

 This is ridiculous.

How many RGs can I fit into one button???

Attachment 1: badMICHrg.pdf
badMICHrg.pdf
  11905   Mon Jan 4 14:45:41 2016 rana, eq, kojiConfigurationComputer Scripts / Programsnodus pwd change

We changed the password for controls on nodus this afternoon. We also zeroed out the authorized_keys file and then added back in the couple that we want in there for automatic backups / detchar.

Also did the recommended Ubuntu updates on there. Everything seems to be going OK so far. We think nothing on the interferometer side cares about the nodus password.

We also decided to dis-allow personal laptops on the new Martian router (to be installed soon).

  11303   Mon May 18 17:42:14 2015 rana, ericQUpdateGeneralsome status

Today at 5 PM we replaced the east N2 cylinder. The east pressure was 500 and the west cylinder pressure was 1000. Since Steve's elogs say that the consumption can be as high as 800 per day we wanted to be safe.

  1. We closed the black valve before the regulator and closed the valve on the cylinder.
  2. We unscrewed the brass fill line to the cylinder.
  3. We unchained the cylinder and put in the dolly (and attached the chains on there).
  4. We rolled in a fresh cylinder from outside using the red dolly (it should have chains).
  5. We put it in place, hooked up the chains, and screwed on the brass nozzle with the large adjustable wrench (need to put a non-adjustable here).
  6. Opened up the cylinder valve.
  7. Opened up the black valve.
  8. New east pressure reading is 2500 PSI. Regulated N2 pressure is 68 PSI.
Quote:

1) Checked the N2 pressures: the unregulated cylinder pressures are both around 1500 PSI. How long until they get to 1000?

 

  11315   Tue May 19 18:55:12 2015 rana, ericQUpdateGeneralsome status

After one day the pressures are east/west = 2200/450 PSI

Quote:

 

  1. New east pressure reading is 2500 PSI. Regulated N2 pressure is 68 PSI.

 

  10418   Thu Aug 21 02:42:17 2014 rana, ericqConfigurationGreen LockingGain changes on Green Y PDH

[rana, ericq]

We spent time trying to relieve the Yend green PDH of it troubles. 

We realized that the mixer in the PDH setup (mini circuits ZAD-8+), wants 7dBm of LO to properly function. However, we use one function generators output, through a splitter, to give signals to the laser PZT and the mixer LO. 

We don't want 7dBm of power hitting the laser PZT, though. The summing node that adds the servo output to the sideband signal was supposedly designed to do some of this attenuation. Rana measured that 10Vpp out of the function generator resulted in 20mVpp on the fast input to the NPRO, after the summing node. Hence, the 0.09V setting was only resulting in something like 0.2mV hitting the PZT. The PZT has something like 30 rad/V PM response, meaning we only had ~0.006 rad of modulation. 

Now, the function generator is set to 2 Vpp, meaning 4 mVpp hitting the PZT, meaning ~0.12 radians of modulation. The mixer is now getting +7dBm on its LO, and the PDH traces look much cleaner. However, the PDH error signal is now something like 100mVpp, which is much bigger than the PDH board is designed for, so there is now a 10dB attenuator between the reflection PD DC block and the RF input to the mixer. 

Here are screenshots of the Inmon channel (which has a gain of ~20) showing a sweep through some PDH signal, and the error signal while in green lock. Huge 60Hz harmonics are still observed. 

TEK00002.PNGTEK00003.PNG

 


Regarding these 60Hz issues, we need to make sure that we remove all situations where long BNCs are chained together with barrel connectors, or Ts are touching other ones. We also should glue or affix the pomona summing box to the shelf, so that its not just laying on the floor.

The concrete next step is to go fiddle with things, and see if we can get the 60Hz noise to go away, then measure the PDH loop and noises again. Hopefully, this should make the ALS much more reliable. 

  9329   Fri Nov 1 19:09:01 2013 rana, evanConfigurationPSLPMC reflected beam nonsense

 While looking at the PMC REFL beam for the AOM diffracted beam, we noticed that although only one beam exists between the PMC and the first steering mirror, there are two afterwards and they both go to the PMC REFL  RFPD!!! This is madness. We only want one beam on our PDH diode.

The reason that we have two beams is that that first steering mirrors is actually a (W1-PW-1025-UV-1064-45P) non-wedged window with an AR coating on only one side. So two beams come out of it. There is a terrible and floppy and illegal anodized aluminum dump close to this beam which *someone* probably intended to use as a "scraper" to get rid of one of the beams.

Black anodized aluminum is a horrible beam dump material at 1064 - its about as grey as Steve's chair. And its so soft that it scatters light back into the PMC and makes more acoustic noise. And it is mounted so poorly (only one screw) that it can easily be bumped and twist and miss the beam. Punchline: only use anodized aluminum dumps for stray light around cameras or for HeNe for OL. Its NOT allowed anywhere where we care about interferometry of NIR beams.

It was also set to dump the dimmer beam. On Monday, we should order ~5 W1 and get them with a wedge of 1-2 deg. Then we use a black glass dump for the dim beam and orient the bright one to hit the REFL camera and the PMC REFL PD.

For the weekend, I have adjusted the crappy grey aluminum flapper to catch the bright beam so that the PMC REFL image no longer shows the interference fringe of two beams. Lets see how the PMC drifts over the next 3 days.

  12646   Tue Nov 29 17:46:18 2016 rana, gautamFrogsComputer Scripts / Programsgateway PWD change

We found that someone had violated all rules of computer security decency and was storing our nodus password as a plain text file in their bash_profile.

After the flogging we have changed the pwd and put the new one in the usual secret place.

  12911   Mon Mar 27 20:41:21 2017 rana, gautamUpdatePSLPMC DAQ assay for feed-forward integration

We are thinking to use the PMC signals to help us in figuring out the feedback / feedforward stuff and making it better.

Today we scoped out the PMC DAQ channels (which were never re-hooked up after the Joe/Jamie CDS upgrade 6 years ago).

There is a 4-pin LEMO connector on the front panel which gives

  1. the error signal (after the 4th order, post-mixer lowpass and a OP27 buffer with a 17 kHz low pass)
  2. the feedback voltage to the PZT, after a resistive divide by 50

Both of these signals are buffered by the AD620 inst amp configured with a gain of 1. In the green scope trace, you can see that there's a ~110 MHz signal strongly evident there. In the spectrum analyzer screen shot there is a instrument noise trace and then a PMC error point trace. You can see that all the peaks are ony there when I connect to the servo board instead of a Terminator. This RF noise is mainly the higher harmonics of the 35.5 MHz modulation getting there. It seems to be in both the error and control DAQ outputs, and a question is whether or not it is also in the servo electronics.

I also attach a close up of the servo board in the region of the post-mixer LC low pass filtering. I think its supposed to be 4th order cutoff at 1 MHz, but maybe the caps are busted or there's a way for the RF from the mixer to bypass the filters and get into the main servo path?

In the medium term, we probably want to use the new PDH servo that Rich is making. Need to buy/make a HV driver to use, but that should be easy.

Attachment 1: TEK00000.PNG
TEK00000.PNG
Attachment 2: 20170327_194931.jpg
20170327_194931.jpg
Attachment 3: 20170327_204554.jpg
20170327_204554.jpg
  13316   Mon Sep 18 15:00:15 2017 rana, gautamFrogsComputer Scripts / Programsgateway PWD change

We implemented the post-SURF-season nodus password change today.

New password can be found at the usual location.

  15173   Wed Jan 29 03:05:47 2020 rana, gautamUpdateSUSMC misalignments / sat box games

In the last couple days, as the IMC ringdowns have been going on, we have noticed that the MC is behaving bad. Misaligning, drifting, etc.

Gautam told me a horror story about him, Koji, and melted wires inside the sat boxes.

I said, "Its getting too hot in there. So let's take the lids off!"

So then we:

  1. Removed the lid (only 4 screws were still there)
  2. cut off some of the shield - ground wires and insulated them with electrical tape
  3. squished the IDC connectors on tightly
  4. left it this way to see if MC would get better - certainly the painfully hot heatinks inside the box were now just 110 F or so

After some minutes, we saw no drifting. So maybe my theory of "hot heatsink partially shorting a coil current to GND through partially melted ribbon cable" makes sense? IF this seems better after a month, lets de-lid all the optics.

Let's look at some longer trends and be very careful next to MC2 for the next 3 days! I have put a dangerous mousetrap there to catch anyone who walks near the vacuum chamber.

gautam: the grounding situation per my assessment is that the shield of all the IDC cables are connected to a common metal strip at 1X5 - but in my survey, I didn't see any grounding of this strip to a common ground.

Attachment 1: IMG_8366.JPG
IMG_8366.JPG
  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
  9925   Wed May 7 23:09:06 2014 rana, jamieSummaryComputer Scripts / ProgramsOttavia back on network

After Jamie fixed the third party repo issue with Ottavia, he was able to upgrade it to Ubuntu 12.04 Precise Pangolin. But its network stopped working.

I tried to fix its issues by ifconfig and GUI, but what it really wanted was for me to put the network cable back into its eth0 slot. The eth1 network card appears not be working anymore.

All seems fine now. Next I will mount the shared user disk from linux1 and put in a .bashrc.

  553   Mon Jun 23 19:33:01 2008 rana, jenneUpdateIOOMC_F Noise check
We looked at the MC_F spectrum because Rob and Yoichi said that it had gone 'all crazy'. It
seemed fine as we looked at it (even with only one boost stage on) so we looked for things
that might be marginal and make it go nuts.

At the error point (Q mon on the demod board and TEST IN1) of the MC Servo board we saw the
old 3.7 MHz signal (comes from the 33 MHz RFAM getting demodulated by the 29.5 MHz MC LO)
and thought that this might cause some worries. So we installed Jenne's passive elliptic
low pass which has a 3.7 MHz zero.

This wiped out the 3.7 MHz noise but we were not able to re-create the extra frequency noise
so its unlikely to have fixed the main problem. However, we leave it in because its good. If
there is a need to revert it, we have left hanging on the side of the rack the old cable which
was a SMA->TNC making a direct, unfiltered connection between the MC Demod board and the MC
servo board.

More before and after results from Jenne tomorrow, but for now here is a calibrated MC_F spectrum
using the new MC_F-Reference.xml template file.

We also noticed that we could make some small effects on the MCF spec by adjusting the PMC gain so
there's probably more hay to be made there using a lead brick and a gain slider. More in Jenne's
entry.
Attachment 1: mcf.png
mcf.png
  873   Sat Aug 23 09:39:51 2008 rana, jenneUpdatePSLPMC Survey
Jenne, Rana

We scoped out the PMC situation yesterday.

Summary: Not broke. UGF ~ 500 Hz. Needs some electronics work (notches, boosts, LPFs)

Ever since we swapped out the PMC because of the broken PZT of the previous one, the UGF has been
limited to a low value. This is because the notches no longer match the mechanical resonant
frequencies of the body. The old one had a resonance at 31.3 kHz which we were notching using
the LC notch on the board as well as a dangling Pomona box in the HV line to the PZT. The one
has a resonance at ~14.5 kHz which we don't yet have a notch for. Jenne has all the real numbers and
will update this entry with them.

Todo:
  • Implement the 4th order Grote low pass after the mixer.
  • Replace the AD797 with an OP27.
  • Change servo filter to have a boost (need DC gain)
  • Make a 14.5 kHz notch for the bode mode.
  • Put a 20 lb. gold-foil wrapped lead brick on the PMC.

Here's the link about the modified PMC board which we installed at LHO:
LHO PMC elog 2006
  1978   Tue Sep 8 20:15:33 2009 rana, jenneSummaryPSLRC temperature servo: Heater Voltage noise

We measured the voltage noise of the heater used to control the RC can temperature. It is large.

TEK00074.PNG

The above scope trace shows the voltage directly on the monitor outputs of the heater power supply. The steps are from the voltage resolution of the 4116 DAC.

We also measured the voltage noise on the monitor plugs on the front panel. If these are a true representation of the voltage noise which supplies the heater jacket, then we can use it to estimate the temperature fluctuations of the can. Using the spectrum of temperature fluctuations, we can estimate the actual length changes of the reference cavity.

I used the new fax/scanner/toaster that Steve and Bob both love to scan this HP spectrum analyzer image directly to a USB stick! It can automatically make PDF from a piece of paper.

The pink trace is the analyzer noise with a 50 Ohm term. The blue trace is the heater supply with the servo turned off. With the servo on (as in the scope trace above) the noise is much much larger because of the DAC steps.

Attachment 1: 09080901.PDF
09080901.PDF
  9187   Thu Oct 3 00:01:59 2013 rana, jenneHowToLSCsteps to full IFO

In moving now to full IFO locking, there are a number of sub-states to diagnose:

  1. PRMI + 1 arm
  • Measure sensing matrix as arm is scanned into resonance. Compare time series of sensing matrix elements with New LoopTickle simulation. But first, we need more than 1 LOCKIN screen in the LSC! That will allow us to measure all of the elements of front_matrix.jpg simulataneously.
  • Measure 3f PRMI noise spectra as a function of arm position. Look for trouble.
  1. DRMI + 1 arm
  • Same as PRMI above.
  • Want to find why this is unstable sometimes. Make stable for t > 10 minutes.
  • Maybe add some QPD->ASC for SRC angular control, but how? Will this still work after the arms are resonant or will it be swamped by carrier contrast defect? Will Berlusconi ruin all of the Italian gelateria? Only time can tell...
  1. FPMI (non optically recombined) for ALS diagnosis
  2. PRFPMI (iLIGO configuration)
  • this ought to be easier than DRFPMI
  • will let us tell if our ALS is good enough to handle the coupled cavity pole
  1. DRFPMI (aLIGO style)

Which to do first and in what order?

  9188   Thu Oct 3 01:06:48 2013 rana, jenneUpdateSUSoplev XY-plots reflect new calibration

As another proof that sometime is ill with ETMX Optical Lever:

We scanned the ETMX bias in PIT using ezcastep and saw that the OL response is very screwy. In the attached, you can see that the ETMX SUSPIT signal shows that the actual motion is good and linear. In fact, our sus diagonalization is extermely good and there's almost no signal in SUSYAW.

Attachment 1: etmx_ol.png
etmx_ol.png
  9191   Thu Oct 3 02:43:34 2013 rana, jenneSummaryLSCPRMI: comparison of 1f and 3f signals w/ calibration

The attached plot shows the spectra of all the REFL signals with the PRMI SB lock.

We excited the ITMY_LSC with 3000 counts. We used the Masayuki calibration of ITMY (5 nm / count * (1/f^2)) to estimate this peak in the REFL spectra.

To correctly scale the REFL spectra we account for the fact that the DTT BW was "0.187 Hz" and we turn off the "Bin" radio box before measuring the peak height with the cursor.

Since the ITMY motion is 3000 * 5e-9 / (580.1 Hz)^2 = 44.6 pm_peak, we want the DTT spectrum of the REFL spectra to report that too.

i.e. to convert from peak height to meters_peak, we use this formula:

meters_peak = peak_height * sqrt(BW) * sqrt(2)

I *think* that since the line shows up in multiple bins of the PSD, we should probably integrate a ~0.5 Hz band around the peak, but not sure. Need to check calibration by examining the time series, but this is pretty close.

Mystery: why are the REFL_I 3f signals nearly as good in SNR as the 1f signals? The modelling shows that the optical gain should be ~30-100x less. Can it be that our 1f electronics are that bad?

Bonus: notice how we have cleverly used the comb of bounce frequencies around the calibration line to determine that REFL11 is clipping!

Attachment 1: REFL_signals_CalLinesLinedUp.pdf
REFL_signals_CalLinesLinedUp.pdf
  9668   Tue Feb 25 00:00:01 2014 rana, jenneUpdateLSCreasons that the REFL signals may be degenerate now

We're exploring some effects which may give some funny macroscopic detuning and cause a near phase degeneracy in the REFL RF signals (see radar plot from Jenne below).

1) Alignment: we centered the oplevs to reduce fluctuations and then tweaked the BS and PRM alignment to build up the power. No significant change in the RF phases of the DOFs.

2) Measuring RAM: we set the dark offsets (by hand since the Masayuki script doesn't really work well anymore) to with 1 counts. We then locked the MC, misaligned the ITMs, and looked at the REFLOUT16 channels using the following command line:

z avg 12 C1:LSC-REFL11_I_OUT16 C1:LSC-REFL11_Q_OUT16 C1:LSC-REFL33_I_OUT16 C1:LSC-REFL33_Q_OUT16 C1:LSC-REFL55_I_OUT16 C1:LSC-REFL55_Q_OUT16 C1:LSC-REFL165_I_OUT16 C1:LSC-REFL165_Q_OUT16
C1:LSC-REFL11_I_OUT16     -12.04
C1:LSC-REFL11_Q_OUT16     -14.34
C1:LSC-REFL33_I_OUT16       0.43
C1:LSC-REFL33_Q_OUT16      -0.28
C1:LSC-REFL55_I_OUT16       2.84
C1:LSC-REFL55_Q_OUT16       5.64
C1:LSC-REFL165_I_OUT16      4.40
C1:LSC-REFL165_Q_OUT16      0.10

So these offsets are small in counts. In meters this corresponds to....less than 3 pm for any of the I signals.

Refl11I = 2.06e-12 meters

Refl11Q = 2.94e-10 meters

Refl33I = 5.28e-13 meters

Refl33Q = 1.07e-11 meters

Refl55I = 2.71e-12 meters

Refl55Q = 3.55e-11 meters

Refl165I = 3.07e-13 meters

Refl165Q = 8.63e-14 meters

 

 

3) Next we want to put large offsets into the error points of the loops

4) Change modulation depth

5) Check IMC length (todo for Q/Manasa for Tuesday - Wednesday)

  9669   Tue Feb 25 02:46:38 2014 rana, jenneUpdateLSCChanging PRCL offset changes REFL 165 degeneracy

[Jenne, Rana]

We put offsets in the PRCL and MICH loops, and measured sensing matrices for each condition. 

What we found was that PRCL offsets of order 1/20th a linewidth (calibration to be checked tomorrow) would give significant changes in the angles of the REFL signal sensing matrix elements.  We broke MICH lock before we were able to put in a significant enough offset to see the demod phases change.

Because there are so many plots, I've put them together in a pdf. Each page has a set of radar plots for sensing matrix elements.  On the bottom of each page I note what our MICH and PRCL offset values were, and where the data is saved (in the 40m scripts directory). To see the differences, make sure your pdf viewer is set to single-page, not scrolling.

PRC_offsetCheck_24Feb2014.pdf

One major thing that we noted was that putting in a PRCL offset also changed the MICH offset.  When we increased the PRCL offset, we saw the AS port get brighter (but not as bright as when we were putting in large MICH offsets). 

Tomorrow, I need to check the calibrations we were using, to see how many meters we were moving the optics.  Also, Q, Gabriele and I need to meditate and do some modelling to figure out why the length offset could be affecting the degeneracy so strongly. 

  9675   Tue Feb 25 23:38:05 2014 rana, jenneUpdatePEMGUR1 Z channel excess noise: oscillating Z channel

Last night we noticed an excess in the GUR1Z seis BLRMS on the StripTool. It was in the 0.1 - 0.3 Hz band. The rumor in the control room was that "this kind of noise has been showing up at night recently".

AS it turns out, this was not some environmental noise around the 40m at night, but instead its some internal servo oscillation in the GUR1 Z channel. In the Guralp seismometers, each channel is a different mechanical sensor (unlike the STS or T240), so when a single channel gets noisy it doesn't always implicate the others.

My guess is that the oscillation came from the Z channel needing to be recentered. I power cycled the interface box just now. The oscillation had already gone away, but I thought this might reduce the excess noise. Maybe it did, but the effect is tiny. You can see in the oscillation reference that the low frequency noise is high, but in the new trace its still kind of high. Needs to be re-centered correctly with the paddle. Or add a centering button to the interface box.

Attachment 1: gur1z.pdf
gur1z.pdf
  9920   Wed May 7 04:01:44 2014 rana, jenneUpdateLSCPRFPMI: Common Mode servo using REFL_DC ON, CARM offset still non-zero
  1. With REFL_DC coupled into the CM board through an SR560 (with an offset subtractor), we were able to transition to use it as the CARM error signal.
  2. We reduced the CARM offset until the arm powers went up to ~13.
  3. We had the AO path turned on and the MCL/AO crossover was ~150 Hz.
  4. We saw the double cavity pole come in from HF down to ~1-2 kHz. The lock stayed stable like this.
  5. We've set the IMC overall gain higher by +4dB in the mcup script. That's -4 dB from Eric's max gain earlier today.
  6. We have some scripts now for this scripts/PRFPMI/ :   camr_cm_down.sh and carm_cm_up.sh
  7. The sequence was ALS -> SqrtInv while digital with CARM -> MC2. Then we digital transition to REFL_DC using the CM board switch to put REFL_DC into the REFL11_I socket.
  8. REFL_DC is noisy, so we upped the SR560 gain by 10 and compensated.

Also, we found the PRM OL off and turned it back on. The ETMY was swinging a lot after lock loss, so we set its SUSPOS damping gain to match the ETMX and it stopped swinging so much.

Next up: more of the same, make this sequence more stable, turn on CARM OSC and watch the LOCKI outputs while we slowly ramp between signals.

Also, what should be the sign of the CARM offset ???

  10396   Thu Aug 14 22:58:59 2014 rana, jenneSummaryGreen LockingALS DIFF tuning

 We've been having trouble tuning the ALS DIFF matrix. Trying to see if the MC2 EXC can be cancelled in ALS DARM by adjusting the relative gains in ALSX and ALSY Phase Tracker outputs.

There's a bunch of intermittent behavior. Between different ALS locks, we get more or less cancellation. We were checking this by driving MC2 at ~100-400 Hz and checking the ALS response (with the ALS loops closed). We noticed that the X and Y readbacks were different by ~5-10 degrees and that we could not cancel this MC2 signal in DARM by more than a factor of 4-5 or so. In the middle of this, we had one lock loss and it came back up with 100x cancellation?

Attached is a PDF showing a swept sine measurement of the ALSX, ALSY, and DARM signals. You can see that there is some phase shift between the two repsonses leading to imperfect cancellation. Any ideas? Whitening filters? HOM resonance? Alignment?

Attachment 1: sweep.pdf
sweep.pdf sweep.pdf
  10708   Thu Nov 13 01:03:28 2014 rana, jenneUpdateSUSOL updates on ITMs and ETMs

 We copied the new SRM filters over onto the OL banks for the ITMs and ETMs. We then adjusted the gain to be 3x lower than the gain at which it has a high frequency oscillation. This is the same recipe used for the SRM OL tuning.

Before this tune up, we also set the damping gains of the 4 arm cavity mirrors to give step response Q's of ~5 for all DOF and ~7-10 for SIDE.

  10807   Wed Dec 17 01:51:44 2014 rana, jenneUpdateASCASS retuned

Did a big reconfig to make the Y-arm work again since it was bad again.

  1. Undid Koji's topology change. The A2L loops now feedback to the arm mirrors to adjust the cavity axis. The cavity transmission signals now feedback to the input beam.
  2. The UGF of the Trans->Input beam servos is ~5-10x higher than the A2L servos.
  3. The Trans loops have a ~10-15 s settling time.
  4. The Input Matrix has been adjusted to fit with our intuition:The ETM tilt moves the beam equally on the ITM and ETM faces.
  5. The Output Matrix has also been adjusted to do like this: we're using an intuitive matrix inverse rather than one based on measurement. It turns out to be a reasonable guess and we can tune this later.
  6. Seems stable with many kinds of steps and misalignments. Seems not reliable if the arm power is less than ~0.5.
  7. Reducing the dither amplitudes to make the power fluctuation less than 5% made it much more stable.

With the arm aligned and the A2L signals all zeroed, we centered the beam on QPDY (after freezing the ASS outputs). I saw the beam going to the QPD on an IR card, along with a host of green spots. Seems bad to have green beams hitting the QPD alogn with the IR, so we are asking Steve to buy a bunch of the broad, dielectric, bandpass filters from Thorlabs (FL1064-10), so that we can also be immune to the EXIT sign. I wonder if its legal to make a baffle to block it on the bottom side?

P.S. Why is the Transmon QPD software different from the OL stuff? We should take the Kissel OL package and put it in place of our old OL junk as well as the Transmons.

Attachment 1: ASSconfig_141217_0205.png
ASSconfig_141217_0205.png
  11041   Tue Feb 17 00:24:47 2015 rana, jenneUpdateLSCALS Fool filter updated for more cancellation

Today we measured the TFs again and then updated the filter in the POY -> ALS FF path so as to get 10x better cancellation.

The cancellation went from ~10 dB to ~30 dB. This seems good enough. The new filter 'Comp1' is just constructed by eye. We then had to tune the filter module gain to a few %. Seems good enough for now, but we should really try to understand what it is and why it is the way that it is. In the above plot, the ORANGE trace is the old cancellation and the GREEN one is the new one. The filter TF is attached below - its not special, we made it by presing buttons in FOTON until the TF matched the measured TF of ALSY/LSC-MC_CTRL_FF_OUT.

Attachment 1: ALSfoo_150216.png
ALSfoo_150216.png
Attachment 2: 15.png
15.png
  2434   Sun Dec 20 21:39:40 2009 rana, jenne, kiwamuUpdateASSOAF Model update and build instructions

After a lot of headache, I got the OAF working again - read on for details.....................

Sometime last week, Jenne, Kiwamu, and I tried to update the OAF model to include the IIR "feed-around" path.

This path is in parallel to the existing FIR-based adaptive FXLMS stuff that Matt put in earlier. The reason for the

new path is that we want to try emulating the same FF technology which has been successful lately at LLO.

 

However, we were unable to make the ASS work after this work. Mostly, the build stuff worked fine, but we couldn't get DTT

to make a transfer function. The excitation channels could be selected and the excitation would actually start and get all the

way into MC1, but DTT would just hang on the first swep-sine measurement with no time-out error. Clearly our ASS building

documentation is no good. We tried using the instructions that Koji gave us for AAA, but that didn't completely work.

 

In particular, the 'make-uninstall-daq-ass' command gave this command:

[controls@c1ass advLigo]$ make uninstall-daq-ass
grep: target/assepics/assepics*.cmd: No such file or directory
Please make ass first
make: *** [uninstall-daq-ass] Error 1

re-arranging the order to do 'make-ass' first fixes this issue and so I have fixed this in the OAF Wiki.

 


The there's the whole issue with the tpchn_C3.par file. This contains all the test point definitions for the ASS/OAF machine. The main

IFO numbers are all in tpchn_C1.par and the OMC is all in tpchn_C2.par. When we do the usual build, in the 'make install-daq-ass' part:

[controls@c1ass advLigo]$ make install-daq-ass
Installing GDS node 3 configuration file
/cvs/cds/caltech/target/gds/param/tpchn_C3.par
Updating DAQ configuration file
/cvs/cds/caltech/chans/daq/C1ASS.ini

we get this .par file installed in the target area. The ACTUAL param file seems to actually be in /cvs/cds/caltech/gds/param  !!

 


Of course, it still doesn't work. That's because the standard build likes to point to /cvs/cds/caltech/gds/bin/awgtpman and the one that runs on

linux is actually /opt/gds/awgtpman. So I've now made a file called startup_ass.cmd.good which runs the correct one. However, the default build

will try to start the wrong one and we have to fix the 'startass' script to point to the correct one on each build. Running the correct awgtpman

allows us to get the TP data using tools like tdsdata, so far no luck with DTT.\

 


UPDATE (23:33): It turns out that it was my old nemesis, NTPD. c1ass had a /etc/ntp.conf file that was pointing at an ntp server called rana113. I

am not an NTP server; I don't even know what time it is. I have fixed the ntp.conf file by making it the same ass c1omc (it now points to nodus). After

this I set the date and time manually (sudo date -s "20 DEC 2009 23:27:45") and then restarted NTPD. It should now be fine even when

we reboot c1ass.

 

After all of this nonsense, I am able to get TP data from c1ass and take transfer functions between it and the rest of the world !

  2437   Mon Dec 21 02:22:31 2009 rana, jenne, kiwamuUpdateASSOAF Model update and build instructions

This allowed measuring the MC1 -> MCL TF finally. Its mostly flat. Data saved as Templates/OAF/OAF-MCLTF.xml

Attachment 1: Untitled.png
Untitled.png
  2836   Fri Apr 23 21:02:14 2010 rana, joeUpdateLSCStarted dev of LSC FE

Joe and I started working on the new LSC FE control today. We made a diagram of the system in Simulink, but were unable to compile it.

Joe checked out the latest CDS software out of their new SVN and put it somewhere (perhaps his home directory).

We then copied the directory with the .mdl files and the CDS parts library into our real Simulink Model Directory:

/cvs/cds/caltech/cds/advLigo/src/epics/simLink

Use this and not someplace in Alex or Rob's home directory !

Joe will put in more details on Monday once he figures out how to build the new stuff. Basically, we decided not to support multiple versions of the CDS real time code here. We'll just stay synced to the latest stable ~versions.

I exported the current version of the LSC FE into our public_html/FE/ area on nodus where we will put all of the self-documenting FE diagrams:

https://nodus.ligo.caltech.edu:30889/FE/lsc_slwebview_files/index.html

To make a web setup like this, you just use the "Export to Web" feature from the top-level Simulink diagram (e.g. lsc.mdl). Choose the following options:

Untitled.png

Note: in order to get the web page to work, I had to change the apache httpd.conf file to allow AddType file overriding. Here's the term cap of the diff:

nodus:etc>diff httpd.conf httpd.conf~
155c155
< ServerAdmin jenne@caltech.edu
---
> ServerAdmin aso@caltech.edu
225d224
<     AllowOverride FileInfo

  4232   Mon Jan 31 12:40:38 2011 rana, joeUpdateGreen LockingDFD - medm screen

This is a plot showing the old filters and the new ones we added this morning.

The new ones have a Cheby for AC coupling below 10 Hz and then a 500 Hz LP after the mixer. The LP frequency has been increased so that we can use this signal in a feedback loop to the ETM with a ~100 Hz UGF.

Attachment 1: a.pdf
a.pdf
  3603   Thu Sep 23 23:24:43 2010 rana, johnny, taraSummaryPSLAM modulate AOM to measure RefCav Thermo-Optic coefficient

Big Johnny and I hacked a function generator output into the cross-connect of the 80 MHz VCO driver so that we could modulate the

amplitude of the light going into the RefCav. The goal of this is to measure the coefficient between cavity power fluctuations and the

apparent length fluctuations. This is to see if the thermo-optic noise in coatings behaves like we expect.

 

To do this we disconnected the wire #2 (white wire) at the cross-connect for the 9-pin D-sub which powers the VCO driver. This is

called VCOMODLEVEL (on the schematic and the screen). In the box, this modulates the gain in the homemade high power Amp which

sends the actual VCO signal to the AOM.

 

This signal is filtered inside the box by 2 poles at 34 Hz. I injected a sine wave of 3 Vpp into this input. The mean value was 4.6 V. The

RCTRANSPD = 0.83 Vdc. We measure a a peak there of 1.5 mVrms. To measure the frequency peak we look in

the FSS_FAST signal from the VME interface card. With a 10 mHz linewidth, there's no peak in the data above the background. This signal

is basically a direct measure of the signal going to the NPRO PZT, so the calibration is 1.1 MHz/V.

 

We expect a coefficient of ~20 Hz/uW (input power fluctuations). We have ~1 mW into the RC, so we might expect a ~20 Hz frequency shift.

That would be a peak-height of 20 uV. In fact, we get an upper limit of 10 uV.


 Later, with more averaging, we get an upper limit of 1e-3 V/V which translates to 1e-3 * 1.1 MHz / 1 mW ~ 1 Hz/uW. This is substantially lower

than the numbers in most of the frequency stabilization papers. Perhaps, this cavity has a very low absorption?

  930   Thu Sep 4 18:02:34 2008 rana, josephbConfigurationPEMAccelerometer gains increased by 10
We increased the Accelerometer gains by 10 by modifying the C1ADCU_PEM.ini file.
[C1:PEM-ACC_MC1_X]
chnnum=15014
gain = 10

etc.
The plot shows the before and after for one channel. The ADC noise floor is ~10^-2 counts/rHz in this plot so now
we can do much better noise subtraction.
Attachment 1: acc.png
acc.png
  882   Mon Aug 25 17:45:34 2008 rana, josephb, robHowToPEMAccelerometer range
Joe shows us by jumping up ~15" in the control rom that the accelerometers are set with not enough gain.

Since this is taken around 5:30 in the evening, so we can take the nearby time series to represent what a
high noise level is. I recommend we up the gain using the ICS-110B .ini file.
Attachment 1: Screenshot-4.png
Screenshot-4.png
  894   Thu Aug 28 19:02:25 2008 rana, josephb, robSummaryComputersbig boot
This afternoon Joe did something with an .ini file (look for his detailed elog entry) and the computers went bad.
RFM network screen not active - filter modules not working.

We went around and booted every machine as has been done before. The correct order for a memory corruption
fixing big boot is the following:

    [1] RESET the RFM switches near the FB racks.
    [2] Power cycle c1dcuepics.
    [3] Power cycle all other crates with real time CPUs:
    c1iscey, daqctrl, daqawg, c1susvme1, c1susvme2, c1sosvme, c1iovme, c1lsc, c1asc, & c1iscex
    [4] Start up all FEs as described in Wiki.
    [5] Burt restore everyone (losepics, iscepics, assepics, omcepics?)
  6034   Tue Nov 29 07:45:56 2011 rana, joshSummaryComputer Scripts / Programs40m Daily News web pages

 As part of the initiative to get a good daily summary page for aLIGO commissioning, Josh is spearheading his Detector Characterization group to produce such web pages for the 40m.

They're starting out with this launching point and then we can add all kinds of other information and plots as we want (e.g. Vac, PEM, Weather, coffee status). If you have suggestions/ideas, just edit this entry and add them, or email Josh directly.

  3014   Sun May 30 13:26:07 2010 rana, kiwamuUpdatePSLnew HIGH-LOW value for PMC_TRANS

We changed the HIGH/LOW values of the PMC_TRANS.

The edited file was updated on the svn.


Since the PMC_TRANSPD was replaced behind the pzt mirror (see the entry), its nominal value were reduced to something like ~1V from the previous value of ~2V.

In the medm screen C1PSL_PMC.adl the PMC_TRAN always indicated red because the value were low compared with the previous one.

We went to /cvs/cds/caltech/target/c1psl, then edited psl.db

- Here are the new parameters we set up in the file.

grecord(ai,"C1:PSL-PMC_PMCTRANSPD")
{

  field(LOW,"0.98")
  field(LOLO,"0.93")
  field(HIGH,"1.15")
  field(HIHI,"1.3")

}

- - - -

These values are based on ~4days trend of the PMC_TRAN.

Then we manually updated those numbers by using ezcawrite in order not to reboot C1PSL.

So now it nicely indicates green in the medm screen.

  2442   Tue Dec 22 02:50:09 2009 rana, kiwamu, jenneUpdateASSOAF Feedaround ON and doing something good

Kiwamu made the OAF screen functional today - screenshot attached.

After this, I used the measured TF of the MC1 to MCL to filter the signals from the Wilcoxon accelerometers and feed them into the MC.

The noise at 3 Hz went down by a factor of ~3. There's a little excess created at 100 Hz. Its good to see that our intuition about feed-forward is OK.

I did all of the filter calculations by adapting the scripts that Haixing, Valera, and I got going at LLO. They're all in the mDV/extra/C1 SVN.

 

The Wiener code predicts much better performance from using more than just 2 horizontal accelerometers, but I was too lazy to do more channels today.

I also added the Rai box to the Ranger readout today - the noise at 0.1 Hz went down by a factor of 10 and the noise at 1 Hz is close to 10^-11 m/rHz.

Attachment 1: oaf.png
oaf.png
Attachment 2: oaf.png
oaf.png
  4331   Sun Feb 20 21:22:33 2011 rana, kiwamu, valeraConfigurationIOOMC Servo Change

For some reason, Kiwamu forced us to change the MC servo electronics today. We are now combining it with the FSS box.

The MC Servo by itself was locking by just driving the NPRO PZT. Becuase of the ~30 kHz mechanical resonances of that system, our badnwidth is limited. To get higher bandwidth, we can either use a wideband frequency shifter like the AOM or just use the ole FSS combo of PZT/EOM. The old MC servo was able to get 100 kHz because it used the AOM.

So we decided to try going through the FSS box. The MC servo board's FAST output now goes into the IN1 port (500 Ohm input impedance) of the TTFSS box. This allows us to use the FSS as a kind of crossover network driving the PZT/EOM combo.

At first it didn't work because of the 5V offset that Jenne, Larisa, Koji, and Suresh put into there, so I cut the wire on the board that connected the power to the summing resistor and re-installed the MC Servo board.

We also removed the old Jenne-SURF 3.7 MHz LP between the MC mixer and servo. Also removed the Kevin-box (1.6:40) stuck onto the NPRO PZT.

We have yet to measure the UGF, but it seems OK. The PCDRIVE is too high (~5-6V) so there is still some high frequency oscillation. Needs some investigation.

* To get the FSS SLOW servo to work (change NPRO temperature to minimize PZT drive onto NPRO) I set the setpoint to 5V in the script so that we operate the FSS box output at 5V mean. I set the threshold channel to point to MC_TRANS_SUM instead of RC_TRANSPD. I also had to fix the crontab on op340m so that it would point to the right scripto_cron script which runs the FSSSlowServo, RCThermalPID.pl, etc. I also had to fix scripto_cron itself since it had the old path definitions and was not loading up the EpicsTools.pm library.

** Also, I was flabbergasted by the dog clamping on the last turning mirror into the MC. Barely touching the mount changes the alignment.

  3556   Fri Sep 10 02:35:30 2010 rana, kiwamu, valera, taraConfigurationPSLupdate

Over the last couple nights we got the beam into the FSS path and all the way to the IMC and out onto the AP table.

Tara and Valera have calculated a mode-matching solution for the reference cavity. It utilizes only a single lens between the AOM and the reference cavity. Valera and Steve will move the reference cavity into place in the morning.

We noticed that the layout was too tight on the end going into the MC and so we adjusted the angle of the final zig-zag. This will put the final mode-matching lens in between the final steering mirrors (which is generally undesirable) but the lens in this case is only f=400 mm. In addition, this lens may provide some more decoupling between the steering mirrors.

The whole layout has to be a little adjusted because of a calculation mistake I made in the mode-matching. I used only the nominal focal lengths from the CVI catalog and not the effective one. For the UV-grade fused silica lenses, the effective focal length is actually 20-30% longer. Today we measured that the "f=200 mm" lens we got is actually f = 238 mm. The BK7 lenses are much closer to the nominal.

We also replaced the Klinger mount ahead of the PMC with a Polanski style so that we could get the PMC REFL beam out without hitting the mount. Valera will continue to refine this section on the weekend.

Tomorrow, we will lock the MC using feedback only to the NPRO. The 0-150 V piezo driver is on the PSL table ready for action.

I also got a LCD video monitor from Frank and hooked it up on the PSL table. If we like this kind of thing, we can get many of them. They are pretty cheap. It would be handy to have 3-4 of them on the PSL and one on every of the ISC tables. They take the standard video for input and need +12V for power. Right now the one in there is looking at the PMC transmission.

The Omnigraffle layout as of tonight is attached.

Attachment 1: 40mPSL.pdf
40mPSL.pdf
  1451   Wed Apr 1 23:18:07 2009 rana, kojiSummaryIOONo Reference Cavity Required
Koji sent us a note about our "No Reference Cavity Required" entry. I thought that it nicely summarizes the
whole shebang and so I post it here for its pedagogical value.

Generally, frequency stabilization is a comparison of the two
frequency references.

1. In the conventional case you are comparing the NPRO stability with
the RC stability. The NPRO cavity is short and probably placed in a
less stable environment than that of the RC. Therefore, the PDH
signal only feels the frequency fluctuation of the NPRO, resulting
in the laser PZT fast feedback dominated by the NPRO stability. As
the MC length at low frequency is controlled by the mass feedback,
the resulting laser stability through the MC is virtually limited
by the RC stability.

2. On the other hand, you are comparing the stabilities of the NPRO
crystal and the MC cavity in the direct control configuration. The
stability of the MC at high frequency is better than that of the
NPRO. It is opposite at low frequency, of course, because of the
pendulum motion. The resulting laser stability through the MC is
limited by the MC stability.

3. In the CM servo, the length of the MC is stabilized such that the
arm stability is duplicated to the MC. As a result, your MC servo
compares the stability between the NPRO and the arm cavity. Again
at around 1Hz, the arm cavity is noisier than the NPRO. (This is
true at least TAMA case. I am quite unsure about it in the LIGO
long arm cases.)

One useful consequence is that in those configurations, the laser PZT
feedback at around 1Hz represents the stability of the NPRO, the MC,
and (possibly) the arm cavity, respectively. It was clearly seen
Yoichi's e-log entry 1432. At TAMA we call this signal as "MCPZTfb"
and use this for the diagnostic purposes of the suspended cavities. As
the laser fast PZT is rarely replaced and considered as a stable
actuator, this signal is considered as a good reference at low
frequency which is consistent across various configurations
(e.g. before/after replacement of the suspensions etc). Once the
response and the coefficient are calibrated you can easily convert
this signal to the length displacement.

Another remark: In the direct configuration, the frequency stability
of the beam goes through the MC is determined by the MC stablity. It
means that the beam to the arm has essentially worse stability than
the arm stability by factor of L_arm/L_MC. In the 40m case this factor
is just 3 or so. This is ok. However, for the LIGO 4km arm, the factor
becomes something like 300. This means that if you have 1um_rms of the
MC length fluctuation, the arm PDH feels 300um_rms. (Maybe some extent
less because of the common mode rejection of the MC suspensions.)

Yes, the actuator to the MC length is very strong this time, and
should be able to stop this amount of fluctuation easily... if the
things are all linear. I am not certain whether you can acquire the
lock even by this strong actuator when the arm is crazily swinging,
the PDH signals are ringing all the way, etc, etc...Particularly in
the recycling case!

One possible remedy is a technique developed by the German
necromancers, as always. They used the NPRO cavity as a reference
cavity. They actuate the MC length at low frequency. But I don't know
the exact configuration and how they accomplished the CM hand-off. We
have to ask Hartmut.

The other possibility is your adaptive stabilization of the MC by the
FIR technique. So far I don't know how much stability you can improve
in the LIGO 4km case.

There would be many possibilities like feedforward injection from the
green arm locking signal to the MC length, etc, etc.
  1731   Fri Jul 10 19:56:23 2009 rana, kojiOmnistructureEnvironmentChanged office temp

I have increased the temperature setpoint in the office area by ~0.75 deg F. Figure attached. Also a few days ago I increased the setpoint of the AC in the control room. Looks like the Laser is able to handle the changes in office area temperature so far, but lets see how it fares over the weekend.

Attachment 1: therm.JPG
therm.JPG
  2242   Wed Nov 11 18:43:57 2009 rana, kojiHowToPhotosIlluminated Paintbrush Technique

IMG_0215.JPGIMG_0214.JPG

1/4" exposure, standard room lights                                                                              3" exposure, slowly moving LED bar light from ~60 cm distance

Note:
Because of the light behind, the focus was attracted by the far objects...
Evenso the magnet ball looks better in the right picture.

The technique is as follows:
Use longer exposure time, move the LED bar illumination through the area like painting the light everywhere.
It is supposed to provide a picture with more uniform light and the diminished shadow.

(KA)

ELOG V3.1.3-