40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 278 of 335  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  8124   Wed Feb 20 21:56:08 2013 yutaUpdateAlignmentclipping centering checklist

I'm not sure about the OMC situation at 40m. I think there are no direct beam reflected back into IFO from OMC path. There must be some backscatter, but we have to open OMC chamber again to put a beam dump.
I don't think we want to put one in OMC path for this pump-down, but we can put a beam dump to dump reflected beam from mis-aligned SRM tomorrow, if available.

  9628   Wed Feb 12 14:59:36 2014 SteveUpdateSUSclipping removed from PRM oplev

 The input pointing of PRM oplev beam was streered just a touch to remove clipping from it's return. 

The spots  did not move visibly on these two lenses.  The spot diameter on the qpd is  ~1.5 mm,  65 micro W and 3440 counts.  

  9629   Wed Feb 12 19:37:05 2014 JenneUpdateSUSclipping removed from PRM oplev

I'm not happy with the beam position on that first lens, but since it's so crazy in the BS chamber, and the PRM oplev has something like 5 in-vac steering mirrors, I'm hesitant to suggest that we do anything about it until our next vent.  But we should definitely fix it.

  5709   Thu Oct 20 04:47:37 2011 kiwamuUpdateLSCclipping search round 1

[Koji / Kiwamu]

  We tried finding a possible clipping in the vertex part.

We couldn't find an obvious location of a clipping but found that the recycling gain depended on the horizontal translation of the input beam.

We need more quantitative examination and should be able to find a sweet spot, where the recycling gain is maximized.

 

(what we did)

  + locked the carrier-resonant PRMI.

  + with IR viewers we looked at the inside of ITMX, ITMY and BS chambers to find an obvious clipping.

    => found two suspicious bright places and both were in the ITMY chamber.

      (1) POY pick off mirror : looked like a small portion of a beam was horizontally clipped by the mirror mount but not 100% sure whether if it is the main beam or a stray beam.

      (2) The top of an OSEM cable connectors tower : although this is in the way of the SRC path and nothing to do with PRC.

 + Made a hypothesis that the POY mirror is clipping the main beam.

 + To reject/prove the hypothesis we shifted the translation of the incident beam horizontally such that more beam hits on the suspicious mirror

 + Realigned and relocked PRMI.

    => Indeed the recycling gain went down from 6 to 0.8 or so. This number roughly corresponds to a loss of about 50%.

         However the MICH fringe still showed a very nice contrast (i.e. the dark fringe was still very dark).

         Therefore our conclusion is that the POY mirror is most likely innocent.

  3368   Thu Aug 5 16:18:37 2010 AlastairUpdateGeneralclocks still not locked fully - hut removed

The rubidium clocks are still not quite locked together, though it is clear that the beat frequency has dropped a lot since yesterday.

I checked on the clocks and the 1pps sync light is on.  The clocks are really hot again though despite the gap left at the bottom of the igloo.  The side of the clocks were hot enough to not be touchable.

I made the executive decision that I would remove the hut just now.  We can let the clocks lock together and then put the hut back on just before measuring.  This way the hut will isolate from temperature fluctuations during the measurement but it won't be running at the hotter equilibrium temperature.  I hope that the temperature won't change too much during the measurement if we put the hut back on.

RA: Attachment deleted because it was in Postscript format. Also not allowed here are the Stone Tablet and Cave Painting formats.

  3377   Fri Aug 6 16:20:08 2010 ranaUpdateGeneralclocks still not locked fully - phase shifted

 I tried to get the clocks to be closer to 90 deg for the relative phase by adding some cable length to one of the lines, but they are still wandering too much. We need to use the serial interface and up the gain in their 1PPS locking loops.

  5613   Tue Oct 4 15:43:10 2011 KojiUpdateIOOclosed the shutter before the MC

The shutter before the MC was closed at 3:30 as I started working on the RFAM.

MC REFL (INLOCK): 0.6~0.7
MC REFL (UNLOCK): 6.9
MC TRANS: 50000~52000

  5617   Tue Oct 4 19:06:46 2011 KojiUpdateIOOclosed the shutter before the MC

Finished the work at 6:30

MC REFL (INLOCK): 0.50-0.52
MC REFL (UNLOCK): 6.9
MC TRANS: 54400~547000


RFAM level

Before the work: -48.5dBm for 1.07VDC (both 50Ohm terminated)

