40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 299 of 341  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  3313   Wed Jul 28 17:32:37 2010 kiwamuUpdateSUSinstallation of in-vac optics

[Jenne, Koji and Kiwamu]

We have installed two steering mirrors and the green periscope.

Also we took the tip-tilt out from the chamber for characterization.


1. installed two steering mirrors

     - We installed IPPOSSM2 and IPPOSSM3.

    - Because IPPOSSM2 is a new 0 deg mirror so we newly engraved "Y1-LW1-2037-1064-0-AR" on the mount and deleted  the previous enegravement.

      For the 0 deg mirror itself, it had already been engraved by Koji. The wedge was horizontally aligned.

      Now IPPOSSM2 is off from the right place by 5 inch for convenience because it may touch our stomachs when we try to lean further into the chamber.

    - IPPOSSM3 is a 45 deg mirror which used to be in the chamber and had been already correctly engraved, so we didn't have to newly engrave on it. Now it's on the right place approximately.

 2. put three oplev mirrors

      - Two of them are approximately on the place, but one which is going to be on the center of the table is not on the place because there is a cable distributer sitting exactly there.

 3. installed the green periscope

      - Both the mirrors and the periscope were correctly engraved.

     - Now it's sitting on the right place approximately.

 4. removed the tip-tilt 

      -  This tip-tilt is now in the clean room and the mechanical mode will be characterized. 

 


 The next things to be done

* Cross-coupling evaluation of the PRM OSEMs

* Rearrangement of the cable distributer panel.

   - In order to do this we have to pull its cables which are attached to the stack.

* Installation of three green steering mirrors

   - All of them need to be engraved.

* Installation of two tip-tilt

  - One for the SRC and the other for the PRC

  3310   Wed Jul 28 14:34:29 2010 channaUpdateComputersinstallation on allegra

I have done the following on allegra and rosalba:

[root@allegra caltech]# yum install glade2

On rosalba the matplotlib was out of date with respect to allegra.  I have no idea how the version 0.98 on allegra got there, but I left it.  However I updated rosalba to the epel version

  1 yum remove python-numpy
  2 yum install python-matplotlib numpy scipy --enablerepo=epel --disablerepo=rpmforge

 

This is all to support the LIGO data listener which now has a shortcut on rosalba and allegra's desktop.  It seems to work for (live mode) right now.
 

 

  15921   Mon Mar 15 20:40:01 2021 ranaConfigurationComputersinstalled QTgrace on donatella for dataviewer

I installed QTgrace using yum on donatella.angel Both Grace and XMgrace are broken due to some boring fight between the Fedora package maintainers and the (non existent) Grace support team. So I have symlinked it:

controls@donatella|bin> sudo mv xmgrace xmgrace_bak
controls@donatella|bin> sudo ln -s qtgrace xmgrace
controls@donatella|bin> pwd
/usr/bin

I checked that dataviewer works now for realtime and playback.cool Although the middle click paste on the mouse doesn't work yet.angry

Attachment 1: cutiegrace.png
cutiegrace.png
  6354   Mon Mar 5 13:11:06 2012 kiwamuUpdateLSCinstalled a long BNC cable for REFL OSA

A long BNC cable was installed and now the REFL OSA signal is happily shown on an oscilloscope in the control room.

Quote from #6352

The OSA for the REFL beam is now fully functional.

The only thing we need is a long BNC cable going from the AP table to the control room so that we can monitor the OSA signal with an oscilloscope.

  4354   Thu Feb 24 21:46:30 2011 kiwamuUpdateGreen Lockinginstalled a summing box

In this past weekend I replaced a summing amplifier for the end green PDH locking by a home-made summing circuit box in order to increase the control range.

It's been working well so far.

However due to this circuit box, the demodulation phase of the PDH locking is now somewhat different from the past, so we have to readjust it at some point.

 

(background)

    At the X end station, the voltage going to the NPRO PZT had been limited up +/- 4 V because of the summing amplifier : SR560.

