The differences between this setup and the one used previously is the lack of the 50 Ohm terminator in the mixer output and

that the SR560 readout with the G=100 should come before the first SR560 via T, so as not to be spoiled by the high noise of the G=1 SR560.

Alex, Joe:

We copied the latest x02 to c1x02 and modified to our the config block in it.

We removed gds_node_id.  We just have one number now, the dcuid, which is unique for each controller, simulated plant and IOP.  Set site to C1 and host to c1sus.

Alex made the latest awgtpman backwards compatible, and checked that into svn.

We installed the latest framecpp onto c1sus from www.ldas-sc.ligo.caltech.edu/packages/ using wget.

wget www.ldas-sc.ligo.caltech.edu/packages/framecpp-1.18 and then used make.

This let us compile diagd on c1sus, using the command make stand in the /advLigoRTS/build area.

We copied gds from the seiteststand over at handford and are trying to build that on megatron.  However, there's a bunch of packages we need for it to install properly.  Alex said he'd work on that later, possibly trying to make some portable binaries.

Checked out the latest dataviewer into /opt/rtcds/caltech/c1/core/daq, however its not quite working yet either.  This is another thing Alex said he'll work on later.

We are also going to test Alex and Rolf's kernel patch over on c1iscex on Centos base kernel (apparently they've been using Gentoo up at hanford for the test stands...) and see how that works.

I measured the phase noise of the LO output of the FSS box from the DAQ. I'm attaching the results.

As we expected, the measurement is limited by the internal phase noise of the Marconi.

The measurement was done as shown in this diagram.

Crane balancing at the south end is continuing today.

 I just turned on the other Sorensen's too in 1Y1.

1. I can not see whether the attaching surface is flat or not.
It should have ~1mm step to avoid "the legs" of the laser at the four corners.
Otherwise we will have ~0.5mm space between the block and the laser
and will squish this gap by the screws => cause the deformation of the block and the laser.

2. The countersinks for the M4 screws can be much deeper so that we can use the existing M4 screws.
In any case, the long M4 screws are not rigid and also not common.

I am feeling that it is ok to carefully make new holes and threads as far as the holes do not penetrate the plate.
The thickness of the plate can be measured by the four holes at the corners.

Today I put the FSS frequency box back into the 1Y1 rack.

To power it on, I turned on the 24V and 15V Sorensen switches in the same rack.

The PMC crystal board in the same rack should not be affected (it runs with 10V), but, to make sure it was not powered, I disconnected it from its crate. Since the board was disconnected from the EOM for the PSL table's upgrade, I wanted to avoid having the RF output floating.

We just have to remember to plug it back in, when we need it again.

1. Steve is handling the mount height increase for the PMC and RC steering mirrors, as well as a mount (non-steerable) for the ISS' AOM.
2. Rana is working on the laser mount.
3. Jenne is drawing and getting the PMC mount made.
4. We got the lenses from CVI for the mode matching, but not the metric screws for the laser mounting. I am tempted to tap holes in the laser base.

A few weeks ago, on Jul 24, Rana and I measured the phase noise of the FSS frequency box (aka the 'Kalmus Box'). See elog entry 3286.

That time, for some reason, we measured a phase noise higher than we expected; higher than that of the Marconi.

I repeated the measurement today using the SR785 spectrum analyzer. Here is the result:

(The measurement of July 24 on the plot was not corrected for the loop gain. The UGF was at about 30 Hz)

To make sure that my measurement procedure was correct, I also measured the combined phase noise of two Marconis. I then confirmed the consistency of that with what already measured by other people in the past (i.e. Rana elog entry 823 in the ATF elog).

This time the noise seemed reasonable; closer to the Marconi's phase noise, as we would expect. I don't know why it was so bad on July 24.

The shoulder in the Marconi-to-Marconi measurement between 80Hz and 800Hz is probably due to the phase noise of the other Marconi, the one used as LO.

I'm going to repeat the measurement connecting the setup to the DAQ, and locking the Marconi to the Rubidium standard.

Ultimately, the goal is to measure the phase noise of the new Sideband Frequency Generation Box of the 40m Upgrade.

