40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 328 of 344  Not logged in ELOG logo
ID Date Author Type Category Subject
  851   Tue Aug 19 13:12:55 2008 JenneUpdateSUSDiagonalized PRM Input Matrix
NOTE: Use the values in elog #860 instead (20Aug2008)

Using the method described in LIGO-T040054-03-R (Shihori's "Diagonalization of the Input Matrix of the Suspension System"), I have diagonalized the input matrices for the PRM.

Notes about the method in the document:
  • Must define the peak-to-peak voltage (measured via DataViewer) to be NEGATIVE for PitLR, PitLL, YawUR, YawLR, and POSITIVE for all others
  • As Osamu noted in his 3 Aug 2005 elog entry, all of the negative signs in equations 4-9 should all be plus.

New PRM Input Matrices:

POSPITYAW
UL1.0001.0001.000
UR1.18771.0075 -1.0135
LR0.8439 -0.9425 -0.9653
LL0.9684 -1.05001.0216
  850   Tue Aug 19 10:36:34 2008 SharonUpdate Calibrating accelerometers
I took apart the accelerometers near MC1 and MC2.
The 2 sets of 3 accelerometers are now covered by a box on the floor. Please try not to move them... I will place it all back once I am done calibrating.
  849   Mon Aug 18 22:47:12 2008 YoichiUpdateIOOMC unlock study
As rob noted, the MC keeps unlocking in a few minutes period.
I plotted time series of several signals before unlocks.
It looks like the MC alignment goes wrong a few hundred msec before the unlock (the attached plot is only one example, but all unlocks
I've looked so far show the same behavior).
I will look for the cause of this tomorrow.

The horizontal axis of the plot is sec. The data values are scaled and offset-removed appropriately so that all curves are shown
in a single plot. Therefore, the vertical axis is in arbitrary units.
Attachment 1: MC-Unlock.png
MC-Unlock.png
  848   Mon Aug 18 17:37:14 2008 robUpdateLockingrecovery progress

I removed the beam block after the PSL periscope and opened the PSL shutter.

There was no MC Refl beam on the camera, so I decided to trust the PSL launch
and aligned the MC to the PSL beam. Here are the old and new values for
the MC angle biases:
 __Epics_Channel_Name______   __OLD_____    ___New___
 C1:SUS-MC1_PIT_COMM          4.490900        3.246900 
 C1:SUS-MC1_YAW_COMM          0.105500	      -0.912500
 C1:SUS-MC2_PIT_COMM          3.809700	      3.658600 
 C1:SUS-MC2_YAW_COMM          -1.837100	      -1.217100
 C1:SUS-MC3_PIT_COMM          -0.614200	      -0.812200
 C1:SUS-MC3_YAW_COMM          -3.696800	      -3.303800

After this, the beam looks a *little low* going into the Faraday Isolator.
Nonetheless, after turning on the IFO input steering PZTs, I was able to
quickly steer the PRM get a beam on the REFL camera and into the REFL OSA.
The PRM optical lever beam is also striking the quad.

I then used the ETMX optical lever as a reference for realigning. After
steering around the input PZTs and ITMX, I saw some flashes in Xarm trans, then got
it locked and ran the alignment script ~5 times. The arm power went
up to 0.9, so I tweaked the MC1 to put the MC refl beam back on MCWFS.
The XARM power then went up to .96. Good enough for now.

Then I started to try and re-align the YARM. Since the oplevs for both ITMY
and the BS are untrustworthy, I first tried to get the beam bouncing off ITMX
and the BS back into the AS OSA, to try and recover some BS alignment. This
didn't work, as the AS OSA may not be a good reference anyways. After
wandering around in the dark for a little while, I decided to try an automated
scan of the alignment space. I used the trianglewave script to scan
the angle biases of BS, ITMY, & ETMY, then looked at the trend of the transmitted
power to find the gps time when there were flashes. I then used
time_machine_conlog to restore the biases to that time. This was close
enough to easily recover the alignment. After several rounds of aligning &
centering oplevs, things look good.

Also locked a PRM. Will work on the DRM tomorrow.

I'm leaving the optics in their "aligned" states over night, so they can
start their "training."

Note: The MC is not staying locked. Needs investigation.

For tomorrow:

lock up the DRM
fix the mode cleaner
re-align mode cleaner to optimize beam through Faraday
re-align all optics again (will be much easier than today)
re-align beam onto all PDs after good alignment of suspended optics is established.
Attachment 1: flatlissa.png
flatlissa.png
  847   Mon Aug 18 15:32:18 2008 josephbConfigurationCamerasHow to multicast with gstreamer and Gige Cameras
In order to get multicasting to work, one simply needs to understand the address scheme.

In general, the address range 224.0.0.0 - 239.255.255.255 are reserved for multicasting. Within in this address space, there are some base level operations in the 224.0.0.x range which shouldn't be interfered with.

For a single site, the address range between 239.252.0.0 and 239.255.255.255 is probably best.

Gstreamer and the current 40m network hubs are designed to handle this kind of communication already, so one merely needs to point them at the correct addresses.

While in /cvs/cds/caltech/target/Prosilica/40mCode/SnapCode type:

CamServe -F 'Mono8' -c 44058 -E 20000 -X 0 -Y 0 -H 480 -W 752 -l 0 -m 300 | gst-launch-0.10 fdsrc fd=0 blocksize=360960 ! video/x-raw-gray, height=480, width=752, bpp=8,depth=8,framerate=60/1 ! ffmpegcolorspace ! queue ! smokeenc keyframe=8 qmax=40 ! udpsink host=239.255.1.1 port=5000

This will multicast to the 239.255.1.1 address, using port 5000.

On the machine you wish to subscribe type:

gst-launch udpsrc multicast-group=239.255.1.1 port=5000 ! smokedec ! ffmpegcolorspace ! ximagesink sync=false
  846   Mon Aug 18 11:50:29 2008 YoichiUpdateSUSIn vacuum free swinging results
The first attachment is the results of the free swinging spectra measurement performed in vacuum this morning.
They are freely swinging, but the suspensions in the BS chamber got even more extra peaks.
Especially, the SRM spectrum looks like a forest.
If those extra peaks are inter-modulations of the primary suspension modes, the heights of them should be
enhanced (compared to the in-the-air case) by the increased quality factors of the primary modes (due to the less air friction).
This might explain the observed increase in the extra peaks.

While doing the free swinging, we had two big spikes in the OSEM signals of the ETMs and only in ETMs.
Those spikes screwed up the spectra of the ETMs. So the ETM spectra were calculated using the time series
after the spikes.
The second attachment shows one of those spikes. It looks like a computer glitch.
Attachment 1: 2008-8-18.pdf
2008-8-18.pdf 2008-8-18.pdf 2008-8-18.pdf 2008-8-18.pdf 2008-8-18.pdf 2008-8-18.pdf 2008-8-18.pdf 2008-8-18.pdf
Attachment 2: spike.pdf
spike.pdf
  845   Mon Aug 18 09:19:55 2008 steveSummaryVAC11 days at atm
It took 11 days to fix earth quake triggered sus problems of ITMX, SRM and PRM
Only ITMX north and BSC north vac doors were removed.

The PRM sus had to be removed form the vac envelope for "hip replacement"-new wire stand off was
epoxied in place.
Note: the PRM has no guide rod on the other side

ITMX, SRM and BS osems were optimized in place.
No crosscoupling optimization was performed.
Beam block was removed from ITMXC, it was too close to the main beam.

POX pick off mirror and mount will be replaced next vent.

Vac viewports were inspected from the inside.
Attachment 1: ventprm.jpg
ventprm.jpg
  844   Mon Aug 18 08:07:10 2008 YoichiConfigurationSUSSuspension free swinging
I've started a free swinging measurement of OSEM spectra now. Please leave the watchdogs untouched.
  843   Fri Aug 15 19:32:49 2008 steveConfigurationVACpumpdown complete
I have just reached vacuum normal. The maglev peaked at 49.8C body temp with aux fan on at 3.2 Torr
cc1 1e-4Torr

note: pumpdown was put on hold for Koji's goodby lunch
Attachment 1: pdprm.jpg
pdprm.jpg
  842   Fri Aug 15 17:38:41 2008 YoichiUpdateSUSOSEM free swinging spectra before the pump down
I ran an overnight measurement of the free swinging OSEM spectra.
The attm1 shows the results. Everything look ok except for the ITMY UL OSEM.
The time series from that OSEM was very noisy and had many spikes.
We suspected the cable from the satellite box to the computer rack because we disconnected the cable
when we tested a spare cable which was used to connect the spare OSEMs to the PRM suspension in the clean room.
Janne remembered when she put the cable back, she trusted the latch on the connector and did not push it in too hard.
However, Rob suggested the latch does not work well. So she pushed the connector again. Then the signal from
the ITMY UL OSEM got back to normal.
The second attachment shows the ITMY spectra after the cable push.
We decided to pump down after confirming this.

There are still a lot of extra peaks especially in the suspensions in the BS chamber.
These may be inter modulations (by the non-linearities of the OSEMs) of the modes of the multiple
suspensions sitting on the same stack.
Attachment 1: 2008-8-15.pdf
2008-8-15.pdf 2008-8-15.pdf 2008-8-15.pdf 2008-8-15.pdf 2008-8-15.pdf 2008-8-15.pdf 2008-8-15.pdf 2008-8-15.pdf
Attachment 2: ITMY2.pdf
ITMY2.pdf
  841   Fri Aug 15 16:45:43 2008 SharonUpdate Converting from FIR to IIR
I have been looking into different techniques to convert from FIR to IIR. This is so we can see how effective the adaptive FIR filter is in comparison to an IIR one with fewer taps.
For now I tried 2 matlab functions: Prony and stmcb (which works on LMS method).
I used the FIR wiener code, MC1_X, (c1wino) and applied the FIR to IIR algorithm.
Seems like the stmcb one works a bit better, and that there isn't much effect for having 1000 and not 400 taps.

Will keep updating on more results I have, and hopefully have the MC in time to actually check this live.
Attachment 1: fir2iir50.png
fir2iir50.png
Attachment 2: fir2iir400.png
fir2iir400.png
Attachment 3: fir2iir1000.png
fir2iir1000.png
  840   Fri Aug 15 14:12:31 2008 steveBureaucracySAFETYsafety glasses required
The MOPA shutter is opened,
the PSL enclosure is switched to bypass mode,
manual block removed from PMC,

the PSL output is still blocked and the mechanical shutter is still closed.

Pumpdown is at 300 Torr continuing

Laser safety glasses are required!
  839   Fri Aug 15 11:52:32 2008 josephbConfigurationCamerasMulti-computer display and recording of digital camera output
Through the magic of gstreamer, I've been able to live play on one machine, compress the image, send it to another machine via udp, and also display it there. The "tee" function also allows one to save at the same images at time as well.

The command line used on the "server", say Rosalba or Mafalda is:

CamServe -F 'Mono8' -c 44058 -E 20000 -X 0 -Y 0 -H 480 -W 752 -l 0 -m 100 | gst-launch-0.10 fdsrc fd=0 blocksize=360960 ! video/x-raw-gray, height=480, width=752, bpp=8,depth=8,framerate=60/1 ! tee name=t1 t1. ! video/x-raw-gray, height=480, width=752, bpp=8,depth=8,framerate=60/1 ! ffmpegcolorspace ! ximagesink t1. ! video/x-raw-gray, height=480, width=752, bpp=8,depth=8,framerate=60/1 ! ffmpegcolorspace ! queue ! smokeenc keyframe=8 qmax=40 ! udpsink host="131.215.113.103" port=5000

This both displays the image and sends it to the host 131.215.113.103 in this case.

I've written a primitive shell script that does most of this.

It requires at the minimum an IP address. You can also give it a number of images (the -m number) and also the exposure value (-E 20000).

Currently in /cvs/cds/caltech/target/Prosilica/40mCode/SnapCode/ there is a script called CameraServerScript.

Typing in "CameraServerScript 131.215.113.107" would send it to that IP address.

Typing in "CameraServerScript 131.215.113.107 500 40000" would run for 500 images at an exposure value of 40000.

To actually receive, you need gstreamer installed and run the following command:

gst-launch udpsrc port=5000 ! smokedec ! queue ! ffmpegcolorspace ! ximagesink sync=false

Make sure you have the right IP address to send to.

Still working on multicasting (basically a server is constantly sending out images, and the client subscribes to the multicast).
  838   Thu Aug 14 21:52:51 2008 KojiSummaryGeneralAbs. Len. Meas. ~ summary of my Summer
I have made the summary of the absolute length measurement.
It is attached here. The file is a bit big (~8.6MB).
Attachment 1: mode_spacing_measurement_080816_v2.pdf
mode_spacing_measurement_080816_v2.pdf
  837   Thu Aug 14 19:35:54 2008 JenneSummaryIOOPRM in the chamber, ready to pump!
Rob, Yoichi, Jenne, Steve

Summary: Everything is back in the chamber, we just need to put on the big doors, and start pumping in the morning.

After letting the PRM's standoff epoxy cure overnight, it was time to put the optic back in the BS Chamber. Rob put the optic cage back in the chamber, as close to the guide points that Rana had placed as possible. A handy technique was discovered for pushing the cage into place: put a long screw into the table, leaving an inch or so above the table, then use that as a push-off point so that you can push the base of the cage with your thumb. According to Rob, this is probably just about as effective as using a pusher-screw.

The guides were helpful in getting the PRM back to its original position, but one of them was placed in such a way that it could move when pushed against. The clamp that was used as a guide point was placed with one of the screws half on the edge of a hole, so that when the cage was pushed against the guide point, that screw could wiggle around, causing the clamp to rotate thus no longer being a definite guide point.

Just after putting the PRM in place, Rob found the standoff that had gone missing. (see elog #835)

Once the PRM was back in place, we put the OSEMs back, and reinstalled the satellite boxes that had been removed (PRM's, which Ben has fixed - an op-amp was blown, and BS's, which we used over in the clean room with the spare OSEMs). We found a problem with the LR PRM OSEM reading on Dataviewer. It was saturating when the OSEM was just sitting on the table, with nothing between the LED and the sensor. We measured the output from the satellite box with the octopus cables, and measured 2.3 volts, which is too much for the DAQ. It seems fine when we install it in the cage, and the magnet is blocking part of the light. We should investigate the gain of the satellite box when convenient. This is not something that needs to be done prior to pump-down. Also, when we put an allen wrench to block the light while checking which OSEM was which, we noticed that the Dataviewer reading would go down to -2V, then come back to 0V when the light was completely blocked. This may be some incorrect compensation for some whitening. Again, we should look into this, but it is not terribly time-sensitive.

Once the OSEMs were centered, we tried to turn on the damping for the PRM. This was successful, so we are confident that we have put all of the OSEMs back in their correct places.

We found that we were easily able to get the PRM's oplev back on the QPD, so we ~centered the oplev, and then centered all of the PRM's OSEMs. This assumes that the oplev was in a good place, but I think we've determined that this is the case.

We did the same thing for the SRM and the BS, to check the OSEM values before we close up for good. We found that some of the SRM OSEMs were reading low (magnet too far in), and that all of the BS OSEMs were low, perhaps as if the table were tilted a tiny bit after removing and replacing the weight of the PRM. We recentered all of the OSEMs for both of these optics.

We checked that all of the pigtails for the PRM OSEMs were anchored to the PRM cage using some copper wire as tie-downs.

We checked that all of the earthquake stops were within 1mm or so of each of the 3 optics in the BS chamber. The SRM's earthquake stops were fairly far out. One of the bottom ones was far enough that when Yoichi turned it the wrong way (accidentally), it fell out. He put it back in, and adjusted all of the earthquake stops appropriately. This 1mm distance comes from Seji, and the specs for the optics' cages.

We did a look-through of the chamber, and took out all of the tools, and other things that were not bolted down to the table.

We have left the damping of the PRM off for the night.

To do: put the doors back on, and start the pump down.
  836   Thu Aug 14 19:08:14 2008 YoichiConfigurationSUSFree swing measurement going on
I started free swinging spectra measurement of all the suspensions now Aug 14 19:05 (PDT).
The watch dogs are all shutdown. Please do not turn them back on until tomorrow morning.
  835   Thu Aug 14 15:51:35 2008 josephbSummaryCamerasFOUND! The Missing Standoff!
We used a zoom lens on the GC750 to take this picture of the standoff while inside a plastic rubber-glove bag. The standoff with bag is currently scotch-taped to the periodic table of the elements.
Attachment 1: standoff.png
standoff.png
  834   Thu Aug 14 11:39:06 2008 steveUpdatePEMparticle counter is out of order
The 40m ifo paricle counter sensor failed last night.
  833   Thu Aug 14 10:26:45 2008 steveHowToSUSsus cable pin cheater for out of vac damping
The 40m D25 vacuum feed troughs give you a mirror image pin count.

Sus damping outside of the vacuum envelope require this cheater cable where
on the male D pin 1 is connected to female D 13 and so on
and male D pin 14 is connected to female D 25 and so on
Attachment 1: suscabmin.png
suscabmin.png
  832   Wed Aug 13 20:13:35 2008 YoichiUpdateSUSPRM stand-off is glued
Steve, Janne, Rob, Bob, Koji, Yoichi

We finally managed to balance the PRM and the stand-off is now glued.

The whole procedure was something like this:

(1) Measure the levelness of the optical table. It was done by a bubble level claiming that
the sensitivity is 60 arcsec (roughly 0.3 mrad).
There was no noticeable tilt along the longitudinal direction of the table.

(2) We put a He-Ne laser on one end of the table. Mounted a QPD on a X-Y-Z stage. Put the QPD very
close to the laser and centered it by moving the QPD.
Then we moved the QPD far away from the laser and centered the beam spot in vertical direction
by changing the tilt of the laser mount.
We then moved the QPD close to the laser again and adjusted the height to center it. By repeating
the centering at two locations (near and far) several times, we aligned the laser beam parallel to
the table.

(3) The PRM suspension tower was put on the other end of the optical table, i.e. far from the laser.
The QPD was moved next to the laser to form an optical lever. The height of the QPD is preserved from
the previous step.


(4) A stand-off was picked by a pair of tweezers. By gently lifting the mirror by the bottom earthquake stops,
the tension of the wire was relieved. Then the stand off was slid in below the guide rod.

(5) Using the microscope, it was confirmed that the wire is in the grooves on both sides.

(6) Without damping, it was too much pain to balance the mirror. So we put spare OSEMs in the suspension and
pulled a long cable from the suspension rack to the clean room with a satellite amp.

(7) It turned out that the pinout of the cable is flipped because of the vacuum feed through. So we asked Ben for help.
He made conversion cables. We also found UR OSEM was not responding. Ben opened the satellite box, and we found an op-amp was burnt.
Probably it was because we connected OSEMs wrongly at first and the LED current driver was shorted. We switched the satellite box
from the PRM one to the BS one. Ben will fix the PRM box.
Bob cleaned up some D-Sub converters for the interface with the clean OSEM pigtails.

(8) While waiting for Ben, we also tried to short the OSEM coils for inductive damping. We saw no noticeable change in the Q.

(9) After the OSEMs were connected to the digital control system, Rob tweaked the damping gains a bit to make it work efficiently.

(10) I pushed the stand-off back and forth to make the reflected beam spot centered on the QPD. I used the PZT buzzer to gently move the stand-off.
For fine tune, just touching it is enough. I found it useful to touch it without clamping the mirror, because if it is clamped, we can easily push
it too hard. When the mirror is freely hanging, once the tip of the buzzer touches the stand-off, the mirror escapes immediately. If the mirror
swings wildly by your touch, you pushed it too hard.

(11) After about an hour of struggle, I was able to level the mirror. We used about 1.5m optical lever arm. A rough calibration tells us that the
beam spot is within 0.6mm of the center of the QPD. So the reflected light is deflected by 0.4mrad. That means the mirror
is rotated by 0.2mrad. The OSEMs should have about 30mrad of actuation range. So this should be fine.

(12) We mixed the Vac Seal epoxy and put it under vacuum for 15min to remove bubbles. Actually 15min was not enough for removing bubbles completely. But
stopped there because we did not want the epoxy to be too stiff.
I dipped a thin copper wire into the epoxy and applied it on the top of the stand-off. I found the epoxy is already not fluid enough, so Steve made
another Vac Seal mixture. This time we put it under vacuum for only 3 min.
I also applied the epoxy to the sides of the stand-off.
While working on this, I accidentally touched the side of the PRM. Now there is a drop of epoxy sitting there (upper left of the attached picture).
We decided not to wipe it out because we did not want to screw up the levelness.

(13) We put an incandescent light about 1m away from the suspension to gently warm up the epoxy but not too much. We will leave it overnight to cure the
epoxy.
Attachment 1: img1.jpg
img1.jpg
  831   Wed Aug 13 17:00:59 2008 steveConfigurationSUSBS sat amp removed
The PRM sat amp is broken. Ben is working on it.
The BS sat amp was removed from the BS sus and it is used with the PRM in
order to damp it for wire stand-off alignment.
  830   Tue Aug 12 21:38:19 2008 JohnUpdateLSCAccidental higher order mode resonances in the arms
Recently we had been having some trouble locking the full IFO in the spring configuration (SRC on +166).
It was thought that an accidental higher order mode resonance in the arms may have been causing problems.

I previously calculated the locations of the resonances using rough arm cavity parameters(Elog #690). Thanks to Koji
and Alberto I have been able to update this work with measured arm length and g factors for the y arm (Elog #801,#802).
I have also included the splitting of the modes caused by the astigmatic ETM. Code is attached.

I don't see any evidence of +166MHz resonances in the y arm.


In the attached plot different colours denote different frequencies +33, -33, +166, -166 & CR.
The numbers above each line are the mn of TEMmn.
Solid black line is the carrier resonance.
Attachment 1: HOMresonances.png
HOMresonances.png
Attachment 2: HOMarms2.m
%Check for accidental resonances of HOM in the arms (maybe due to
%sidebands). At the moment there is only data for the y arm.

clear all
close all
clc


%Stuff one might change often
modeorder = 0:5;          % Look for TEMmn modes where m,n run over modeorder
... 157 more lines ...
  829   Tue Aug 12 19:48:24 2008 JenneUpdateIOOPRM standoff is in....mostly
Yoichi, Jenne

The missing PRM standoff is now partially installed. The standoff is in, and the wire is in the groove, but we have not finished adjusting its position to make the PRM stand up straight. It turns out to be pretty tricky to get the position of the standoff just right.

We have set up a HeNe laser as an oplev on the flow bench (which we checked was level) in the clean assembly room, and are using it to check the pitch of the mirror. We set a QPD at the height of the laser, and are looking at the single-reflected light. When the single-reflected light is at the same height as the center of the QPD, then the mirror is correctly aligned in pitch. (Actually, right now we're just trying to get the single-reflected light to hit the diode at all...one step at a time here).

We'll continue trying to align the PRM's standoff in the morning.
  828   Tue Aug 12 12:21:13 2008 josephbConfigurationCamerasVariation in fit over 140 images for GC650 and GC750
Used matlab to calculate Gaussian fits on 145 GC650 images and 142 GC750 images. These were individual images (no averaging) looking at the PSL output from May 29th 2008. The GC650 and GC750 were looking at a split, but had different exposure values, slightly different distances to the nominal waist of the beam, and were not centered on the beam identically. Mostly this is a test of the fluctuations in the fit from image to image.

Note the mm refer to the size or position on the CCD or CMOS detector itself.
GC650

Mean
Amplitude  X center       Y center       X waist  Y waist  Background offset from zero
           position (mm)  position (mm)  (mm)     (mm)
0.3743     1.7378         2.6220         0.7901   0.8650  0.0047

Standard Deviation
Amplitude  X center       Y center       X waist  Y waist  Background offset from zero
           position (mm)  position (mm)  (mm)     (mm)
0.0024     0.0006         0.0005         0.0005   0.0003  0.00001

Std/Mean x100 (percent)
Amplitude  X center       Y center       X waist  Y waist  Background offset from zero
           position (mm)  position (mm)  (mm)     (mm)
0.6%       0.03%          0.02%          0.06%    0.04%    0.29%


GC750

Mean
Amplitude  X center       Y center       X waist  Y waist  Background offset from zero
           position (mm)  position (mm)  (mm)     (mm)
0.2024     2.5967         1.4458         0.8245   0.9194  0.0418

Standard Deviation
Amplitude  X center       Y center       X waist  Y waist  Background offset from zero
           position (mm)  position (mm)  (mm)     (mm)
0.0011     0.0005         0.0005         0.0003   0.0005  0.00003

Std/Mean x100 (percent)
Amplitude  X center       Y center       X waist  Y waist  Background offset from zero
           position (mm)  position (mm)  (mm)     (mm)
0.6%       0.02%          0.04%          0.04%    0.05%    0.07%
  827   Tue Aug 12 12:05:36 2008 YoichiUpdateComputersHP color printer is back
I restarted the HP printer server (a little box connected to the HP color laser) so that we can use the HP LaserJet 2550.
After this treatment, the printer spat out a bunch of pages from suspended jobs, many of these were black and white.
I think people should use the black-and-white printer for these kind of jobs, because the color printer is slow and troublesome.
  826   Mon Aug 11 19:09:28 2008 JenneDAQPEMSeismometer DAQ is being funny
While looking at the Ranger seismometer's output to figure out what our max typical ground motion is, Rana and I saw that the DAQ output is at a weird level. It looks like even though the input to the DAQ channel is being saturated, the channel isn't outputing as many counts as expected to Dataviewer.

Sharon and I checked that the output of the seismometer looks reasonable - sinusoidal when I tap on the seismometer, and the the output of the SR560 (preamp) is also fine, and not clipping. If I stomp on the floor, the output of the SR560 goes above 2V (to about 3V ish), so we should be saturating the DAQ, and getting the max number of counts out. However, as you can see in the first figure, taken when I was tapping the seismometer, the number of counts at saturation is well beneath 32768counts. (16 bit machine, so the +-2V of the DAQ should have a total range of 65536. +2V should correspond to +32768counts.) The second figure shows 40 days of seismometer data. It looks like we saturate the DAQ regularly.

I did a check of the DAQ using an HP6236B power supply. I sent in 1V, 2V and 2.2V (measuring the output of the power supply with a 'scope), and measured the number of counts output on the DAQ.

Input Voltage [V]Counts on DataviewerExpected counts from 16 bit machine
11898316384
22933132768
2.22934732768


I'm not sure why the +1V output more than the expected number of counts (unless I mis-measured the output from the power supply).

Moral of the story is...when the DAQ is saturated, it is not outputting the expected number of counts. To be explored further tomorrow...
Attachment 1: SeisDAQ.png
SeisDAQ.png
Attachment 2: SeisData.png
SeisData.png
  825   Mon Aug 11 15:07:49 2008 josephbConfigurationComputersProcyon aka fb40m switched to new switch
I've connected Procyon to the Prosafe 24 port switch with a new, labeled Cat6 cable. Quick tests with dataviewer shows that its working.
  824   Mon Aug 11 13:59:23 2008 josephbConfigurationComputers 
While poking around the crate, I noticed an error light on one of the c1susvme2 related boards was lit, while the corresponding light on the c1susvme1 was not. This confuses me as the c1susvme1 is the one having problems.

As a quick sanity check, I unplugged the ethernet connection from the c1susvme1 labeled board, and confirmed I couldn't log into it, and then plugged it back in, restarted it, and re-ran the startup script. This time c1susvme1 seemed to come up fine. Re-enabling the watchdogs doesn't seem to kick anything, and in fact seems to be bringing everything into line properly.

Although the error light on the c1susvme2 clk drvr board is still on. So I'm not sure what thats trying to tell us. Open to suggestions.
  823   Mon Aug 11 12:42:04 2008 josephbConfigurationComputersContinuing saga of c1susvme1
Coming back after lunch around 12:30pm, c1susvme1's status was again red. After switching off watchdogs, a reboot (ssh, su, reboot) and restarting startup.cmd, c1susvme1 is still reporting a max sync value (16384), occassionally dropping down to about 16377. The error light cycles between green and red as well.

At this point, I'm under the impression further reboots are not going to solve the problem.

Currently leaving the watchdogs associated with c1susvme1 off for the moment, at least until I get an idea of how to proceed.
  822   Mon Aug 11 11:36:11 2008 josephb, SteveConfigurationComputersc1susvme1 minor problems
Around 11 am c1susvme1 start having issues. Namely C1:SUS-PRM_FE_SYNC was railing at some large value like 16384 (2^14). I presume this means the computer was running catastophically late.

I turned off the BS and ITM watch dogs (the PRM was already off), tried hitting reset and sshing in, and running startup, but this didn't help. I then turned off the c1susvme2 associated watch dogs (MC1-3, SRM) and went out to do a hard reboot by switching the crate power off. c1susvme2 came back up fine, was restarted and associated watch dogs turned back on. However, c1susvme1 came back up without mounting /cvs/cds/.

As a test, I replaced the ethernet connection with a CAT6 cable to the Prosafe switch in 1Y6, and then ran reboot on c1susvme1. When it came back up, it had mounted properly, and I was able to run the ./startup.cmd file. At this point it seems to be happy. The new cable is in the trays coming in from the top of the 1Y4 and 1Y6 and approriately labeled.

Edit: Apparently ITMX and ITMY became excited after the reboot (perhaps I turned the watchdogs back on too early? Although that was after the DAQ light was listed as green for c1susvme). Steve noticed this when the alarms went off again (I had turned them off after the reboot seemed successful), and he damped them. Interestingly, the BS remained unexcited.
  821   Mon Aug 11 09:39:29 2008 ranaUpdatePEM2 years of temperature trend
Steve and I went around and inspected and then adjusted the thermostats and humidostats.

All the thermostats were set at 70F in 2005 by Steve. We adjusted the ones on the arms up to 72F
and set the one on the wall west of the framebuilder up to 74F (this area was consistently colder
than all the others and so we're over-correcting intentionally).
  820   Mon Aug 11 00:58:31 2008 ranaUpdatePEM2 years of temperature trend
The PSL RMTEMP alarmed again because it says the room temperature is 19.5 C. Steve said in
an earlier log entry that this is a false alarm but he didn't say why he thought so...

I say that either the calibration of the RMTEMP channel has drifted, the setpoint of the HVAC
has shifted, or there's a drift in the RMTEMP channel. I don't know what electronics exactly
are used for this channel so not sure if its susceptible to so much drift.

However, since the Dust Monitor (count_temp) shows a similar temperature decline in the
last two years I am inclined to blame the HVAC system.

The attached plot shows 2 years of hour-mean trend.
Attachment 1: Untitled.png
Untitled.png
  819   Sun Aug 10 16:57:02 2008 ranaSummaryPhotosPhotos from Vent 8/4 - 8/8
http://www.ligo.caltech.edu/~rana/40m/VentAug08/

I've added the D40 pictures from last week to this web page. I have done some cropping and
rotating to make things look better.

On page 3, there are some over head shots of the Michelson area so that one can use screw holes
to judge what the spacing between the suspensions is and also possibly the cavity lengths. Lets
also remember to measure the ITM-BS distance accurately using a tape measure or ruler while we
have the thing open.
  818   Fri Aug 8 17:54:52 2008 JenneUpdateSUSStandoffs and Guide Rods
After closer inspection of other small optics, it is clear that the guide rods should be above the standoffs on our small optics. Yoichi took a picture of the SRM that shows this clearly. This makes sense since the tension of the wire will make the standoff 'want' to go up during pre-epoxy adjustment, so the guide rod prevents the standoff from popping up and out.

Looking at the side of the PRM without the groove, it looks like there is lots of space between the guide rod and the alignment etch in the glass, so we can just place a standoff directly under the guide rod that is present.

A spare standoff is being shipped tomorrow morning, so we should have it by Monday for installation on the PRM.
Attachment 1: SRM_Standoff_and_guide.JPG
SRM_Standoff_and_guide.JPG
  817   Fri Aug 8 15:10:35 2008 YoichiUpdateSUSNo groove in the stand-off ... wait, it is not even a stand-off !
I tried to find the missing stand-off and the guide rod in the BS chamber, but I couldn't.
  816   Fri Aug 8 13:29:54 2008 YoichiUpdateSUSNo groove in the stand-off ... wait, it is not even a stand-off !
Yoichi, Steve, Seiji

We took magnified pictures of the stand-offs of the PRM.
Attm1: North side stand-off.
Attm2: South side stand-off.
Attm3: Zipped file of the full pictures.

We found no groove in the south side stand-off.
After some discussion, we concluded that it is actually a guide rod. You can see it from the size difference (the magnification is the same for the two pictures).
The stand off on the south side is missing (fell off, ran away, evaporated or whatever ...).
Also we noticed that the guide rod on the north side is missing.

We have to find a stand-off and place it on the south side.
Seiji suggested that it is better to put a guide rod next to the north side stand-off, otherwise the stand-off itself is too weak to hold the load.
He also said that the PRM was installed after he left, so it was not his fault.
Attachment 1: north-standoff-preview.jpg
north-standoff-preview.jpg
Attachment 2: south-standoff-preview.jpg
south-standoff-preview.jpg
Attachment 3: No-groove.zip
  815   Fri Aug 8 12:21:57 2008 josephbConfigurationComputersSwitched X end ethernet connections over to new switch
In 1X4, I've switched the ethernet connections from c1iscex and c1auxex over to the new Prosafe 24 port switches. They also use the new cat6 cables, and are labeled.

At the moment, everything seems to be working as normally as it was before. In addition:

I can telnet into c1auxex (and can do the same to c1auxey which I didn't touch).
I can't telnet into c1iscex (but I couldn't do that before, nor can I telnet into c1iscey either, and I think these are computers which once running don't let you in).
  814   Fri Aug 8 11:04:34 2008 SharonUpdate MCL Wiener filter
I took some old data from Rana and converted the units of the Weiner filter to m/m so to make the effect of the seismometer and accelerometers more obvious.

The data is in counts, and so to convert to m this is what I did:

%%% MC_L calibration
v_per_counts = 5/32768;
v_per_v = 3;
amp_per_N = 1/0.064;

%%% Accelerometers calibration
v_per_counts_acc = 61.045e-6;
g_per_v = 9.8/100;

%%% Seismometer calibration
v_per_counts_seis = 61.045e-6;
m_per_s_per_s_per_volt = 9.8/100;
m_per_v_per_s = 1/345;



for jj=1:6
hfmatm(:,jj)=hfmat(:,jj).*(v_per_counts.*v_per_v.*amp_per_N.*f)./(v_per_counts_acc*g_per_v); %%% accelerometers' data
end
hfmatm(:,7)=hfmat(:,7).*(v_per_counts.*v_per_v.*amp_per_N)./(v_per_counts_seis*m_per_v_per_s); %%% Seismometer data
Attachment 1: m_per_m.png
m_per_m.png
  813   Fri Aug 8 10:58:05 2008 josephbConfigurationCamerasCameras and gstreamer
In regards to camera failure:
1) I forgot to reconnect that particular camera to the network (my fault) so thats why it was failing.

2) Even with the correct camera connected, I've realized at full frame rate, op440m is going to get a few frames and then fail, as I don't think it has a fast enough ethernet card. It will work on Rosalba, and will also work ssh-ing from Rosalba because it is using a new ethernet card. It also works on my laptop, which is where I originally tested the command. One way to get around this is to increase the time between pictures, by changing -l 0 to -l 1 (or higher), where the number after the "ell" is the number of seconds to wait between frame captures.

3) What I should do is figure out the UDP transmission plugins for gstreamers and compress first (using the theoraenc since it gets compression ratios of better than 100:1) and transmit that over the network.

I have since reconnected the camera, so it should work on Rosalba and any sufficiently well connected computer. For other machines like linux2 or op440, try the following line:

Running the following command on Mafalda (via ssh -X mafalda) or Rosalba while in /cvs/cds/caltech/target/Prosilica/40mCode/SnapCode/

CamSnap -F 'Mono8' -c 44058 -E 10000 -X 0 -Y 0 -H 480 -W 752 -l 1 -m 100 | gst-launch-0.10 fdsrc fd=0 blocksize=360960 ! video/x-raw-gray, height=480, width=752, bpp=8,depth=8,framerate=1/1 ! ffmpegcolorspace ! ximagesink

This will be at a much slower frame rate (1 per second) but should work on any of the machines. (Tested on linux2).
  812   Fri Aug 8 09:54:10 2008 ranaUpdateCamerasNew code + gstreamer allows for easy saving and compression of images

Quote:
Modified the CamSnap code to output the image data stream to standard out. This can then be piped into a gstreamer plugin and then be used


Didn't work; Prosilica has only 1 "l". Even so, sshing from op440m to mafalda, I got this:
mafalda:SnapCode>CamSnap -F 'Mono8' -c 44058 -E 5000 -X 0 -Y 0 -H 480 -W 752 -l 0 -m 300 | gst-launch-0.10 fdsrc fd=0 blocksize=360960 ! video/x-raw
-gray, height=480, width=752, bpp=8,depth=8,framerate=30/1 ! ffmpegcolorspace ! theoraenc ! oggmux ! filesink location="./testVideo.ogm"
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...

** (gst-launch-0.10:27121): WARNING **: Size 60 is not a multiple of unit size 360960
Caught SIGSEGV accessing address 0x487c
ERROR: from element /pipeline0/ffmpegcsp0: subclass did not specify output size
Additional debug info:
gstbasetransform.c(1495): gst_base_transform_handle_buffer (): /pipeline0/ffmpegcsp0:
subclass did not specify output size
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7deddae in __lll_mutex_lock_wait ()
#2  0xb7de9aac in _L_mutex_lock_51 () from /lib/tls/i686/cmov/libpthread.so.0
#3  0xb7de949d in pthread_mutex_lock ()
#4  0xb7e452e0 in g_static_rec_mutex_lock () from /usr/lib/libglib-2.0.so.0
#5  0xb7f1fa08 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#6  0x080c1220 in ?? ()
#7  0x00000001 in ?? ()
#8  0x0809586c in ?? ()
#9  0x00000001 in ?? ()
#10 0x08095868 in ?? ()
#11 0xb7f7a2a8 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#12 0xb7e8da80 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0xb7f7a2a8 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#14 0xb7f7a2a8 in ?? () from /usr/lib/libgstreamer-0.10.so.0
#15 0x00000000 in ?? ()
Spinning.  Please run 'gdb gst-launch 27121' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.
Caught interrupt -- 
  811   Thu Aug 7 17:32:23 2008 JenneUpdateSUSAfternoon PRM activities
Rana, Jenne, Yoichi, Dmass

After Yoichi confirmed this morning that the wire was in both grooves, Rana attempted to lift the PRM a tiny bit, and twist it around (very gently of course) to see if we could make the wire slip back to its nominal position underneath the optic. On the first attempt, the wire ended up slipping the wrong way, causing slightly more tilt. On another attempt, the wire came out of the groove nearest the chamber door by about 0.5mm. We got the wire back in the groove by slightly lifting the optic, and pushing the wire back in. Then, on further attempts at making the wire slip back to its nominal position, the wire came out of the groove farthest from the chamber door. It is very difficult to get at that side of the PRM, because the table is crowded, and it is on the far side of the optical table from the chamber door. We decided to pull the PRM out of the chamber. Rana clamped the mirror into its cage using the earthquake stops and removed the OSEMS, and then we pulled the mirror out. We put it on a cart that was covered with foil and had a little foil house for the optic cage. We rolled the mirror+cage over to the flow bench at the end of the y-arm.

We saw that the wire is no longer even on the standoff (~3mm away from the groove) on the side that was farthest from the chamber door.

Since we have not confirmed that we have spare wire and spare magnets (and due to the time of day), we have decided to cover the cage with some foil, while it is sitting on the flow bench, and we'll fix the wire in the morning.
  810   Thu Aug 7 12:20:52 2008 YoichiUpdateSUSPRM stand-offs and wire
We removed the side OSEM of the PRM so that we can see the stand-off on the farther side.

Attachment 1: Farther side stand-off from an angle before removing the OSEM
Attachment 2: Farther side stand-off through the empty OSEM hole.
Attachment 3: Near side stand-off

The wire is definitely in the near side stand-off groove.
Probably the wire is in the groove also on the farther side.
Attachment 1: IMG_1456.JPG
IMG_1456.JPG
Attachment 2: IMG_1478.JPG
IMG_1478.JPG
Attachment 3: IMG_1470.JPG
IMG_1470.JPG
  809   Thu Aug 7 11:54:26 2008 josephbConfigurationCamerasNew code + gstreamer allows for easy saving and compression of images
Modified the CamSnap code to output the image data stream to standard out. This can then be piped into a gstreamer plugin and then be used to save, encode, transmit, receive, slice, dice and or mangle video (or virtually any type of data stream).

The gstreamer webpage can be found at: http://www.gstreamer.net/

Under documentation you can find a list off all available plug-ins. Some good, some bad, some ugly.

Running the following command on Mafalda (via ssh -X mafalda) or Rosalba while in /cvs/cds/caltech/target/Prosilica/40mCode/SnapCode/

CamSnap -F 'Mono8' -c 44058 -E 15000 -X 0 -Y 0 -H 480 -W 752 -l 0 -m 1000 | gst-launch-0.10 fdsrc fd=0 blocksize=360960 ! video/x-raw-gray, height=480, width=752, bpp=8,depth=8,framerate=1/1 ! ffmpegcolorspace ! ximagesink

This command will create a window which displays what the camera with UID 44058 is looking at. It will display 1000 images, then quit. (You can switch the -m 100 to -i to just have it continue until the process is stopped).

You can also encode the data into compressed format and save it in a media file. The following command line will encode the images into an ogg media file (.ogm), which can be played with the totem viewer (available on Rosalba or almost any machine running Ubuntu or Centos) or any other viewer capable of handling ogm files. By switching the plugins you can generate other formats as well.

The compression is good, putting 300 images normally about 500K individually uncompressed to about 580K as a single file.

The following command line was used to generate the attached video file:

CamSnap -F 'Mono8' -c 44058 -E 5000 -X 0 -Y 0 -H 480 -W 752 -l 0 -m 300 | gst-launch-0.10 fdsrc fd=0 blocksize=360960 ! video/x-raw-gray, height=480, width=752, bpp=8,depth=8,framerate=30/1 ! ffmpegcolorspace ! theoraenc ! oggmux ! filesink location="./testVideo.ogm"

Currently looking into plugins which allow you to pull individual frames out of a video file and display or save them in a variety of formats. This would allow us to save long term images in compressed video format, and then pull out individual frames as needed.

Also need to look into how to "T" the streams, so one can be displaying while another encodes and saves.
Attachment 1: testVideo.ogm
  808   Thu Aug 7 10:27:59 2008 ranaUpdateSUSFree swinging OSEM spectra
Sometimes we see extra peaks in the OSEM spectra coming from a beat between the regular eigenmodes.
This probably comes from the OSEM shadow sensor not being entirely linear - the nonlinearity is
greatly increased if the magnet is not perfectly centered in the LED beam. So the beats are
probably there at some level in all of them; usually below the noise.
  807   Thu Aug 7 10:07:13 2008 YoichiUpdateSUSFree swinging OSEM spectra
Looks like there are more extra peaks in the SRM than other optics.
Maybe because it is closer to the door ?
Attachment 1: FreeSwingSpectra.pdf
FreeSwingSpectra.pdf FreeSwingSpectra.pdf FreeSwingSpectra.pdf FreeSwingSpectra.pdf FreeSwingSpectra.pdf FreeSwingSpectra.pdf FreeSwingSpectra.pdf FreeSwingSpectra.pdf
  806   Wed Aug 6 22:19:07 2008 YoichiUpdateSUSBS alignment
Koji, Yoichi

We realized that we did not pay attention to the BS alignment while working on the alignment of the ITMX today. Because we were injecting the ALM laser (absolute length measurement laser) from the AS port, the ITMX alignment depends on the BS alignment.
The BS optical lever was not centered and the sum was about 2000cnt, which is low compared, for example, to the SRM oplev.
So we were not sure if the BS was in a good alignment or not.
So we decided to move the BS to center the QPD.
In doing so, we also moved the ITMX so that we do not lose the ALM laser beam coming back to the AS port.
When the BS oplev was centered, the sum of the QPD was still about 2000. So it was not far off centered.
After the tweaking, we were able to see some interference between the light reflected by the ITMY and ITMX at the AS port (actually this is the bright port for the ALM laser). By tweaking the ITMY, we were able to see Michelson fringes at the AS port.
If we believe the ALM laser alignment is still good after the vent, the ITMX, ITMY, BS and SRM should be now in a good alignment condition.
The OSEM values for the ITMX, BS, SRM seem to be ok (0.9+/-0.2). The ITMY LL is a bit low (~ 0.45).
  805   Wed Aug 6 19:01:15 2008 AlbertoUpdateGeneralITMX and SRM OSEM post-earthquake diagnostic
Koji, Yoichi, Alberto

Today we reset the OSEMs on ITMX and SRM in order to be centered when the mirrors are aligned to the IFO beam. Since the PRM is still out of order, we used the beam from NPRO laser of the absolute length measurement experiment as it is injected through the AS port.
Thatís how we did it:

1) We aligned the SRM so that the reflected beam from the NPRO was at the camera after at the AS port.

2) We traded off the alignment of SRM in order for the reflected beam at the camera to have a nice shape, avoiding any clipping from the optics, and for the optical lever to be not too far from zero. The final alignment for SRM, as read on the sliders on the MDM screen, is: Pitch=1.1650, Yaw=1.4674.

3) We aligned ITMX checking out by an IR card that the incoming and the reflected main beam in between ITMX and the BS matched. The alignment of the two beams was improved checking the matching after the SRM. The final alignment for ITMX, as read on the sliders on the MDM screen, is: Pitch=-1.2937, Yaw=-0.9890.

4) After the alignment of SRM and ITMX these were the voltages at the OSEMs:

SRM
UL=0.957
UR=1.254
LR=0.768
LL=0.620
Side=0.958

ITMX
UL=1.144
UR=1.360
LR=0.591
LL=0.325
Side=-----

5) Finally we centered the OSEMs on both mirrors and we read these voltages:

SRM
UL=0.939
UR=0.994
LR=0.782
LL=0.938
Side=0.953

ITMX
UL=0.918
UR=0.891
LR=0.887
LL=0.875
Side=0.883
  804   Wed Aug 6 13:57:44 2008 MashaSummaryAuxiliary lockingweekly summary
Finished second progress report.

Working on improving the sensitivity of the Mach Zehnder to more accurately measure the fiber noise. Making more stable mounts that have fewer degrees of freedom/springs and are more solid should get rid of their vibrational modes and help with the noise. I found a good mount for the Faraday Isolator, and John and Aidan helped me to make the solid aluminum blocks to mount the fiber couplers. I'll also replace the laser feet with a similar solid mount. I will also get a plastic box to block out acoustic noise/air currents/etc. Am starting to couple into the fiber again; now I am using polarization maintaining fiber.

I am starting to plan the fiber noise cancellation setup, and thinking about the noise sources and their effects.
  803   Wed Aug 6 13:15:57 2008 YoichiUpdateSUSSRM ETMX freeswing spectra
After yesterday's work on the SRM, I took free swinging spectra of SRM.
The eigen modes look ok. But there are many other peaks which were not present in vacuum.
Some of those peaks may be resonances of the air inside the chambers and the pipes.
However, the peaks around 0.2Hz are too low frequency for those air compression modes.
I took the ETMX spectra at roughly the same time. I chose ETMX because we have not touched it after the vent.
ETMX also shows some extra peaks but the frequencies are different.
Attachment 1: SRM-ETMX-freeswing.pdf
SRM-ETMX-freeswing.pdf SRM-ETMX-freeswing.pdf
  802   Wed Aug 6 11:43:52 2008 KojiUpdateGeneralAbs. Len. Meas. ~ analysis of the TEM01 scan
Analysis of the data on August 3th ~ Part 2

o I already have reported that the resonant freq of TEM10 and TEM01 split.

o Again, note that TEM10/01 were arranged almost in the horizontal/vertical by the observation of the video.

o The peaks of TEM10 and TEM01 were fitted with the same method as of TEM00.

o The peak freqs were:
f_TEM10: 5087040 Hz +/- 20 Hz
f_TEM01: 5068322 Hz +/- 15 Hz
The split is 18.7kHz.

o The additional parameter from the previous entry:
f_TEM00: 3879252 Hz +/- 9 Hz
L_yarm: 38.6462 m +/- 0.0003 m

o Radius of curvature
Rx = L /(1-Cos^2(Pi (f_TEM10 - f_TEM00) / (c/L/2) ))
Ry = L /(1-Cos^2(Pi (f_TEM01 - f_TEM00) / (c/L/2) ))

from these formula we get the value
Rx = 56.1620 +/- 0.0013 [m]
Ry = 57.3395 +/- 0.0011 [m]
Attachment 1: TEM01fit.png
TEM01fit.png
ELOG V3.1.3-