Right after the work: -80dBm for 0.896VDC (both 50Ohm terminated)
10min after:   -70dBm
1hour after:   -65dBm
3hours after: -62dBm
1day after (Oct 5, 20:00):    -62.5dBm
2days after (Oct 6, 23:20): -72.5dBm
3 days after (Oct 7, 21:00): -57.8dBm

Quote:

The shutter before the MC was closed at 3:30 as I started working on the RFAM.

MC REFL (INLOCK): 0.6~0.7
MC REFL (UNLOCK): 6.9
MC TRANS: 50000~52000

 

  12705   Thu Jan 12 10:14:49 2017 SteveHowTosafetyclosing a door

The door was not locked this morning.

Please do not use this door if you can not close it!

Last person leaving the lab should check that the latch is cut by the strike plate.

  12706   Thu Jan 12 13:43:02 2017 ranaHowTosafetyclosing a door

This is one of those unsolved door lock acquisition problems. Its been happening for years.

Please ask facilities to increase the strength of the door tensioner so that it closes with more force.

  12707   Thu Jan 12 13:45:58 2017 SteveHowTosafetyclosing a door

It was requested this morning.

Quote:

This is one of those unsolved door lock acquisition problems. Its been happening for years.

Please ask facilities to increase the strength of the door tensioner so that it closes with more force.

 

  8785   Fri Jun 28 14:57:15 2013 SteveUpdateGeneralclosing lab doors

I found the south end emergency doors not latched completely. There was a ~ 3/8" vertical gap from top to bottom.

Please pull or push  doors harder if they not catch fully.

  6072   Mon Dec 5 19:21:55 2011 kiwamuUpdateLSCcoarse beat note signal : ADC limited above 30 Hz

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

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

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

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

 

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

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

   (2) Redesign of the servo filter

 

Here is a brief noise budget of the coarse sensor.

Yarm_ALS_coarse.png

Gray curve: free running noise when no servo is applied

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

Red curve : ADC noise of the coarse discriminator

