40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
 40m Log, Page 43 of 341 Not logged in
ID Date Author Type Category Subject
6951   Tue Jul 10 10:50:02 2012 JamieConfigurationGeneralSeismometer repositioning

 Quote: Today I REPOSITIONED THE SEISMOMETERS in order to triangulate noise sources (as Rana suggested). I re-levelled all of them, locked them, and turned them on. They should be located out of sight, but just in case: GUR 1 IS DOWN THE X-ARM, behind the interferometer. GUR 2 IS BETWEEN THE TWO ARMS, BEHIND THE CABLE TRAP THAT RUNS PARALLEL TO THE X-ARM. STS 1 IS DOWN THE Y-ARM behind the interferometer. I'll wait a day for them to stabilize (continuing to reset STS-1 every hour or so) and then begin taking data tomorrow morning, depending on the condition of the signal. Ideally, I'd like a few days' worth of data, so I'll update when I've changed the configuration back to the way it was prior.

Highlighting good, ALL CAPS LESS SO!

6997   Fri Jul 20 17:11:50 2012 JamieUpdateCDSAll custom MEDM screens moved to cds_users_apps svn repo

Since there are various ongoing requests for this from the sites, I have moved all of our custom MEDM screens into the cds_user_apps SVN repository.  This is what I did:

For each system in /opt/rtcds/caltech/c1/medm, I copied their "master" directory into the repo, and then linked it back in to the usual place, e.g.:

a=/opt/rtcds/caltech/c1/medm/${model}/master b=/opt/rtcds/userapps/trunk/${system}/c1/medm/${model} mv$a $b ln -s$b $a  Before committing to the repo, I did a little bit of cleanup, to remove some binary files and other known superfluous stuff. But I left most things there, since I don't know what is relevant or not. Then committed everything to the repo. 7005 Mon Jul 23 18:16:13 2012 JamieUpdateSUSDQ block added to sus_single_control library parts I have added a DQ block to the sus_single_control library part. This means that all sus models will automatically generate DQ channels based on what is specified in this doc block: #DAQ Channels SUSPOS_IN1 SUSPIT_IN1 SUSYAW_IN1 SUSSIDE_IN1 ULSEN_OUT URSEN_OUT LRSEN_OUT LLSEN_OUT SDSEN_OUT OLPIT_IN1 OLYAW_IN1 OLSUM_IN1  So for instance, for BS will have the following DQ channels: C1:SUS-BS_SUSPOS_IN1_DQ C1:SUS-BS_SUSPIT_IN1_DQ ...  etc. The channels names modified by the activateDQ.py script after install are still modified appropriately. This is now the place where we should be maintaining DQ channels. 7007 Mon Jul 23 18:41:15 2012 JamieUpdateGreen LockingALS_END.mdl model added for end station green ALS channels The end sus models (c1scx and c1scy) both contain some ALS stuff. This stuff could maybe be moved to their own models, but whatever. The stuff at X and Y were identical, but were code copies (BAD!). I made a new library part for the ALS end controls:${userapps}/isc/c1/model/ALS_END.mdl

It contains just some filter modules for the ALS end laser control, and a monitor of the ALS end REFL PD DC.  I also added a DQ block for the recorded channels (see screen shot).

When I added this new part to c1scx and c1scy I made it so the channel names would be more sensible.  Instead of "GCX" and "GCY", they are now "ALS-X" and "ALS-Y".  They will now all show up under the ALS subsystem.

Attachment 1: alsend.png
7008   Mon Jul 23 18:57:52 2012 JamieUpdateCDSc1scx and c1scy models recompiled and restarted

After the changes listed in 7005 and 7007, I have rebuilt, installed, and restarted the c1scx and c1scy models.  Everything seems to have come back up ok.

Running into some daqd troubles because of a change to c1ioo, but will report on the new ALS channels when I can.

7011   Mon Jul 23 19:50:43 2012 JamieUpdateCDSc1gcv model renamed to c1als

I decided to rename the c1gcv model to be c1als.  This is in an ongoing effort to rename all the ALS stuff as ALS, and get rid of the various GC{V,X,Y} named stuff.

Most of what was in the c1gcv model was already in a subsystem with and ALS top names, but there were a couple of channels that were outside of that that had funky names, namely the "GCV_GREEN" channels.  This fixes that, and make things more consistent and simple.

Of course this required a bunch of other little changes:

• rename model in userapps svn
• target/fb/master had to be modified to point to the new chans/daq/C1ALS.ini channel file and gds/param/tpchn_c1als.par testpoint file
• rename RFM channels appropriately, and fix in receiver models (c1scx, c1scy, c1mcs)
• move custom medm screens in userapps svn (isc/c1/medm/c1als), and link to it at medm/c1als/master
• moved old medm/c1gcv directory into a subdirectory of medm/c1als
• update all medm screens that point to c1gcv stuff (mostly just ALS screens)

The above has been done.  Still todo:

• FIX SCRIPTS!  There are almost certainly scripts that point to GC{V,X,Y} channels.  Those will have to be fixed as we come across them.
• Fix the c1sc{x,y}/master/C1SC{X,Y}_GC{X,Y}_SLOW.adl screens.  I need to figure out a more consistent place for those screens.
• Fix the C1ALS_COMPACT screen
• ???

7013   Mon Jul 23 20:34:38 2012 JamieOmnistructureComputersCHECK IN YOUR CHANGES TO THE SVN

I'm seeing LOTS OF STUFF NOT CHECKED INTO THE SVN!!!  both modified things that haven't been updated, and things that looked like they haven't been checked in at all.

### Please check in your stuff to the SVN!  We need the record!

Look through EVERYTHING that you think you might have touched, or even care about, and make sure it's checked in.

7043   Fri Jul 27 14:27:14 2012 JamieUpdateCDSnew c1tst model for testing RCG code

 Quote: I wanted to test biquad form in this model. I added biquad=1 flag to cdsParameters, compiled, installed and restarted it. After that c1iscey suspended. The same thing as we had several month ago controls@c1iscey /opt/rtcds/caltech/c1/target/c1tst/c1tstepics 0$cat iocC1.log  Starting iocInit iocRun: All initialization complete sh: iniChk.pl: command not found Failed to load DAQ configuration file I have fixed the iniChk.pl issue (which actually fixed a separate model startup-on-boot issue that we had been having). However, that is completely unrelated to the system freeze. I'll discuss that in a separate post. 7045 Fri Jul 27 14:30:49 2012 JamieUpdatedigital noisebiquad key is working What is "DQF"? Is that the biquad? And what is the difference between DF1 and DF2? Why don't you just write out the name, so it's more clear. 7046 Fri Jul 27 16:32:17 2012 JamieUpdateCDSRCG bug exposed by simple c1tst model As Den mentioned in 7043, attempting to run the c1tst model was causing the entire c1iscey machine to crash. Alex came over this morning and we spend a couple of hours trying to debug what was going on. c1tst is the simplest possible model you can have: 1 ADC and 2 filter modules. It compiles just fine, but when you tried to load it the machine would completely freeze. We eventually tracked this down to a non-empty filter file for one of the filter modules. It turns out that the model was crashing when it attempted to load the filter file. Once we completely deleted all the filters in the module, the model would run. But then if you added back a filter to the filter file and tried to "load coefficients", the model/machine would immediately crash again. So it has something to do with the loading of the filter coefficients from the filter file. We tried different filters and it didn't seem to make a difference. Alex thought it might have something to do with zeros in some of the second-order sections, but that wasn't it either. There's speculation that it might be related to a very similar bug that Joe reported at LLO a month ago: https://bugzilla.ligo-wa.caltech.edu/bugzilla/show_bug.cgi?id=398 Things we tried, none of which worked: • adding a DAC • turning on/off biquad • disabling the float denormalization fix This is a real mystery. Alex and I are continuing to investigate. 7049 Mon Jul 30 12:38:45 2012 JamieUpdateCDSMove to RCG 2.5 tag release I moved the RCG to the advLigoRTS-2.5 tag: controls@c1iscey ~ 0$ ls -al /opt/rtcds/rtscore/release
