40m QIL Cryo_Lab CTN SUS_Lab CAML OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 302 of 354  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  6970   Thu Jul 12 16:27:04 2012 steveUpdateVACdrypump changed

TP2  dry_pump was changed at intake pressure 982 mTorr at 84,889 hrs  This seal hold up for one year.

The rebuilt  pump seal performing well at 28 mTorr

  14256   Mon Oct 15 13:59:42 2018 SteveUpdateVACdrypump replaced

Steve & Bob,

Bob removed the head cover from the housing to inspect the condition of the the tip seal. The tip seal was fine but the viton cover seal had a bad hump. This misaligned the tip seal and it did not allow it to rotate.

It was repositioned an carefully tithened. It worked. It's starting current transiant measured 28 A and operational mode 3.5 A

This load is normal with an old pump. See the brand new DIP7 drypump as spare was 25 A at start and  3.1 A in operational mode. It is amazing how much punishment a slow blow ceramic 10A  fuse can take [ 0215010.HXP ]

In the future one should measure the current pick up [ transient <100ms ] after the the seal change with Fluke 330 Series Current Clamp


It was swapped in and the foreline pressure dropped to 24 mTorr after 4 hours. It is very good. TP3 rotational drive current  0.15 A at 50K rpm   24C


Gautam and Steve,

Our TP3 drypump seal is at 360 mT [0.25A load on small turbo]  after one year.  We tried to swap in old spare drypump with new tip  seal. It was blowing it's fuse, so we could not do it.

Noisy aux drypump turned on and opened to TP3 foreline [ two drypumps are in  the foreline now ]  The pressure is 48 mT and 0.17A load on small turbo.


Attachment 1: drypump_swap.png
  6554   Sat Apr 21 17:38:19 2012 JamieUpdateCDSdtt, dataviewer working; problem with trend frames


Another big problem is the workstation application upgrades.  The NDS protocol version has been incremented, which means that all the NDS client applications have to be upgraded.  The new dataviewer is working fine (on pianosa), but dtt is not:

controls@pianosa:~ 0$ diaggui
diaggui: symbol lookup error: /ligo/apps/linux-x86_64/gds-2.15.1/lib/libligogui.so.0: undefined symbol: _ZN18TGScrollBarElement11ShowMembersER16TMemberInspector
controls@pianosa:~ 127$

 dtt (diaggui) and dataviewer are now working on pianosa to retrieve realtime data and past data from DQ channels.

Unfortunately it looks like there may be a problem with trend data, though.  If I try to retrieve 1 minute of "full data" with dataviewer for channel C1:SUS-ITMX_SUSPOS_IN1_DQ around GPS 1019089138 everything works fine:

Connecting to NDS Server fb (TCP port 8088)
Connecting.... done
T0=12-04-01-00-17-45; Length=60 (s)
60 seconds of data displayed

but if I specify any trend data (second, minute, etc.) I get the following:

Connecting to NDS Server fb (TCP port 8088)
Connecting.... done
Server error 18: trend data is not available
datasrv: DataWriteTrend failed in daq_send().
T0=12-04-01-00-17-45; Length=60 (s)
No data output.

Alex warned me that this might have happened when I was trying to test the new daqd without first turning off frame writing.

I'm not sure how to check the integrity of the frames, though.  Hopefully they can help sort this out on Monday.

  15833   Mon Feb 22 14:53:47 2021 gautamUpdateCDSdtt-ezca-tools installed on rossa

The defaults cds-crtools didn't come with some of the older ezcautils (like ezcaread, ezcawrite etc). This is now packaged for debian, so I installled them with sudo apt update && sudo apt install dtt-ezca-tools on rossa. Now, we don't have to needlessly substitute the commands in our old shell scripts with the more modern z read, z write etc.

I am wondering if there is a relative implicit minus sign between the z servo and ezcaservo commands...

  579   Thu Jun 26 21:07:11 2008 ranaConfigurationASSdust & MC1