Apparently updating to the latest revision of the RCG has some issues with diaggui and awgtpman.  Alex had to do some recompiling up at Hanford which apparently took him some time.  He'll be coming by tomorrow to try to bring those codes to the front end machines.

As a temporary fix, until Alex gets here tomorrow, we're reverting to the 2005 revision in the svn of the cds code.  I'm placing it in the location it is supposed to go in the new advLIGO scheme, which is /opt/rtcds/caltech/c1/core/, which is where Keith had it at LLO.  Once we get the new codes working, we will do an svn update on that location and migrate our work to that install location, at which point I'll remove the old /cvs/cds/caltech/cds/advLigoRTS/ location.

And I raised it back to 73F. The thermometers on the wall show 74-75F as the actual room temp. The dial on the temperature controller is not calibrated.

Our toilets were replaced by a green Gerber 1.6 gpf ( 6 lpf ) last week.

I lowered room 101 thermostat setting from 74F to 72F

 { Joe and Kiwamu },

 Now we  are able to compile the model file with more than 4 binary input/outputs (BIOs).

 As I wrote in a past entry (see here), the number of the BIOs was limited to 4, which is not enough for us.

  We modified a header file called "cdsHardware.h"  in order to allow model files having more than four BIOs.

The header file lives under /cvs/cds/caltech/advLigoRTS/src/include/drv/.

There was a sentence defining the maximum number in the file:

 #define MAX_DIO_MODULES         4.

We changed this to

 #define MAX_DIO_MODULES         8.

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

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

I plugged the new CDS to the vertex suspensions. 

Now PRM, SRM, ITMs, MCs and BS are under the control of the new CDS. 

From now on we will never go back to the old system.

Though,  the watchdogs are still running on the old system.

So if you need to turn on/off the watchdogs, you can simply enable/disable them from the usual medm screens.

To test out this website - emachineshop.com, Jenne and I are designing some of the mounts for the new beam height.

It took me a few hours to figure out how to do it, but the software is easy enough for simple stuff. This is a brass mount with M4 clearance holes which are countersunk and a lip so that it can be dogged down to the table.

{ Joe and Kiwamu }

Today we made some efforts to get the binary outputs (BOs) working.

They still are not working but the situation is getting better.

    So far the BO cards were not recognized by any realtime codes when we ran the codes on the new front end machine C1SUS.

We put some printk commands in an initialization code like Yoichi did (see this entry) to confirm if the initialization of the BOs properly happens or not.

Then we found that we had to put the BO modules also in an IOP model file which controls all the ADCs and the DACs.

We put the BO modules in the IOP file and then BOs started being recognized by the IOP, however they still are not fully recognized by the realtime control process.

We continue this work...

[Some notes]

[front end code]

First of all we looked at the front end c-code c1sus.c living under /cvs/cds/calech/cds/advLigoRTS/src/fe/c1sus/.

It was okay because there was a proper BO statement like

CDS_CARDS cards_used[] = { {CON_32DO,0}, {CON_32DO,2}};

[initialization code]

 There is an initialization code called map.c living under /cvs/cds/calech/cds/advLigoRTS/src/fe.

This code is complied when we do the make commands as described on the wiki.

Eventually the initialization code is executed only when the IOP starts up. This happens when we type startc1x02 at /cvs/cds/rtcs/caltech/c1/script/.

[printk statments]

   We made a backup file named map_20100830.c.back for map.c. Then we added to map.c some pintk statements in a while loop which looks for available BOs.   

After running the make commands for the IOP file and startc1x02, we basically can check the results of those printk statements by using dmesg.

We found that map.c was running correctly because  map.c went in the while loop 4 times which is exactly the same number as the BOs we put in the model file.

However the code failed to install the BOs each time.

[BO modules in IOP file]

  Joe pointed out the failure in map.c was caused by lack of the BO modules in the IOP file c1x02.mdl.

Indeed putting the BO modules in the IOP fixed the problem. 

Another thing we found at this time is that there is a maximum number of BOs we can put in a model file.

The maximum number is 4, which is not enough for us because we need to put 5 of them including a 16bit BIO and four 32bit BOs.

Now Joe is asking to Alex about this issue.

Anyway now the IOP can recognize the BO cards, this fact can be found if you look at the log file /cvs/cds/rtcds/caltech/c1/target/c1x02/logs/log.txt.