lrwxrwxrwx 1 controls 1001 19 Jul 30 12:02 /opt/rtcds/rtscore/release -> tags/advLigoRTS-2.5
controls@c1iscey ~ 0$ There are only very minor differences between what we were running on the the 2.5 branch. I have NOT rebuilt all the models yet. I was hoping that there was something in the tagged release that might fix this hard-crash-on-filter-load issue that we're seeing in the c1tst model. It didn't. Still have no idea what's going on there. 7057 Tue Jul 31 15:17:58 2012 JamieUpdateCDSc1ifo medm screens checked into CSD userapps svn I moved the medm/c1ifo directory into the CDS userapps svn at cds/c1/medm/c1ifo, and then linked it back into the medm directory: controls@rossa:~ 0$ ls -al /opt/rtcds/caltech/c1/medm/c1ifo
lrwxrwxrwx 1 controls controls 56 2012-07-31 11:53 /opt/rtcds/caltech/c1/medm/c1ifo -> /opt/rtcds/caltech/c1/userapps/release/cds/c1/medm/c1ifo
controls@rossa:~ 0I then committed whatever useful was in there. We need to remember to commit when we make changes. 7060 Tue Jul 31 18:59:59 2012 JamieUpdateCDSupdated medm paths for MISC (IFO,CDS,VIDEO), IFO alignment scripts updated accordingly In an attempt to clean up the medm situation, I did a bunch of further rearrangement and cleanup. Instead of having c1ifo, I moved a bunch of stuff into a MISC directory, including all of the CDS, IFO, and VIDEO screens: controls@rossa:~ 0 ls -1 /opt/rtcds/caltech/c1/medm/MISC | grep -v _BAK
help
ifoalign
ifoalign.orig
IFO_CONFIGURE.txt
snap
controls@rossa:~ 0I updated the sitemap and the relevant screens accordingly. I also updated the IFO_ALIGN script infrastructure a bit. The new IFO ALIGN location is /opt/rtcds/caltech/c1/medm/MISC/ifoalign. The scripts are now called simply: /opt/rtcds/caltech/c1/medm/MISC/ifoalign/misalign_soft.csh /opt/rtcds/caltech/c1/medm/MISC/ifoalign/restore_soft.csh /opt/rtcds/caltech/c1/medm/MISC/ifoalign/save_soft.csh These run Jenne's new soft restore stuff, and store burt snapshots for optic alignment in /opt/rtcds/caltech/c1/medm/MISC/ifoalign/burt. This has all been checked into the svn. 7062 Tue Jul 31 20:59:35 2012 JamieUpdateCDSfixing up MEDM snapshots I've started to try to fix all the old non-working medm snapshots. I've made a new snapshot directory, and some new snapshot scripts to handle taking the snapshots, and view old ones. Snapshots are now in: /opt/rtcds/caltech/c1/medm/snap There is one main script: /opt/rtcds/caltech/c1/medm/snap/snapcommands. This is linked by: • updatesnap: update a snapshot • viewsnap: view most recent snapshot • viewold: view old snapshots These commands take either the path to the screen in question, or it's relative path to the medm directory (/opt/rtcds/caltech/c1/medm). The snapshots for a specific screen are stored in a directory specific to the screen, in a place relative to the snap directory that mimics the screens relative path to the overall medm directory. So for instance, the snap directory for: /opt/rtcds/caltech/c1/medm/c1lsc/master/C1LSC_OVERVIEW.adl  is: controls@rossa:~ 0 find /opt/rtcds/caltech/c1/medm/snap/c1lsc/master/C1LSC_OVERVIEW/
/opt/rtcds/caltech/c1/medm/snap/c1lsc/master/C1LSC_OVERVIEW/
/opt/rtcds/caltech/c1/medm/snap/c1lsc/master/C1LSC_OVERVIEW/2012-08-01-02:21:34-UTC.png
/opt/rtcds/caltech/c1/medm/snap/c1lsc/master/C1LSC_OVERVIEW/2012-08-01-02:21:04-UTC.png
/opt/rtcds/caltech/c1/medm/snap/c1lsc/master/C1LSC_OVERVIEW/2012-08-01-02:21:23-UTC.png
/opt/rtcds/caltech/c1/medm/snap/c1lsc/master/C1LSC_OVERVIEW/2012-08-01-03:41:34-UTC.png
/opt/rtcds/caltech/c1/medm/snap/c1lsc/master/C1LSC_OVERVIEW/current.png
controls@rossa:~ 0 The "current.png" is a link to the most recent snapshot, and is what you get when you "viewsnap". Below is an example medm snippet of what could be used in screens to enable this functionality. I've fixed up a couple of the screens, but there are a lot more that need to be updated. "shell command" { object { x=666 y=597 width=40 height=40 } command[0] { label="Settings and Procedures" name="emacs" args="./help/IFO_ALIGN.txt &" } command[1] { label="View Snapshot" name="/opt/rtcds/caltech/c1/medm/snap/viewsnap" args="MISC/IFO_ALIGN.adl &" } command[2] { label="View old snapshots" name="/opt/rtcds/caltech/c1/medm/snap/viewold" args="MISC/IFO_ALIGN.adl &" } command[3] { label="Update Snapshot" name="/opt/rtcds/caltech/c1/medm/snap/updatesnap" args="MISC/IFO_ALIGN.adl &" } clr=14 bclr=30 }  7067 Wed Aug 1 11:50:49 2012 JamieUpdateCDSadded input monitors to LSC_TRIGGER library part I added an EPICS monitor to the input of the LSC_TRIGGER part, to allow monitoring the signal used for the trigger. I then added the monitors to the C1LSC_TRIG_MTRX screen (see below). This should hopefully aid in setting the trigger levels. Attachment 1: trigmtrx.png 7073 Wed Aug 1 18:20:58 2012 JamieUpdateLSCYarm recovered [Jenne, Jamie] We recovered lock and alignment of the Y arm. TRY_OUT is now at ~0.9, after tweaking {I,E}TMY pit/yaw and PZT2. YARM_GAIN is 0.1. I saved ITMY, ETMY, and PZT2 alignments in the IFO_ALIGN screen with the new alignment save/restore stuff I got working. Working on getting Yarm ASS working now... 7079 Thu Aug 2 21:40:55 2012 JamieUpdateSimulationsETMX simplant model revived I revived the ETMX simplant model, c1spx. It's running on cpu4 on c1iscex, and interfaces with C1scx via SHMEM. The channel names for the simplant suspensions will be SUP, so the channel from this model will C1:SUP-ETMX_. Next I'll try to get the ITMX and LSC ("LSP") simplant models running so we can run a "full" cavity simulation. Sasha has been working on LSP, so we should be ready to do something with that soon. In the mean time she's going to fix up the SPX MEDM screens, since some channel names have been changed since it was last run. 7093 Mon Aug 6 19:37:50 2012 JamieUpdateCDSdaqd and CDS network problems today For some reason this afternoon we've been experiencing a lot of problems with the framebuilder, and with the CDS network in general. The framebuilder has been very unresponsive, although the daqd logs seem to indicate that things are ok. All models will loose contact with fb for very long stretches. Attempts to kill/restart daqd don't seem to fix the problem. These problems seem to be associated with the general CDS network issues as well. The network seems to become very slow, and the workstations all become very slow. The later I assume is because of the network and that so much of the work we do is on network mounted filesystems (/opt/rtcds, /ligo, etc.). My current speculation is that daqd on fb is doing something stupid, like trying to read or write a bunch of stuff from /frames, which is also network mounted, and that clogs up the entire network. Some serious network debugging is going to be needed to figure out what's going on, though. I'm afraid daqd is caught in some bad state now, though. It's not responding to anything, and every attempt to kill it seems to bring it back into the bad state. Hopefully I can get Alex to help me figure out what's going on tomorrow. Maybe it will clear up on it's own tonight... 7094 Mon Aug 6 19:54:53 2012 JamieUpdateCDSdaqd and CDS network problems today It looks like daqd is indeed caught in some bad state. It seems to die at some point after making GPS corrections to minute trender: ... [Mon Aug 6 19:45:13 2012] Minute trender made GPS time correction; gps=1028342727; gps%60=27 tail: fb/logs/daqd.log' has been replaced; following end of new file 263596 MX endpoint opened startup file interpreter thread tid=140334118615312 calling yyparse(5, 6) [Mon Aug 6 19:50:08 2012] ->5: #set avoid_reconnect [Mon Aug 6 19:50:08 2012] ->5: set thread_stack_size=102400 [Mon Aug 6 19:50:08 2012] new threads will be created with the stack of size 102400K [Mon Aug 6 19:50:08 2012] ->5: set allow_tpman_connect_fail [Mon Aug 6 19:50:08 2012] ->5: #set dcu_status_check=5 [Mon Aug 6 19:50:08 2012] ->5: #set symm_gps_offset=-1 [Mon Aug 6 19:50:08 2012] ->5: #set symm_gps_offset=31535998 [Mon Aug 6 19:50:08 2012] ->5: ##set symm_gps_offset=347155213 [Mon Aug 6 19:50:08 2012] ->5: #set symm_gps_offset=378691215 [Mon Aug 6 19:50:08 2012] ->5: #set symm_gps_offset=378691212 [Mon Aug 6 19:50:08 2012] ->5: #set symm_gps_offset=315964799 [Mon Aug 6 19:50:08 2012] ->5: set symm_gps_offset=315964801 [Mon Aug 6 19:50:08 2012] ->5: set debug=0 [Mon Aug 6 19:50:08 2012] ->5: set log=2 [Mon Aug 6 19:50:08 2012] ->5: set zero_bad_data=0 [Mon Aug 6 19:50:08 2012] ->5: set dcu_status_check=9 [Mon Aug 6 19:50:08 2012] ->5: set controller_dcu=33 [Mon Aug 6 19:50:08 2012] ->5: set master_config="/opt/rtcds/caltech/c1/target/fb/master" [Mon Aug 6 19:50:10 2012] finished configuring data channels [Mon Aug 6 19:50:10 2012] ->5: configure channels begin end Unable to find GDS node 90 system c1x00 in INI files Unable to find GDS node 92 system c1tst2 in INI files Unable to find GDS node 95 system c1x10 in INI files [Mon Aug 6 19:50:10 2012] ->5: tpconfig "/opt/rtcds/caltech/c1/target/gds/param/testpoint.par" [Mon Aug 6 19:50:10 2012] ->5: set gps_leaps = 820108813 [Mon Aug 6 19:50:10 2012] ->5: set detector_name="CIT" [Mon Aug 6 19:50:10 2012] ->5: set detector_prefix="C1" [Mon Aug 6 19:50:10 2012] ->5: set detector_longitude=-90.7742403889 [Mon Aug 6 19:50:10 2012] ->5: set detector_latitude=30.5628943337 [Mon Aug 6 19:50:10 2012] ->5: set detector_elevation=.0 [Mon Aug 6 19:50:10 2012] ->5: set detector_azimuths=1.1,4.7123889804 [Mon Aug 6 19:50:10 2012] ->5: set detector_altitudes=1.0,2.0 [Mon Aug 6 19:50:10 2012] ->5: set detector_midpoints=2000.0, 2000.0 [Mon Aug 6 19:50:10 2012] ->5: set num_dirs = 10 [Mon Aug 6 19:50:10 2012] ->5: set frames_per_dir=225 [Mon Aug 6 19:50:10 2012] ->5: set full_frames_per_file=1 [Mon Aug 6 19:50:10 2012] ->5: set full_frames_blocks_per_frame=16 [Mon Aug 6 19:50:10 2012] ->5: set frame_dir="/frames/full", "C-R-", ".gwf" [Mon Aug 6 19:50:10 2012] ->5: set trend_num_dirs=10 [Mon Aug 6 19:50:10 2012] ->5: set trend_frames_per_dir=1440 [Mon Aug 6 19:50:10 2012] ->5: set trend_frame_dir= "/frames/trend/second", "C-T-", ".gwf" [Mon Aug 6 19:50:10 2012] ->5: set raw-minute-trend-dir="/frames/trend/minute_raw" [Mon Aug 6 19:50:10 2012] ->5: set nds-jobs-dir="/opt/rtcds/caltech/c1/target/fb" [Mon Aug 6 19:50:10 2012] ->5: set minute-trend-num-dirs=10 [Mon Aug 6 19:50:10 2012] ->5: set minute-trend-frames-per-dir=24 [Mon Aug 6 19:50:10 2012] ->5: set minute-trend-frame-dir="/frames/trend/minute", "C-M-", ".gwf" [Mon Aug 6 19:50:10 2012] ->5: start main 10 [Mon Aug 6 19:50:12 2012] main started [Mon Aug 6 19:50:12 2012] ->5: start profiler [Mon Aug 6 19:50:12 2012] ->5: # comment out this block to stop saving data [Mon Aug 6 19:50:12 2012] frame saver started [Mon Aug 6 19:50:12 2012] ->5: start frame-saver [Mon Aug 6 19:50:13 2012] ->5: sync frame-saver [Mon Aug 6 19:50:13 2012] ->5: start trender [Mon Aug 6 19:50:13 2012] trender started [Mon Aug 6 19:50:13 2012] trend frame saver started [Mon Aug 6 19:50:13 2012] ->5: start trend-frame-saver [Mon Aug 6 19:50:14 2012] ->5: sync trend-frame-saver [Mon Aug 6 19:50:14 2012] minute trend frame saver started [Mon Aug 6 19:50:14 2012] ->5: start minute-trend-frame-saver [Mon Aug 6 19:50:14 2012] Done creating ADC structures [Mon Aug 6 19:50:15 2012] ->5: sync minute-trend-frame-saver [Mon Aug 6 19:50:15 2012] raw minute trend frame saver started [Mon Aug 6 19:50:15 2012] ->5: start raw_minute_trend_saver [Mon Aug 6 19:50:15 2012] ->5: #frame-writer "225.225.225.1" broadcast="131.215.113.0" all [Mon Aug 6 19:50:15 2012] ->5: #sleep 5 [Mon Aug 6 19:50:15 2012] producer started [Mon Aug 6 19:50:15 2012] ->5: start producer [Mon Aug 6 19:50:15 2012] ->5: start epics dcu [Mon Aug 6 19:50:15 2012] MX receiver thread started [Mon Aug 6 19:50:15 2012] edcu started [Mon Aug 6 19:50:15 2012] ->5: start epics server "C0:DAQ-DC0_" "C1:DAQ-DC0_" [Mon Aug 6 19:50:15 2012] epics server started [Mon Aug 6 19:50:15 2012] ->5: start listener 8087 [Mon Aug 6 19:50:15 2012] ->5: start listener 8088 1 [Mon Aug 6 19:50:15 2012] ->5: sleep 60 [Mon Aug 6 19:50:15 2012] Epics server started [Mon Aug 6 19:50:15 2012] EDCU has 2553 channels configured; first=0 [Mon Aug 6 19:50:18 2012] Minute trender made GPS time correction; gps=1028343032; gps%60=32 ...  The "tail:..." line indicates that the log was moved and replaced, which indicates a daqd restart. As far as I know this was not manually triggered. After the restart the same thing happens again. About once every five minutes. 7095 Mon Aug 6 20:08:45 2012 JamieUpdateCDSdaqd and CDS network problems today When daqd is caught in this state it can not be killed. It's in "uninterruptable sleep" ('D' state in the top output below). This usually indicates that it's waiting for the kernel, usually due to some missing or hung IO.  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 28038 controls 20 0 4430m 2.0g 19m D 0 27.1 0:15.00 daqd  The memory footprint also seems to be getting big. It's clearly trying to do something stupid that it can't handle. 7096 Mon Aug 6 20:22:50 2012 JamieUpdateCDSdaqd segfaulting after five minutes I tried running daqd manually, and sure enough it segfaults after about five minutes (see log below). I've uncommented it from /etc/inittab on fb and I'm leaving it off for now until we can figure out what's going on. controls@fb /opt/rtcds/caltech/c1/target/fb 0 /opt/rtcds/caltech/c1/target/fb/daqd -c /opt/rtcds/caltech/c1/target/fb/daqdrc
263596
MX endpoint opened
calling yyparse(5, 6)
[Mon Aug  6 20:15:27 2012] ->5: #set avoid_reconnect
[Mon Aug  6 20:15:27 2012] ->5: set thread_stack_size=102400
[Mon Aug  6 20:15:27 2012] new threads will be created with the stack of size 102400K
[Mon Aug  6 20:15:27 2012] ->5: set allow_tpman_connect_fail
[Mon Aug  6 20:15:27 2012] ->5: #set dcu_status_check=5
[Mon Aug  6 20:15:27 2012] ->5: #set symm_gps_offset=-1
[Mon Aug  6 20:15:27 2012] ->5: #set symm_gps_offset=31535998
[Mon Aug  6 20:15:27 2012] ->5: ##set symm_gps_offset=347155213
[Mon Aug  6 20:15:27 2012] ->5: #set symm_gps_offset=378691215
[Mon Aug  6 20:15:27 2012] ->5: #set symm_gps_offset=378691212
[Mon Aug  6 20:15:27 2012] ->5: #set symm_gps_offset=315964799
[Mon Aug  6 20:15:27 2012] ->5: set symm_gps_offset=315964801
[Mon Aug  6 20:15:27 2012] ->5: set debug=0
[Mon Aug  6 20:15:27 2012] ->5: set log=2
[Mon Aug  6 20:15:27 2012] ->5: set zero_bad_data=0
[Mon Aug  6 20:15:27 2012] ->5: set dcu_status_check=9
[Mon Aug  6 20:15:27 2012] ->5: set controller_dcu=33
[Mon Aug  6 20:15:27 2012] ->5: set master_config="/opt/rtcds/caltech/c1/target/fb/master"
[Mon Aug  6 20:15:30 2012] finished configuring data channels
[Mon Aug  6 20:15:30 2012] ->5: configure channels begin end
GDS server NODE=19 HOST=c1iscex DCUID=19
GDS server NODE=20 HOST=c1sus DCUID=20
GDS server NODE=21 HOST=c1sus DCUID=21
GDS server NODE=22 HOST=c1lsc DCUID=22
GDS server NODE=25 HOST=c1iscex DCUID=61
GDS server NODE=28 HOST=c1ioo DCUID=28
GDS server NODE=33 HOST=c1ioo DCUID=33
GDS server NODE=34 HOST=c1ioo DCUID=34
GDS server NODE=36 HOST=c1sus DCUID=36
GDS server NODE=38 HOST=c1sus DCUID=38
GDS server NODE=39 HOST=c1sus DCUID=39
GDS server NODE=40 HOST=c1lsc DCUID=40
GDS server NODE=42 HOST=c1lsc DCUID=42
GDS server NODE=45 HOST=c1iscex DCUID=45
GDS server NODE=46 HOST=c1iscey DCUID=46
GDS server NODE=47 HOST=c1iscey DCUID=47
GDS server NODE=48 HOST=c1lsc DCUID=48
GDS server NODE=50 HOST=c1lsc DCUID=50
GDS server NODE=51 HOST=c1ioo DCUID=51
GDS server NODE=60 HOST=c1lsc DCUID=60
GDS server NODE=61 HOST=c1iscex DCUID=61
GDS server NODE=62 HOST=c1sus DCUID=62
Unable to find GDS node 90 system c1x00 in INI files
GDS server NODE=91 HOST=c1lsc DCUID=60
Unable to find GDS node 92 system c1tst2 in INI files
Unable to find GDS node 95 system c1x10 in INI files
TP: node = 19, host = c1iscex, dup = 0, prog = 0x31002013, vers = 1
Initialized TP interface node=19, host=c1iscex
TP: node = 20, host = c1sus, dup = 0, prog = 0x31002014, vers = 1
Initialized TP interface node=20, host=c1sus
TP: node = 21, host = c1sus, dup = 0, prog = 0x31002015, vers = 1
Initialized TP interface node=21, host=c1sus
TP: node = 22, host = c1lsc, dup = 0, prog = 0x31002016, vers = 1
Initialized TP interface node=22, host=c1lsc
TP: node = 25, host = c1iscex, dup = 0, prog = 0x31002019, vers = 1
Initialized TP interface node=25, host=c1iscex
TP: node = 28, host = c1ioo, dup = 0, prog = 0x3100201c, vers = 1
Initialized TP interface node=28, host=c1ioo
TP: node = 33, host = c1ioo, dup = 0, prog = 0x31002021, vers = 1
Initialized TP interface node=33, host=c1ioo
TP: node = 34, host = c1ioo, dup = 0, prog = 0x31002022, vers = 1
Initialized TP interface node=34, host=c1ioo
TP: node = 36, host = c1sus, dup = 0, prog = 0x31002024, vers = 1
Initialized TP interface node=36, host=c1sus
TP: node = 38, host = c1sus, dup = 0, prog = 0x31002026, vers = 1
Initialized TP interface node=38, host=c1sus
TP: node = 39, host = c1sus, dup = 0, prog = 0x31002027, vers = 1
Initialized TP interface node=39, host=c1sus
TP: node = 40, host = c1lsc, dup = 0, prog = 0x31002028, vers = 1
Initialized TP interface node=40, host=c1lsc
TP: node = 42, host = c1lsc, dup = 0, prog = 0x3100202a, vers = 1
Initialized TP interface node=42, host=c1lsc
TP: node = 45, host = c1iscex, dup = 0, prog = 0x3100202d, vers = 1
Initialized TP interface node=45, host=c1iscex
TP: node = 46, host = c1iscey, dup = 0, prog = 0x3100202e, vers = 1
Initialized TP interface node=46, host=c1iscey
TP: node = 47, host = c1iscey, dup = 0, prog = 0x3100202f, vers = 1
Initialized TP interface node=47, host=c1iscey
TP: node = 48, host = c1lsc, dup = 0, prog = 0x31002030, vers = 1
Initialized TP interface node=48, host=c1lsc
TP: node = 50, host = c1lsc, dup = 0, prog = 0x31002032, vers = 1
Initialized TP interface node=50, host=c1lsc
TP: node = 51, host = c1ioo, dup = 0, prog = 0x31002033, vers = 1
Initialized TP interface node=51, host=c1ioo
TP: node = 60, host = c1lsc, dup = 0, prog = 0x3100203c, vers = 1
Initialized TP interface node=60, host=c1lsc
TP: node = 61, host = c1iscex, dup = 0, prog = 0x3100203d, vers = 1
Initialized TP interface node=61, host=c1iscex
TP: node = 62, host = c1sus, dup = 0, prog = 0x3100203e, vers = 1
Initialized TP interface node=62, host=c1sus
TP: node = 91, host = c1lsc, dup = 0, prog = 0x3100205b, vers = 1
Initialized TP interface node=91, host=c1lsc
[Mon Aug  6 20:15:30 2012] ->5: tpconfig "/opt/rtcds/caltech/c1/target/gds/param/testpoint.par"
[Mon Aug  6 20:15:30 2012] ->5: set gps_leaps = 820108813
[Mon Aug  6 20:15:30 2012] ->5: set detector_name="CIT"
[Mon Aug  6 20:15:30 2012] ->5: set detector_prefix="C1"
[Mon Aug  6 20:15:30 2012] ->5: set detector_longitude=-90.7742403889
[Mon Aug  6 20:15:30 2012] ->5: set detector_latitude=30.5628943337
[Mon Aug  6 20:15:30 2012] ->5: set detector_elevation=.0
[Mon Aug  6 20:15:30 2012] ->5: set detector_azimuths=1.1,4.7123889804
[Mon Aug  6 20:15:30 2012] ->5: set detector_altitudes=1.0,2.0
[Mon Aug  6 20:15:30 2012] ->5: set detector_midpoints=2000.0, 2000.0
[Mon Aug  6 20:15:30 2012] ->5: set num_dirs = 10
[Mon Aug  6 20:15:30 2012] ->5: set frames_per_dir=225
[Mon Aug  6 20:15:30 2012] ->5: set full_frames_per_file=1
[Mon Aug  6 20:15:30 2012] ->5: set full_frames_blocks_per_frame=16
[Mon Aug  6 20:15:30 2012] ->5: set frame_dir="/frames/full", "C-R-", ".gwf"
[Mon Aug  6 20:15:30 2012] ->5: set trend_num_dirs=10
[Mon Aug  6 20:15:30 2012] ->5: set trend_frames_per_dir=1440
[Mon Aug  6 20:15:30 2012] ->5: set trend_frame_dir= "/frames/trend/second", "C-T-", ".gwf"
[Mon Aug  6 20:15:30 2012] ->5: set raw-minute-trend-dir="/frames/trend/minute_raw"
[Mon Aug  6 20:15:30 2012] ->5: set nds-jobs-dir="/opt/rtcds/caltech/c1/target/fb"
[Mon Aug  6 20:15:30 2012] ->5: set minute-trend-num-dirs=10
[Mon Aug  6 20:15:30 2012] ->5: set minute-trend-frames-per-dir=24
[Mon Aug  6 20:15:30 2012] ->5: set minute-trend-frame-dir="/frames/trend/minute", "C-M-", ".gwf"
[Mon Aug  6 20:15:30 2012] ->5: start main 10
Allocated move buffer size 11616356 bytes
[Mon Aug  6 20:15:32 2012] main started
[Mon Aug  6 20:15:32 2012] ->5: start profiler
[Mon Aug  6 20:15:32 2012] ->5: # comment out this block to stop saving data
[Mon Aug  6 20:15:32 2012] frame saver started
[Mon Aug  6 20:15:32 2012] ->5: start frame-saver
[Mon Aug  6 20:15:33 2012] ->5: sync frame-saver
[Mon Aug  6 20:15:33 2012] ->5: start trender
[Mon Aug  6 20:15:33 2012] trender started
[Mon Aug  6 20:15:33 2012] trend frame saver started
[Mon Aug  6 20:15:33 2012] ->5: start trend-frame-saver
[Mon Aug  6 20:15:34 2012] ->5: sync trend-frame-saver
[Mon Aug  6 20:15:34 2012] minute trend frame saver started
[Mon Aug  6 20:15:34 2012] ->5: start minute-trend-frame-saver
[Mon Aug  6 20:15:34 2012] Done creating ADC structures
[Mon Aug  6 20:15:35 2012] ->5: sync minute-trend-frame-saver
[Mon Aug  6 20:15:35 2012] raw minute trend frame saver started
[Mon Aug  6 20:15:35 2012] ->5: start raw_minute_trend_saver
[Mon Aug  6 20:15:35 2012] ->5: #frame-writer "225.225.225.1" broadcast="131.215.113.0" all
[Mon Aug  6 20:15:35 2012] ->5: #sleep 5
[Mon Aug  6 20:15:35 2012] producer started
[Mon Aug  6 20:15:35 2012] ->5: start producer
[Mon Aug  6 20:15:35 2012] ->5: start epics dcu
[Mon Aug  6 20:15:35 2012] edcu started
[Mon Aug  6 20:15:35 2012] ->5: start epics server "C0:DAQ-DC0_" "C1:DAQ-DC0_"
[Mon Aug  6 20:15:35 2012] epics server started
[Mon Aug  6 20:15:35 2012] ->5: start listener 8087
[Mon Aug  6 20:15:35 2012] ->5: start listener 8088 1
[Mon Aug  6 20:15:35 2012] ->5: sleep 60
Creating C1:DAQ-DC0_PEM_SLOW_STATUS
Creating C1:DAQ-DC0_PEM_SLOW_CRC_CPS
Creating C1:DAQ-DC0_PEM_SLOW_CRC_SUM
Creating C1:DAQ-DC0_C1X01_STATUS
Creating C1:DAQ-DC0_C1X01_CRC_CPS
Creating C1:DAQ-DC0_C1X01_CRC_SUM
Creating C1:DAQ-DC0_C1X02_STATUS
Creating C1:DAQ-DC0_C1X02_CRC_CPS
Creating C1:DAQ-DC0_C1X02_CRC_SUM
Creating C1:DAQ-DC0_C1SUS_STATUS
Creating C1:DAQ-DC0_C1SUS_CRC_CPS
Creating C1:DAQ-DC0_C1SUS_CRC_SUM
Creating C1:DAQ-DC0_C1OAF_STATUS
Creating C1:DAQ-DC0_C1OAF_CRC_CPS
Creating C1:DAQ-DC0_C1OAF_CRC_SUM
Creating C1:DAQ-DC0_C1ALS_STATUS
Creating C1:DAQ-DC0_C1ALS_CRC_CPS
Creating C1:DAQ-DC0_C1ALS_CRC_SUM
Creating C1:DAQ-DC0_C1X03_STATUS
Creating C1:DAQ-DC0_C1X03_CRC_CPS
Creating C1:DAQ-DC0_C1X03_CRC_SUM
Creating C1:DAQ-DC0_C1IOO_STATUS
Creating C1:DAQ-DC0_C1IOO_CRC_CPS
Creating C1:DAQ-DC0_C1IOO_CRC_SUM
Creating C1:DAQ-DC0_C1MCS_STATUS
Creating C1:DAQ-DC0_C1MCS_CRC_CPS
Creating C1:DAQ-DC0_C1MCS_CRC_SUM
Creating C1:DAQ-DC0_C1RFM_STATUS
Creating C1:DAQ-DC0_C1RFM_CRC_CPS
Creating C1:DAQ-DC0_C1RFM_CRC_SUM
Creating C1:DAQ-DC0_C1PEM_STATUS
Creating C1:DAQ-DC0_C1PEM_CRC_CPS
Creating C1:DAQ-DC0_C1PEM_CRC_SUM
Creating C1:DAQ-DC0_C1X04_STATUS
Creating C1:DAQ-DC0_C1X04_CRC_CPS
Creating C1:DAQ-DC0_C1X04_CRC_SUM
Creating C1:DAQ-DC0_C1LSC_STATUS
Creating C1:DAQ-DC0_C1LSC_CRC_CPS
Creating C1:DAQ-DC0_C1LSC_CRC_SUM
Creating C1:DAQ-DC0_C1SCX_STATUS
Creating C1:DAQ-DC0_C1SCX_CRC_CPS
Creating C1:DAQ-DC0_C1SCX_CRC_SUM
Creating C1:DAQ-DC0_C1X05_STATUS
Creating C1:DAQ-DC0_C1X05_CRC_CPS
Creating C1:DAQ-DC0_C1X05_CRC_SUM
Creating C1:DAQ-DC0_C1SCY_STATUS
Creating C1:DAQ-DC0_C1SCY_CRC_CPS
Creating C1:DAQ-DC0_C1SCY_CRC_SUM
Creating C1:DAQ-DC0_C1ASS_STATUS
Creating C1:DAQ-DC0_C1ASS_CRC_CPS
Creating C1:DAQ-DC0_C1ASS_CRC_SUM
Creating C1:DAQ-DC0_C1CAL_STATUS
Creating C1:DAQ-DC0_C1CAL_CRC_CPS
Creating C1:DAQ-DC0_C1CAL_CRC_SUM
Creating C1:DAQ-DC0_C1MCC_STATUS
Creating C1:DAQ-DC0_C1MCC_CRC_CPS
Creating C1:DAQ-DC0_C1MCC_CRC_SUM
Creating C1:DAQ-DC0_C1MCP_STATUS
Creating C1:DAQ-DC0_C1MCP_CRC_CPS
Creating C1:DAQ-DC0_C1MCP_CRC_SUM
Creating C1:DAQ-DC0_C1LSP_STATUS
Creating C1:DAQ-DC0_C1LSP_CRC_CPS
Creating C1:DAQ-DC0_C1LSP_CRC_SUM
Creating C1:DAQ-DC0_C1SPX_STATUS
Creating C1:DAQ-DC0_C1SPX_CRC_CPS
Creating C1:DAQ-DC0_C1SPX_CRC_SUM
Creating C1:DAQ-DC0_C1SUP_STATUS
Creating C1:DAQ-DC0_C1SUP_CRC_CPS
Creating C1:DAQ-DC0_C1SUP_CRC_SUM
[Mon Aug  6 20:15:35 2012] Epics server started
[Mon Aug  6 20:15:35 2012] EDCU has 2553 channels configured; first=0