Quote from #6071

 So far I still kept failing to increase the UGF of the ALS servo for some reason (see #6024).

  3850   Wed Nov 3 02:37:39 2010 yutaSummaryGreen Lockingcoarse locked green beat frequency

(Kiwamu, Yuta)

We succeeded in coarse locking the green beat frequency, using a frequency counter and feeding back the signal to the X-end laser temperature.

Setup:
  beat note -> RF PD -> SHP-25 -> SLP-100 -> ZFL-1000LN -> ZFL-1000LN -> ZFL-500LN -> ZFRSC-42 -> SBP-70 -> ZFRSC-42 -> SR620 -> c1psl(C1:PSL-126MOPA_126MON)
  c1auxey(C1:LSC-EX_GREENLASER_TEMP) -> X-end laser temp

  The frequency counter SR620 converts the beat frequency to voltage.
  We added some filters (SHP-25, SLP-100, SBP-70). Otherwise, SR620 doesn't count the frequency correctly.

What we did:

  1. Getting green beat note again
     Set PSL laser temp to 31.81 °C and X-end laser temp to 37.89 °C.
     Set PPKTP crystal temp to 37.6 °C, which maximizes output green beam power.

  2. ADC channel and DAC channel
     Disconnected one channel going into VME-3123 (at 1X1) and used c1psl's C1:PSL-126MOPA_126MON as ADC channel for the output from SR-620
     Made a new DAC channel on c1auxey named C1:LSC-EX_GREENLASER_TEMP, and disconnected one channel from VME-4116 (at 1X9) to use it as DAC channel for X-end laser temperature control.

  3. Coarse lock by ezcaservo
     Ran;
        ezcaservo C1:PSL-126MOPA_126MON -s 150 -g -0.0001 C1:LSC-EX_GREENLASER_TEMP
     "-s" option is a set value. The command locks C1:PSL-126MOPA_126MON to 150 (in counts), using 0Hz pole integrator.

Result:
  The beat frequency locked on to ~77MHz. The frequency fluctuation of the beat note during the servo is ~3MHz with ~10sec timescale.
  VCO has  ~+/-5MHz range, so this coarse locking meets the requirement.

  Here's a plot of the error signal and feed back signal;
  Screenshot_LowFreqLock.png

  3851   Wed Nov 3 03:00:47 2010 KojiSummaryGreen Lockingcoarse locked green beat frequency

Wow! Great guys!!

Can I expect to see the spectra of the frequency counter output with and without the servo?

RA: I think the SBP-70 is a bad idea. It limits the capture range. So does the SHP-25. You should instead just use a DC-block; the SR620 should work from 1-200 MHz with no problems.

Also, we have to figure out a better solution for the DAC at the ends: we cannot steal the QPD gain slider in the long run and the 4116 DAC at the ends has all 8 channels used up. Should we get the purple box for testing or should we try to use the fast DAC in the EX IO chassis as the actuator?

  6779   Thu Jun 7 05:39:41 2012 yutaUpdateGreen Lockingcoarsely stabilized Y arm length with ALS

I coarsely stabilized Y arm length to off resonance point for IR using ALS.
Currently, ASL servo loop is unstable and oscillates so much that I can't hold the length to the resonance point.
We need more investigation on the servo loop before doing the mode scan.

Below is a snapshot of ALS medm screens and time series data of the error signal for ALS coarse loop (C1:ALS-BEATY_COARSE_I_ERR) and IR transmission for the Y arm (C1:LSC-TRY_OUT) when I turned the servo on.

MyFirstALS20120607.png

 

Note:
  I took off amplifiers right after the beat PD on PSL table.
  Also, I reverted the gain change Jenne made last night (elog #6750), because they no longer show overload lights.

  9087   Wed Aug 28 23:09:55 2013 jamieConfigurationCDScode to generate host IPC graph
  13140   Tue Jul 25 00:03:01 2017 ranaOmnistructureTreasurecoffee pot lid

I have recommissioned the Zojirushi coffee pot lid. You may, once again, align the dots in order to make the carafe pourable.

Details:

The Zojirushi lid is a two part mechanism:

  1. The top part of the lid must be removed for cleaning.
  2. When replacing the lid the two components must be aligned to < 3 mrad precision so that the "teeth" are able to land in the groove.
  3. There is a 4-fold degeneracy in this process. To break the degeneracy, align the dot on top with the spout gap (visible from the bottom view).
  4. After proper alignment and mating, the two parts should snap together and the relative alignment wiggle available should be < 2 mrad.
  5. After screwing the two-piece lid onto the carafe, ensure that the 2 dots are separated by < 170 deg in the closed position.
  5816   Fri Nov 4 21:52:58 2011 DenUpdateAdaptive Filteringcoherence

[Mirko, Den]

We still think about the coherence between seismic noise and mode cleaner length. We beleive that

1. Below ~0.1 Hz tilt affects on the seismometers as was simulated http://nodus.ligo.caltech.edu:8080/40m/5777

2. From 0.1 to 1 Hz is an interesting region. We try to figure out why we do not see any coherence here. Tilt does not seem to dominate.

At 1 Hz coherence might be lost because of the sharp resonance. For example, if the mirror is suspended to the platform by wires with f = 1 Hz and Q = 1000, then the coherence between platform motion and mirror motion will be lost as shown on the figure below.

mirror_platform.jpg

For this reason we tried to "help" to the adaptive filter to guess transfer function between the ground motion and mirror motion by multiplying seimometer signal by the platform -> mirror transfer function. As we do not know exactly eigen frequency and Q of the wires, we did a parametric simulation as shown on the figure below

coherence.jpg

The maximum coherence that we could achieve with treak was 0.074 compared to 0.056 without. This was achieved at f=1.0011 Hz but with surprisingly high Q = 330. And though this did not help, we should keep in mind the tecnique of "helping" the adaptive filter to guess the transfer function if we partly know it.

Another unexpected thing is that we see come coherence between gur1_x and mode cleaner WFS pitch signal at frequencies 0.1 - 1 Hz

Screenshot-4.png

 

 

 From this we can suggest that either mode MC_F channel does not completely reflect the mc length at low frequencies or WFS2 shows weard signal.

  5825   Sun Nov 6 21:09:03 2011 ranaUpdateAdaptive Filteringcoherence

Quote:

[Mirko, Den]

We still think about the coherence between seismic noise and mode cleaner length. We beleive that

The 'helping' trick is a good one: we should use our best guess for the stackTF and the pendulumTF and put it into the IIR filter bank to pre-filter the seismometer signals before they get to the MC mirrors. Also should remember that the signal we send to suppress the seismic motion is applied to the pendulum as a force, not a displacement.

The 3 Hz fast cutoff in the MC_F signal is a good clue. It means that at low frequencies, perhaps the noise source is going through a digital 3 Hz elliptic or Chebychev filter.

  6065   Sat Dec 3 18:29:20 2011 DenUpdateAdaptive Filteringcoherence

I've looked through the coherence between the MC length and seismometers after the if-statement problem was fixed. Coherence improved for all seismometers but is still not 1. It is possible that contribution from X, Y, Z directions split the coherence between them but at ~0.2-03 Hz we do not see much coherence for all these directions.

coh_mcl_seis.pdf

I looked at the coherence between MC2 OSEM signal and MC_F when the AUTO LOCKER is ON and OFF. I thought that we'll ses the same coherence for both regimes as laser is locker to the MC length. However, I figured out the coherence is worse when AUTO LOCKER is ON at frequencies 0.2-0.3 Hz.

sensor_locker.pdf

The first idea that comes to mind is that when feedback to the laser is provided, the pressure to the mirrors from the laser beam is changed.

  2206   Mon Nov 9 01:52:56 2009 ranaUpdatePEMcoherence v. time for 2 accelerometers

I used the coh_carpet.m function from the mDV to calculate this plot:

coh_carpet('C1:PEM-ACC_MC1_X','C1:PEM-ACC_MC2_X',gps('now - 3 days'),3600*12,4,10,64)

It shows the coherence v. time of two of our X-direction accelerometers starting around 1AM on Friday and going for 12 hours.

I'm not sure what it means exactly, but it looks like the coherence is relatively steady as a function of time. I will need more RAM than Rosalba or a smarter code to calculate longer time stretches.

  13417   Wed Nov 8 12:19:55 2017 gautamUpdateSUScoil driver series resistance

We've been talking about increasing the series resistance for the coil driver path for the test masses. One consequence of this will be that we have reduced actuation range.

This may not be a big deal since for almost all of the LSC loops, we currently operate with a limiter on the output of the control filter bank. The value of the limit varies, but to get an idea of what sort of "threshold" velocities we are looking at, I calculated this for our Finesse 400 arm cavities. The calculation is rather simplistic (see Attachment #1), but I think we can still draw some useful conclusions from it:

  • In Attachment #1, I've indicated with dashed vertical lines some series resistances that are either currently in use, or are values we are considering.
  • The table below tabulates the fraction of passages through a resonance we will be able to catch, assuming velocities sampled from a Gaussian with width ~3um/s, which a recent ALS study suggests describes our SOS optic velocity distribution pretty well (with lcoal damping on).
  • I've assumed that the maximum DAC output voltage available for length control is 8V.
  • Presumably, this Gaussian velocity distribution will be modified because of the LSC actuation exerting impulses on the optic on failed attempts to catch lock. I don't have a good model right now for how this modification will look like, but I have some ideas.
  • It would be interesting to compare the computed success rates below with what is actually observed.
  • The implications of different series resistances on DAC noise are computed here (although the non-linear nature of the DAC noise has not been taken into account).
Series resistance [ohms] Predicted Success Rate [%] Optics with this resistance
100 >90 BS, PRM, SRM
400 62 ITMX, ITMY, ETMX, ETMY
1000 45 -
2000 30 -

So, from this rough calculation, it seems like we would lose ~25% efficiency in locking the arm cavity if we up the series resistance from 400ohm to 1kohm. Doesn't seem like a big deal, becuase currently, the single arm locking

  10563   Fri Oct 3 10:10:37 2014 SteveUpdateVACcold cathode gauge reading switched

 

We have two cold cathode gauges at the pump spool and one  signal cable to controller. CC1  in horizontal position and CC1 in vertical position.  

CC1 h started not reading so I moved cable over to CC1 v

  7044   Fri Jul 27 14:28:36 2012 steveUpdateVACcold cathode gauges

Our cold cathode 423 gauges are 10 years old. They get insulated by age and show no ionization current.  We should replace them at the next vent. I'm buying 4 at $317ea

 

  11625   Mon Sep 21 11:12:14 2015 SteveUpdateVACcold cathode is flaky

CC4 cold cathode gauge jump triggered interlock to close VM1 valve to protect the RGA.

The IFO pressure is 1e-5 Torr

Vac normal was recovered by opening VM1

 

  11633   Tue Sep 22 08:58:38 2015 SteveUpdateVACcold cathode is flaky

The cold cathode gauge is back to normal. cc4 is the last gauge is "functioning"

MKS is not responding. The spare controller and gauges are back for repair.

 

  11644   Fri Sep 25 17:00:38 2015 SteveUpdateVACcold cathode is flaky

The IFO pressure is estimated ~1E-6 Torr with modified Vac normal valve configuration.

CC4 is in a jumping mode between 2e-5 and 1e-6 Torr

 Pressure based interlock kicks in to close VM1   at 2e-5 Torr to protect the RGA.

I did open VM1 repeatedly in the last few mornings but as cc4 jumps VM1 closes.

As VM1  closed to RGA scans are not seeing the IFO. I will look at some scans on Monday.

Mean while I opened VM2 to lower the pressure for the RGA. This change will be read by "Current Status: Undefined State"

So do not panic, the IFO pressure is normal.

I need someone's help to raise the interlock threshold to 5e-5 Torr

I'm buying a new cold cathode gauge on Monday.

 

note: cc1 is out of order!

         just read P1  the pressure is < 7e-4 Torr  This gauge is very reliable and it is at the low end of it's range.

 

  4424   Tue Mar 22 16:39:51 2011 kiwamuUpdateGreen Lockingcomaprator installed : 80 pm residual displacement

 A comparator has been installed before the MFDs (mixer-based frequency discriminator) to eliminate the effect from the amplitude fluctuation (i.e. intensity noise).

As a result we reached an rms displacement of 580 Hz or 80 pm.

 

(differential noise measurement)

noise_curve20110322.png

  Here is the resultant plot of the usual differential noise measurement.

The measurement has been done when the both green and red lasers were locked to the X arm.

In the blue curve I used only MFD. In the black curve I used the combination of the comparator and the MFD.

Noise below 3 Hz become lower by a factor of about 4, resulting in a better rms integrated from 40 Hz.

Note that the blue and the black curve were taken while I kept the same lock.

A calibration was done by injecting a peak at 311 Hz with an amplitude of 200 cnt on the ETMX_SUS_POS path.

 

(installation)

  Yesterday Koji modified his comparator circuit such that we can take a signal after it goes thorough the comparator.

The function of this comparator is to convert a sinusoidal signal to a square wave signal so that the amplitude fluctuation doesn't affect the frequency detection in the MFD.

I installed it and put the beat-note signal to it. Then the output signal from the comparator box is connected to the MFDs.

The input power for the comparator circuit has been reduced to -5 dBm so that it doesn't exceeds the maximum power rate.

  13954   Wed Jun 13 11:59:03 2018 keerthanaUpdateelogcommand line enabled code for frequency scanning

I have modified the code for frequency scanning and have made it completely command line enabled. The code is written in python. It is saved in the name "frequency_scanning_argparse.py". I have uploaded it to the Mode-Spectroscopy Github repository.

Inorder to use this code there are two ways.

1. We can mention the ' frequency' on which marconi need to work. Then it will change the marconi frequency to that perticular value.

eg: Type in the terminal as follows for changing the marconi frequency to 59 Mhz.

python frequency_scanning_argparse.py 59e6

2. Inorder to give a scan to the marconi frequency, provide the 'start frequency', 'end frequency' and the 'number of points' in between. This will be more conveniant when we want to run the scan in different ranges.

eg: Type in the terminal as follows for a start frequency of 59 Mhz, end frequency of 62MHz and number of points in between equal to 1000.

python frequency_scanning_argparse.py 59e6 62e6 1000

In both cases the code will show you the frequency of the marconi before we run this code and it will change the marconi frequency to the desired frequency.

  9468   Fri Dec 13 18:03:00 2013 DenUpdateIOOcommon mode servo

Quote:

Well, let's see how the CM servo can handle this.
The key point here is that we have enough data to start the design of the CM servo.

 It seems to me that current design of the common mode servo is already fine. Attached plots show common mode open and closed loop transfer function.

Frequency response of the servo is taken from the document D040180. I assumed coupled cavity pole to be ~100 Hz.

The only question is if our EOM has enough range. Boost 2 increases noise injection by 10 dB in the frequency range 20-50 kHz. Boost 3 has even higher factor.

  9470   Fri Dec 13 23:07:04 2013 KojiUpdateIOOcommon mode servo

Looks good.

Once the control cable (bakplane cable) is identified, we can install the module to the LSC analog rack.

We should be able to test the CM servo with either POX or POY and only one correspoding arm without modifying the servo TF.
Just for this test, we don't need to use MCL.

  9472   Sat Dec 14 11:56:54 2013 ranaUpdateLSCcommon mode servo

Quote:

 

 It seems to me that current design of the common mode servo is already fine. Attached plots show common mode open and closed loop transfer function.

 These seem like pretty terrible loop shapes. Can you give us a plot with the breakdown of several of the TFs and some .m file?

We should be able to estimate the noise coming out of the MC using the single arm and then make a guess for the CM loop gain requirement. There's no reason to keep the old Boost shapes; those were used in the old MC configuration which had a RefCav. In addition to minimizing the EOM range, we should also minimize the AO signal as Koji has pointed out. In practice, I've seen that using ~300 Hz of offset makes no harm with 4 kHz MC pole.

  9474   Sat Dec 14 14:21:46 2013 DenUpdateLSCcommon mode servo

Quote:

 

 These seem like pretty terrible loop shapes. Can you give us a plot with the breakdown of several of the TFs and some .m file?

Attached is matlab code that I used

 % IMC OL
G = zpk(-2*pi*8964, 2*pi*[-10; -10; -10; -1000; -274000], db2mag(242.5)) * ...
    tf([1 0.8*1.55e+05 3.1806e+10], 1);

% CARM PATH
CARM = G/(1+G);

% Common mode boosts
BOOST = zpk(-2*pi*4000, -2*pi*40, 1);
BOOST1 = zpk(-2*pi*20000, -2*pi*1000, 1);
BOOST2 = zpk(-2*pi*20000, -2*pi*1000, 1);
BOOST3 = zpk(-2*pi*4500, -2*pi*300, 1);

% Coupled cavity pole
CCPole = zpk([], -2*pi*100, 2*pi*100);

% Servo gain
Gain = db2mag(43);

% CARM OL with boosts
H = CARM * CCPole * BOOST * Gain;
H1 = H * BOOST1;
H2 = H1 * BOOST2;
H3 = H2 * BOOST3;

% Plot
% bode(H, H1, H2, H3, 2*pi*logspace(3, 5, 10000));
% bode(1/(1+H), 1/(1+H1), 1/(1+H2), 1/(1+H3), 2*pi*logspace(3, 5, 10000));

  4161   Sun Jan 16 02:20:59 2011 SureshUpdateLockingcomparing the PSL with the X-end-NPRO through the green beat

Objective:

      We wish to study the coherence of the two NPROs i.e. PSL and the X-end-NPRO by locking both of them to the X-arm and then observing the green beat frequency fluctuations. 

What we did:

   a) locked the PSL to the X-arm as described in 4153

   b) locked the x-end-NPRO to the X-arm with a PDH lock to the reflected green from the ETMX

   c) Obtained the green beat signal with a spectrum analyser as described in 3771

