40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 24 of 329  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  4460   Wed Mar 30 16:32:29 2011 AidanConfigurationComputer Scripts / ProgramsAdded a sitemap alias

I added an alias to the sitemap MEDM screen in /cvs/cds/caltech/target/cshrc.40m

Now you can enjoy launching sitemap from a terminal.

alias sitemap 'medm -x /cvs/cds/rtcds/caltech/c1/medm/sitemap.adl'

  4463   Wed Mar 30 18:50:57 2011 KojiConfigurationComputer Scripts / ProgramsAdded a sitemap alias

I thought that "m40m" was the traditional alias for the sitemap...


m40m ${medm_base} ${medm_newtail} &
sitemap medm -x /cvs/cds/rtcds/caltech/c1/medm/sitemap.adl

rossa:~>set|grep medm
medm_base       medm
medm_newtail    -x /opt/rtcds/caltech/c1/medm/sitemap.adl

medm_tail       -x /cvs/cds/caltech/medm/sitemap.adl


I added an alias to the sitemap MEDM screen in /cvs/cds/caltech/target/cshrc.40m

Now you can enjoy launching sitemap from a terminal.

alias sitemap 'medm -x /cvs/cds/rtcds/caltech/c1/medm/sitemap.adl'



  3226   Thu Jul 15 11:58:50 2010 josephbUpdateComputersAdded channel to ADCU_PEM (C0DCU1)

I modified the C1ADCU_PEM.ini file in /cvs/cds/caltech/chans/daq/ (after making a backup), and added a temporary channel called C1:PEM-TEMP_9, the 9 corresponding to the labeled 9 channel on the front of the BNC breakout in the 1Y7 rack.  The chnnum it was set to is 15008 (it was commented out and called C1:PEM-PETER_FE).  I also set the data rate to 2048.

I then did telnet fb40m 8087, and shutdown, and also hit the blue reconfig button on the DAQ status screen for the C0DCU1 machine.  The framebuilder came back up.  I confirmed the temporary channel, as well as the Guralp channels were still working from C0DCU1.

We have strung a cable in the cable trays from the SP table to the 1Y7 rack, which has been labeled as "Phasecam PD".  This will be used to record the output of an additional photodiode.


  7521   Wed Oct 10 19:22:03 2012 jamieUpdateIOOAdded control for input tip-tilts to c1ass

I have added some control logic and appropriate output DAC channels for the input tip-tilts (TT1 and TT2) to the c1ass model.

The plan is for all the tip-tilt drive electronics to live in a Eurocrate in 1Y2.  They will then interface with a DAC in c1lsc.

c1ass runs on the c1lsc front-end machine, and therefore seemed like an appropriate place for the control logic to go.

I added and interface to DAC0, and a top_named IOO block, to c1ass:


The IOO block includes two TT_CONTROL library parts, one for each of TT1 and TT2:


This is just a start so that I can start testing the DAC output.

I have not recompiled c1ass yet.  I will do that tomorrow.

  4396   Thu Mar 10 13:44:56 2011 josephbUpdateCDSAdded digitization noise to the c1spy model for simulated ADCs/DACs

To simulate digitization noise, the easiest way I found was to use the MathFunction block, found in the CDS_PARTS model, under simLinkParts. 

The MathFunction block supports square of input value, square root of input value, reciprocal of input value, and modulo of two input values.

The last is useful because it casts the input values as integers before taking the modulo.By placing this block after the saturation block (set to +/- 32768), adding 32768.5, choosing the 2nd input to be larger than 2 * 32768 (100,000 in this case), and then subtracting 32768, we wind up with a rounding function. 

The above method has been applied to the c1spy model in the CI and SO out sub-blocks.

  16269   Wed Aug 4 18:19:26 2021 pacoUpdateGeneralAdded infrasensing temperature unit to martian network

[ian, anchal, paco]

We hooked up the infrasensing unit to power and changed its default IP address from (factory default) to in the martian network. The sensor is online with user controls and the usual password for most workstations in that IP address.

  6869   Mon Jun 25 15:19:07 2012 YaakovUpdatePEMAdded microphone channels, moved accelorometer channels

Jenne and I renamed the mic channels Den created (elog 6664) to MIC_1, MIC_2, etc from the original accelerometer names to keep things clear. We then added 6 new channels (22-27) for the accelerometers, named ACC_MC1_X, Y, Z, ACC_MC2_X, Y, Z, etc. (See the screenshot below). We also added a DAQ channel block and listed out the IN1 channel of all the sensors. We compiled and started the model, and checked that all the channels were there in DataViewer.


  2477   Tue Jan 5 10:26:32 2010 Alberto, SteveOmnistructureEnvironmentAdded new wall cable-racks

we hung two new WALL cable racks. One is on the pillar next to the Sp table, the other is next to the PSL computer rack.

To do that we had to drill holes in the wall since the simple screws weren't strong enough to keep them up.

One of the racks, the yellow, is dedicated to 4-pin lemos and other thick cables.


  2478   Tue Jan 5 11:00:04 2010 ranaOmnistructureEnvironmentAdded new wall cable-racks


we hung two new WALL cable racks. One is on the pillar next to the Sp table, the other is next to the PSL computer rack.

 awesome - I have ordered 5 blue racks so that we can hang power cables. The fat BLUE ones are for fat cables and the orange ones for the coax cables.

  15275   Fri Mar 13 14:28:39 2020 gautamUpdatePSLAdded tees to PMC Trans and REFL