Symmetricom status: LOCKED
Starting at gps 1028344552 prev_gps 1028344552 frac 312500000 f 314094022
[Mon Aug  6 20:15:38 2012] Minute trender made GPS time correction; gps=1028344552; gps%60=52
Segmentation fault (core dumped)


7097   Mon Aug 6 20:27:59 2012 JamieUpdateSimulationsMore work on getting simplant models running: c1lsp and c1sup

I'm trying to get more of the simplant models running so that we (me and Sasha Surf) can get a full real-time cavity simplant running.  As I reported last week, c1spx is running again on c1iscex.

The two new simplant models are c1sup, which holds the simplant for ITMX, and c1lsp, which holds the IFO simplant, specifically the one we're working on for XARM.

Here's the relevant info:

model  host     dcuid  cpu
c1spx  c1iscex  61     4
c1sup  c1sus    62     6
c1lsp  c1lsc    60     6


c1spx and c1sup will be running the sus_single_plant parts for ETMX and ITMX simplant.  All the simplant suspension channels will be names "SUP" (as opposed to "SUS" for control).

c1lsp is now running, but c1sup won't run for unknown reasons.  The c1sup model is not very complicated, and in fact is more-or-less identical to c1spx.  It compiles and installs and even loads, but it completely unresponsive after loading.  Unfortunately I've had enough CDS bullshit for today, so I'll try to figure out what's going on tomorrow.

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.