Observations:

   Please see the attached screen shots from the spectrum analyser.   They are taken with different BW and sweep range settings.  They give a estimate of the width of the green beat signal and the range of the frequency fluctuations of the beat-note.

P1160510.JPGP1160511.JPGP1160515.JPG

P1160516.JPG

 

Estimates:

   a) width of the beat note is less than 6KHz if measured over time scales of a few milli seconds

   b) the frequency fluctuations of the beat note are about 100KHz over time scales longer than 100ms

Next Step:

    We wish to record the beat note frequency as a function of time in order to establish the stability over time scale of a day.

 

 

  4166   Wed Jan 19 03:37:30 2011 SureshUpdateLockingcomparing the PSL with the X-end-NPRO through the green beat

 

 

 [Kiwamu, Suresh]

Today we attempted to convert the beat-note frequency into an analog voltage using the SR620 frequency counter.

First an observation: the stability of the green beat was seen to be much better than the 100kHz fluctuation seen yesterday. Probably because Kiwamu noticed that one of the MC mirrors had a large variance in its motion and changed the  gain and filter parameters to decrease this.  The PSL was therefore more stable and the green peak fluctuation was less than 10kHz over time scales of a few seconds. 

SR620 D/A output resolution given by the manufacturer is 5mV over the -10 to +10V range and this range corresponding to 300MHz.  We, however saw fluctuations of 100mV on the screen which looked as if they corresponded to the  least significant bit.  This would imply a resolution of 1.5MHz at this range.   Even if the manufacturer's claim was true it would lead to a resolution of 75kHz, far in excess of the required resolution a few hundred Hz.