I want to monitor the PMC TRANS and REFL levels on the PSL table - previously there were some cables going to the oscilloscope on the shelf but someone had removed these. I re-installed them just now. While there, I disconnected the drive to the AOM - there must've been some DC signal going to it because when I removed the cable, the PMC and IMC transmission were recovered to their nominal levels.

  16330   Tue Sep 14 17:22:21 2021 AnchalUpdateCDSAdded temp sensor channels to DAQ list

[Tega, Paco, Anchal]

We attempted to reboot fb1 daqd today to get the new temperature sensor channels recording. However, the FE models got stuck, apparantely due to reasons explaine din 40m/16325. Jamie cleared the /var/logs in fb1 so that FE can reboot. We were able to reboot the FE machines after this work successfully and get the models running too. During the day, the FE machines were shut down manually and brought back on manually, a couple of times on the c1iscex machine. Only change in fb1 is in the /opt/rtcds/caltech/c1/chans/daq/C0EDCU.ini where the new channels were added, and some hacking was done by Jamie in gpstime module (See 40m/16327).

  16270   Thu Aug 5 14:59:31 2021 AnchalUpdateGeneralAdded temperature sensors at Yend and Vertex too

I've added the other two temperature sensor modules on Y end (on 1Y4, IP: and in the vertex on (1X2, IP: I've updated the martian host table accordingly. From inside martian network, one can go to the browser and go to the IP address to see the temperature sensor status . These sensors can be set to trigger alarm and send emails/sms etc if temperature goes out of a defined range.

I feel something is off though. The vertex sensor shows temperature of ~28 degrees C, Xend says 20 degrees C and Yend says 26 degrees C. I believe these sensors might need calibration.

Remaining tasks are following:

  • Modbus TCP solution:
    • If we get it right, this will be easiest solution.
    • We just need to add these sensors as streaming devices in some slow EPICS machine in there .cmd file and add the temperature sensing channels in a corresponding database file.
  • Python workaround:
    • Might be faster but dirty.
    • We run a python script on megatron which requests temperature values every second or so from the IP addresses and write them on a soft EPICs channel.
    • We still would need to create a soft EPICs channel fro this and add it to framebuilder data acquisition list.
    • Even shorted workaround for near future could be to just write temperature every 30 min to a log file in some location.

[anchal, paco]

We made a script under scripts/PEM/temp_logger.py and ran it on megatron. The script uses the requests package to query the latest sensor data from the three sensors every 10 minutes as a json file and outputs accordingly. This is not a permanent solution.

  16319   Mon Sep 13 04:12:01 2021 TegaUpdateGeneralAdded temperature sensors at Yend and Vertex too

I finally got the modbus part working on chiara, so we can now view the temperature data on any machine on the martian network, see Attachment 1. 

I also updated the entries on /opt/rtcds/caltech/c1/chans/daq/C0EDCU.ini, as suggested by Koji, to include the SensorGatway temperature channels, but I still don't see their EPICs channels on https://ldvw.ligo.caltech.edu/ldvw/view. This means the channels are not available via nds so I think the temperature data is not being to be written to frame files on framebuilder but I am not sure what this entails, since I assumed C0EDCU.ini is the framebuilder daq channel list.

When the EPICs channels are available via nds, we should be able to display the temperature data on the summary pages.


I've added the other two temperature sensor modules on Y end (on 1Y4, IP: and in the vertex on (1X2, IP: I've updated the martian host table accordingly. From inside martian network, one can go to the browser and go to the IP address to see the temperature sensor status . These sensors can be set to trigger alarm and send emails/sms etc if temperature goes out of a defined range.

I feel something is off though. The vertex sensor shows temperature of ~28 degrees C, Xend says 20 degrees C and Yend says 26 degrees C. I believe these sensors might need calibration.

Remaining tasks are following:

  • Modbus TCP solution:
    • If we get it right, this will be easiest solution.
    • We just need to add these sensors as streaming devices in some slow EPICS machine in there .cmd file and add the temperature sensing channels in a corresponding database file.
  • Python workaround:
    • Might be faster but dirty.
    • We run a python script on megatron which requests temperature values every second or so from the IP addresses and write them on a soft EPICs channel.
    • We still would need to create a soft EPICs channel fro this and add it to framebuilder data acquisition list.
    • Even shorted workaround for near future could be to just write temperature every 30 min to a log file in some location.

[anchal, paco]

We made a script under scripts/PEM/temp_logger.py and ran it on megatron. The script uses the requests package to query the latest sensor data from the three sensors every 10 minutes as a json file and outputs accordingly. This is not a permanent solution.


Attachment 1: Screen_Shot_2021-09-13_at_4.16.22_AM.png
  4243   Thu Feb 3 04:43:58 2011 SureshUpdateElectronicsAdded two new DAQ channels

[Suresh, Joe]

We added the following two new DAQ channels into the c1:GCV model.  The daq:analog input channels are on card ADC0 and correspond to channels 3 and 4 on the card.

c1:GCV-EXT_REF_OUT_DAQ   Sampling rate=2kHz  acquiring a 1Hz sine wave from the SRS Function Generator DS345.  This is using the Rb 10MHz signal as an external frequency reference.

