40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  ATF eLog, Page 1 of 56  Not logged in ELOG logo
ID Date Authorup Type Category Subject
  11   Wed Nov 28 16:20:04 2007 Andrey Lab InfrastructureGeneralEnclosure cleaning
Previous Tuesday, Nov. 20, I tried to wipe the curtain plastic enclosure around the optical table with the laser using methanol. It turned out, though, that methanol damages the surface of the enclosure, dissolving it and leaving lines/ traces. I stopped my activities with methanol after I realized that negative effect on three corner strips of enclosure.

Lesson for everyone: NEVER USE METHANOL FOR THOSE CURTAINS!

I tried 25% solution of isopropil alcohol in water on Wednesday, Nov. 21, and such mixture did not have any bad effect on the surface of the enclosure. I wiped the curtains, so they should be clean of dust now.

Andrey.
  504   Fri Dec 18 13:27:12 2009 DmassLaserDoublingConfusion Abounds ^3

Quote:

What's confusing? It looks fine. Should take the TF of the DC and AC signals and compare that with the expected TF of the electronics.

** also, lower case names for channels are illegal. I suggest naming the PDs with what wavelength they have as well, e.g.   PD_1064_1_DC, PD_532_2_AC, etc.

 

Here are the spectra and transfer functions for all four channels. If the DC channel is really just DC (and is not loaded by the AC coupling circuit), then I would expect this to just reproduce the high pass filter itself.

  • I put a white noise source into the ADC
  • I piped this signal to five output channels of the DAC (DIODE_34_CUR_OUT_DAQ, DIODE_12_CUR_OUT_DAQ, NPRO_CUR_OUT_DAQ, NPRO_PZT_OUT_DAQ recorded)
  • I put four of these outputs to the input of my AC Couple circuit
  • I put the other DAC output to the input of my ADC
  • I measured the transfer function between the input of my noise and the signals i am sending from the DAC to the AC coupler
  • I took the transfer function of the spare ADC channel and the eigth outputs of my AC coupler as recorded by the DAQ
  • I noticed funniness (below).

I really don't understand what's going on with the differences I see in my filters. This may have to wait until I get back from Xmas vacation unless someone knows the answer immediately.

For later reference: This setup is recorded in the DAQ from 1:28:00 PST - 1:40:00 PST on Fri Dec 8th

Attachment 1: MZACCoupTFALL.pdf
MZACCoupTFALL.pdf
  505   Fri Dec 18 15:42:22 2009 DmassLaserDoublingConfusion Abounds ^3

Quote:

Quote:

What's confusing? It looks fine. Should take the TF of the DC and AC signals and compare that with the expected TF of the electronics.

** also, lower case names for channels are illegal. I suggest naming the PDs with what wavelength they have as well, e.g.   PD_1064_1_DC, PD_532_2_AC, etc.

 

Here are the spectra and transfer functions for all four channels. If the DC channel is really just DC (and is not loaded by the AC coupling circuit), then I would expect this to just reproduce the high pass filter itself.

  • I put a white noise source into the ADC
  • I piped this signal to five output channels of the DAC (DIODE_34_CUR_OUT_DAQ, DIODE_12_CUR_OUT_DAQ, NPRO_CUR_OUT_DAQ, NPRO_PZT_OUT_DAQ recorded)
  • I put four of these outputs to the input of my AC Couple circuit
  • I put the other DAC output to the input of my ADC
  • I measured the transfer function between the input of my noise and the signals i am sending from the DAC to the AC coupler
  • I took the transfer function of the spare ADC channel and the eigth outputs of my AC coupler as recorded by the DAQ
  • I noticed funniness (below).

I really don't understand what's going on with the differences I see in my filters. This may have to wait until I get back from Xmas vacation unless someone knows the answer immediately.

For later reference: This setup is recorded in the DAQ from 1:28:00 PST - 1:40:00 PST on Fri Dec 8th

 

I also swapped the cables going in to my AC Coupler at Rob's suggestion and had the same channels misbehaving.

 

  288   Thu Aug 27 21:40:20 2009 (not) AlastairLab Infrastructurestuff happensLenses

Quote:

I ordered some lenses for the lens kit.

 What focal lengths/coatings

  939   Mon Aug 16 18:56:28 2010 1954 B-movieLab InfrastructureANTS!How do we get rid of ants?

ANTS!

Quote:

Quote:

It's that time of year again in Pasadena and the ants are going a bit crazy.  There are about 10 on the floor in the ATF, and no doubt there will soon be about 1e6 of them.  Do we have a standard ant removal scheme for cleanrooms?  The stuff I use at home is a spray and probably not very nice for optics.  We could use some of the slightly illegal ant chalk I guess.

 Steve has the cleanroom janitor mop the 40m floor in the LVEA/IFO room with diluted ant poison.

 

  1445   Fri Jul 8 12:19:46 2011 ???Mystery contributor???LaserGYRONoise in temp measurement...

??....this looks like its all ADC noise.

How about a plot showing the spectrum of the ADC noise and the sensor noise and the measured temperature noise all on one plot with the y-axis in units of temperature (i.e. not cubits/sqrt(furlong))

 

  82   Tue Sep 2 11:01:00 2008 AidanElectronicsFiberFiber stabilization loop diagram
Attached is a diagram of the current version of the stabilization loop. The beam (red) into the AOM is the output from the fiber and the other red line represents the reference beam.
  83   Tue Sep 2 15:06:42 2008 AidanLaserFiberAttempted calibration of fiber noise ... issues!