We therefore require to set up the VCO-PLL to obtain a finer frequency resolution.

In the mean time the green beat drifted beyond the 100MHz detection band of the green-PD.  So we changed the x-end-NPRO temperature by -0.05 to bring it back into the detection band.

 

We are also considering, Rana and Koji's suggestion of using a set of 14 flip-flops to divide the ~80MHz beat frequency so that it comes down to about 4kHz.  This could then be sampled by the usual 16-bit, 64kSa/s ADC cards and brought into the digital domain where further digital processing would be needed to extract the the required frequency variations  in the 0 to 10kHz band.  Found a nice paper on this object

  181   Fri Dec 7 18:28:30 2007 tobinUpdateComputer Scripts / Programscompiled matlab hoses itself
Andrey pointed out to me that some matlab functions in the Signal Processing Toolbox were dying with errors. Looking into the .m file (identified using the "which" command), I was surprised to see binary garbage rather than glistening, clear Matlab prose. Then I noticed the directory in which it was finding the .m file:
>> which decimate
/cvs/cds/caltech/apps/mDV/extra/linetrack_c_mcr/toolbox/signal/signal/decimate.m
See that "linetrack_c_mcr" directory? This is what is generated when a "compiled" (grumble) Matlab program is run--it decompresses itself into a subdirectory containing weird semi-compiled binary .m files. Unfortunately this is somehow getting incorporated into the matlab path. (I assume there is something in mDV that says "put all subdirectories into the path.")