c1:GCV-PLL_OUT_DAQ    Sa.rate=2kHz acquiring the demodulated signal from the PLL servo.

This work is connected to the study of VCO PLL loop noise at frequencies below 0.1Hz.    We are trying to measure phase noise in the VCO PLL servo at low frequencies as this noise would result in arm length fluctuations in the green-locking scheme.




  10130   Sat Jul 5 04:18:45 2014 AndresUpdate40m Xend Table upgradeAdding Two Lenses After the Second Steering Mirror in Order Two Increase the Gouy Phase Difference Between the Sterring Mirrors

I had been working on the Xend table optical layout update. Since the two steering mirrors in the Xend green are too close to each, there is a very small Gouy Phase different between these two mirrors. It was suggested to place two lenses so that we can increase the Gouy Phase. I have been working with Nick on this problem, and we had found a solution by using a la mode. We had written an a la mode code that optimize the Gouy Phase and the Mode Matching at the same time. After trying different lenses, we found the following results: a mode matching of 0.9939 as it is show in the first attachment below, and we found a Gouy Phase different between the two mirrors of about 60 degrees. I took photos of the Xend Table. The first photo is the Xend table as we had it right now. In the second photo, I moved the 2nd lens, and I placed the two more lenses that we need it, with more or lenses the correct position where they will be placed. The three old lenses will be replaced by three lenses of different focal length as it can be seen in the first attachment below. The first lens and third lens will stay in the same position where the old first lens and old third lens are, and the second lens will be moved by about half of an inch. We might have one or two of the lenses that we need, but we will have to order the rest of the lenses that need. My plan is to verify the lenses that we already have. Then, I need to let Nick know with lenses we need to order. Hopefully, we will be able to update the table by the end of this week if everything turn out fine.

Attachment 1: OverlapAndComponentsOfTheSolution.png
Attachment 2: CloseLookToTheGouyPhaseBetweenMirr1AndMirr2.jpg
Attachment 3: EntireRangeOfBeamPath.jpg
Attachment 4: XendTableWithTwoNeedLensesAdding.JPG
Attachment 5: SchematicOfSolutionForTheLensesGouyPhase.jpeg
Attachment 6: XendGreenModeMatchingAndGouyPhaseOptimization.m
clear all
% In this code we are using a la mode to optimatize the mode matching and
% to optimatize the Gouy phase between mirror 1 and mirror 2. All the units
% are in meter

w0=2.943*1e-5; % The Waist of the laser measured before the faraday
z0_laser=-0.039; % position measured where the waist is located 
lamb= 532*10^-9; % wavelength of green light in mm
lFaraday=.0638; % Length of the faraday

... 148 more lines ...
Attachment 7: BeforeIncludingLensesORMovingLenses.JPG
  14074   Mon Jul 16 18:12:00 2018 KojiUpdateVACAdding a manual gate valve between TP1 and V1/VM2

[Steve Koji]

We are in the process of adding a manual gate valve between TP1 (Osaka Maglev) and the other gate valves (I suppose V1 and VM2).
The work is still on going and we will continue to work on this tomorrow. Because this section is isolated from the main volume, this work does not hold off the possible rough pumping tomorrow morning.

The motivation of this work is as follows:
- Since TP2 failed, the main vacuum volume has been pumped down by TP1 and TP3. However TP3 is not capable to handle the large pressure difference at the early stage of the turbo pumping. This cause TP3 to have excessive heating or even thermal shutdown.
- The remedy is to put a gate valve between TPs and the main vacuum to limit the amount of gas flowing into the TPs. This indeed slows down the pumping speed of turbo, but this is not the dominant part of the pumping time.

Actual work:
- Comfirmed TP1 is isolated.
- Unscrewed the flange of TP1.
- Remove TP1. This required to lift up TP1 with some shim as the nuts interferes with the TP1 body. (Attachment1, 2, 3)
- Now remove 10inch flange adapter. (Attachment4)
Attach 10"-8" adapter and 8" rotational sleeve. (Attachment5)

Attachment 1: P_20180716_155413.jpg
Attachment 2: P_20180716_155645.jpg
Attachment 3: P_20180716_155738.jpg
Attachment 4: P_20180716_162307.jpg
Attachment 5: P_20180716_172000.jpg
  4271   Thu Feb 10 14:52:36 2011 AidanHowToComputersAdding filenames in MATLAB plots

The following code is incredibly useful when creating  MATLAB plots as it adds the filename of the script to the plot itself. I think it should be used for all MATLAB plots that go on the elog.

For example, I have no idea where the data/script is that was used to generate these plots.


orient landscape

xposn = 0.0;

yposn = -0.13; % you sometimes have to tweak this value depending on the page size and the number of subplots

text(xposn,yposn,[filename('fullpath'), '.m'], ...

     'Units', 'normalized', ...

     'Interpreter', 'none', ...

     'FontSize', 6)

print('-dpdf', [filename('fullpath'), '.pdf'])

  9430   Wed Nov 27 18:31:26 2013 KojiSummaryLSCAdittion of the ALS error signals to the LSC input matrix

The Phase tracker outputs (= ALS X/Y error signals) are now conveyed to the LSC model.

Their entry points at the LSC model are C1:LSC-ALSX_IN1 and C1:LSC-ALSY_IN1.
They are connected to the signal matrix (28th and 29th signals) via signal conditioning filters (C1:LSC-ALSX and C1:LSC-ALSY).