7102   Tue Aug 7 14:17:07 2012 JamieUpdateCDSdaqd running again; related to c1sup issue

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

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

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

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

 Quote: So daqd's problem was apparently the bad/non-running c1sup model.  The c1sup model, which I reported on attempting to get running in 7097, was not running because there were no available CPUs on the c1sus FE machine.  This was due to my stupid undercounting of the number of CPUs.  Anyway, for reasons I don't understand, this was causing daqd to segfault.  Removing c1sup from c1sus "fixed" the problem. Alex agreed that daqd should definitely not be segfaulting in this circumstance.  It's still unclear exactly what daqd was looking at that was causing it to crash. I'm going to move c1sup to c1iscex, which has a lot of spare CPUs.

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

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

7105   Tue Aug 7 15:04:23 2012 JamieUpdateCDSdaqd problem was root-owned files and directories

Apparently the last problem was because of root-owned frame directories that daqd was trying to write to.  During debugging Alex had run daqd as root, but it's supposed to run as controls.  All the /frame directories are supposed to be owned by controls.  When daqd was run as root, it created new frame directories owned by root, which controls couldn't write to when I restarted daqd the proper way.  Once we chown'd the directories daqd started running again.

Alex also put in a "fix" for the core dump problem.  He touched an empty core file owned by root:

-rw-r--r-- 1 root root 0 Aug  7 14:38 /opt/rtcds/caltech/c1/target/fb/core

This will prevent any dying daqd process owned by controls from dumping it's core at that location.  Personally I think this is a horribly hacky "solution" that doesn't actually fix any of the issues that were causing the segfaults to begin with, but it might prevent some of the network slow down we see when the core does dump.  It's mostly just masking the problem, though, so I'm tempted to remove it so we all feel the pain when daqd starts shitting all over the network again.

7175   Tue Aug 14 11:46:22 2012 JamieUpdateCDSIPC senders know nothing about rates of IPC receivers, we need to filter signals appropriately

 Quote: When signals are transmitted between the models running at different rates, no AI or AA filters are automatically applied. We need to fix our models.

This is known, but we just haven't fully groked it yet.  We need to look closely at every place we have IPCs between models running at different rates.  The sender has no information about receivers, so it can't reasonably do anything to pre-filter the signal on it's own.

So for transmission from:

• faster -> slower models: add anti-aliasing on the sender side
7182   Tue Aug 14 17:47:44 2012 JamieUpdateCDSc1sus machine replaced

Rolf and Alex came back over with a replacement machine for c1sus.   We removed the old machine, removed it's timing, dolphin, and PCIe extension cards and put them in the new machine.  We then installed the new machine and booted it and it came up fine.  The BIOS in this machine is slightly different, and it wasn't having the same failure-to-boot-with-no-COM issue that the previous one was.  The COM ports are turned off on this machine (as is the USB interface).