I realized today, that yesterday while we were trying to debug the adaptive noise canceler, I turned
off the analog dewhitening on MC1. I did this by changing settings on the Xycom screen but I
forgot to elog this -- this may have caused problems with locking via increased frequency noise.
I have now returned it to its nominal, dewhitening on, configuration.

I also used mDV to look at the last year of dust trend. I have plotted here the cumulative
histogram in percentile units of the 0.5 micron dust level. The x-axis is in units of particles per cu. ft.
and the y-axis is percentage. For example, the plot tells us that over the last year, the counts were
below 6000, 90% of the time. I have set the yellow and red alarm levels to alarm at the 95-th and 99-th
percentile levels, respectively.
Attachment 1: Screenshot-2.png
  581   Fri Jun 27 09:20:15 2008 steveFrogsPEMdust particle count is up & alarm handler is on
This 3 years plot show the trend of seasons.
When outside air quality goes bad ( 0.5 micron > 1 million ) the lab follows.
I will demonstrate this effect with a 4th of July fire works calibration.
Let's do not forget the construction activity next door either.

The alarm handler is busy:
It's sound level were reset to a modest level yesterday.
It would be nice to change the alarm sound so it can play Wagner:Der Ring des Nibelungen:
Das Rheingold, Die Walkure & Siegfried and Gotterdammerung
or something more appropriate than the present frog call