The main LSC screen has not been updated. The conventional ALS servos are still remains as they were.

This renovation required the recompilation of c1als, c1rfm, and c1lsc. Two PCIe-RFM bridge paths were added resulting in
increase of the c1rfm timing budget from 38 to 44.

  6409   Wed Mar 14 03:34:44 2012 kiwamuUpdateSUSAdjustment of BS suspension output matrix : coupling from SIDE to POS

[Rana / Kiwamu]

 We put some elements in the BS output matrix to mitigate the actuator coupling from SIDE to POS.

As a result the degree of the coupling reduced by a factor of 2 or so.

Rana did the "Q of 5" test on the SIDE damping servo after putting the elements and set the gain to be 40.


The attached screen shot is the new elements that we put in the suspension output matrix.



(How to)

  • Excite the SIDE motion by AWG at 3 Hz.
  • Monitor the POS signal in DTT
  • Try some numbers in the matrix elements until the peak at 3 Hz in the POS signal is minimized

Quote from #6369

The BS SIDE damping gain seemed too low. The gain had been 5 while the rest of the suspensions had gains of 90-500.

I increased the gain and set it to be 80.


I did the "Q of 5" test by kicking the BS SIDE motion to find the right gain value.

However there was a big cross coupling, which was most likely a coupling from the SIDE actuator to the POS motion.

Due to the cross coupling, the Q of 5 test didn't really show a nice ring down time series. I just put a gain of 80 to let the Q value sort of 5.

I think we should diagonalize the out matrices for all the suspensions at some point.


  5288   Tue Aug 23 14:49:14 2011 jamie, jenne, kiwamu, suresh, keikoUpdateSUSAdjustment of ETMY, issue with ITMY whitening

Before lunch we took a closer look at two of the suspensions that were most problematic: ITMY and ETMY.  Over lunch we took new free swinging data.  Results below:

  • For ITMY we discovered that the whitening on the UL sensor was not switching.  This was causing the UL sensor to have a different response, with a steeper roll of, which was causing all of the transfer function estimates to the other sensors to have large imaginary components.   We took new free swing data with all of the whitening turned OFF.  The result is a much improved matrix and diagnalization.  The input matrix elements are mostly the same, but the coupling is basically gone.  We'll fix the whitening after the pump down.
ITMY ITMY.png       pit     yaw     pos     side    butt
UL    0.157   1.311   1.213  -0.090   0.956 
UR    1.749  -0.490   0.886  -0.038  -1.042 
LR   -0.251  -2.000   0.787  -0.007   1.066 
LL   -1.843  -0.199   1.114  -0.059  -0.936 
SD   -0.973  -0.205   1.428   1.000   0.239 
  • ETMY has a very problematic SIDE OSEM.  The magnet does not line up with the OSEM axis, and since there is no lateral adjustment in the side OSEMs, there's not much we can do about this.  We're using aluminum foil to wedge the OSEM over as far as possible, but it's not quite enough.  With the OSEM plates horizontal there is a lot of POS->SIDE coupling.  With the OSEM plates vertical, the magnetic sits a little too close to the rear face, which can cause the magnet to get stuck to the LED plate.  We're trying to decide where to leave it now, but the new diagnalization with the OSEM plates vertical is definitely better: 
ETMX ETMY.png        pit     yaw     pos     side    butt
UL   -0.138   1.224   1.463  -0.086   0.944  
UR    0.867  -0.776   1.501  -0.072  -1.051  
LR   -0.995  -0.896   0.537  -0.045   0.754  
LL   -2.000   1.104   0.499  -0.059  -1.251  
SD    0.011   0.220   1.917   1.000   0.224 
  7901   Tue Jan 15 19:26:35 2013 jamieUpdateAlignmentAdjustment of active TTs and input alignment

[Jamie, Manasa, Jenne]

We started by verifying that the tip-tilts were getting the correct signals at the correct coils, and were hanging properly without touching.

We started with TT2.  It was not hanging freely.  One of the coils was in much further than the others, and the mirror frame was basically sitting on the back side yaw dampers.  I backed out the coil to match the others, and backed off all of the dampers, both in back and the corner dampers on the front.

Once the mirror was freely suspended, we borrowed the BS oplev to verify that the mirror was hanging vertically.  I adjusted the adjustment screw on the bottom of the frame to make it level.  Once that was done, we verified our EPICS control.  We finally figured out that some of the coils have polarity flipped relative to the others, which is why we were seeing pitch as yaw and vice-versa.  At that point we were satisfied with how TT2 was hanging, and went back to TT1.

Given how hard it is to look at TT1, I just made sure all the dampers were backed out and touched the mirror frame to verify that it was freely swinging.  I leveled TT1 with the lower frame adjustment screw by looking at the spot position on MMT1.  Once it was level, we adjusted the EPICS biases in yaw to get it centered in yaw on MMT1.

I then adjusted the screws on MMT1 to get the beam centered at MMT2, and did the same at MMT2 to get the beam centered vertically at TT2.

I put the target at PRM and the double target at BS.  I loosened TT2 from it's base so that I could push it around a bit.  Once I had it in a reasonable position, with a beam coming out at PR3, I adjusted MMT1 to get the beam centered through the PRM target.  I went back and checked that we were still centered at MMT1.  We then adjusted the pitch and yaw of TT2 to get the transmitted beam through the BS targets as clear as possible.