I hate the Matlab compiler.
  182   Fri Dec 7 18:31:30 2007 tobinUpdateComputer Scripts / Programscompiled matlab hoses itself
Addendnum. The reason the linemon_mcr command was in the path was because of the user issuing the command "addpath(genpath(pwd))" where genpath(D) "returns a path string starting in D, plus, recursively, all the subdirectories of D."

The Matlab compiler is still bad, however.
  9432   Mon Dec 2 14:24:10 2013 SteveUpdateCDScomputer problems

Rack 1x6 is very noisy.

 SunFire X4600 computer: FB (directly below Megatron) has it's yellow warning light on. It must be loosing one of it's  fan bearings.

 

Jetstore's error message: IDE channel #2 reading error

  9436   Tue Dec 3 17:08:06 2013 KojiUpdateCDScomputer problems

It seems that the front fan unit was running at the full speed. The fan itself seems still OK.

I talked with Jamie and make a power cycling (i.e. shutdown gracefully, unplug the power supply cables (x4), plug them in again, and pushed the power button)

The warning signal went off and the fan is quiet. FOR NOW.

Now, daqd and ndsd is down.

FB cannot mount /opt/rtcds and /cvs/cds during its boot.

After mounting these manually, I tried to run /opt/rtcds/caltech/c1/target/fb/start_daqd.inittab and /opt/rtcds/caltech/c1/target/fb/start_nds.inittab
but they don't keep running.