I tried to calibrate the fiber phase noise measurements in DTT by determining the fringe visibility (peak-to-peak size) in counts (to determine radians per count). I shifted the carrier on the VCO by 100Hz to 200.0001MHz and left the other signal generator (LO for both mixers) at exactly 200MHz. The demodulated signals from the PDs then looked like nice 100Hz sine waves. It was only then that I noticed that the amplitude of these sine waves was varying by 50% over a timescale of 20 seconds to a number of minutes.

NPRO level: 1.500A

I plotted 20 minutes worth of Max-Min data from the 2 PDs in DataViewer (see attached pdf) - there was 100Hz frequency difference between the signal generators for all but the first four minutes or so of this plot. In principle this plot shows the fringe visibility in counts and can be used for calibration purposes. As you can see, though, the pk-pk value is fluctuating with time. Presumably, as nothing has been altered on the table over the last week, the fringe visibility has been fluctuating for all previous noise measurements. Therefore only a rough calibration is possible. So here it is ...

C2: OMS-SUS_TOP1_INI_65536: pi radians: [-2750, -700] counts -> ~1500 urad/count
C2: OMS-SUS_TOP2_INI_65536: pi radians: [-3600, 4000] counts -> ~410 urad/count

Eric G happened to come in shortly after I had discovered this. He suggested that the mode-matching between the two beams may not be good enough. I will look into this.
Attachment 1: peak_peak_calibration.pdf
peak_peak_calibration.pdf
  85   Tue Sep 2 23:09:38 2008 AidanLaserFiberAttempted calibration of fiber noise. NPRO current = 1.903A

Quote:

I tried to calibrate the fiber phase noise measurements in DTT by determining the fringe visibility (peak-to-peak size) in counts (to determine radians per count). I shifted the carrier on the VCO by 100Hz to 200.0001MHz and left the other signal generator (LO for both mixers) at exactly 200MHz. The demodulated signals from the PDs then looked like nice 100Hz sine waves. It was only then that I noticed that the amplitude of these sine waves was varying by 50% over a timescale of 20 seconds to a number of minutes.

NPRO level: 1.500A

I plotted 20 minutes worth of Max-Min data from the 2 PDs in DataViewer (see attached pdf) - there was 100Hz frequency difference between the signal generators for all but the first four minutes or so of this plot. In principle this plot shows the fringe visibility in counts and can be used for calibration purposes. As you can see, though, the pk-pk value is fluctuating with time. Presumably, as nothing has been altered on the table over the last week, the fringe visibility has been fluctuating for all previous noise measurements. Therefore only a rough calibration is possible. So here it is ...

C2: OMS-SUS_TOP1_INI_65536: pi radians: [-2750, -700] counts -> ~1500 urad/count
C2: OMS-SUS_TOP2_INI_65536: pi radians: [-3600, 4000] counts -> ~410 urad/count

Eric G happened to come in shortly after I had discovered this. He suggested that the mode-matching between the two beams may not be good enough. I will look into this.


I repeated this measurement with the NPRO drive current set to 1.903A as per noise measurements made by Masha before she left. The same behaviour in the fringe visibility was seen. Additionally I noticed that the SR560 for channel 2 was periodically overloading. I didn't alter the gain on this amplifier because this was the state that the system was in for Masha's measurements. Attached is the max-min counts in the presence of a 100Hz frequency difference between the VCO and LO carrier frequencies. The following estimates for the radians/count calibrations are quite rough.


CH2: OMS-SUS_TOP1_IN1_65536: pi radians: [-4500, 1000] counts -> 570 urad/count
CH2: OMS-SUS_TOP2_IN1_65536: pi radians: [-6500, 6500] counts -> 240 urad/count
Attachment 1: peak_peak_calibration_1903mA.eps
peak_peak_calibration_1903mA.eps
  86   Wed Sep 3 13:35:56 2008 AidanLaserFiberCalibrated noise spectra ... does not agree with previous measurements
I recorded the closed loop, open loop and electronics noise in the current fiber stabilization system (single-pass through fiber, AOM after fiber). The NPRO current level was set to 1.500A. The calibrations were applied to convert from counts to radians (see here for details). The results are plotted in the attached diagram (available in JPG and EPS flavours for your viewing pleasure).

I'm concerned that the magnitude of these results are not consistent with the noise measurements made previously using the spectrum analyzer(?) ... (see here). It's probably something straightforward that I'm missing.
Attachment 1: noise_calibrated_080902.jpg
noise_calibrated_080902.jpg
Attachment 2: noise_calibrated_080902.eps
noise_calibrated_080902.eps
  88   Wed Sep 3 18:22:20 2008 AidanLaserFiberCalibrated noise spectra ... does not agree with previous measurements

Quote:
I recorded the closed loop, open loop and electronics noise in the current fiber stabilization system (single-pass through fiber, AOM after fiber). The NPRO current level was set to 1.500A. The calibrations were applied to convert from counts to radians (see here for details). The results are plotted in the attached diagram (available in JPG and EPS flavours for your viewing pleasure).

I'm concerned that the magnitude of these results are not consistent with the noise measurements made previously using the spectrum analyzer(?) ... (see here). It's probably something straightforward that I'm missing.


Apparently the previous measurements were with a different fiber.
  96   Mon Sep 22 20:20:25 2008 AidanLaserFiberFringe magnitude fluctuation investigation

The attached photo shows the fiber coupler in question and the ROLL angle adjustment and graduations (set to 120 degrees)