At this point we stopped and closed up.  Tomorrow first thing AM we'll get our beams at the ETMs, try to finalize the input alignment, and see if we can do some in-air locking.

The plan is still to close up at the end of the week.

  7902   Tue Jan 15 20:00:42 2013 ManasaUpdateAlignmentAdjustment of active TTs and input alignment


Just for reference! The changes made to the TT matrix in order to fix the polarity problem:

The old matrix values are mentioned in elog!


PIT    YAW                   New                   

Pit slider           |  -100   -100  |  UL  

     0               | -100    100   |  LL

Yaw slider           |  100   -100   |  UR

    0                |  100    100   |  LR








  4580   Thu Apr 28 10:53:50 2011 josephbUpdateCDSAdventures in Hyper-threading

What was done:

1) Turn off MC1, MC2, MC3, BS, ITMX, ITMY, PRM, SRM watchdogs.

2) Turn c1sus computer off (sudo shutdown now)

3) Go connect monitor and keyboard to c1sus.  Turn c1sus on.

4) Hit "del" key at the right time to go to setup (BIOS).

5) Go to BIOS advanced tab, CPU options, enable Multi-threading.

6) Hit F10 to save and let the computer continue booting.

What went wrong:

Once c1sus was up, I noticed several red lights and dead keep alives for the c1sus models.

Typing dmesg on c1sus revealed many messages like:

[  107.583420] c1x02: cycle 33737 time 20; adcWait 10; write1 0; write2 0; longest write2 0
[  107.583771] c1x02: cycle 33760 time 19; adcWait 11; write1 0; write2 0; longest write2 0

This indicates the Input/Output Processor (IOP) is not completing its duties within the 15 microseconds (1/64 kHz) that it has.  These lines indicate its take 20 or 19 microseconds.  (I saw messages ranging from 16 to 22 microseconds).

So this seems to agree with Rolf's observations that hyperthreading can cause a 5-10 microsecond increase in computation time.

So the next thing to do is modify which core the codes are running on, and try to get them paired up on the same physical core.

  811   Thu Aug 7 17:32:23 2008 JenneUpdateSUSAfternoon PRM activities
Rana, Jenne, Yoichi, Dmass

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

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

Since we have not confirmed that we have spare wire and spare magnets (and due to the time of day), we have decided to cover the cage with some foil, while it is sitting on the flow bench, and we'll fix the wire in the morning.
  5977   Tue Nov 22 14:39:50 2011 JenneUpdateelogAfternoon elog restart

Gave the elog its afternoon / tea-time reboot, since it was hanging yet again.

  5343   Tue Sep 6 11:27:19 2011 JenneUpdateGeneralAfternoon pre-pumpdown todo list

These are the things that I can think of that we need to do before we can close up:

* Take a close look at both ITMs' OSEMs, and ensure that the magnets aren't too close to either plate in the OSEMs.  Both have had funny business over the past week.

* Do a free swinging test on both ITMs.  (ITMY may not need it, if we haven't touched it since the last free swinging test, but it can't hurt to take the data)

* Confirm that POX is exiting the chamber.

* Is there anything else???


Our goal is to finish this work by tonight, so that we can close doors and start pumping tomorrow.

  138   Thu Nov 29 10:36:47 2007 albertoConfigurationComputer Scripts / ProgramsAgilent 82357B GPIB to USB Interface Installation Procedeure
To run the Agilent Automation-Ready CD provided with the interface is only the first step of the installation. Apparently there should be also a second CD with the drivers for Windows XP but I couldn't find it. So, after Installaing the IO Libraries Suite from the CD, I had to install the drivers with an executable downloaded from the Agilent's website at:


and only then I could plug in the interface.
Anyway, I burned a cd with the file and put it together with the other one.
  14322   Tue Nov 27 17:06:51 2018 SteveConfigurationVACAgilent 84FS turbo installed as TP2

Chub & Steve,

We swapped in our  replacement of Varian V70D "bear-can" turbo as factory clean.

The new Agilent TwisTorr 84 FS  turbo pump [ model x3502-64002,  sn IT17346059 ]  with intake screen, fan, vent valve. The controller  [ model 3508-64001, sn IT1737C383 ] and a larger drypump IDP-7,  [ model x3807-64010, sn MY17170019 ] was installed.