I'll be back to this issue tomorrow with Jamie's help.

  1771   Tue Jul 21 18:46:47 2009 steveConfigurationComputerscomputers are down

All suspentions are kicked up. Sus dampings and  oplev servos turned off.

c1iscey and c1lsc are down. c1asc and c1iovme are up-down

  1772   Wed Jul 22 01:57:19 2009 AlbertoConfigurationComputerscomputers are down

Quote:

All suspentions are kicked up. Sus dampings and  oplev servos turned off.

c1iscey and c1lsc are down. c1asc and c1iovme are up-down

 The computers and RFM network are up working again. A boot fest was necessary.Then I restored all the parameters with burtgooey.

The mode cleaner alignment is in a bad state. The autolocker can't get it locked. I don't know what caused it to move so far from the good state that it was till this afternoon.  I went tuning the periscope but the cavity alignment is so bad that it's taking more time than expected. I'll continue working on that tomorrow morning.

  1773   Wed Jul 22 09:04:10 2009 AlbertoConfigurationComputerscomputers are down

Quote:

Quote:

All suspentions are kicked up. Sus dampings and  oplev servos turned off.

c1iscey and c1lsc are down. c1asc and c1iovme are up-down

 The computers and RFM network are up working again. A boot fest was necessary.Then I restored all the parameters with burtgooey.