Using Masha's fiber stabilization setup, I looked at the interference fringe magnitude on transmission through the fiber. The frequency difference between the two arms in the MZ interferometer was (200MHz + 20Hz = 200.000020MHz). I demodulated the output by exactly 200MHz leaving a 20Hz signal on the output. I observed this output on an oscilloscope and monitored the fringe magnitude over time. In the past, the magnitude has been observed to drift (Eric G thinks this is most likely due to the input into the polarization maintaining fiber not being injected with the correct polarization). Over a period of 2-3 minutes I recorded the maximum and minimum fringe magnitudes (the maximum and minimum peak-to-peak values). I did this for several of ROLL rotation angles for the input fiber coupler (FC1). I only did a quick job of optimizing the output of the fiber when it was rotated to a new position, but I did secure it into that position once it was optimized.

Here are the results:
Fringe Size (Vpp)
ROLL ANGLE | MAXIMUM (V) | MINIMUM (V)
--------------------------------------------
120 deg | 3.27 | 0.04
139 deg | 4.00 | 1.60
150 deg | 4.74 | 2.64
165 deg | 4.94 | 3.62
180 deg | 4.42 | 3.88
195 deg | 3.80 | 3.48
210 deg | 3.36 | 2.54
225 deg | 2.53 | 1.47
240 deg | 1.84 | 0.68
255 deg | 1.46 | 0.15
---------------------------------------------

We can define the relative fluctuation in the fringe visibility/magnitude as the difference between the maximum and minimum divided by the maximum fringe size. The results are shown in the attached plot. It's obvious that the optimum rotation angle to be at is at arodun 190 degrees.
Attachment 1: fiber_coupler_rotation_angle_output_fluctuation.jpg
fiber_coupler_rotation_angle_output_fluctuation.jpg
Attachment 2: 00003.jpg
00003.jpg
  97   Tue Sep 23 10:15:15 2008 AidanLaserFiberFringe magnitude fluctuation investigation - why isn' the maximum 45 degrees from the minimum?

Quote:

The attached photo shows the fiber coupler in question and the ROLL angle adjustment and graduations (set to 120 degrees)

Using Masha's fiber stabilization setup, I looked at the interference fringe magnitude on transmission through the fiber. The frequency difference between the two arms in the MZ interferometer was (200MHz + 20Hz = 200.000020MHz). I demodulated the output by exactly 200MHz leaving a 20Hz signal on the output. I observed this output on an oscilloscope and monitored the fringe magnitude over time. In the past, the magnitude has been observed to drift (Eric G thinks this is most likely due to the input into the polarization maintaining fiber not being injected with the correct polarization). Over a period of 2-3 minutes I recorded the maximum and minimum fringe magnitudes (the maximum and minimum peak-to-peak values). I did this for several of ROLL rotation angles for the input fiber coupler (FC1). I only did a quick job of optimizing the output of the fiber when it was rotated to a new position, but I did secure it into that position once it was optimized.

Here are the results:
Fringe Size (Vpp)
ROLL ANGLE | MAXIMUM (V) | MINIMUM (V)
--------------------------------------------
120 deg | 3.27 | 0.04
139 deg | 4.00 | 1.60
150 deg | 4.74 | 2.64
165 deg | 4.94 | 3.62
180 deg | 4.42 | 3.88
195 deg | 3.80 | 3.48
210 deg | 3.36 | 2.54
225 deg | 2.53 | 1.47
240 deg | 1.84 | 0.68
255 deg | 1.46 | 0.15
---------------------------------------------

We can define the relative fluctuation in the fringe visibility/magnitude as the difference between the maximum and minimum divided by the maximum fringe size. The results are shown in the attached plot. It's obvious that the optimum rotation angle to be at is at arodun 190 degrees.


The reason that the output polarization wanders is as follows: the fiber is birefringent and will, in general, convert linearly polarized light into elliptically polarized light unless the input is aligned with the fast axis of the fiber. So, in this respect, it functions exactly like every other birefringent material. The fiber complicates matters because small changes in its length (e.g. due to temperature fluctuations) will vary the phase delay between the fast and slow axes and cause the ellipticity of the output light to fluctuate ... again, assuming that the light is not aligned with the fast axis.

So if the input field is mostly aligned with the fast axis (e.g. in the 175 - 205 degree range) then the output polarization fluctuates between being linearly polarized and slightly elliptically polarized. If it is far from being aligned then the polarization of the output is expected to fluctuate by a large amount.

Which leaves a problem ... shouldn't the maximum amount of polarization fluctuation occur at 45 degrees from the fast axis? After all, if the input field is 100% aligned to the slow axis then one would naively expect that the polarization should be insensitive to fluctuations in length. It might be time to get a PBS into the system to look at the output from the fiber.
  98   Tue Sep 23 12:10:08 2008 AidanLaserFiberMaximized fiber coupler ROLL angle.

Set the input fiber coupler roll angle to 190 degrees on the graduated scale. Rotated the half wave plate after the output of the fiber to maximize the fringe magnitude output from the MZ.

Vpp max = 4.52V (peak-to-peak value of demodulated output of PD with residual 20Hz signal)
Vpp min = 4.22V

Fringe magnitude fluctuation = 7% of maximum fringe magnitude.

(All this was running open loop in the fiber stabilization, by the way)
  100   Thu Oct 9 08:47:54 2008 AidanLaserFiberDismantled fiber stabilization setup


Packed up the current setup. Am going to rebuild with beam double passed through the fiber and an 80MHz AOM.
  102   Tue Nov 25 17:12:01 2008 AidanThings to BuyFiberResidual things to buy for FS