Unfortunately the problem we were experiencing with the old machine, that unloading certain models was causing others to twitch and that dolphin IPC writes were being dropped, is still there.  So the problem doesn't seem to have anything to do with hardware settings...

After some playing, Rolf and Alex determined that for some reason the c1rfm model is coming up in a strange state when started during boot.  It runs faster, but the IPC errors are there.  If instead all models are stopped, the c1rfm model is started first, and then the rest of the models are started, the c1rfm model runs ok.  They don't have an explanation for this, and I'm not sure how we can work around it other than knowing the problem is there and do manual restarts after boot.  I'll try to think of something more robust.

A better "fix" to the problems is to clean up all of our IPC routing, a bunch of which we're currently doing very inefficient right now.  We're routing things through c1rfm that don't need to be, which is introducing delays.  It particular, things that can communicate directly over RFM or dolphin should just do so.  We should also figure out if we can put the c1oaf and c1pem models on the same machine, so that they can communicate directly over shared memory (SHMEM).  That should cut down on overhead quite a bit.  I'll start to look at a plan to do that.

7592   Tue Oct 23 00:51:41 2012 JamieUpdateAdaptive Filteringmicrophone noise

 Quote: I will do some experiments on acoustic noise canceling during my stay. Now I am planning to cancel acoustic noise from PMC and see how the acoustic noise work and how we should place microphones.a First, I measured the noise in microphones and its circuit. -blue, green, red, solid lines; microphone signals -blue, green, red, dashed lines; un-coherent noise in signals -yellow, black, solid lines; circuit noise (signal input is open, not connected to the microphones) We can see the acoustic signal above 1 Hz, and the circuit does not seem to limit its sensitivity. But I do not know why yellow and black is so different. I will check it tomorrow.

Hi, Ayaka.  It would be good if you could give a little bit more detail about this plot:

• What exactly are the "signals"?  Are you making a sound somehow?  If so, what is producing the sound?  What is it's spectrum?
• Are the blue/green/red traces from three different microphones?
• Coherence usually implies a comparison between two signals.  Is something being compared in the dashed traces?
• Are the yellow and black traces from different amplifiers?
• What are the units of the Y axis?

7818   Wed Dec 12 20:22:03 2012 JamieUpdateComputer Scripts / Programsilluminators fixed and added to VIDEO screen

I fixed the illuminator setup.  ETMY was not hooked up, and the screen wasn't configured quite right.  The ITMX illuminator still needs to be hooked up to the vertex switch.

I made an updated illuminator script that works more like the videoswitch scripts, with a saner interface, and is located here:

/opt/rtcds/caltech/c1/scripts/general/illuminator


I also fixed up the illuminator MEDM interface a bit and added it to the VIDEO screen:

While I was at it, I cleaned up the sitemap a bit:

I hope everyone won't be too confused.

7842   Mon Dec 17 20:22:07 2012 JamieUpdateGeneralVent plan: WE VENT TOMORROW

### We will vent tomorrow (12/18)

After lengthy discussion, I have determined that we should vent now, with the primary goal of this vent to replace the input steering PZTs with the new active tip-tilts.  Since we still don't understand exactly what's going on with the PRC, it's unclear what we would do to attack the problem.  We need to do more modeling and measurements first.  We should limit the goal of this vent to replacing the PZTs, and then close up and do more measurements with better modeling and improved input point in hand.

There is limited time this week before everyone leaves for two-week holidays on Thursday or Friday.  The reason to not vent would be that we don't want to leave the IFO at air during the two week holiday.  People seem to think that this is not a problem, so we don't gain anything by waiting.  Therefore we vent now and do what we can before people take off.

### The goal for this week is to replace PZT1 only:

Now: Jenne and Manasa are doing vent prep.  Manasa is lowering the input power and preparing the mode cleaner.  Jenne centered IPPOS and IPANG.  This will allow us to check how the input alignment changed during the vent.

12/18: Steve is going to start the vent as soon as he gets back from the dentist, at around 10am.  He will regulate the vent such that we are ready to lock the mode cleaner by 4pm.  At that time we will lock the MC and recheck the input alignment with IPPOS/ANG, with the idea being to see if anything moves during the vent.

12/19: First thing in the morning we take off the access connector ONLY.  The access connector is all we'll need to replace PZT1.    Put light door on the OMC chamber side immediately, since we won't need to get in there at all.  We won't need the light access connector.

For the rest of Wednesday we'll remove PZT1 and install the new active TT.  We'll be using the current out-of-vac cable for PZT1 for the new TT.  We should only have to modify the rack end of the cable to accommodate the coil driver.  This should be a small modification.  Given that we have no wiring diagrams we'll have to pin it out in situ.

12/20: Hopefully finish up TT installation.

Jenne leaves 12/20, Manasa and Jamie leave 12/21.  We will either leave light doors on access connector holes, or possibly Rana, Koji, and Steve will replace access connector on Friday so that we can pump down to 1 Torr or something so that we leave it there over the holiday.

### After we return from vacation:

PZT2/TT2 installation.  This will be less straight forward since the new TT has a bigger foot print than PZT2 and will block the PRM optical levers.  We'll need one additional steering mirror to redirect the oplev around the TT.  See elog 7815.

Once the new TTs are installed, we'll reevaluate where we're at.  If PRC modeling has progressed and we have an idea of something to work on with the PRC, we can.  Otherwise, we'll just button up, pump down, and get on with some better PRC measurements.

7852   Tue Dec 18 16:37:17 2012 JamieUpdateAlignmentPost vent, pre door removal alignment

[Jenne, Manasa, Jamie]

Now that we're up to air we relocked the mode cleaner, tweaked up the alignment, and looked at the spot positions:

The measurements from yesterday were made before the input power was lowered.  It appears that things have not moved by that much, which is pretty good.

We turned on the PZT1 voltages and set them back to their nominal values as recorded before shut-down yesterday.  Jenne had centered IPPOS before shutdown (IPANG was unfortunately not coming out of the vacuum).  Now we're at the following value: (-0.63, 0.66).  We need to calibrate this to get a sense of how much motion this actually is, but this is not insignificant.

7863   Thu Dec 20 12:14:19 2012 JamieUpdateGeneralproblem with in-vac wiring for TTs

Nic and I discovered a problem with the in-vac wiring from the feed-thru to the top of the table.  Pin 13 at the top of the stack, which is one of the coil pins on the tip-tilt quadrapus cables, is *the* shield braid on the cable that goes to the feed-thru.  This effectively shorts one of our coil signals.

There are three solutions as we see it:

* swap pin 13 for something else at the top of the stack, and then swap it back somewhere else outside of the vacuum.

* swap *all* the pins at the top of the table to be the mirror.  We would then need to mirror our cables on the outside, but that's less of an issue.

* make a mirror adapter that sits at the top.  This would obviously need to be cleaned/baked.

None of these solutions is particularly good or fast.