1, half micron count is climbing ( it's close to 16k now )
2, MZ refl signal is too high
3, MC lenght servo LO is too
Attachment 1: dust3y.jpg
  10922   Tue Jan 20 09:32:19 2015 SteveUpdatePEMdusty Monday morning

Yesterday morning was dusty. I wonder why?

The PRM sus damping was restored this morning.

Attachment 1: dustyMorning.png
  10983   Fri Feb 6 10:03:23 2015 SteveUpdatePEMdusty days



Yesterday morning was dusty. I wonder why?

The PRM sus damping was restored this morning.

Yesterday afternoon at 4 the dust count peaked 70,000 counts

Manasa's alergy was bad at the X-end yesterday. What is going on?

There was no wind and CES neighbors did not do anything.

Attachment 1: duststorm.png
  12084   Wed Apr 20 14:36:45 2016 SteveUpdatePEMdusty lab

It is worth wiping table top covers. Use isopropanol soaked lint free wipes.


Attachment 1: AP_accm.jpg
Attachment 2: wiped_AP.jpg
Attachment 3: temp-partic_6months.png
Attachment 4: 3_years_PEM.png
  13990   Wed Jun 20 09:16:56 2018 SteveUpdatePEMdusty lab

You should wipe off the table cover before you take it off next time.

It is important to turn up the PSL encloure HEPA Variac voltage if you are working in there. It takes less than 10 minutes to reach lab condition.

Lab air count normal. It is not logged. I have a notebook of particle count on the SP table next to the Met One counter.


Chris replaced some air condition filters and ordered some replacement filter today.



Attachment 1: AP.JPG
Attachment 2: ITMY.JPG
Attachment 3: ITMX.JPG
Attachment 4: SP.JPG
  9591   Mon Feb 3 10:17:14 2014 SteveUpdatePEMdusty surfaces

Please wet WIPE before opening chamber or optical table ! ! 

 with methanol soaked kimwipes.

The Met One particle counter is located on CES wall, just behind ITMX chamber. 

The numbers are not so bad, but have you ( ...a)  asked the IFO lately?

Attachment 1: AP-ISCT.jpg
Attachment 2: BSC-rim.jpg
Attachment 3: ITMX-ISCT.jpg
Attachment 4: 12daysAtm.png
  3426   Mon Aug 16 23:13:25 2010 ZachUpdateeloge to the log


  • I get so many freebies it's ridiculous
  3540   Tue Sep 7 23:34:15 2010 Kiwamu, SanjitConfigurationComputerse-log

e-log was repeatedly hanging and several attempts to start the daemon failed.

problem was solved after clearing the (firefox) browser cache, cookie, everything!!


  2446   Tue Dec 22 15:49:31 2009 kiwamuUpdateGenerale-log restarted

I found the e-log has been down around 3:40pm, then I restarted the e-log. Now it's working.


  17833   Thu Sep 7 21:09:17 2023 PacoUpdate eCARM and eDARM to ALS CARM and ALS DARM

Tonight I managed to lock CARM and DARM under ALS control only


  • Arm cavities well aligned, TRY ~ 1.07, TRX ~ 0.98, GTRY ~ 1.2, GTRX ~ 0.77
  • HEPA off, WFS 60s offloaded, PD offsets removed, all lights inside the lab were off
  • BEATX and BEATY ool residual noise shown in Attachment #1.
  • Error points, the A path was the same as what is used for electronic FPMI. For the B path, I describe the tuning below.
    • CARM_A = 0.5 * POX11_I + 0.5 * POY11_I
    • DARM_A = 0.19 * POX11_I - 0.19 * POY11_I
    • CARM_B = -0.7 * ALSX + 0.4 * ALSY  
    • DARM_B = -0.25 * ALSX - 0.17 * ALSY
  • Power normalization of the error signals was 0.5 * TRX + 0.5 * TRY in both paths.
  • LSC filter banks are the same ones we use for electronic FPMI, and the gains were
    • CARM = 0.011  (UGF ~ 200 Hz) using FM1 to FM5, FM6 and FM8
    • DARM = 0.055 (UGF ~ 150 Hz) using FM1 to FM5, FM6 and FM8
  • Control points, I temporarily disabled violin filters around 600 Hz to ease the lock acquisition ... we should really use the VIO TRIG here to avoid having to do this.
    • CARM = -0.734 * MC2
    • DARM = 0.5 * ETMX - 0.5 * ETMY

ALS error signal tuning

To find the error signals for CARM/DARM, I turned on the oscillators (at 307.8 and 313.31 Hz respectively) with 150 counts and enabled FM10 (Notch for sensing matrix) in the CARM and DARM servo banks. I then removed the ALS offsets (C1:LSC-ALSX_OFFSET, C1:LSC-ALSY_OFFSET) and looked at the transfer functions shown in Attachment #2. I optimized the ALS blending until I maximized the CARM and DARM A to B paths and minimized CARM and DARM cross couplings. The signs were chosen to leave a phase of 0.


After measuring the OLTFs for eCARM and eDARM (loop closed with the A error point) and tuning the ALS error signals, I gradually blended the A and B paths and checked the OLTFs for CARM and DARM. During this I realized I needed to disable some of the notch violin filters because they sometimes made the DARM loop unstable after >50% blending. In the end the simultaneous CARM_A/DARM_A to CARM_B/DARM_B handoff was successful in 0.5 seconds. Attachment #3 shows the OLTFs under ALS control.

CARM offset

After getting nominally stable ALS control, I tried adding an offset. The LSC CARM offset range was insufficient, so I ended up directly scanning the C1:LSC-ALSX_OFFSET and C1:LSC-ALSY_OFFSET. The first couple of attempts the ramp time was set to 2.0 seconds, and a step of 0.01 was enough to break the lock. I managed to hold the control with as much as C1:LSC_CARM_A_IN1 offset by ~ 500 (rms ~ 200 counts). I roughly estimate this to be ~ 5% of the CARM pole which is 4 kHz in this case so overall 200 Hz which is not that large.

Attachment 1: ALSCARMDARMlock_oolnoise_Screenshot_2023-09-07_21-32-31.png
Attachment 2: ALSerrortuning_Screenshot_2023-09-07_21-33-10.png
Attachment 3: ALSCARMDARM_oltfs_Screenshot_2023-09-07_21-36-34.png
  1076   Thu Oct 23 18:51:19 2008 AlbertoMetaphysicsComputerseLog
I checked it and the latest version of the elog software, the 2.7.5 (we have the 2.6.5) has, among new nice features, the very good ability to fit the entries into the screen width without showing kilometric lines like we see now. Should we upgrade it?
  1   Wed Oct 17 18:46:33 2007 ranaConfigurationGeneraleLog Change
This is the first entry in the new 40m eLog.

Its GWs or bust now! Big grin

  3384   Sat Aug 7 21:09:59 2010 DmassConfigurationComputer Scripts / ProgramseLog changes

I made some changes to the elog on nodus:

  • Made a backup of /cvs/cds/caltech/elog/elog-2.7.5/elogd.cfg called elogd.cfg.bk.20100407 in the same directory
  • Added a folder: /cvs/cds/caltech/elog/elog-2.7.5/logbooks/EAGER_Lab
  • Restarted the elog daemon via the start-elog-nodus script in the elog-2.7.5 directory

I saw that the current version of the elog seems to be in the svn, so tried to svn the changes from nodus via ssh, but got this message:

"svn: This client is too old to work with working copy '/cvs/cds/caltech/elog/elog-2.7.5'; please get a newer Subversion client."

I feel I should svn this but don't want to *&#@ the svn/elog up.

For now I will leave it alone and ask a question: Is the folder /cvs/cds/caltech/elog/elog-2.7.5/ under SVN control? Is it also under CVS control?


TL;DR:  New tab added to elog.


  416   Mon Apr 7 16:42:56 2008 ranaUpdateComputerseLog intermittent
Phil Ehrens restarted Dziban again this morning. Looks like its still crashing each Monday around 8 AM.

Here is the latest suspect:

  491   Thu May 22 11:21:45 2008 steveBureaucracySAFETYearly surf sudent
Caltech under grad Eric Mintun received the 40m safety training.
Now he has to read and sign SOP of laser and ifo.
He'll be working with GigE cameras with Joe
  11610   Thu Sep 17 08:36:14 2015 SteveUpdatePEMearth quake

No damage. The BS sensor UR 0.220 V has been low for some times.

Dataviewer does not work for long term trend.

Attachment 1: Chilian_eq_8.3M.png
Attachment 2: BS_UR_0.220V.png
Attachment 3: LowSensingV_BS-UR.png
  14176   Wed Aug 22 08:44:09 2018 SteveUpdateGeneralearth quake

6.2M Bandon, OR did not trip any sus


Attachment 1: yesterday_EQs.png
  14321   Tue Nov 27 10:50:20 2018 SteveUpdatePEMearth quake Mexico

Nothing tripped.


Attachment 1: 5.5M.Mexico.png
  33   Tue Oct 30 20:15:24 2007 tobinOtherEnvironmentearthquake
Rana, Tobin

Largish (M5.6) earthquake in San Francisco sent our optics swinging.
  1539   Fri May 1 18:51:34 2009 AlbertoSummaryEnvironmentearthquake

Earthquake 4.4 Leo Carrillo Beach.

Some of the watchdogs tripped out.

  2046   Fri Oct 2 18:26:32 2009 robAoGEnvironmentearthquake

quake coming through.  I've re-enabled optic damping (except ETMY), and left off the oplevs for now.  We can do a resonant-f  check over the weekend.

Looks like it was a magnitude 5 near Olancha, where they sell really good fresh jerky.  quake

Earthquake Details

Magnitude 5.2
  • Saturday, October 03, 2009 at 01:15:59 UTC
  • Friday, October 02, 2009 at 06:15:59 PM at epicenter
Location 36.393°N, 117.877°W
Depth 0 km (~0 mile) (poorly constrained)
  • 11 km (7 miles) S (182°) from Keeler, CA
  • 16 km (10 miles) ENE (59°) from Cartago, CA
  • 18 km (11 miles) NE (37°) from Olancha, CA
  • 28 km (17 miles) SE (141°) from Lone Pine, CA
  • 239 km (148 miles) W (276°) from Las Vegas, NV
Location Uncertainty horizontal +/- 0.6 km (0.4 miles); depth +/- 2.2 km (1.4 miles)
Parameters Nph=030, Dmin=19 km, Rmss=0.28 sec, Gp= 79°,
M-type=local magnitude (ML), Version=C
Event ID ci14519780
  • This event has been reviewed by a seismologist.

latest news: there's actually been about a dozen earthquakes in Keeler in the last couple hours:   http://earthquake.usgs.gov/eqcenter/recenteqsus/Maps/special/California_Nevada_eqs.php


  6558   Tue Apr 24 09:58:37 2012 steveUpdatePEMearthquake 3.9 magnitude

Local eq shakes the lab

Attachment 1: eq3.9.png
  797   Tue Aug 5 10:23:00 2008 steveUpdateSUSearthquake and venting effects
atm 1, EQ
atm 2, vent 7 days later: venting kicks optic into place to be free,
PRM: LR magnet gets pushed in and it is stocked, side in free
Attachment 1: eq4h.jpg
Attachment 2: vent4hr.jpg
  2765   Mon Apr 5 08:43:48 2010 steveUpdatePEMearthquake mag 7.2

Large earthquake shakes Baja California, Mexico and 6 over Magnitude 5 aftershakes follow.  The frontend computers are still down since Friday.

Attachment 1: eq7.2.jpg
  462   Thu May 1 08:31:51 2008 steveUpdateSUSearthquake trips etmy & mc1
Earthquake at Lake Isabel magnitude 4.4 at 1am today shakes the 40m
ETMY and MC1 watchdogs tripped.
Sus damping restored.
  7281   Mon Aug 27 08:34:18 2012 SteveUpdatePEMearthquakes

Shasky day yesterday postpones venting. We had about 11 shakes larger than mag 4.0 Mag5.5 was the largest at  13:58 Sunday, Aug 26 at  the Salton Sea area.

Atm3,  ITMX and ETMX  did not come back to it's position

Attachment 1: eq5.5Msaltonsea.png
Attachment 2: M5.5inaction.png
Attachment 3: EQeffect.png
  13309   Mon Sep 11 16:46:09 2017 SteveUpdatePEMearthquakes

I was trying to get a lossmap measurement over the weekend but had some trouble first with the IMC and then with the PMC.

For the IMC: It was a bit too misaligned to catch and maintain lock, but I had a hard time improving the alignment by hand. Fortunately, turning on the WFS quickly once it was locked restored the transmission to nominal levels and made it maintain the lock for longer, but only for several minutes, not enough for a lossmap scan (can take up to an hour). Using the WFS information I manually realigned the IMC, which made locking easier but wouldn't help with staying locked.

For the PMC: The PZT feedback signal had railed and the PMC had been unlocked for 8+ hours. The PMC medm screen controls were generally responsive (I could see the modes on the CCDs changing) but I just couldn't get it locked. c1psl was responding to ping but refusing telnet so I keyed the crate, followed by a burt restore and finally it worked.

After the PMC came back the IMC has already maintained lock for more than an hour, so I'm now running the first lossmap measurements.

Southern Mexio is still shaking..... so as we

Attachment 1: M5.4eq.png
  13322   Tue Sep 19 14:00:41 2017 SteveUpdatePEMearthquakes

No sus tripped. Seimometers do not see the 5.3M  ?


Southern Mexio is still shaking..... so as we


Attachment 1: 7.1MX5.3J.png
  13402   Fri Oct 27 09:34:20 2017 SteveUpdatePEMearthquakes

Lompoc 4.3M and 3.7M Avalon


Attachment 1: recentEQs.png
  13581   Thu Jan 25 08:27:25 2018 SteveUpdatePEMearthquakes

M4 local earthquake at 10:10 UTC    There is no sign of damage.

....here is an other one.........M5.8 Ferndale, CA at 16:40 UTC


Attachment 1: M4_local_eq.png
Attachment 2: M4.png
Attachment 3: M5.8Ferndale_CA.png
  5566   Wed Sep 28 15:33:58 2011 SureshUpdateComputer Scripts / Programsediting database files for medm screens and restarting the slow c1psl machine

I changed the names on a switch(SW1) in the C1:PSL-FSS screen.  To do this I had to edit the psl.db database file in the directory /cvs/cds/caltech/target/c1psl.  After this change, when I executed this screen, all fields in the C1PSL_FSS screen went blank.  As the change to database file takes effect only after we restart the C1PSL machine (slow machine) I went ahead and reset the c1psl machine.  I then used the burttoday to locate the most recent snapshot files and then used burtgooey to restore all the values in the c1psl.snap file.

Everything back to normal now.


  3959   Sat Nov 20 01:58:56 2010 yutaHowToCDSeditting RT models and MEDM screens

(Suresh, Yuta)

If you come up with a good idea and want to add new things to current RT model;

 1. Go to simLink directory and open matlab;
    cd /cvs/cds/rtcds/caltech/c1/core/advLigoRTS/src/epics/simLink

 2. In matlab command line, type;
    addpath lib

 3. Open a model you want to edit.
    open modelname

 4. Edit! CDS_PARTS has useful CDS parts.
    open CDS_PARTS
    There are some traps. For example, you cannot put cdsOsc in a subsystem

 5. Compile your new model. See my elog #3787.
 6. If you want to burt restore things;
    cd /cvs/cds/caltech/burt/autoburt/snapshots/YEAR/MONTH/DATE/TIME/

 7. Edit MEDM screens
    cd /cvs/cds/rtcds/caltech/c1/medm

 8. Useful wiki page on making a new suspension MEDM screens;

  3708   Wed Oct 13 18:01:43 2010 yutaHowToCDSeditting all the similar medm screens

(Joe, Yuta)

Say, you want to edit all the similar medm screens named C1SUS_NAME_XXX.adl.

1. Go to /opt/rtcds/caltech/c1/medm/master and edit C1SUS_DEFAULTNAME_XXX.adl as you like.

2. Run generate_master_screens.py.

That's it!!

  2980   Tue May 25 09:12:46 2010 kiwamuConfigurationGreen Lockingeffect from air conditioner

We should completely turn off the air conditioner when working on green locking.

Even if green beams propagates inside of chambers, the air conditioner does affect the spatial jitter of the beam. 

The attached picture was taken when Steve and I were seeing how the green beam jittered. 

At that time the beam was injected from the end table and going through inside of the ETM, the ITM and the BS camber.

Eventually it came out from the camber and hit the wall outside of the chamber. It was obvious, we could see the jittering when the air cond. was ON.

Attachment 1: green_spot.png
  1533   Wed Apr 29 15:56:43 2009 robUpdateLockingeffect of SRCL detune on ARM powers in a CARM sweep

With no DARM offset, sweeping CARM shows an asymmetry between the state where we lock to a DARM spring and the state with a DARM anti-spring.  This is why we have a link between the DARM and CARM optical springs. 

For each DARM detune direction (positive or negative, spring or anti-spring), there is only one CARM direction which can yield a DC-based error signal lock with a CARM offset but no DARM offset, which is what we want.

Attachment 1: CARMsweep_DARMspringnospring.png
  16967   Thu Jun 30 19:24:24 2022 ranaSummaryPEMeffect of nearby CES construction

For the proposed construction in the NW corner of the CES building (near the 40m BS chamber), they did a simulated construction activity on Wednesday from 12-1.

In the attached image, you can see the effect as seen in our seismometers:

this image is calculated by the 40m summary pages codes that Tega has been shepherding back to life, luckily just in time for this test.

Since our local time PDT = UTC - 7 hours, 1900 UTC = noon local. So most of the disturbance happens from 1130-1200, presumably while they are setting up the heavy equipment. If you look in the summary pages for that day, you can also see the IM lost lock. Unclear if this was due to their work or if it was coincidence. Thoughts?

  3023   Tue Jun 1 06:30:38 2010 KojiConfiguration40m Upgradingeffect of the arm length

I checked the effect of the arm length to the reflectance of the f2(=5*f1) sidebands.

Conclusion: If we choose L_arm = 38.4 [m], it looks sufficiently being away from the resonance
We may want to incorporate small change of the recycling cavity lengths so that we can compensate the phase deviation from -180deg.

f1 of 11.065399MHz is assumed. The carrier is assumed to be locked at the resonance.

Attachment 1: (Left) Amplitude reflectance of the arm cavity at f2 a a function of L_arm. (Right) Phase
Horizontal axis: Arm length in meter, Vertical Magnitude and Phase of the reflectance

At L=37.93 [m], f2 sidebands become resonant to the arm cavity. Otherwise, the beam will not be resonant.

Attachment 2: close-up at around 5 f1 frequency.
The phase deviation from the true anti resonance is ~0.7deg. This can be compensated by both PRC and SRC lengths.

Attachment 1: arm_cavity1.png
Attachment 2: arm_cavity2.png
Attachment 3: arm_cavity.nb.zip
  1962   Tue Sep 1 11:23:36 2009 steveUpdateGeneralelectrical ground

I was told yesterday, that on Friday the construction people accidentally ripped out one of the 40m soil ground.....AND HOW MANY MORE ARE THERE? nobody knows.

It was ~8 ft long and 0.5" diameter buried in the ground. There is no drawing found to identify this exact building ground. They promised to replace this on Wednesday with a 10 ft long and 0.75" diameter.

The  the wall will be resealed where the conduit enters  the  north west corner of the IFO room 104


There should be no concern about safety because the 40m building main ground is connected to the CES Mezzanine step-down transformer.

Attachment 1: ground.JPG
  1965   Thu Sep 3 11:20:26 2009 steveUpdateGeneralelectrical ground in place


I was told yesterday, that on Friday the construction people accidentally ripped out one of the 40m soil ground.....AND HOW MANY MORE ARE THERE? nobody knows.

It was ~8 ft long and 0.5" diameter buried in the ground. There is no drawing found to identify this exact building ground. They promised to replace this on Wednesday with a 10 ft long and 0.75" diameter.

The  the wall will be resealed where the conduit enters  the  north west corner of the IFO room 104


There should be no concern about safety because the 40m building main ground is connected to the CES Mezzanine step-down transformer.

 Atm1 is showing ground bus under N-breaker panel in 40m IFO room north-west corner.

The second ground bus is visible farther down south under M-breaker panel.

Atm2 is the new ground that will be connected to ground bus-N

Attachment 1: Gs-n.JPG
Attachment 2: newground.JPG
  2200   Fri Nov 6 19:29:24 2009 JenneUpdateelogelog acting up

elog was acting up again (not running), so I restarted it. 

  2201   Fri Nov 6 20:10:15 2009 JenneUpdateelogelog acting up


elog was acting up again (not running), so I restarted it. 


And again.  This makes 4 times since lunchtime yesterday....something bad is up.

  1562   Fri May 8 04:31:35 2009 ranaUpdateComputer Scripts / Programselog and NDS
In the middle of searching through the elog, its stopped responding. So I followed the Wiki instructions
and restarted it (BTW, don't use the start-elog-nodus script that's in that directory). Seems OK now,
but I am suspicious of how it sometimes does the PDF preview correctly and sometimes not. I found a
'gs' process on there running and taking up > 85% of the CPU.

I also got an email from Chris Wipf at MIT to try out this trick from LASTI to maybe fix the
problems I've been having with the DMF processes failing after a couple hours. I had compiled but
not tested the stuff a couple weeks ago.

Today after it failed, I tried running other stuff in matlab and got some "too many files open" error messages.
So I have now copied the 32-bit linux NDS mex files into the mDV/nds_mexs/ directory. Restarted the
seisBLRMS.m about an hour ago.
  1567   Fri May 8 16:29:53 2009 ranaUpdateComputer Scripts / Programselog and NDS
Looks like the new NDS client worked. Attached is 12 hours of BLRMS.
Attachment 1: Untitled.png
  10819   Fri Dec 19 16:39:25 2014 ericqUpdateComputer Scripts / Programselog autostart

I've set up nodus to start the ELOG on boot, through /etc/init/elog.conf. Also, thanks to this, we don't need to use the start-elog.csh script any more. We can now just do:

controls@nodus:~  $ sudo initctl restart elog

I also tweaked some of the ELOG settings, so that image thumbnails are produced at higher resolution and quality. 

  5304   Thu Aug 25 17:40:07 2011 DmassUpdateComputer Scripts / Programselog broke, fixed

elog died b/c someone somewhere did something which may or may not have been innocuous. I ran the script in /cvs/cds/caltech/elog to restart the elog (thrice).


I have now banned Warren from clicking on the elog from home

ELOG V3.1.3-