A large fraction of the equipment is already in the lab from Masha's experiment earlier in the year. The following is required for the latest design of the experiment. In the interim we can probably use the Marconi to drive AOM1.


Specifics
---------
2x Half wave plates - QWPO-1064-05-2-R10
1x Quarter wave plate - QWPO-1064-05-4-R10
3x rotation stages - New Focus 9401


General
-------
Partially transmitting retro-reflector
AOM # 2
Mode-matching lenses (possibly - might have enough downstairs)
RF photodiodes - (10-MHz InGaAs Photoreceiver (Free Space input) Model 2053-FS?)
VCO + power amp for AOM#1 - center frequency probably 77.5MHz, ~2W to AOM
Crystal oscillator + power amp for AOM#2 - probably 80MHz, ~2W to AOM
Oscillator for demod - probably 5MHz, 17dBm

What else? hmm ...
Attachment 1: adhikari_lab_v1C.jpg
adhikari_lab_v1C.jpg
  103   Tue Nov 25 17:30:32 2008 AidanLaserFiberPreliminary noise budgets for fibre stabilization

Here are some preliminary noise budgets for the FS experiment ... or rather, the setup shown in attached figure. Looks like the laser frequency noise dominates.
Not surprising given that the optical path length difference is ~150m.

The photodiode noise is not particularly high, although if we stabilize the frequency and intensity of the NPRO it might become a factor.

Anyway, the phase and frequency noise plots are attached. Will post references to the origin of the actual curves for the different noise sources soon.
Attachment 1: simulation_v1B.jpg
simulation_v1B.jpg
Attachment 2: phaseNoiseBudget-NPRO-PDA255.pdf
phaseNoiseBudget-NPRO-PDA255.pdf
Attachment 3: freqNoiseBudget-NPRO-PDA255.pdf
freqNoiseBudget-NPRO-PDA255.pdf
  104   Thu Jan 8 19:59:50 2009 AidanMiscGeneralEarthquake ...

Just felt the building shake. Didn't feel as a large as last year's quake.

Apparently a 5.0 in San Bernadino ...
  105   Wed Jan 14 11:33:58 2009 AidanThings to BuyFiberResidual things to buy for FS - QWPs, HWPs, output coupler

Quote:

A large fraction of the equipment is already in the lab from Masha's experiment earlier in the year. The following is required for the latest design of the experiment. In the interim we can probably use the Marconi to drive AOM1.


Specifics
---------
2x Half wave plates - QWPO-1064-05-2-R10
1x Quarter wave plate - QWPO-1064-05-4-R10
3x rotation stages - New Focus 9401


General
-------
Partially transmitting retro-reflector
AOM # 2
Mode-matching lenses (possibly - might have enough downstairs)
RF photodiodes - (10-MHz InGaAs Photoreceiver (Free Space input) Model 2053-FS?)
VCO + power amp for AOM#1 - center frequency probably 77.5MHz, ~2W to AOM
Crystal oscillator + power amp for AOM#2 - probably 80MHz, ~2W to AOM
Oscillator for demod - probably 5MHz, 17dBm

What else? hmm ...


Ordered the following:
2x Half wave plates - CVI - QWPO-1064-05-2-R10
1x Quarter wave plate - CVI - QWPO-1064-05-4-R10
3x rotation stages - New Focus - 9401
1x partially transmitting retro-reflector: CVI - PR1-1064-95-IF-1037 - 95% reflectance
  106   Wed Jan 14 18:14:23 2009 AidanThings to BuyFiberResidual things to buy for FS - extra photodiodes

Quote:

Quote:

A large fraction of the equipment is already in the lab from Masha's experiment earlier in the year. The following is required for the latest design of the experiment. In the interim we can probably use the Marconi to drive AOM1.


Specifics
---------
2x Half wave plates - QWPO-1064-05-2-R10
1x Quarter wave plate - QWPO-1064-05-4-R10
3x rotation stages - New Focus 9401


General
-------
Partially transmitting retro-reflector
AOM # 2
Mode-matching lenses (possibly - might have enough downstairs)
RF photodiodes - (10-MHz InGaAs Photoreceiver (Free Space input) Model 2053-FS?)
VCO + power amp for AOM#1 - center frequency probably 77.5MHz, ~2W to AOM
Crystal oscillator + power amp for AOM#2 - probably 80MHz, ~2W to AOM
Oscillator for demod - probably 5MHz, 17dBm

What else? hmm ...


Ordered the following:
2x Half wave plates - CVI - QWPO-1064-05-2-R10
1x Quarter wave plate - CVI - QWPO-1064-05-4-R10
3x rotation stages - New Focus - 9401
1x partially transmitting retro-reflector: CVI - PR1-1064-95-IF-1037 - 95% reflectance



Also ordered 2x Thorlabs - PDA10CS 17MHz InGaAs photodiodes
  114   Fri Apr 17 20:05:59 2009 AidanLab InfrastructureGeneralAnother workbench and a filing cabinet

We're starting to accumulate a lot of loose data sheets and other paraphernalia. We should arrange to get a small filing cabinet down here. I'm sure Office Depot can serve us well on that one.

Also DMass and I think we should get a third IAC Industries workbench (the white ones with the Linux machines on them).

A.

 

 

  122   Fri May 1 16:39:12 2009 AidanComputingCDSRCG make screwiness - how do i clean up old and failed makes?

Had problems compiling/making the Realtime Code Generator (RCG) example application in the document T080135-00-C.