The mode cleaner alignment is in a bad state. The autolocker can't get it locked. I don't know what caused it to move so far from the good state that it was till this afternoon.  I went tuning the periscope but the cavity alignment is so bad that it's taking more time than expected. I'll continue working on that tomorrow morning.

 I now suspect that after the reboot the MC mirrors didn't really go back to their original place even if the MC sliders were on the same positions as before.

  1776   Wed Jul 22 11:14:11 2009 AlbertoConfigurationComputerscomputers are down

Quote:

Quote:

Quote:

All suspentions are kicked up. Sus dampings and  oplev servos turned off.

c1iscey and c1lsc are down. c1asc and c1iovme are up-down

 The computers and RFM network are up working again. A boot fest was necessary.Then I restored all the parameters with burtgooey.

The mode cleaner alignment is in a bad state. The autolocker can't get it locked. I don't know what caused it to move so far from the good state that it was till this afternoon.  I went tuning the periscope but the cavity alignment is so bad that it's taking more time than expected. I'll continue working on that tomorrow morning.

 I now suspect that after the reboot the MC mirrors didn't really go back to their original place even if the MC sliders were on the same positions as before.

 Alberto, Rob,

we diagnosed the problem. It was related with sticky sliders. After a reboot of C1:IOO the actual output of the DAC does not correspond anymore to the values read on the sliders. In order to update the actual output it is necessary to do a change of the values of the sliders, i.e. jiggling a bit with them.

  3493   Tue Aug 31 10:44:17 2010 steveUpdatePEMconcrete sealed

The PSL -leg concrete was sealed with a single coat of SCOFIELD Cureseal-S to minimize shedding of particles.

The optical table was covered  and optics were removed from the shelf. Accelerometers were turned off.

  12825   Mon Feb 13 17:19:41 2017 yinziConfiguration configuring ethernet for raspberry pi

Gautam and I were able to get the Raspberry Pi up and running today, including being able to ssh into it from the control room.

Below are some details about the setup/procedure that might be helpful to anyone trying to establish Ethernet connection for a new RPi, or a new operating system/SD card.

Here is the physical setup:

 

The changes that need to be made for a new Raspbian OS in order to communicate with it over ssh are as follows, with links to tutorials on how to do them:

1. Edit dhcpcd.conf file: https://www.modmypi.com/blog/how-to-give-your-raspberry-pi-a-static-ip-address-update

2. Edit interfaces file: https://www.mathworks.com/help/supportpkg/raspberrypi/ug/getting-the-raspberry_pi-ip-address.html

3. Enable ssh server: http://www.instructables.com/id/Use-ssh-to-talk-with-your-Raspberry-Pi/

 

The specific addresses for the RPi we set up today are:

IP Address: 192.168.113.107

Gateway/Routers/Domain Name Servers: 192.168.113.2

Netmask: 255.255.255.0

GV: I looked through /etc/var/bind/martian.hosts on chiara and decided to recycle the IP address for Domenica.martian as no RPis are plugged in right now... I'm also removing some of the attachments that seem to have been uploaded multiple times.

  3862   Thu Nov 4 17:24:49 2010 steveUpdateGeneralconflat flanges for MIT

8 pieces of 10" CF blanks were shipped to MIT

  9802   Fri Apr 11 14:57:53 2014 steveUpdateLSCcongratulation

 

 

  9803   Fri Apr 11 16:04:31 2014 KojiUpdateLSCcongratulation

It's just one of the stepping stones, but not yet a mile stone.
Keep going forward!

  990   Thu Sep 25 03:12:13 2008 ranaSummaryComputersconlog and linux1
It would be nice to have conlog from outside. Right now its on linux1 and so its unavailable. To
test it for speed we ran the command line conlog on linux1, linux2, and nodus.

It was slightly faster on nodus than linux1, implying that its not a network speed issue. It was
phenomenally slower on linux2.

I used the command '/sbin/lspci -vvv' to check what network cards are installed where. As it turns
out, linux2 has a GigE card, but linux1, our NFS server, has only a 100 Mbit card:
01:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 01)
        Subsystem: Intel Corporation Unknown device 304a
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min, 14000ns max), Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 209
        Region 0: Memory at ff8ff000 (32-bit, non-prefetchable) [size=4K]
        Region 1: I/O ports at bc00 [size=64]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-

We (Joe) need to buy a GigE card for linux1 and to also set up conlog and conlogger to run on Nodus.
ELOG V3.1.3-