The log file saids "3 Contec 32ch PCIe DO cards found", which is a good sign. 

[BO modules in realtime code] 

Although the IOP started seeing the BO cards, the realtime code c1sus still didn't fully recognize the BO cards.

If we look at the log file log.txt at /cvs/cds/rtcds/caltech/c1/target/c1sus/logs/, there is an evidence that the code found some cards.

The log file saids  

   Model 6 = 10

   Model 7 = 4

   Model 8 = 4

   Model 9 = 4

   Model 10 = 0.

 It looks like these corresponds to the BO cards.

So the code found some cards, but doesn't know what they are.

We need few more debugging for the BOs... 

As it turns out, data seems to fall off the 16Tb drives after ~20 days.  Which makes it a good thing that I saved all of my raw data from my good Mode Cleaner / seismic weekend for offline Wiener Filtering in the following secret place:

/cvs/cds/caltech/users/jenne/AdaptiveFiltering/mat/MCseis_raw_data_7Aug2010

It's not linked to the svn, since it's a boatload of data.

The lifting and resetting of the BLUE PSL enclosure has made it unstable somehow. When I push on it a little it rocks back and forth a lot.

Steve, please look into what's happening and stiffen it if you can. Its too unstable right now.

Jenne and Koji

Last week Jenne has put the accelerometers on and under the PSL table immediately after the plastic sheets were removed.

So I took the same measurement as I did on 9th Aug.

Here is the comparison of the vibrational performance of the table before and after the modification.

Basically the table is now stiffer and more damped than it was before.
We don't find any eminent structure below (at least) 70Hz.
This result is obtained despite elevating of the table.

1) Attachment 1

For the horizontal comparison (top),  it is clearly seen that the large resonant peak at 20Hz was eliminated.
At least the new resonances went up to 70-90Hz region. Y is basically equivalent to X.

For the vertical comparison (bottom), it is clearly seen that the resonant peaks at around 50 & 70Hz were eliminated. 
At least no new resonance is seen.

2) Attachment 2

All-in-one plot for the measurement --- spectra, coherences, transfer functions --- after the upgrade. I put the same plot for the one before the upgrade.

 {Rana and Kiwamu}

Yesterday we disabled the sendmail daemon and the isdn daemon on allegra because we don't need these daemons always running.

-   How to disable/enable daemons:

sudo ntsysv

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.

I've taken the FSS frequency generation box out of the 1Y1 rack. It's sitting on one of the electronics benches. I'm measuring its phase noise.

In fact, many of the mounts need to be adapted to 4": the beefy steering mirrors going into the PMC, the PMC RFPD, the ISS AOM, the Faraday between the NPRO and the AOM, the NPRO itself, the ISS PDs.

Also for the FSS: the 21.5 MHz EOM, the PBS, the AOM, the refcav periscope, and the RFPD.

Its obvious, in retrospect, that we would have to do this, but it somehow didn't occur to me until actually trying to put things on the table...

The NPRO itself is already tapped with 3 (metric) M3 holes. It also has 4 (un-tapped) holes at its 4 corners which look like they are for feet. Anyone have a mount design for the Innolight NPRO already?

We also started labeling the table with the new coordinate system. In this system, the NE corner is the origin. The screw hole which is most NE is 1,1. The numbering increases in the south (+X) direction and goes negative in the west (-Y) direction.

[Rana, Jenne]

Like a new phoenix, the 40m PSL is in the process of being reborn...