Got Dmass onto the case and we tried the following things:
1. Renamed the file AFB.mdl so that it was lowercase: afb.mdl - result: 'make' still failed
2. Replaced the mux/demux elements in the ETMX subsystem with standard 8x8 matrices - called 'Matrix' and 'Matrix1' - result: 'make' still failed
3. Renamed the output elements in the ETMX subsystem so that there were no lowercase names: ULOut -> UL_OUT, UROut -> UR_OUT, etc. Result: 'make' still failed
4. I compared the 'make' output of making oms.mdl, which is a working version of the same example application, with the 'make' output of making afb.mdl. Initially the making of afb.mdl differed because it couldn't find the elements ETMX_Matrix and ETMX_Matrix1. I renamed these matrices in afb.mdl with all uppercase names (IN_MTRX and OUT_MTRX) and the make of afb.mdl progressed further before encountering an error and failing again.

At this point it gave the following complaints:
../AFB/AFB.c: In function `feCode':
../AFB/AFB.c:88: error: structure has no member named `AFB'

To be honest, I suspected that there was some residual junk code somewhere from all the previous failed compliations and the renaming of the filename from uppercase to lowercase

I copied the simuLink model afb.mdl to afc.mdl, a completely clean and shiny new name, and tried making afc.mdl instead. And it worked fine.

So the good news is that the simLink example I created makes and that 'make' itself is working fine.

The bad news is that some combination of the above actions has, presumably, left some junk files somewhere that are screwing up the making of afb.mdl. So ... how do i completely clean up an old and failed make?

  123   Tue May 5 14:43:05 2009 AidanComputingCDSRCG make screwiness - how do i clean up old and failed makes?

 

Found uninstall solution in DMass's elog entry:

 

Quote:

Had problems compiling/making the Realtime Code Generator (RCG) example application in the document T080135-00-C.

Got Dmass onto the case and we tried the following things:
1. Renamed the file AFB.mdl so that it was lowercase: afb.mdl - result: 'make' still failed
2. Replaced the mux/demux elements in the ETMX subsystem with standard 8x8 matrices - called 'Matrix' and 'Matrix1' - result: 'make' still failed
3. Renamed the output elements in the ETMX subsystem so that there were no lowercase names: ULOut -> UL_OUT, UROut -> UR_OUT, etc. Result: 'make' still failed
4. I compared the 'make' output of making oms.mdl, which is a working version of the same example application, with the 'make' output of making afb.mdl. Initially the making of afb.mdl differed because it couldn't find the elements ETMX_Matrix and ETMX_Matrix1. I renamed these matrices in afb.mdl with all uppercase names (IN_MTRX and OUT_MTRX) and the make of afb.mdl progressed further before encountering an error and failing again.

At this point it gave the following complaints:
../AFB/AFB.c: In function `feCode':
../AFB/AFB.c:88: error: structure has no member named `AFB'

To be honest, I suspected that there was some residual junk code somewhere from all the previous failed compliations and the renaming of the filename from uppercase to lowercase

I copied the simuLink model afb.mdl to afc.mdl, a completely clean and shiny new name, and tried making afc.mdl instead. And it worked fine.

So the good news is that the simLink example I created makes and that 'make' itself is working fine.

The bad news is that some combination of the above actions has, presumably, left some junk files somewhere that are screwing up the making of afb.mdl. So ... how do i completely clean up an old and failed make?

 

  124   Tue May 5 16:36:40 2009 AidanComputingCDSRealtime code generation (RCG) troubleshooting

Useful things to try when making Simulink models with RCG


1. When making a new model foo.mdl use the following text
make uninstall-daq-foo
make clean-foo foo install-foo
make install-daq-foo
make install-screens-foo


2. start the MEDM screen C2FOO_GDS_TP.adl

2. A. kill whatever is running:
e.g. on oms > killoms
       > killatf

2. B.  find the .ini (C2FOO.ini) and edit it so that at least one channel is acquiring - do this whenever an install or reinstall are run.
2. C. manually edit the master file in fb0 to point to C2FOO.ini
  /cvs/cds/caltech/target/fb/master
2. D. start foo on oms > startfoo

see if things start to light up on the MEDM screen C2FOO_GDS_TP.adl

check if the front end is running
      /sbin/lsmod
  - should see 'foofe' and 'gm' running

look at the log file in /cvs/cds/caltech/target/c2foo
 - log.txt - will either be a couple of lines with an error message or a lot of stuff that looks like things are working:


3. go to /etc/rc.local and add foo to file. file is read-only so use 'sudo vi rc.local'
e.g. /etc/setup_shmem.rtl ipc sas test oms atf afb afc foo&