Next things to do:

  1. implement hardware interlock to close V4 at 80% pumping speed slowdown of "standby" rotation speed, estimated to be ~ 40,000 RPM ( when Standby 50K RPM  )
  2. set up isolation valve in the foreline of TP2, with delayed start of the IDP-7 and/or use relay to power drypump.  This turbo controller can not switch off or start of the dry pump. [ Agilent isolation valve #X3202-60055, with position indicator, pneumatic actuation, 115V solenoid ]..........as a second thought, we do not need isolation valve if we go with the relay option. The IDP-7 has built in delay of 10-15 sec
  3. test performance of new turbo
  15681   Wed Nov 18 17:51:50 2020 gautamUpdateVACAgilent pressure gauge controller delivered

It is stored along with the cables that arrived a few weeks ago, awaiting the gauges which are now expected next week sometime.

  14572   Thu Apr 25 10:13:15 2019 ChubUpdateGeneralAir Handler Out of Commission

The air handler on the roof of the 40M that supplies the electronics shop and computer room is out of operation until next week.  Adding insult to injury, there is a strong odor of Liquid Wrench oil (a creeping oil for loosening stuck bolts that has a solvent additive) in the building.  If you don't truly need to be in the 40M, you may want to wait until the environment is back to being cool and "unscented".  On a positive note, we should have a quieter environment soon!

  11928   Tue Jan 12 08:40:06 2016 SteveUpdatePEMAir cond maintenance

Air condition maintenance is happening. It should be done by 10am

  12415   Tue Aug 16 21:54:27 2016 gautamUpdateSUSAir-bake - IN PROGRESS

I put in both ETMX and ETMY into the air-bake oven at approximately 8.45pm tonight. They can be removed at 8.45am tomorrow morning. 

  • Given that we had previously melted a thermocouple in this oven, and there have been no high temperature bakes in it since, we ran the oven at 100C for about 3 hours in the afternoon
  • After that, I left the oven door open for an hour for the interior to return to room temperature
  • I then re-connected the controller (which doesn't seem very precise, it pulses the AC power to the oven in order to control the temperature), and dialled the oven back down to heating level 4, which is what Bob had it set at. I then waited for a couple of hours for the oven to reach ~34C
  • Before putting the optics in, I gave the inside of the oven a quick wipe with a clean wipe, and palced a layer of Al foil on the bottom of the oven
  • The optics are sitting on their donuts (see Attachment #1) - the copper wire elevates the optic+donut slightly and provides a path for air flow
  • ETMY was drag wiped with acetone+isopropanol prior to baking (to remove acetone stains from soaking to remove epoxy residue
  • We will of course be cleaning the optics with first contact prior to re-installation in the vacuum chambers
  • I am not sure what the extra cylindrical piece in there is, but Bob advised me to leave it in there so that's what I did
  • I've observed the temperature over ~2hours since I first put it in, and the oven/controller isn't going bonkers, so I'm trusting the controller and leaving for the night
Attachment 1: IMG_3005.JPG
  12416   Wed Aug 17 08:47:43 2016 ericqUpdateSUSAir-bake finished

I turned off the air bake oven at 8:45AM. I'll leave the optics alone for a bit while it cools.

  12420   Wed Aug 17 23:00:57 2016 gautamUpdateSUSAir-bake of towers

I just put in the following into the air bake oven for a 12 hour, 70C bake:

  • ETMX and ETMY cages (with sanded suspension blocks loosely tightened for now, we will tighten them after the bake)
  • 13 new wire clamps that were recently made by the shop
  • 7 lengths of suspension wire (since the new wire is unlikely to arrive for another 2 weeks). This should be sufficient in case we overtighten the wire clamps a couple of times and the wire snaps.

I put these in at 10.30pm. So the oven will be turned off at 10.30am tomorrow morning. The oven temperature seems stable in the region 70-80 C (there is no temperature control except for the in built oven control, I just adjusted the dial till I found the oven remains at ~70C.

Tomorrow, we will look to put on first contact onto the ETMs, and then get about to re-suspending them.

Attachment 1: IMG_3006.JPG
  12422   Thu Aug 18 14:14:20 2016 gautamUpdateSUSAir-bake of towers - finished

I took the two cages, wires and wire clamps out this morning, back into the cleanroom after their 12 hour 70C bake. 

I've also applied first contact to the AR face of the optics. Steve is preparing a jig which will allow us to apply first contact on the HR side with the optic horizontal. The idea is to apply a large coating first, to clean the bulk of the HR surface, and peel it off before re-suspending the optic. Then we can paint on a smaller area, suspend the optic (and hope the pitch balancing is alright) before taking the whole assembly into the chamber where it will be peeled off. 

Calum recommended that we buy a new ionizing gun + electrometer assembly (apparently our current set up is woefully obsolete) but I don't know if we can have these in time for the first contact peeling...

  12411   Mon Aug 15 18:28:15 2016 gautamUpdateSUSAir-bake preparation

I assume that we are prepared to live with the pitch bias situation of ETMY (i.e. we can achieve a configuration in which there is some pitch bias to the coils, and the OSEMs are inserted such that the PD outputs are half their maximum value). Or at least that we don't want to go through the whole standoff-regluing procedure for ETMY as well.

So today I took the optic out, and began to make some preparations for the air bake.

  • Both optics are now sitting in their respective metal donuts. 
  • How do we want to bake the optics? Bob has said he has prepared the oven for this bake, and that he has configured the temperature controller to a setpoint of 34C, and a ramp time of 2 hours to reach that temperature from lab temperature (we should check this before putting the optics in there with our independent temperature sensor - also, he is away for the week now so we can't get his input on any of these). But what about the actual logistics of how the optics are going to be housed? Specifically:
    • Do we want the donut to sit on some sort of tray? Presumably it is not ideal to have the HR surface in close proximity to the oven floor? 
    • Does the oven need any special cleaning?
    • Do we cover the donut+optic setup with a glass jar? If we do, any particles we eject off the optic can't escape the confines of the bowl, and if we don't, detritus from elsewhere may settle on the optic?
    • How long do we want this bake to last? 24hours? 48 hours? Bob didn't have an answer when I asked him earlier in the afternoon...
  • I also removed the suspension block from the top of the towers of both ETMX and ETMY, so that Steve could work on sanding them before we acetone-wipe and bake the towers themselves.
    • It was very apparent that the weights of the two pieces were largely different (ETMY suspension block ~350g, ETMX suspension block ~960g), even though they have the same physical dimensions.
    • Investigation into why this was yielded nothing conclusive. But Steve and I think that the ETMY suspension block is made out of Aluminum rather than SS, which would explain why the wire grooves seem deeper in the ETMY piece than the ETMX piece. It is worth noting that the specification calls for SS and not aluminum. But the top piece of the ETMY suspension (and indeed the old ETMX suspension) looks different from the specification, in that they don't have tapped holes for the secondary wire clamps (see Attachment #1).
    • I'm not sure if this is important, but it is worth noting. Steve and I also checked the remaining suspension towers. We think that ITMY, BS, SRM and PRM have the correct (to specification) suspension block. We couldn't get a look at ITMX and didn't want to take the door off. So ETMY (and possibly ITMX) will be the only suspension(s?) with a different suspension block.
  • Steve's sanding efforts did not go ideally.
    • He was successful in removing the wire grooves.
    • But the sharp edge which is supposed to clamp the wire seems to have been rounded a little bit (see Attachment #1). 
    • Overall, the section that we was sanded looks lower (i.e. its like we've dug a small channel into the plane of the suspension block)
    • Given that we suspect the ETMY suspension block is Aluminum, it is likely that attempting to sand it will yield an even deeper channel.
  • Do we want to bake the suspension towers in the large baking oven? Presumably we don't want to bake the optics with anything else. But does the large oven need any special cleaning before we stick the towers in there?
  • ETMY has some acetone marks on it. I will try and have this removed by drag wiping with more acetone and isopropanol prior to the bake tomorrow. Anyways we will first-contact clean the HR (and AR) sides after the bake before installing the optic.

In summary, the questions that remain (to me) are:

  1. Are we okay using an Al suspension block?
  2. How perfectly do we want wire grooves from prior suspensions removed? It looks like sanding doesn't work well, do we want to consider sending this into the shop?
  3. Baking logistics, as described above.

I think we can start the baking of the optics tomorrow. The timeline for the suspension towers is unclear, depends on how we want to deal with the sanding dilemma.

Attachment 1: IMG_6816.JPG
  578   Thu Jun 26 20:59:22 2008 ranaUpdateComputer Scripts / ProgramsAlarm Handler
Please do not turn off the Alarm Handler on op540m.
  570   Thu Jun 26 01:08:22 2008 ranaConfigurationGeneralAlarm Handler Revived
I have revived the Alarm Handler by turning it on on op540m and adjusting the levels of
several of the alarming channels to not alarm (like laser power). The alarm levels are now
set to something reasonable and people should start actually paying attention to them.

I also removed the EO Shutter and Stacis alarm stuff since we don't use them.

To really get in and edit it, you have to close the Alarm Handler and edit the file
in /cvs/cds/caltech/alh/. It allows you to add/subtract useful channels and put in
guidance information.

If the alarm handler beeps about something, don't just close it or silence it, Steve. Just
fix it somehow (either set the threshold better or find the real cause).
Attachment 1: b.gif
  571   Thu Jun 26 01:10:18 2008 ranaUpdatePEMAlarm Handler indicates that dust level is high
In its first useful act, the Alarm Handler started beeping indicating that the dust particle
counts for particles of diameter less than 0.5 micron had exceeded 5000 /cu. ft.
Here's the
80 day trend of particles, temperature and humidity:
Attachment 1: Untitled.png
  644   Tue Jul 8 00:14:28 2008 JohnSummaryComputersAlarm handler
Rob thought it would be nice to have some alarms on the cpu loads and FE syncs.
I added all these channels to the alarm handler config file and wrote a script
which would set their values (HIHI,HIGH etc).

Ezcawrite allowed me to set the alarm levels (and ezcaread would give the correct
value) but no matter what I set the value to the alarm wouldn't sound.

After experimenting with a few other channels it appears that the alarm handler will
not show alarms if the alarm levels are absent from the db file (even though ezca
gives a value).

I edited the following files so we can have alarms on the cpus.

In c1iscepics:

In c1losepics:

I saved backups in the appropriate folders.

Next time we have a bootfest please also do c1iscepics and c1losepics so these changes
will be implemented.
  14863   Fri Sep 6 16:38:24 2019 aaronUpdateALARMAlarm noise from smart-ups machine under workstation?

There was an alarm sound from the Smart-UPS 2200 sitting under the workstation. I see that the 'replace battery' light is red, and this elog tells me that these batteries are replaced every ~1-4 years; the last replacement was march 2016. Holding down the 'test' button for 2-3 seconds results in the alarm sound and does not clear the replace battery indicator.

  14864   Fri Sep 6 18:08:29 2019 ranaUpdateComputersAlarm noise from smart-ups machine under workstation?

please no one touch the UPS: last time it destroyed ROSSA. Please ask Chub to order the replacement batteries so we can do this in a controlled way (fully shutting down ALL workstations first). Last time we wasted 8 hours on ROSSA rebuilding.


There was an alarm sound from the Smart-UPS 2200 sitting under the workstation. I see that the 'replace battery' light is red, and this elog tells me that these batteries are replaced every ~1-4 years; the last replacement was march 2016. Holding down the 'test' button for 2-3 seconds results in the alarm sound and does not clear the replace battery indicator.

  1766   Tue Jul 21 01:11:30 2009 DmassAoGComputersAlarms going off

I came into the 40m to sign things out briefly then swiftly return them, and the alarms were going off on op540m at 1am.


The cat and donkey? were making much noise.

  15634   Mon Oct 19 15:40:02 2020 KojiUpdatePEMAlaska EQ M7.5

Alaska M7.5 20:54UTC https://earthquake.usgs.gov/earthquakes/eventpage/us6000c9hg/executive

I looked at the suspensions. The watchdogs have not been tripped.

IMC was locked but continually shaken. (and occasional unlock)

  4758   Sat May 21 17:02:38 2011 KojiUpdateElectronicsAlberto's 11MHz was modified to POP55MHz

- Resonant at 55MHz. The transimpedance is 258Ohm. That is about half of REFL55 (don't know why).

- 11MHz&110MHz notch

- The 200MHz oscillation of MAX4106 was damped by the same recipe as REFL11.



Attachment 1: POP55_schematic_110520_KA.pdf
POP55_schematic_110520_KA.pdf POP55_schematic_110520_KA.pdf
Attachment 2: POP55_transimpedance.pdf
  1159   Mon Nov 24 16:43:34 2008 ranaConfigurationComputersAlex and Jay took away some computers from the racks
I was over at Wilson house and saw Jay and Alex bring in 3 rackmount computers. One was a Sun 4600 and
then there were 2 3U black boxes. I got the impression that these were the data concentrators or
data collectors or framebuilder test boxes. They said that they got these from the 40m and no one was
in the lab to oppose them except for Bob and he didn't put up much of a fight.

Everything looks green on the DAQ Detail and RFM network screens so perhaps everything is OK. Beware.
  3836   Mon Nov 1 14:53:30 2010 josephb, alex, rolfUpdateCDSAlex updated FB and mx_streams code


The framebuilder was being flaky.  MX_streams would go down, prevent testpoints from working and so forth.


Send Alex up North for a week to fix the code. 

Alex came back and installed updates to the frame builder and the mx_streams code (Myrinet Express over Generic Ethernet Hardware) used by the front ends to talk to the frame builder.  Instead of 1 stream per model, there's now just 1 per front end handling all communications.

Alex did an SVN update and we now have the latest CDS code.

Self restarting codes:

The frame builder code (daqd) and nds pipe have been added to the fb machine's inittab.  Specifically it calls a script called /opt/rtcds/caltech/c1/target/fb/start_daqd.inittab and /opt/rtcds/caltech/c1/target/fb/start_nds.inittab.

The addition to the /etc/inittab file on fb is:



When these codes die they should automatically restart.

Self starting codes at boot up:

The front ends now start the mx_stream script (which lives in /opt/rtcds/caltech/c1/target/fb/ directory) at boot up.  They call it with the approriate command line options for that front end. It can be found in the /etc/rc.local file.

They look like: mx_stream -s "c1x02 c1sus c1mcs c1rms" -d fb:0

As always, the front end codes to be started are defined in the /etc/rtsystab file (or on fb, in the /diskless/root/etc/rtsystab file).

However, if it does go down you would need to restart it manually, although it seems more robust now and doesn't seem to go down every time we restart the frame builder.

All the usual front end IOCs and modules should be started and loaded on boot up as well.


Current CDS status:

MC damp dataviewer diaggui AWG c1ioo c1sus c1iscex RFM Sim.Plant Frame builder  ...
  7101   Tue Aug 7 11:46:24 2012 JamieUpdateCDSAlex working on daqd

Alex is apparently working on daqd (remotely).  I'll report back when I find out more.

  683   Wed Jul 16 16:59:07 2008 AlbertoUpdateGeneralAligment
I think the two beams are aligned again - they both pass the Faraday, they match at the irises and all along the optical path on the AP table. Although the NPRO beam does not show up at the AS port.
  14151   Thu Aug 9 22:50:13 2018 gautamUpdateCDSAlignSoft script modified

After this work of increasing the series resistance on ETMX, there have been numerous occassions where the insufficient misalignment of ETMX has caused problems in locking vertex cavities. Today, I modified the script (located at /opt/rtcds/caltech/c1/medm/MISC/ifoalign/AlignSoft.py) to avoid such problems. The way the misalign script works is to write an offset value to the "TO_COIL" filter bank (accessed via "Output Filters" button on the Suspension master MEDM screen - not the most intuitive place to put an offset but okay). So I just increased the value of this offset from 250 counts to 2500 counts (for ETMX only). I checked that the script works, now when both ETMs are misaligned, the AS55Q signal shows a clean Michelson-like sine wave as it fringes instead of having the arm cavity PDH fringes as well yes.

Note that the svn doesn't seem to work on the newly upgraded SL7 machines: svn status gives me the following output.

svn: E155036: Please see the 'svn upgrade' command
svn: E155036: Working copy '/cvs/cds/rtcds/userapps/trunk/cds/c1/medm/MISC/ifoalign' is too old (format 10, created by Subversion 1.6)

 Is it safe to run 'svn upgrade'? Or is it time to migrate to git.ligo.org/40m/scripts?

Attachment 1: MichelsonFringing.png
ELOG V3.1.3-