We cleared many old optics and components (including Alberto's favorite periscope) off of the north end of the PSL table.  Some optics are stored on the SP table, others on the shelf inside the PSL enclosure.

The new Innolight 2W NPRO is on the table, the PMC has been moved, and the main path of the laser has been sketched out using steering mirrors. Since we still don't have a beam, we're roughly placing all of our optics, and we'll finalize the alignment after turning on the laser.

Using a leveled HeNe, I checked the height of optics we should use to match the height of optics in the chambers by shining the light at the first steering mirror in the chamber, and ensuring that the beam hit the center of that optic .  Since the new PSL table height is identical to the AP table, it's not a surprise that from now on we will be using a 4" beam height on the PSL table, rather than the old PSL 3" beam height.

On the to-do list is to make a plate with 4 through holes to raise the PMC up by 1 inch, and to make an adapter plate (or come up with another plan) for mounting the AOM that goes directly after the NPRO/Faraday, among many other things.  We also still need to make some space for the RefCav to be put in its new place on the table, and then install it with Steve's help.   

For the future SLOW controls our current plan is to keep using the VME based stuff and associated processors (Baja, Motorola, etc.). This is not

a sustainable plan since these are obsolete and eventually will die. One option is to use these boxes from Diamond Systems:

http://www.diamondsystems.com/products/octavio

 { Joe, Kiwamu }

Yes !

We now are damping all of the vertex suspensions including PRM, BS, ITMs and MCs by the new CDS. 

( Note that we are not damping SRM because we don't have it in the chamber. )

 (things to be done)

- Make the binary outputs work.

- Make DTT work

For a futher damping test, I again turned off the vertex optics watchdogs temporarily, including BS, ITMs, SRM, PRM, MCs.

 [Joe, Kiwamu]

We found that the vertex watchdogs were not correctly running.

After I powercycled c1susaux, the problem was fixed successfully.

The symptom: the watchdogs didn't disable the coil signal even when PD_VAR signals went larger than the threshold values PD_MAX_VAR.

Also we replaced the label by the correct name "C1SUSAUX" on a tag which was tied to the front end machine mounted on the new 1X5 rack.

I posted the crane safety document on the 40m wiki, vacuum page as 26 August 2010

Please add your comments and corrections.

The South End Crane will be balanced on Tuesday,  31 August 2010

This will mean that the back door of the south arm will be open on and off. Air quality will bad.

Please plan accordingly.

I think op540m has finally bitten the dust.  I noticed that both of its screens were black, so I assumed that it had crashed due to known graphics card issues or something.  But upon closer inspection, it is way more dead than that.  I checked that it does have power (at least the power cable is securely plugged in at both ends, and the power strip its on is successfully powering several other computers), but I can't make any lights or anything come on by pressing the power button on the front of the computer tower.

Immediate consequences of op540 not being operational are the lack of DMT, and the lack of Alarms. 

Joe is doing an autopsy right now to see if its really dead, or only 'mostly dead'.

EDIT: Joe says maybe it's the power supply for the computer.  But he can't turn it on either.

 was down.  I restarted the version in the 2.7.5 folder.  It went down again almost immediately but stayed up after the second restart.

[Joe, Kiwamu] 

Woooo Yeaaaah ! 

With the new CDS we succeeded in damping of PRM and BS !!

We are in the process of doing a damping test with the real time code and have turned off the vertex optics watchdogs temporarily, including BS, ITMs, SRM, PRM, MCs.

The tile work was done yesterday after noon.

This morning Mike Gerfen and me lowered the enclosure frame to normal height.

Keven- janitor and I removed plastic covers from chambers, racks, SP, MC2 and clean tool boxes.

The afternoon Jenne, Kiwamu, Joe and Aiden cleaned the enclosure inside out. The particle count measured zero inside the enclosure with HEPAs on when the covers were

removed. The MOPA and all other components were happy to see us in excellent condition.

This table height is very user friendly!

Safety grounds were reconnected.

Atm1, new tiles around the concrete slab

Atm2, frame lowered with low cross bars reinstalled

Atm3, the enclosure frame's north west foot is connected to ground

Atm4, PSL optical table is connected to ground at the north east corner through 1 Mohm

Atm5, PSL optical table level at a stimulating, back-friendly height

Turns out the elog version 2.8.0 uses a different encryption method than 2.7.5.  This mean the encrypted passwords stored in the elogd.cfg don't work with the new code.  elogd includes functionality to generate encrypted passwords, but unfortunately I don't know the administration passwords for some of the logbooks.  So I'm going to leave 2.7.5 running until I can get those added properly to the 2.8.0 cfg file.

Thoughts on where to take the pickoff for the SHG for the PSL-green?  We discussed today at the meeting the possibility of putting a 90/10 beam splitter right after the PMC, so that the green team would get somewhere between 100-200mW. 

In a manner similar to the now classic 'Mode Matching from PMC to IMC' entry, I have calculated the lenses and positions needed to match the 2W NPRO beam into the PMC.

The added complication is that we also want to have a reasonable beam size to get into the Faraday and the AOM. It seems that this should be possible using one lens.

After the beam comes out of the AOM, there's another lens to match to the PMC. Its possible to do this with more lenses, but this is just an effort to minimize the number

of surfaces in the beam.

So apparently the themes/configurations didn't work so nicely on some of the logbooks with 2.8.0, so I'm reverting to 2.7.5 until I can figure out (assuming I can) how to get them to display properly.

So unfortunately, I made the start-elog-nodus script smart enough to kill the debugging run I had (although thats probably good since there might have been issues with continuing to run - just poor timing on part of the crash).

In related news, I have gotten the latest version of the elog code to actually compile on Nodus.  I had to hack the cryptic.c file (elog/src/cryptic.c) to get it to work though.

The following was copied from the #ifdef _MSC_VER section of the code into the #else directly following that section. 

#define MAX(x,y) ((x)>(y)?(x):(y))
#define MIN(x,y) ((x)<(y)?(x):(y))
#define __alignof__(x) sizeof(x)
#define alloca(x) malloc(x)
#define mempcpy(d, s, n) ((char *)memcpy(d,s,n)+n)
#define ERANGE 34

I also removed #include <stdint.h> as the functionality it provides is covered by inttypes.h on Solaris machines, which is automatically included.

This new code was released August 5th 2010, while the old elog code we were running was 2.7.5 and was released sometime in 2008.  There are several crash fixes mentioned in the version notes so I'm hoping this may improve stability. I'm in the process of making a copy of the elog logbooks into the elog-2.8.0 install (so as to have a backup with the original 2.7.5).  I'm also copying over all the configuration files.   In a few minutes I'm going to try switching over to the new elog.  If it doesn't work, or is worse, its easy enough to just start up the current version.

All files are located in /cvs/cds/caltech/elog/elog-2.8.0 (the old directory is elog-2.7.5).  I've made  a new startup script called start-elog-nodus-2.8.0.  To start the new one, just run that script.  To start the old one, just go to the elog-2.7.5 directory and run the old start-elog-nodus script.

took two again

 Restarted the elog using the script. I had to do it twice for it to work. This is not the first time this has happened---does anyone know why this might be?

I'm going to take the elog down for one minute and restart it under gdb (using a copy of gdb stolen from fb40m since I couldn't figure out how to install an old enough version on nodus from source).  The terminal with information is running on Rosalba under the "Phase Noise" panel, so please don't close it.  Ideally, the next time the elog crashes, I'll have some output indicating why or at least the line in the code.  I can then look at the raw source code or send the line back to the developer and see if he has any ideas.

I used the free software called 'ABCD' for Mac to construct this mode matching solution for going from the PMC to the IMC.

After getting it close by eye, I plugged the initial guess into Matlab and let it optimize the distances. I then plugged this into 'ABCD'

to get the exact solution. ABCD doesn't actually optimize anything; it just makes a nice table and graphically plots the solution.

• The first waist between the first lens (f = +200 mm) and the second lens (f = -150 mm) is where the triple mod EOM goes. I have not accounted for the index (1.75) of the KTP.
• The third lens we need is a f = +400 mm lens. I have put the lenses in the new layout drawing at the positions indicated in the Omnigraffle drawing. Each grid square corresponds to 1 inch.

The part numbers for these lenses are:

PLCX-25.4-103.0-UV-1064

PLCC-25.4-77.3-UV-1064

PLCX-25.4-206.0-UV-1064

Bertine Robby, Bertin and Jerry completed the installation by pouring concrete yesterday and cleaning up today.

Atm1-2, steel bars, grouted feet and side forms are ready

Atm3,    bounding agent is applied for better bounding

Atm4,    pumping concrete

Atm5,    shaker is used to fill-all

Atm6,    late after noon the forms- sides were removed,     NOTE: actual table to concrete distance is 12.75"

Atm7,    construction people left and the tile man is on the way

The tile patching should complete today so tomorrow we can remove plastic covers.

...was down.  Have restarted it.

Woops, I am sorry about that. I've just cleaned them up.

Bad CDS team. Bad.