update shared library index (see Tobin's entry)
   > /sbin/ldconfig


4. try a restart of oms
   > sudo reboot

try 'startfoo' again - hopefully at this stage parts of the MEDM screen should start lighting up


5. if still problems (parts of GDS MEDM screen are still white), try to reboot fb0
   > telnet fb0 8087
      > shutdown

 
try to start again
   > killfoo
   > startfoo


6. check last line of log file /cvs/cds/caltech/target/c2foo/log.txt -
might require BURT restore

go to C2FOO_GDS_TP.adl MEDM screen and set BURT restore value to 1

should be okay now ...
 

  130   Fri May 15 17:32:30 2009 AidanComputingFiberStarted screen for Fiber Stabilization - and claiming CDS channels

I'd like to use ADC channels 13-16 for the photodiodes in the FS experiment. Also going to use DAC channel 16 for feeding back to the AOM. We should decouple the signals on the MEDM screens so that you can't, inadvertantly, feed gyro error signals to the FS output.

Started work on a FS control screen (C2ATF_FS_CONTROL.adl shown below). It's accesible from the C2ATF_MASTER screen (also shown below). There won't be that much too it ... just an box allowing you to control the in-loop signals and the feedback to the frequency of the AOM. The lower box will simply be the input  signals from the out-of-loop PDs.

 

 

 

Attachment 1: Screenshot-C2ATF_FS_CONTROL.adl.png
Screenshot-C2ATF_FS_CONTROL.adl.png
Attachment 2: Screenshot-C2ATF_MASTER.adl.png
Screenshot-C2ATF_MASTER.adl.png
  134   Sat May 23 16:04:57 2009 AidanLaserFiberBlocking out FS experiment ...

 I've started to to block out the parts for the fiber stabilization experiment as in the attached layout ... basically to check that everything is there.

Nothing is aligned and some of the lenses are just standing in right now. 

The photos show before and after for the table. I think we're going to need a rack or bench nearby for scopes, analyzers, power supplies, etc.

Attachment 1: Table_Layout_v1.0.jpg
Table_Layout_v1.0.jpg
Attachment 2: photo.jpg
photo.jpg
Attachment 3: photo1.jpg
photo1.jpg
  135   Sat May 23 17:19:08 2009 AidanThings to BuyGeneralClamps, pedestals, mirror mounts, photodiodes

Unless there is another stash somewhere, we are now short of clamps (two or three are now spare), 3" pedestals (four or five spare), mirror mounts (maybe half a dozen left) and InGaAs photodiodes.

We should put together a general order for this stuff in the near future.

  136   Sat May 23 17:22:58 2009 AidanLaserFiberFS expt is blocked out

I have blocked out the FS experiment. The following stuff is not installed:

1. Partial reflector (PR1-1064-95-IF-1037)

2. A QWP

3. A second AOM at 80MHz

According to Techmart, I ordered the Partial Reflector and QWP back in January, however, I remember that CVI had contacted me about a couple of longer lead time items - can't quite remember what they were. Will check the delivery notes.

 

  137   Sat May 23 17:39:46 2009 AidanLaserFiberFS expt is blocked out

 

Quote:

I have blocked out the FS experiment. The following stuff is not installed:

1. Partial reflector (PR1-1064-95-IF-1037)

2. A QWP

3. A second AOM at 80MHz

According to Techmart, I ordered the Partial Reflector and QWP back in January, however, I remember that CVI had contacted me about a couple of longer lead time items - can't quite remember what they were. Will check the delivery notes.

 

 

 I checked my files and could find no record of the delivery of the QWP and the partial reflector from CVI. The purchase orders were PO S064180 and PO S064169, respectively.

 

  138   Mon May 25 16:31:36 2009 AidanLaserFiberPhoto of FS setup
Attachment 1: photo5.jpg
photo5.jpg
  148   Thu Jul 2 15:37:57 2009 AidanMiscFiberWeekly Report - query on previous reply

Quote:

Quote:
Most of this week was spent on three tasks: characterizing the beam divergence of the NPRO Laser and fitting a curve to the data, the progress report, and contending with serious computer problems. The information on the beam divergence can be accessed in a previous log. The waist size is around 120 micrometers, and according to a least-squares fit, it is located 21cm behind the aperture. My understanding of the fiber suppression setup and its relationship to the second-harmonic generation system was strengthened, but nowhere near completed, in the process of writing the progress report. We plan to send the NPRO beam through an AOM driven at f1, then double-pass it through a 50m fiber (not to be bent at a 90 degree angle as drawn in the meeting today) and another AOM driven at f2. This signal will be interferometrically mixed with the original beam from the NPRO, producing beats at 2(f2-f1), then run through a multiplying mixer driven at 2(f1-f2) and a low-pass filter so the final signal consists mostly of the noise acquired when travelling through the fiber. A computer characterizes this noise, and sends a signal to the first AOM which actuates on the original beam so as to suppress the noise. ********************NOTE: Aidan plans on changing the setup slightly, and I'll give the details on that in the next report************************* Finally, my computer acquired a terrible virus yesterday morning when I clicked on an innocuous-looking facebook message that was sent to my email and titled "hi." All of yesterday and the first part of today was spent rebuilding the computer. Don't trust facebook. I now have a centos operating system, so I'll be learning to use Linux fast (hopefully).

 FORMAT PLEASE!

 

Who was the author of the previous entry? It wasn't Connor apparently.

  150   Fri Jul 3 19:49:30 2009 AidanComputingDAQDAQ Map medm screen - Connectors and Channel names

I've created an medm screen that displays the current data channels associated with each of the connectors on the front of the DAQ. Basically its supposed to make it really easy to figure out what each channel in the DAQ physically corresponds to. I've added a link (DAQ MAP button) to it on the main medm screen

Eventually this should be automatically generated every time we rebuild the front end. I'd also like to include an indication on there of the units of each channel and whether they are in the frame or not.

medm screen: /cvs/cds/caltech/medm/c2/atf/C2ATF_DAQ_MAP.adl

Please do not edit this screen in the medm editor. I've added some comments to the file and moved the definition of each of the channels to the end of the file. The comments get erased when the screen is edited and the channel definitions get moved back to different places in the file.

 

Attachment 1: C2ATF_DAQ_MAP.png
C2ATF_DAQ_MAP.png
  151   Fri Jul 3 21:26:13 2009 AidanComputingDAQDAQ Map medm screen - added channel frame acquisition status

Quote:

I've created an medm screen that displays the current data channels associated with each of the connectors on the front of the DAQ. Basically its supposed to make it really easy to figure out what each channel in the DAQ physically corresponds to. I've added a link (DAQ MAP button) to it on the main medm screen

Eventually this should be automatically generated every time we rebuild the front end. I'd also like to include an indication on there of the units of each channel and whether they are in the frame or not.

medm screen: /cvs/cds/caltech/medm/c2/atf/C2ATF_DAQ_MAP.adl

Please do not edit this screen in the medm editor. I've added some comments to the file and moved the definition of each of the channels to the end of the file. The comments get erased when the screen is edited and the channel definitions get moved back to different places in the file.

 

 

I've added some indicators to the DAQ_MAP medm that show whether channels are saved to frame ("SAVED") or not ("LOST"). I'll have to add a routine to the frame builder start up so that these are updated whenever the frame builder is rebooted.

Attachment 1: C2ATF_DAQ_MAP_v1.1.png
C2ATF_DAQ_MAP_v1.1.png
  156   Tue Jul 7 09:26:48 2009 AidanComputingDAQFrame builder not restarting ...

 

I tried to reboot the frame builder last night, as below, and now it won't restart and I can't log into it. If I can find the box then I can try to physically reset it.

[controls@ws1 ~]$ telnet fb0 8087
dadq> shutdown
  157   Tue Jul 7 15:16:35 2009 AidanComputingDAQFrame builder not restarting ... fixed!

Fixed!

The problem was a typo that had cropped up in /cvs/cds/caltech/chans/daq/C2ATF.ini when I was editing this file. I had to fix that file and reboot oms to get the frame builder working again. Now it appears to be fine - I can telnet into fb0 again.

 

Quote:

 

I tried to reboot the frame builder last night, as below, and now it won't restart and I can't log into it. If I can find the box then I can try to physically reset it.

[controls@ws1 ~]$ telnet fb0 8087
dadq> shutdown

 

 

 

  165   Thu Jul 9 10:45:16 2009 AidanComputingDAQAlex's frame builder problem diagnosis ...

 

This from Alex: 

 

The filesystem is full. If you look at the log messages:

[controls@oms fb]$ pwd
/cvs/cds/caltech/target/fb
[controls@oms fb]$ tail -5 logs/daqd.log.19816 
[Thu Jul  9 10:07:51 2009] Couldn't open full frame file
`/frames/full/data38/.C-R-931194464-16.gwf' for writing; errno 28
[Thu Jul  9 10:07:51 2009] Couldn't open full trend frame file
`/frames/trend/second/data2/C-T-931194420-60.gwf' for writing; errno 28
[Thu Jul  9 10:08:07 2009] Couldn't open full frame file
`/frames/full/data38/.C-R-931194480-16.gwf' for writing; errno 28
[Thu Jul  9 10:08:23 2009] Couldn't open full frame file
`/frames/full/data38/.C-R-931194496-16.gwf' for writing; errno 28
[Thu Jul  9 10:08:39 2009] Couldn't open full frame file
`/frames/full/data38/.C-R-931194512-16.gwf' for writing; errno 28
[controls@oms fb]$ df -h /frames/
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                     275G  261G     0 100% /frames


I stopped the frame builder for now until we figure out the data
directories. Can I delete all the data in /frames/full and recreate a new
set of directories? Otherwise this is too messy to rearrange. Let me know.

-alex


On Wed, 8 Jul 2009, Aidan Brooks wrote:


Hi Alex,

I fixed the problem with being able to telnet into fb0. There was just a typo in the file:
/cvs/cds/caltech/chans/daq/C2ATF.ini
Once I fixed that the frame builder rebooted just fine.

The problem at the moment is that the data does not appear to be writing to file. If I rebuild the front end from the start, so I go to oms and run the following commands:

cd /cvs/cds/advLigo
make realclean
make atf
make install-atf
make install-daq-atf
make install-screens-atf

And if I edit the file C2ATF.ini so that a single channel, e.g. C2:ATF-CTRL_PMC_REFL_IN1_DAQ is set to acquire. 

and killatf, followed by startatf and reboot the frame builder

Then: the front end starts okay and I can see signals in the EPICS screen that make sense. I can run StripTool and see the real time time series of a channel, I can start dataviewer and see C2:ATF-CTRL_PMC_REFL_IN1_DAQ in the list of fast channels. I can run the realtime viewer in dataviewer and see that channel realtime in a Grace window. However, I cannot get a playback of that channel to work and if I run dtt I can only get a spectrum if I specify a start time for that spectrum within the last (approximately) 30s in the past.

The data rate in the .mdl simulink model is 16K, the data rate in the C2ATF.ini files is 16K, the data rate in the file:
/cvs/cds/caltech/target/fb/daqdrc is set to 16K and there are 120 data directories in the /frames/full directory.

I can't think of any reason why the data is not being written to file. Can you log in and figure out what's wrong? You should be able to get access via controls@131.215.114.183

Thanks for your help,
Aidan.
 

  166   Thu Jul 9 10:46:52 2009 AidanComputingDAQDeleted old /frame/full directories and rebuilt directory structure ...

 

This was also from Alex:

 

Too late, I deleted /frame/full data already, sorry.

So I changed the number of full frames dirs from 120 down to 60 and
restarted the frame builder and c2atf front-end. Looks like the data is
written out to disk now. Please check it out.

Alex

  168   Thu Jul 9 13:29:08 2009 AidanComputingDAQMore from Alex on frame builder disk being full

 Hey Alex,


I've got a couple of questions (just for my own understanding).

- I thought the frames were supposed to overwrite old data. Why then  
did the disk appear full? And is it likely to appear full in future?  
If so how do we deal with it?

I reduced the total number of data directories from 120 to 60. I think the
frame size has increased and  so the disk filled up. daqd program, the
version you have there, erases old frames based on total number of
directories, it doesn't look at the disk full percentage. I have a new
version which doesn't do that, so we may want to install that new version
at some point, especially when you guys decide to upgrade to the latest
real-time code generator software. The new version of daqd/nds is not
erasing anything but simply relies on a cron job to erase old files.

- why did you reduce the number of directories in /frame/full to 60?

Thanks for your help,
Aidan.
 

  183   Sun Jul 19 09:44:09 2009 AidanComputingGeneralAliases added for standard LIGO tools

 

I've updated the /home/controls/.bashrc file to include some aliases to standard ligo tools. These should now be accessible anywhere from the command line.

alias dtt="/bin/diaggui"
alias dmt="/bin/dmtviewer"
alias foton="/bin/foton"
alias dv="dataviewer"
 
StripTool is already accessible from the command line.

  192   Wed Jul 22 20:40:13 2009 AidanLab InfrastructurefubarFiling cabinet lock engaged ... with no key

This happened mysteriously and had absolutely nothing to with me. The fact that I was the last person to open the filing cabinet before this happened is circumstantial and beside the point.

Will get the lockshop onto this in the next couple of days. In the meantime, just try and exercise your clairvoyance.

  193   Thu Jul 23 07:22:35 2009 AidanComputingCDSChecked out the 40m MEDM screens from SVN to /cvs/cds/caltech/medm/c1

 

As title says ...

  194   Thu Jul 23 07:33:41 2009 AidanComputingCDSAdded C2 MEDM screens to 40m SVN.

 

I've added our medm screens from the ATF to the 40m SVN. They can be found in 

https://nodus.ligo.caltech.edu:30889/svn/trunk/medm/c2/atf/

  232   Thu Aug 6 09:55:39 2009 AidanComputingDAQAnd it all comes crashing down again ...

It appears that the frame builder has stopped writing to file again. Actually what I see if the following:

  1. I can't retrieve any data from the last couple of days in dataviewer or DTT
  2. I can see data from three days ago.

I'm not sure why this is. Perhaps the disk is full again. Restarting the frame builder didn't help so we need to start digging a little deeper I think.

  240   Mon Aug 10 08:43:22 2009 AidanLaserFiberDC intensity noise measurement over the weekend

 

Friday 7th Aug 2009
2009-08-08 00:18:45 UTC - switched to DC output of PD2 in C2:ATF-QPD_SEG4_IN1_DAQ
Gain is 2000x on SR560. Loop is closed with 10,000x gain. So capture a longer spectra of intensity noise and convert to phase noise taking into account gain, transimpedance difference between AC and DC channels and phase difference at mixer(s). (933 725 940)

6:56:10 UTC PM - saved spectra with uncalibrated DC noise in it. (although it's divided by 10050)
    - also running realtime long term 0.003Hz bandwidth measurement over the weekend

Monday 10th Aug 2009
8:28:00 AM - Laser OFF to get zero level for DC noise measurement. The DC-OUT from PD2 (out-loop) has been plugged into C2:ATF-QPD_SEG4_IN1_DAQ for the weekend.

Minute average time series of PD2 DC-out for last two days is shown in the attached plot from dataviewer.

Attachment 1: 2009-08-10_two_day_DC_level.pdf
2009-08-10_two_day_DC_level.pdf
  244   Mon Aug 10 20:14:11 2009 AidanLab InfrastructurefubarFiling cabinet lock engaged ... with no key

Quote:

This happened mysteriously and had absolutely nothing to with me. The fact that I was the last person to open the filing cabinet before this happened is circumstantial and beside the point.

Will get the lockshop onto this in the next couple of days. In the meantime, just try and exercise your clairvoyance.

 

 

Fixed! The key is now hanging in the second bay from the right above the main bench.

  248   Tue Aug 11 15:33:38 2009 AidanElectronicsGeneralMarconi Memory Settings 101 and 102

DMass and I have been using the Marconi a lot recently, each with different settings. I saved these into its memory and they can now be recalled easily by doing the following:
1. Press [RCL]
2. Type setting number
3. Press [ENTER]

Settings
DMass 35.5MHz - memory# 101
Aidan 80.0MHz - memory# 102

They are shown in full in the photos below ...

 

Attachment 1: Memory_101.png
Memory_101.png
Attachment 2: Memory_102.png
Memory_102.png
  249   Tue Aug 11 16:38:25 2009 AidanThings to BuyGeneralOrdered mixers, splitters, LPFs and HPFs

 

I've ordered the following:

Mini Circuits
--------------
- ZX05-1MHW-S+ (mixers) x4
- SHP-100+ (High pass filter) x4
- SLP-1.9+ (low pass filter) x4
- ZFSC-2-1W-S+ (splitter) x2

  250   Tue Aug 11 18:14:49 2009 AidanMiscGeneralHive of activity ...
Attachment 1: 00001.png
00001.png
  257   Wed Aug 12 11:19:57 2009 AidanThings to BuyGeneralNew Focus Order pending ...

Going to order 15x 2.5" pedestals from New Focus. Will submit order this afternoon.

  258   Wed Aug 12 14:12:22 2009 AidanThings to BuyGeneralNew Focus Order pending ...

Quote:

Going to order 15x 2.5" pedestals from New Focus. Will submit order this afternoon.

 never mind.

ELOG V3.1.3-