Therefore the laser was following the cavity motion only up to ~ +/- 4 MHz, which is not wide enough. (it's okay for night time)

So we decided to put a passive circuit instead of SR560 to have a wider range.

 

(summing box)

   We made a passive summing circuit and put it into a Pomona box.

The circuit diagram is shown below. Note that we assume the capacitance of the 1W Innolight has the same capacitance as that of the PSL Innolight (see #3640).

summing_box.png

The feedback signal from a PDH box goes into the feedback input of the circuit.

Then the signal will be low passed with the corner frequency of 200 kHz because of the combination of RC (where R is 681 Ohm and C is capacitance of the PZT).

Because of this low pass filter, we don't drive the PZT unnecessarily at high frequency.

On the other hand the modulation signal from a function generator goes into the other input and will be high passed by 50 pF mica capacitor with the corner frequency of 200 kHz.

This high pass filter will cut off noise coming from the function generator at low frequency.

In addition to it, the 50 pF capacitor gives a sufficient amount of attenuation for the modulation because we don't want have too big modulation depth.

 

Here is a plot for the expected transfer functions.

You can see that the modulation transfer function (blue curve) has non-zero phase at 216 kHz, which is our modulation frequency.

transfer_func.png
 

 

  6330   Tue Feb 28 12:00:54 2012 kiwamuUpdateLSCinstalled anti-whitening filters

I found that none of the filter banks in the LSC input signals have the precise anti-whitening filters.

I installed the precise filters on REFL11, REFL33, REFL55 and AS55 based on Jenne's measurement (#4955)

After installing them I briefly checked the REFL11 sensing matrix with the PRMI locked, but it didn't change so much from what I got (#6283).

But I felt that the PRMI became more robust after that ... I just felt so ...

 


(Background)

The lock of the PRMI doesn't look healthy, especially the sensing matrix doesn't make sense at all (#6283).
A very staring thing in the sensing matrix is that the REFL11 and REFL55 didn't show the 90 degree separation between MICH and PRCL.
So I suspected some electronics, particularly the demodulation boards.
 

(What I did)

I checked the anti-whitening filters shape to see if they are ok or not.
I found that they all had the default filters of two zeros at 150 Hz and two poles at 15 Hz. So they weren't quite tuned.
I thought this could be a problem when I measure the sensing matrix because I usually excite the length DOFs at a high frequency of 283.1 Hz
and the mismatches between the anti-whitening and whitening filters may lead to something funny at such a high frequency.
 
So I installed the precise filters on REFL11, REFL33, REFL55 and AS55.
After that I did a orthogonality test on each I-Q pair of the demod signals to correct the D-phases and the relative gain between I and Q.

 

(Next ?)

 Rana and I discussed the plan and decided to go back to a simple Michelson which should be easy enough to understand what is going on and should allow us a complete set of measurements.
Our big concern behind it is that we maybe locking the PRMI at a funny operation point.
In order to assess the issue I will do the following actions on the Michelson at first and then apply the same things on the PRMI later :
  • Check  the amount of of the sidebands using the OSA
  • Check the amount of the DC light
  • Check the sensing matrix to see if the absolute values in watt / meter make sense or not
    • This work needs calibrations on all the demodulated board (this is equivalent to measuring the conversion losses of the mixers in the demod boards).
  • Measure the contribution from the RAMs (it must be measurable by some means)
  6331   Tue Feb 28 15:48:32 2012 kiwamuUpdateLSCinstalled anti-whitening filters

I installed the rest of the precise anti-whitening filters. Now all of the LSC sensors have the right filters.

Quote from #6330

I found that none of the filter banks in the LSC input signals have the precise anti-whitening filters.

I installed the precise filters on REFL11, REFL33, REFL55 and AS55 based on Jenne's measurement (#4955)

  4093   Thu Dec 23 12:19:43 2010 kiwamuUpdateGreen Lockinginstalled doubling oven base at PSL table

I gave a christmas present to a doubling oven who has been sitting on the PSL table.

The below is a picture of the present I gave. It's a base plate for the doubling oven, made from a block of aluminum, and black-anodized.

The size and the shape are nicely tailored for the combination of the Newfocus kinematic mount and the Covesion oven.

The design had been done by using Solid Works 2010

 

DSC_2820_ss.jpg

 

Here is a picture before he got the present.

DSC_2814_ss.jpg

 

Now he looks pretty happy.

DSC_2815_ss.jpg

  4095   Thu Dec 23 18:51:37 2010 ranaUpdateGreen Lockinginstalled doubling oven base at PSL table

This is not such a bad base design, but remember that we have to get a couple of parts with the purple anodize to see if there is a difference between black and purple in terms of the 532 nm reflectivity.

  3990   Mon Nov 29 18:05:17 2010 Leo SingerConfigurationComputersinstalled graphviz on Rosalba

I installed the following packages on Graphviz in order to support visualization of GStreamer pipeline graphs:

graphviz

  4779   Thu Jun 2 10:19:37 2011 Alex IvanovSummaryDAQinstalled new daqd (frame builder) program on fb (target/fb/daqd)

I hope that new daqd code will fix the problem with non-aligned at 16 seconds frame file GPS times.

I have compiled new daqd program under /opt/rtcds/caltech/c1/core/release/build/mx and installed it under

target/fb/daqd, then restarted daqd process on "fb" computer. It was installed with the ownership of user root

and I did chmod +s on it (set UID on execution bit). This was done in order to turn on some code to renice daqd process

to the value of -20 on the startup. Currently it runs as the lowest nice value (high priority).

 

controls@fb /opt/rtcds/caltech/c1/target/fb $ ls -alt daqd
-rwsr-sr-x 1 root controls 6592694 Jun  2 10:00 daqd

 

Backup daqd is here:

 

controls@fb /opt/rtcds/caltech/c1/target/fb $ ls -alt daqd.02jun11
-rwxr-xr-x 1 controls controls 6768158 Feb 21 11:30 daqd.02jun11

 

 

  4055   Tue Dec 14 22:42:56 2010 kiwamuUpdateSUSinstalled the last TT . And some more progresses

  [Koji, Oasmu and Kiwamu]

We made the following progresses :

   (1) installation of the last TT called SR2.

 (2) fixing an earthquake stop issue on the BS

  (3) fixing a clipping of beams at the dark port


(earthquake stops on the BS)

 - When we were aligning the BS, we found that the BS showed funny behaviors.

For example a kick on LR didn't shake LRSEN, and a big DC angular offset (~ 8 in the medm screen ) was needed to keep a horizontal beam axis in the reflection.

We checked all the earthquake stops and found two suspicious earthquake stops at right bottom side.

They looked like slightly touching the BS. So we moved them further away from the BS.

Then the problem had gone.  We doublechecked the health by kicking, applying an angular offset  and so on.

 

(beam clipping)

We found transmitted/reflected beams from the BS to the dark port was clipped at the BS tower.

We moved the BS tower by ~1cm and realigned the rotation of the BS tower.

We also found the beam spots on the two TTs, PR2 and PR3, were offcentered. Especially the beam spot on PR3 was almost on the edge of the mirror.

Probably this was because we touched PZT1 when aligning the beam to the Y end.

So it means, it is not a good idea to align the beam to the end only by steering PZT1. We should use PR2 and PR3 as well when we align the beam to the Y end.

We realigned them such that the beam hits the center of PR2, PR3 and ETMY.

  7613   Wed Oct 24 20:09:41 2012 jamieUpdate installing the new dirchoic mirros in PR3/SR3

When installing the dichroics we need to pay attention to the wedge angle.  I didn't, so the ghost beam is currently point up and to the right (when facing the optic).  We should think carefully about where we want the ghost beams to go.

I also was using TT SN003, which I believe was being used for PR2.  However, I don't think we want to install dichroics in the PR2, and we might want to put all the tip-tilts back in the same spots they were in before.  We therefore may want to put the old optic back in SN003, and put the dichroics in SN005 (PR3) and SN001 (SR3) (see 7601).

  8946   Wed Jul 31 10:27:00 2013 SteveUpdateVACinstrument grade air is discontinoued

We have been using Air Liquide Instrument Grade Air for venting the 40m vacuum envelope. It is no longer available.

The replacement is Alphagas 1, total hydrocarbon <0.1% ppm

LINK TO Alphagaz

 

A- A+ Imprimer Partager

ALPHAGAZ™ Specifications

ALPHAGAZ™ range of Pure Gases for Analysis: two purity levels tailored to cover all your analytical needs.

Because each analytical application is sensitive to critical impurities that can affect your results, tests in our research center and analyzer manufacturers' studies confirm that the main impurities are moisture, oxygen and hydrocarbons.

Based on these critical impurities, Air Liquide has developed ALPHAGAZ™ brand with a Maximum Impurity Level (H2O, O2, CnHm).

  • The Maximum Impurity Level is the same across the whole product range. This constitutes a guarantee of quality with regard to major critical impurities and contamination tracers. ALPHAGAZ™ 2 offers an even greater guarantee in terms of purity (CO, CO2, H2).
  • The Minimum Total Purity is a prerequisite for product quality, but we do not stop there: Air Liquide selects and controls its gas sources by defining specifications regarding impurities that are critical for your analysis or application.

 

ALPHAGAZ™ 1 ALPHAGAZ™ 1 ALPHAGAZ™ 2 ALPHAGAZ™ 2 ALPHAGAZ™ AUTO IV ALPHAGAZ™ CO2 SFC
He, N2, H2,
Ar, O2
Air He, N2, H2,
Ar, O2
Air Air*, N2, O2 CO2
Specifications (ppm vol):
H2O < 3 ppm
O2 < 2 ppm
CnHm < 0.5 ppm
H2O< 3 ppm
CnHm< 0.1 ppm
CO2 < 1 ppm
CO < 1 ppm
H2O < 0.5 ppm
O2 < 0.1 ppm
CO2 < 0.1 ppm
CO < 0.1 ppm
CnHm < 0.1 ppm
H2 < 0.1 ppm
H2O < 0,5 ppm
CnHm < 50 ppb
CO2 < 0,1 ppm
CO < 0,1 ppm
NOx < 10 ppb *
SO2 < 10 ppb*
CnHm < 0.2 ppm
CO2 < 0.5 ppm
CO < 0.5 ppm
NO/NOx < 0.1 ppm
H2O < 5 ppm
O2 < 2 ppm
CnHm < 2 ppm
NVOC* < 2 ppm
CO < 5 ppm
NO + NO2 < 2 ppm
S Total < 1 ppm
H2 < 0.5 ppm
  20 ± 1 % O2 (Europe)
21 ± 1% O2 (North America)
  20,9 ± 1 % O2
*: Detection limit
*20 ± 1 % O2 *NVOC: Non Volatile Organic Compounds
Minimum Total Purity

 

 

  4181   Fri Jan 21 02:45:43 2011 kiwamuUpdateGreen Lockinginterface for PLL to ADC

 [Suresh, Kiwamu]

  We did the following things:

     - installed a 1/10 voltage divider such that the signal won't be saturated at the AA board (see here)

     - put a Ithaco preamplifier 1201 as a whitening filter

     - checked the entire beat detection system without using the real beat note

Here are some items to be done before the sun goes down tomorrow:

       - calibration of ADC and the interfaces including the voltage divider and the whitening filter.

     - fine matching of unwhitening filter at the digital side

         - PLL response measurement ( freq to voltage response ) over the frequency range of interest

         - plotting an well calibrated spectrum of the PLL output 


(whitening filter)

The Ithaco 1201 was setup to have a zero at 0 Hz and two poles at 0.1 Hz and 10 Hz in order to emphasize the signal over the frequency range of interest.

Around 1Hz it is supposed to have a gain of 1000. These settings have done by tweaking the knobs on the front panel of the Ithaco 1201.

In addition to that, we made an unwhitening filter in digital filter banks. This filter was designed to cancel the analog whitening filter.

(system check) 

 To check the entire beat detection system, we phase-locked the VCO to a Marconi running at 80 MHz, which is the center frequency of the VCO.

Then we imposed a frequency modulation on the Marconi to see if the signal is acquired to ADC successfully or not. It's quite healthy.

According to the spectra corrected by the unwhitening filter, we confirmed that the noise floor at 1Hz is order of 1Hz/sqrt Hz, which is already quite good.

Then we took several spectra while putting a modulation on the Marconi at a different frequency in each measurement.

The peak due to the artificial modulation essentially works as a calibration peak in the spectra.

So in this way we briefly checked the flatness of the response of the system in the frequency domain.

As a result we found that the response is not perfectly flat in the range of 0.05 - 30Hz, probably due to a mismatch of the combination of the whitening and unwhitening filters.

We will check it tomorrow.

 

  5374   Sat Sep 10 01:36:15 2011 kiwamuUpdateASCinterferometer coarsely aligned

The interferometer was coarsely aligned.

Now spatially overwrapped DRMI and FP arm fringes are visible on the AS camera although the incident beam alignment was done only with PZT2.

All the DC biases were saved so that we can go back to this condition any time.

 

/***** some health checks *******/

 [FINE] IPPOS : it looks okay but the spot on the QPD is a little bit too low by a few mm.

 [NOT GOOD] IPANG : maybe hitting a post or something because the spot is vertically split into two. The spot is too low.

 [FINE] POX/POY/POP : they all are coming out. POP is visible with an IR viewer.

 [FINE] REFL :  no clipping but the beam looks a little bit too low relative to the CCD camera.

 [FINE] AS : no clipping and the spot position on the AS camera looks fine.

 [FINE] Green beams : both X and Y beams are successfully landing onto the PST table without no clipping.

 [FINE] Suspensions : all of them are reasonably quiet without the oplevs, which is good.

  8230   Tue Mar 5 06:27:14 2013 yutaUpdateLSCintra-cavity power dependence on mirror misalignment

I measured intra-cavity power dependance on mirror misalignment.
Intra-cavity power of PRC in PRMI degrates roughly 20 % when there's 0.5 mrad 5 urad misalignment. (edited by YM)
Currently, PRMI lock is not so stable, so it is hard to do this measurement and error bars are huge.

Measurement method:
  0. Align the cavity and lock.
  1. Misalign one optic and measure oplev output value and intra-cavity power.
  2. Also, dither the optic in pitch or yaw in 8.5 Hz and get demodulated amplitudes at 8.5 Hz of oplev output and intra-cavity power using tdsdmd.
  3. Misalign the optic again and do the same things.

  1. gives intra-cavity power dependence on mirror misalignment directly, but 2. should give better S/N because of dithering.


Scripts:
  /opt/rtcds/caltech/c1/scripts/dither/dithergfactor.py does these things, and ./plotgfactor.py plots the result.
  They work quite well, but it should be made better so that

  - it checks if the cavity is locked
  - automatically change the oplev calibration factor for each optic
  - automatically adjusts the region and modulation amplitude
  - read data with better error evaluation

  etc...


PRMI alignment:
  Y green looks like it drifted quite a lot somehow. If we start aligning Yarm to Y green, we get AS and POP beam at different spot on camera compared with last week. Also, TRY and TRX only goes as high as ~0.7. Since we have A2L now (elog #8229), let's start using Yarm spot positions as input pointing reference.


PRMI locking details:
  Same as in elog #8212, but I changed gains in the lock acquisition mode.

  == PRMI carrier ==
  MICH: AS55_Q_ERR, AS55_PHASE_R = -12 deg,  MICH_GAIN = -0.2, feedback to ITMX(-1),ITMY(+1)
  PRCL: REFL55_I_ERR, REFL55_PHASE_R = 70 deg, PRCL_GAIN = 1.0, feedback to PRM

  I made gainx5 in LSC_MICH filter bank so that it increases the overall gain when locked by trigger.
  I also made gainx0.3 in LSC_PRCL filter bank so that it reduces the overall gain when locked by trigger.


Result for PRC in PRMI:
  For PRMI, I couldn't done dithering method because dithering takes time to measure and I could not hold PRMI locking during the measurement.
  Below is the result when reading just the DC values. Mirror angle is calibrated by oplev (elog #8221). Error bars are huge because of beam motion mainly in yaw.


PRM in pitch: PRM_PIT_20130305a.png    PRM in yaw:PRM_YAW_20130305b.png


Results for the arms:
  For the arms, I could do both in DC and dithering. Below are the results, but ITMs misalignments are not calibrated because we don't have calibrated oplev yet.
  Results for the arms can be used to verify this method because we know g-factors of the arms from mode scan.


ITMX in yaw: ITMX_YAW_20130305.png    ITMY in yaw: ITMY_YAW_20130305.png



By the way:
  I found C1:SUS-ITMY_LSC_GAIN is somehow set to be 2.895 recently. I think this should be 1.0. Maybe this is why we had actuation imbalance in ITMs(elog #8212).


Next:
 - more stable lock
 - calibrate ITM oplevs to apply this method to the arms
 - derive g-factor from these measurements
 - measure PRM angular motion spectra using calibrated oplev

  2098   Thu Oct 15 12:35:09 2009 ZachUpdatePSLinventory

I'm at the PSL table taking inventory of the elements I don't have down yet.

  2099   Thu Oct 15 12:57:23 2009 ZachUpdatePSLinventory

Quote:

I'm at the PSL table taking inventory of the elements I don't have down yet.

 OK, I'm out--hopefully for good. HEPAs back at 20%.

  5597   Sun Oct 2 18:33:36 2011 kiwamuUpdateSUSinversion of the input matrix on ETMX, ITMX and PRM

The input matrices of ETMX, ITMX and PRM have been newly inverted.

Those were the ones having some troubles (see #5444, #5547).

After a coarse adjustment of the damping Q factors, they look damping happily.

 

    optic                    spectra    inverted matrix   BADNESS
ETMX ETMX.png       pit     yaw     pos     side    butt
UL    0.848   0.108   1.578   0.431   1.025 
UR    0.182  -1.892   1.841  -0.128  -1.172 
LR   -1.818  -1.948   0.422  -0.122   0.939 
LL   -1.152   0.052   0.159   0.438  -0.864 
SD    1.756  -3.794  -0.787   1.000  -0.132 
  5.37028
ITMX ITMX.png     pit     yaw     pos     side    butt
UL    0.510   0.584   1.228   0.458   0.203 
UR    0.783  -1.350   0.348  -0.050   0.555 
LR   -1.217   0.065   0.772   0.264   0.312 
LL   -1.490   2.000   1.652   0.772  -2.930 
SD   -0.635   0.853  -1.799   1.000  -1.597  
 7.5125
PRM PRM.png       pit     yaw     pos     side    butt
UL    0.695   1.422   1.774  -0.333   0.954 
UR    1.291  -0.578   0.674  -0.068  -0.939 
LR   -0.709  -1.022   0.226   0.014   0.867 
LL   -1.305   0.978   1.326  -0.251  -1.240 
SD    0.392  -0.437  -0.500   1.000   0.420
 5.09674

 

(some notes)

 Before running the peakFit scripts, I woke up the nds2 sever process on Mafalda because it hasn't been recovered from the power outage.

To start the nds2 process I followed the instruction by Jamie (#5094).

Then I started requesting the data of the last night's free swinging test (#5594)

However the NDS2_GetData command failed everytime when data with long duration were requested.

It maybe because some of the data are missing in sometimes, but I haven't seriously checked the data stored in fb.

So for the reason, I had to use a short duration of 1200 sec (default is 3600 sec). That's why spectra look noisier than usual.

  12038   Fri Mar 18 11:04:56 2016 SteveUpdateSUSinverted pendulum

Kate Dooley picked up this item today.

Attachment 1: invPeng.jpg
invPeng.jpg
  2812   Tue Apr 20 07:48:42 2010 steveUpdatePSLion pump HV turned on

We found ref-cavity HV was off yesterday afternoon. It was turned back on.

  3873   Fri Nov 5 23:05:43 2010 ranaConfigurationIOOioo.db file changed in c1iool0 to get back MC TRANS

 

We like to have the MC TRANS channels so that we can run all of our old scripts and trends on it. This is the usual BROWN

channel that's on the LockMC screen. Its also the thing that we use for thresholding to activate the MC Autolocker Daemon.

I modified the ioo.db file in the target/c1iool0/ directory so that the MC_TRANS_SUM, _P, and _Y channels are all now just

CALC records of the MC2 OL channels (where the calculation is MC_TRANS_SUM = MC2 OL_SUM + 0.001, etc.). I then

rebooted c1iool0 a few times to get the syntax right. It SEEMS to be working now. I'm sure that this won't effect anything.
I've committed the new file to the SVN repo. Once Suresh is done hacking the QPD circuit, we can set the threshold in the Autolocker.

  11723   Fri Oct 30 16:56:04 2015 gautamUpdateCDSis there a problem with the SCHMITTTRIGGER CDS library part?

Over the course of my investigations into the systematic errors in the frequency readout using digital frequency counting, I noticed that my counter variable that keeps track of the number of clock cycles between successive zero crossings was NOT oscillating between 2 values as I would have expected (because of there being a +/- 1 clock cycle difference between successive zero crossings due to the fixed sampling time of 1/16384 seconds), but that there were occassional excursions to values that were +/- 3 clock cycles away. I then checked the output of the SCHMITTTRIGGER CDS library part (which I was using to provide some noise immunity), and noticed that it wasn't triggering on every zero crossing at higher frequencies. I tested this by hooking up a digital oscillator to the SCHMITTTRIGGER part, and looked at its output for different frequencies. The parameters used were as follows:

CLKGAIN: 10000

SCHMITTTRIGGER lower threshold: -1.0

SCHMITTTRIGGER upper threshold: +1.0

I am attaching plots for two frequencies, 3000Hz and 4628Hz (Attachments #1 and #2) . I would have expected a flip in the state of the output of the schmitt trigger between every pair of horizontal red lines in this plot, but at 4628 Hz, it looks like the schmitt trigger isn't catching some of the zero crossings? Come to think of it, I am not even sure why the output of the schmitt trigger takes on any values other than 0 or 1 (could this be an artefact of some sort of interpolation in the visualization of these plots? But this would not affect the conclusion about the schmitt trigger missing some of the zero crossings?)

As an interim measure, I implemented a Schmitt trigger in my C code block - it was just a couple of extra lines anyways - I have designated the schmitt trigger output as a static variable that should hold its value in successive execution cycles, unless it is updated by comparing the input value to the thresholds (code attached for reference). Attachments #3 and #4 show the output of this implementation of a Schmitt trigger at the same two frequencies, and I am seeing the expected flip in the state between successive zero crossings as expected (though I'm still not sure why it takes on values other than 0 and 1?). Anyways this warrants further investigation. An elog regarding the implications of this on the systematic error in the frequency counter readout to follow.

Attachment 1: 3000Hz.pdf
3000Hz.pdf
Attachment 2: 4628Hz.pdf
4628Hz.pdf
Attachment 3: 3000Hz_software_SCHMITT.pdf
3000Hz_software_SCHMITT.pdf
Attachment 4: 4628Hz_software_SCHMITT.pdf
4628Hz_software_SCHMITT.pdf
  14770   Thu Jul 18 00:51:52 2019 KojiSummaryCDSiscaux electronics modifications

Along with the plan in ELOG 14744, the ISC PD interface and the whitening filter board have been modificed. The ISC PD I/Fs were restored to the crate and the cables were connected. The whitening filteres are still on the electronics bench for some more tests before being returned to the crate.

The updated schematics were uploaded as https://dcc.ligo.org/D1900318 and https://dcc.ligo.org/D1900319

- Modification of the ISC PD interface: Jumpers between DIN96 P1 and P2. Replace all AD797s with OP27. In fact only I/F #1 (the left most)  had total 12 AD797 but the other units already had OP27s.

- Modification of the whitening filter: Jumpers between DIN96 P1 and P2.

Attachment 1: LSC_whitening2.jpg
LSC_whitening2.jpg
Attachment 2: LSC_whitening.jpg
LSC_whitening.jpg
  14775   Thu Jul 18 22:34:40 2019 KojiSummaryCDSiscaux electronics modifications

The whitening filter modules have been restored to the crates. The SMA cables have been restored and fastened by a spanner. The ribbon cable to the antialiasing board was also connected. The backplane cables have not been moved from the upper DIN96 connector to the lower one.

Everything is expected to be good, but just keep eyes on the LSC signals as the boards were not quantitatvely tested yet. If you find something suspicious, report on the elog.

  10853   Mon Jan 5 18:15:18 2015 JenneUpdateCDSiscex reboot

Rana noted last week that TRX's value was stuck, not getting to the lsc from iscex.  I tried restarting the individual models scx, lsc and even scy (since scy had an extra red rfm light), to no avail.  I then did sudo shutdown -r now on iscex, and when it came back, the problem was gone.  Also, I then did a diag reset which cleared all of the unusual red rfm lights.

Things seem fine now, ready to lock all the things.

  6730   Thu May 31 11:38:19 2012 DenUpdatePEMisolation system

I've put Guralps into the Steve's 2 box isolation system. Noise got better, coherence between 2 seismometers improved. We still need better performance. Probably, one device is noisy and we can not determine which one using these 2 seismometers. We need more seismometers. Sadly, STS-2 readout box is not working.

lin_box_noise2.png    lin_box_coh.png

  4906   Wed Jun 29 01:23:21 2011 haixingUpdateSUSissues in the current quad maglev system

Here I show several issues that we have encountered in the quad magnetic levitation system. It would be great if you can give
some suggestions and comments (Poor haixing is crying for help)

The current setup is shown by the figure below (I took the photo this morning):

config_2.png

Basically, we have one heavy load which is rigidly connected to a plane that we try to levitate. On corners of the
plane, there are four push-fit permanent magnets. Those magnets are attracted by four other magnets which are
mounted on the four control coils (the DC force is to counteract the DC gravity). By sensing the position of the plane
with four OSEMs (there are four flags attached on the plane), we try to apply feedback control and levitate the plane.
We have made an analog circuit to realize the feedback, but it is not successful. There are the following main issues
that need to be solved:

(1) DC magnetic force is imbalanced, and we found that one pair has a stronger DC force than others. This should
be able to solved simply by replacing them with magnets have comparable strength to others.

(2) The OSEM not only senses the vertical motion, but also the translational motion. One possible fast solution is to
cover the photodiode and only leave a very thin vertical slit so that a small translational motion is not sensed.
Maybe this is too crappy. If you have better ideas, please let me know. Koji suggested to use reflective sensing
instead of OSEM, which can also solve the issue that flags sometimes touche the hole edge of the OSEM and
screw up the sensing.

(3) Cross coupling among different degrees of freedom. Basically, even if the OSEM only senses the vertical motion,
the motion of four flags, which are rigidly connected to the plane, are not independent. In the ideal case, we only
need to control pith, yaw and vertical motion, which only has three degrees of freedom, while we have four sensing outputs
from four OSEMs. This means that we need to work out the right control matrix. Right now, we are in some kind of dilemma.
In order to obtain the control matrix, we first have to get the sensing matrix or calibrate the cross coupling; however, this is
impossible if the system is unstable. This is very different from the case of quad suspension control used in LIGO,
in which the test mass is stable suspended and it is relatively easy to measure the cross coupling by driving the test mass
with coils. Rana suggested to include a mechanical spring between the fixed plane and levitated plane, so that
we can have a stable system to start with. I tried this method today, but I did not figure out a nice way to place the spring,
as we got a hole right in the middle of the fixed plane to let the coil connectors go though. As a first trial, I plan to
replace the stop rubber band (to prevent the plane from getting stuck onto the magnets) shown in the figure with mechanical
springs. In this case, the levitated plane is held by four springs instead of one. This is not as good as one, because
of imbalance among the four, but we can use this setup, at least, to calibrate the cross coupling. Let me know if you come
up better solution.

After those issues are solved, we can then implement Jamie's Cymac digital control, which is now under construction,
to achieve levitation.

  4907   Wed Jun 29 11:13:13 2011 JenneUpdateSUSissues in the current quad maglev system

magnetQuote


(1) DC magnetic force is imbalanced, and we found that one pair has a stronger DC force than others. This should
be able to solved simply by replacing them with magnets have comparable strength to others.

 I don't know if this would work, but it might be worth a try:

You've achieved single levitation before, with fairly good stability.  Can you try taking each magnet + coil and finding the DC coil current required to hold a mass at a given position?  If you can hold the same mass at the same place with all the different magnets+coils, then you're exerting the same force against gravity, so your DC forces are balanced. 

  9828   Fri Apr 18 09:40:28 2014 SteveUpdateElectronicsit is a kick

10 days of on-off glitching?   It is a kick. The LSC is off, so it must be the ALS

Attachment 1: theLifeofGlithes.png
theLifeofGlithes.png
Attachment 2: glitchingEndsMC2.png
glitchingEndsMC2.png
Attachment 3: itisaKick.png
itisaKick.png
  10075   Thu Jun 19 17:11:52 2014 steveUpdatePEMit is warmer today

 The PSL HEPA was running at 30VAC-variac. It is 1 degree C warmer than usual. The HEPA fan motor turned up to 60 V

Attachment 1: warmertoday.png
warmertoday.png
  114   Mon Nov 19 14:19:25 2007 steveOmnistructurePEMjackhammer
The construction personal successfully jackhemmered a fence around the "Drever's parking slot"
There is no parking space available close by
Attachment 1: jackhammer.jpg
jackhammer.jpg
Attachment 2: jackhammer2.jpg
jackhammer2.jpg
  2313   Mon Nov 23 11:03:00 2009 steveUpdateSUSjackhammer special well under control

Quote:

I've changed the watchdog rampdown script so it brings the SUS watchdogs to 220, instead of the 150 it previously targeted.  This is to make tripping less likely with the jackhammering going on next door.  I've also turned off all the oplev damping.

 Saturday's special event of braking up the large concrete pieces in CES bay was un event full.

Attachment 1: dig10d.png
dig10d.png
Attachment 2: P1050740.JPG
P1050740.JPG
  2694   Mon Mar 22 11:37:09 2010 steveUpdatePEMjackhammering

There was more jackhammering this morning just about 20 ft north-west of the beamsplitter chamber, outside.

Attachment 1: jackhammering2.jpg
jackhammering2.jpg
  11203   Mon Apr 6 09:13:49 2015 SteveUpdatePEMjackhammering at ETMX
Quote:

The 40m fenced area will start storing this large chamber on April 14. The asphalt will be cut, jack hammered the next 2-3 days in order to lay concrete.

Their schedule is from 8 to 5 starting tomorrow.  We are asking them to work from 6 to 3pm

ETMX is about 12-15 ft away

Jackhammering was happening around 7:30am

It looks like it did no harm. It is too early to say what may have moved. Rana's worrisome  email was late.

The ground preparation is completed.

Attachment 1: jackhammerCalb.png
jackhammerCalb.png
Attachment 2: jackHcalETMX.jpg
jackHcalETMX.jpg
Attachment 3: jackHetmx.png
jackHetmx.png
  11204   Mon Apr 6 13:23:40 2015 ranaUpdatePEMjackhammering at ETMX

Unfortunately, this kind of trend plot is not detailed enough to know if something has gone bad in a quantitative way. But at least we can tell that the suspension wire didn't break.

  11205   Tue Apr 7 04:17:42 2015 JenneUpdatePEMjackhammering at ETMX

Q is writing the locking elog for the night, but just to reply to this thread:  The IFO worked well tonight, so things are at least not broken.

Quote:

Unfortunately, this kind of trend plot is not detailed enough to know if something has gone bad in a quantitative way. But at least we can tell that the suspension wire didn't break.

 

  11211   Thu Apr 9 07:41:22 2015 SteveUpdatePEMjackhammering at ETMX

There was a period of short unexpected jackhammering this morning. I asked them to stop.

The good mood of GTRX was not changed.smiley

 

Attachment 1: moreJackHam.png
moreJackHam.png
Attachment 2: GTRX.jpg
GTRX.jpg
  2439   Mon Dec 21 08:16:54 2009 steveMetaphysicsPEMjackhammering next door

At ITMX, on the CES side, 5 Ft  from the wall the jackhammer is on. The susses are holding well.

  8350   Tue Mar 26 08:50:02 2013 SteveUpdateGeneraljanitor day

Keven, our janitor accidentally pushed the main entry door laser emergency stop switch.

The laser was turned back on. The MC and the arms were  started  flashing happily as they were before.

  438   Tue Apr 22 22:19:02 2008 robMetaphysicslorejiggling sliders

In the interests of tacit communication of scientific knowledge, I here reveal a nugget of knowledge which may or may not prove useful to new LIGOites: sometimes when front-end machines are rebooted, the hardware they control can wind up in a state which is not accurately represented by the EPICS values you may see. This can be easily rectified by momentarily changing the EPICS settings in question. For reference, this came up tonight in the context of the whitening gain sliders for the TransMon QPDs.
  1538   Fri May 1 18:24:36 2009 AlbertoSummaryGeneraljitter of REFL beam ?
Some loud thinking.
 
For the measurement of the length of the PRC, I installed a fast photodiode in the path of the beam reflected by PRM which goes to the 199 PD on the AS table. I picked up the beam by a flipping mirror on the same table.
I have the problem that the DC power that I measure at the PD when the PRC is locked is not constant but fluctuates. This fluctuation is irregular and has a frequency of about one Hz or so. I.e. it makes the 33 Mhz line on the PD oscillate by +/- 10 dBm.
 
Since this fluctuation does not appear at the REFL 33 PD, which has a much larger surface, but also shows up on the REFL 199 PD, I suspected that it was due to the very small size of the fast PDs. If the spot is too large, I thought, the power on the PD should be affected by the beam jitter.
 
Trying to avoid any beam jitter, I placed two lenses with focal lengths one ten times the other on the optical path in such a way to reduce the spot size on my fast PD by the same factors. The DC power was still fluctuating, so I'm not sure it's beam jitter anymore.
 
SPOB is definitely not constant when the PRC is normally locked, even with high loop gains, so maybe the reflected power really fluctuates that much.
Although, if it's actually the DC power that is fluctuating, shouldn't it appear also at the REFL 33 and shouldn't it be a problem that it shows up also in REFL 199? The elog doesn't say anything about that.
 

It's crucial that I get a stable transmitted power to have an accurate measurement of the PRC transmissivity and thus of its macroscopic length.

  7103   Tue Aug 7 14:34:01 2012 JamieUpdateCDSjk. daqd still segfaulting

Quote:

So daqd's problem was apparently the bad/non-running c1sup model.  The c1sup model, which I reported on attempting to get running in 7097, was not running because there were no available CPUs on the c1sus FE machine.  This was due to my stupid undercounting of the number of CPUs.  Anyway, for reasons I don't understand, this was causing daqd to segfault.  Removing c1sup from c1sus "fixed" the problem.

Alex agreed that daqd should definitely not be segfaulting in this circumstance.  It's still unclear exactly what daqd was looking at that was causing it to crash.

I'm going to move c1sup to c1iscex, which has a lot of spare CPUs.

I spoke too soon.  It's still segfaulting, but at a different place. Alex and I are looking into it.

But another mystery solved is the cause of all the network slowness: the daqd core dump.  When daqd segfaults it dumps it's core, which can typically be >4G, to /opt/rtcds/caltech/c1/target/fb/core.  This is of course an NFS mount from linux1, so it's dumping 4G on the network, which not surprisingly clogs the network.

  495   Sun May 25 16:20:27 2008 ranaConfigurationComputersjoinPDF
I have installed joinPDF 2.1 on rosalba. Since its written in Java, I didn't have to tinker with it at all to work on a 64-bit machine. Now Caryn can put all of her plots into 1 file.
  4552   Thu Apr 21 15:03:29 2011 steveUpdateComputersjuction board finds home

The anti aliasing box was opened up at the back to accommodate the junction board and the SCSI cable towards the ADC. Aluminum plate was attached to the bottom to hold the strain relief clamp.

Three more hanging junction cards will be replaced in this manner.

Attachment 1: P1070570.JPG
P1070570.JPG
Attachment 2: P1070568.JPG
P1070568.JPG
  502   Wed May 28 14:19:47 2008 steveUpdatePSLkaleidoscope of psl
atm 1: scattering psl table optics from the top of the output periscope f4, 60s @MOPA 3 W
atm 2: scattering psl table optics from the top of the output periscope f4, 20s
atm 3: competing GigE cameras on the north end of psl table
atm 4: yellow "soft" washer to be replaced on psl output periscope
atm 5: ETMY-ISCT in disarray
Attachment 1: pslscat.png
pslscat.png
Attachment 2: pslscat2.png
pslscat2.png
Attachment 3: 2GigEs.png
2GigEs.png
Attachment 4: perwash.png
perwash.png
Attachment 5: etmydisarray.png
etmydisarray.png
  3485   Sun Aug 29 21:18:00 2010 ranaUpdateComputerskallo -> rossa

We changed the name of the new control room computer from kallo to rossa (since its red).

I also tried to install the nVidia graphics driver, but failed. I downloaded the one for the GeForce 310

for x86_64 from the nVidia website, but it failed to work. I installed it, but then X windows wouldn't start.

I've left it running a basic VESA driver.

Kiwamu updated the host tables to reflect the name change. We found that both rossa and allegra were

set up to look at the old 131.* DNS computers and so they were not resolving correctly. We set them up for new way.

  2663   Tue Mar 9 09:04:20 2010 steveUpdatePEMkeep vacuum chamber closed

They are sandblasting at CES: our particle counts are very high. DO NOT OPEN CHAMBER!

Attachment 1: sandblasting.jpg
sandblasting.jpg
  14679   Mon Jun 17 16:02:17 2019 aaronUpdateComputerskeyed PSL crate

Milind pointed out that all boxes on the medm screens were white. I didn't have diagnostics from the medm screens, so I started following the troubleshooting steps on the restart procedures page.

It seemed like maybe a frontend problem. I tried telnet-ing into several of the fe, and wasn't able to access c1psl. The section on c1psl mentions that if this machine crashes, the screens will go white and the crate needs to be turned off and on. Millind did this.

Now, most of the status lights are restored (screenshot).

 


Milind: I did a burtrestore following this and locked the PMC following the steps described in this elog.

Attachment 1: after_keying_crate.png
after_keying_crate.png
ELOG V3.1.3-