7864   Thu Dec 20 17:13:56 2012 JamieUpdateGeneralhow to deal with problem with in-vac wiring for TTs

So this is obviously a general problem for all the TTs.  Our in-vacuum wiring is unfortunately mirrored relative to that of aLIGO, or at least:

• aLIGO: in-vacuum pin 1 tied to shield (T1200131)
• 40m: in vacuum pin 13 tied to shield

And again, the problem is that pin 13 on the TT quadrapus cables is the one of the coil pins for one of the OSEMs.

I think the right solution is to make mirroring adapter cables for the TTs.  Modifying the pins on the stack-top brackets for just the TTs would leave us with a bunch of brackets that are different than all the rest, which I think is a bad idea.  Therefore we leave all the feed-thru-->bracket wiring the same, and make adapters.  I'll describe the adapters in a follow-up post.

The silver lining to this whole thing, if there is one, is that I wired the polarity on the out-of-vac adapter cable at the coil driver in such a way that the drive/send signal went to the grounded in-vac pin.  If I had by chance wired the polarity oppositely everything would probably have worked, except that the return for one of the coils would have gone through the cable shield and the chamber, rather than the return pin to the coil driver.  I'll let you image the problems that would have caused.

Making new adapters will take a little while, but I think we can proceed with the installation and alignment with a temporary setup in the mean time by taking advantage of the polarity I mention above.  We can temporarily swap the polarity so that we can drive current to the coil using pin 13.  This will allow us to complete the installation and do all the alignment.  Once the in-vac adapter cable arrives, we just put it in, fix the out-of-vac polarity, check that everything works as expected, and button up.

We'll pick up all this when we're back on Jan 7.  Steve will put in an order for the in-vac adapter cables ASAP.

I take full responsibility for this fuck up.  We've been unable to find any in-vac wiring diagrams, but I should have checked all of the wiring during the last vent so that we could have prepared for this ahead of time.  Sorry.

7865   Thu Dec 20 18:33:52 2012 JamieUpdateGeneralin-vac adapter cables for TTs

We need short cables that mirror the pins:

The male side will plug into the 25-pin female on the stack-top bracket.  The tip-tilt quadrapus cable will plug into the female side. This will match up pin 1 on the tip-tilt cable, which is connected to it's shield, to pin 13 on the bracket, which is the shield of the cable that runs to the stack.

They need to be vacuum compatible.  Shorter length is preferred, and there is no minimum length (something like an all-in-one gender changer would be ideal, but probably expensive to have made).




7970   Thu Jan 31 10:23:39 2013 JamieUpdateComputersc1iscex still down

 Quote: [Koji, Jenne] We noticed that the iscex computer is still down, but the IOP is (was) running.  When we sat down to look at it, c1x01 was 'breathing', had a non-zero CPU_METER time, and the error was 0x4000, which I've never seen before.  The fb connection was still red though.  Also, it is claiming that its sync source is 1pps, not TDS like it usually is.  Since things were different, Koji restarted the 2 other models running on iscex, with no resulting change.  We then did a 'rtcds restart all', and the IOP is no longer breathing, and the error message has changed to 0xbad.  The sync source is still 1pps. Moral of the story:  c1iscex is still down, but temporarily showed signs of life that we wanted to record.

There's definitely a timing issue with this machine.  I looked at it a bit yesterday.  I'll try to get to it by the end of the week.

7981   Fri Feb 1 09:33:11 2013 JamieUpdateLockingPRM/PR2 cavity

I replaced the BS1 between the POPDC PD and the camera with a 98 reflector, and moved the 50 up before the BS to dump half the light.  Still saturating POPDC, but hopefully the ratio between POPDC and the camera should be better.  We just need to dump more of the power before we get there.  I'll come back to this after C&D if no one else has already gotten to it.

I don't know why I didn't pay more attention last night, but things look way WAY better.  The beams are much cleaner and the power level is much much higher.

7990   Mon Feb 4 10:45:51 2013 JamieSummaryGeneralrough analysis of aligned PRM-PR2 mode scan

Here's a sort of rough analysis of the aligned PRM-PR2 cavity mode scan.

On Friday we took some mode scan measurements of the PRM-PR2 cavity by pushing PRM (C1:SUS-PRM_LSC_EXT) with a 0.01 Hz, 300 count sine wave.  We looked at the transmitted power on the POP DC PD and the error signal on REFL11_I.

Below is a detail of the scan, chosen because the actuation was in its linear region and there were three relatively ok looking transmission peaks with nice PDH response curves:

The vertical green lines on the bottom plot indicate the rough averaged separation of the 11 MHz side-band resonances from the carrier, at +- 0.0275 s.  If we take this for our calibration, we get roughly 400 MHz / second.

The three peaks in top plot have an average FWHM of 0.00381 s.  Given the calibration above, the average FWHM = ~1.52 MHz.

If we assume a cavity length of 1.91 m, FSR = 78.5 MHz.

Putting this together we get a finesse = ~51.6.

Analysis of misaligned mode scans to follow.

7993   Mon Feb 4 15:26:10 2013 JamieUpdateComputer Scripts / ProgramsNew "getdata" program to pull NDS channel data, including test points

I've added a new program called getdata (to scripts/general/getdata) that will conveniently pull arbitrary data from an NDS server, either DQ or online (ie. testpoints).

Start times and durations may be specified.  If past data is requested, you must of course be requesting DQ channels.  If no start time is specified, data will be pulled "online", in which case you can specify testpoints.

If an output directory is specified, the retrieved data will be stored in that directory in files named after the channels.  If an output directory is not specified, no output will be

Help usage:

controls@pianosa:~ 0$/opt/rtcds/caltech/c1/scripts/general/getdata --help usage: getdata [-h] [-s START] [-d DURATION] [-o OUTDIR] channel [channel ...] Pull online or DQ data from an NDS server. Use NDSSERVER environment variable to specify host:port. positional arguments: channel Acquisition channel. Multiple channels may be specified acquired at once. optional arguments: -h, --help show this help message and exit -s START, --start START GPS start time. If omitted, online data will be fetched. When specified must also specify duration. -d DURATION, --duration DURATION Length of data to acquire. -o OUTDIR, --outdir OUTDIR Output directory. Data from each channel stored as '.txt'. Any existing data files will be automatically overwritten. controls@pianosa:~ 0$


7995   Mon Feb 4 19:48:32 2013 JamieSummaryGeneralarbcav recalc of PRC with correct ITM transmission

I noticed that Koji used a high reflector for the ITMs for his full PRC arbcav calculation. I just redo it here with the correct ITM transmission and RoC for completeness.

In this case the finesse is 95, instead of 121.

7996   Mon Feb 4 22:46:03 2013 JamieSummaryGeneralarbcav for SRC with curved TTs

I ran Zach's arbcav on our SRC with curved TTs and the situation looks much worse than the PRC.

I used the following parameters

SRM: RoC = 142 m, T = 10%
ITM: RoC = 83.1e3 m, T = 1.4%
SRC length: 5.37 m

In this case, with TT RoC of -600, the combined cavity g-factor = 0.9986, and astigmatism from SR3 makes the cavity patently not stable.  You have to go up to an RoC of -710 before the cavity is just over the edge.

8005   Tue Feb 5 19:16:22 2013 JamieSummaryGeneralarbcav of PRC with +600 RoC PR2/3

This is just a simple rerun of arbcav from #7995 but with the PR2/3 RoCs set to 600, instead of -600.  Overall g-factor = 0.922, and the modes are well separated:

This doesn't take into account the effect of traveling through the substrates (still working on it).  It assumes the PR2/3 have been moved such that the cavity fold lengths remain the same.

This is something that we need to keep in mind: we will need to adjust the position of the PR2/3 to keep the fold lengths the same.

8019   Wed Feb 6 22:39:23 2013 JamieUpdateGeneralPRC/arm mode matching with flipped PR2/PR3: coming soon

I intended to post a long analysis of the PRC/arm mode matching for the various TT situations using Nic's a la mode mode matching program, but I seem to have encountered what I think might be a bug.  I'll talk to Nic about it first thing in the AM.  Once the issue is resolved I should be able to post the full analysis fairly quickly.  Sorry about the delay.

8022   Thu Feb 7 12:56:18 2013 JamieSummaryGeneralPRC/arm mode matching calculations

NOTE: There was a small bug in my initial calculation.  The plots and numbers have been updated with the fixed values.  The conclusion remains the same.

Using Nic's a la mode mode matching program, I've calculated the PRC mode and g-parameter for various PR2/3 scenarios.  I then looked at the overlap of the resultant PRC eigenmodes with the ARM eigenmode.  Here are the results:

NOTE: each optical element below (PR2, ITM, etc.) is represented by a compound M matrix.  The z axis in these plots is actually just the free space propagation between the elements, not the overall optical path length.

## ARM

This is the ARM mode I used for all comparisons:

 tangential sagittal gouy shift, one-way 55.63 55.63 g (from gouy) 0.303 0.303 g (product of individual mirror g) 0.303 0.303

## PRC, nominal design (flat PR2/3)

This is the nominal "as designed" PRC, with flat PR2/3 folding mirrors.

 tangential sagittal gouy shift, one-way 14.05 14.05 g (from gouy) 0.941 0.941 g (product of individual mirror g) 0.942 0.942

## PRC, both PR2/3 flipped

This assumes both PR2 and PR3 have a RoC of -600 when not flipped, and includes the affect of propagation through the substrates.

 tangential sagittal gouy shift, one-way 19.76 18.45 g (from gouy) 0.886 0.900 g (product of individual mirror g) 0.888 0.902

## PRC, only PR2 flipped

In this case we only flip PR2 and leave PR3 with it's bad -600 RoC:

 tangential sagittal gouy shift, one-way 18.37 18.31 g (from gouy) 0.901 0.901 g (product of individual mirror g) 0.903 0.903

# Discussion

I left out the current situation (PR2/3 with -600 RoC) and the case where only PR3 is flipped, since those are both unstable according to a la mode.

### I guess the main take away is that we get slightly better PRC stability and mode matching to the arms by only flipping PR2.

8032   Fri Feb 8 11:01:18 2013 JamieUpdateLockingPRMI work

I completely agree with Koji.  We definitely should have locked the half PRC first.  We were all set up for that.  Why go through all this work to align MICH when we haven't confirmed with the half PRC that the flipping is helping us?  The first rule of debugging is to only make one change at a time.  We have measurements from the half PRC, so we could have made a direct comparison with those to see how things have changed.  If we jump the gun we're going to end up wasting more time when we have to back-track.

Also, we never talked about moving PR2 to adjust optical path length, although I can understand why we would think that should be done.  My calculations were all done assuming the free-space separation between PRM/PR2 and PR2/PR3 were unchanged.  It's possible changing the position is better, but again, it's more work and it changes multiple things at one.  I can redo my calculations for this new scenario, but we need to update our drawings with this new configuration.  Please note precisely where PR2 has moved to.

We should have just flipped PR2 and that's it.  Then we could have run the exact same measurements we had previously.  Only then, once we understood this new simple cavity, should we have done further adjustments.

8033   Fri Feb 8 11:07:07 2013 JamieSummaryGeneralPRC/arm mode matching calculations

 Quote: I would guess that either flipping PR2 or PR3 would give nearly the same effect (g = 0.9) and that flipping both makes it even more stable (smaller g). But what we really need is to see the cavity scan / HOM resonance plot to compare the cases. The difference of 0.5% in mode-matching is not a strong motivation to make a choice, but sensitivity to accidental HOM resonance of either the carrier or f1 or f2 sidebands would be. Should also check for 2*f2 and 2*f1 resonances since our modulation depth may be as high as 0.3. Accidental 2f resonance may disturb the 3f error signals.

You would guess, and I would have guessed too, but the calculations tell the story.   Flipping both does not increase the stability.  The main issue is that flipping PR3 induces considerable astigmatism.  This is why flipping PR3 alone does not make the cavity stable.  I will do some simple calculations today that will demonstrate this effect.

But again, we should only change one thing at a time and understand that before moving on.  Given that the calculations show that flipping only PR2 should alone have a positive affect, we should do just that first, and verify that we understand what's going on, before we move on to making more changes.

I will try to make some more arbcav runs as well, for just the flipped PR2.

8040   Fri Feb 8 18:23:32 2013 JamieSummaryGeneralarbcav of half PRC with flipped PR2

Arbcav with half PRC (flat temporary mirror in front of BS), PR2 RoC = 600m, PR3 RoC = -600m:

NOTE: this does NOT include the affect of the PR2 substrate in the cavity.  Arbcav does not handle that.  It would have to be modified to accept arbitrary ABCD matrices.

NOTE: I added to the mode plot the frequency separation of the first HOMs from the carrier (\omega_{10/01}), in units of carrier FSR.

8059   Mon Feb 11 17:17:30 2013 JamieSummaryGeneralmore analysis of half PRC with flipped PR2

 Quote: We need expected finesse and g-factor to compare with mode-scan measurement. Can you give us the g-factor of the half-PRC and what losses did you assumed to calculate the finesse?

This is exactly why I added the higher order mode spacing, so you could calculate the g parameter.  For TEM order N = n + m with spacing f_N, the overall cavity g parameter should be:

g = (cos( (f_N/f_FSR) * (\pi/N) ))^2

The label on the previous plat should really be f_N/FSR, not \omega_{10,01}

BUT, arbcav does not currently handle arbitrary ABCD matrices for the mirrors, so it's going to be slightly less accurate for our more complex flipped mirrors.  The affect would be bigger for a flipped PR3 than for a flipped PR2, because of the larger incidence angle, so arbcav will be a little more correct for our flipped PR2 only case (see below).

 Quote: Also, flipped PR2 should have RoC of - R_HR * n_sub (minus measured RoC of HR surface multiplied by the substrate refractive index) because of the flipping.

This is not correct.  Multiplying the RoC by -N would be a very large change.  For an arbitrary ABCD matrix:

R_eff = -2 / C


When the incident angle in non-zero:

tangential: R_eff = R_eff / cos(\theta)
sagittal:   R_eff = R_eff * cos(\theta)


For flipped PR2, with small 1.5 degree incident angle and RoC of -706 at HR:

M_t = M_s = [1.0000, 0.0131; -0.0028, 1.0000]
R_eff = 705.9


For flipped PR3, with large 41 degree incident angle and RoC of -700 at HR:

M_t = [1.0000, 0; 0.0038, 1.0000]
M_s = [1.0000, 0; 0.0022, 1.0000]
R_eff = 592.4
`

The affect of the substrate is negligible for flipped PR2 but significant for flipped PR3.

# The current half-PRC setup

OK, I have now completely reconciled my alamode and arbcav calculations.  I found a small bug in how I was calculating the ABCD matrix for non-flipped TTs that made a small difference.  I now get the exact same g parameter values with both with identical input parameters.

 Quote: According to Jenne dictionary, HR curvature measured from HR side is; PRM: -122.1 m PR2: -706 m PR3: - 700 m TM in front of BS: -581 m

Sooooo, I have redone my alamode and arbcav calculations with these updated values.  Here are the resulting g parameters

 arbcav a la mode measurement g tangential 0.9754 0.9753 0.986 +/- 0.001 g sagital 0.9686 0.9685 0.968 +/- 0.001

So the sagittal values all agree pretty well, but the tangential measurement does not.  Maybe there is an actual astigmatism in one of the optics, not due to angle of incidence?

arbcav HOM plot:

8062   Mon Feb 11 18:44:34 2013 JamieUpdateComputerspasswerdz changed

 Quote: Be Prepared http://xkcd.com/936/

Password for nodus and all control room workstations has been changed.  Look for new one in usual place.

We will try to change the password on all the RTS machines soon.  For the moment, though, they remain with the old passwerd.

8068   Tue Feb 12 18:25:43 2013 JamieSummaryGeneralhalf PRC with astigmatic PR2/3

Quote:
 arbcav a la mode measurement g tangential 0.9754 0.9753 0.986 +/- 0.001 g sagital 0.9686 0.9685 0.968 +/- 0.001

Given that we're measuring different g parameters in the tangential and sagittal planes, I went back to alamode to see what astigmatism I could put into PR2 and/or PR3 to match what we're measuring.  I looked at three cases: only PR2 is astigmatic, only PR3 is, or where we split the difference.  Since the sagittal measurement matches, I left all the sagittal curvatures the same in

### case 1: PR3 only

 PR2 RoC (m) PR3 RoC (m) g (half PRC) tangential 706 -420 0.986 sagittal 706 -700 0.969

### case 2: PR3 only

 PR2 RoC (m) PR3 RoC (m) g (half PRC) tangential 5000 -700 0.986 sagittal 706 -700 0.969

### case 3: PR2 and PR3

 PR2 RoC (m) PR3 RoC (m) g parameter tangential 2000 -600 0.986 sagittal 706 -700 0.969

From Koji's post about the scans of the G&H mirrors, it looks entirely reasonable that we could have these levels of astigmatism in the optics.

## What this means for full PRC

These all make the same full PRC situation:

g (tangential):  0.966

g (sagittal):  0.939

ARM mode matching:  0.988

ELOG V3.1.3-