Thanks so much Rolf (and Keith)!

Jamie tells me that the 2 big consequences of this are (a) we are not archiving any data that is collected on the ioo machine, and (b) that we will not have access to test points on the IOO or ALS models.

To make sure that this is not a show-stopper for locking, I have locked the arms using ALS.  The signals seem to still be getting from the ALS model to the LSC model, and I'm able to acquire ALS lock, so we should be able to work tonight.  All of the data that I have been looking at lately has been coming off of the LSC machine, so we should even be okay in terms of look-back for lockloss studies, etc.

c1lsc and c1ioo computers had FB net statuses all red. So, I restarted mx_stream on each computer.

ssh controls@c1lsc
sudo /etc/init.d/mx_stream restart

Just as Yuta and I were sitting down to look at our beatnote (really the output of the freq discriminator) on Dataviewer, all the FB net boxes on the CDS status screen were white.  I restarted daqd, and most of the computers came back fine.  c1iscey and c1sus still had some red bad boxes.  So I restarted mx_stream on both, and they are now fine.

Somehow, this also fixed whatever I had done to the lsc model yesterday (although I think TRY is still not recorded at this time - not messing with it yet).

We removed all the folding mirrors ({P,S}R{2,3}) from the IFO and took them into the bake lab clean room.  The idea was that at the very least we would install the new dichroic mirrors, and then maybe replace the suspension wires with thinner ones.

I went in to spend some quality time with one of the tip-tilts.  I got the oplev setup working to characterize the pointing.

I grabbed tip-tilt SN003, which was at PR2.  When I set it up it  was already pointing down by a couple cm over about a meter, which is worse than what we were seeing when it was installed.  I assume it got jostled during transport to the clean room?

I removed the optic that was in there and tried installing one of the dichroics.  It was essentially not possible to remove the optic without bending the wires by quite a bit (~45 degrees).  I decided to remove the whole suspension system (top clamps and mirror assembly) so that I could lay it flat on the table to swap the optic.

I was able to put in the dichroic without much trouble and get the suspension assembly back on to the frame.  I adjusted the clamp at the mirror mount to get it hanging back vertical again.  I was able to get it more-or-less vertical without too much trouble.

I poked at the mirror mount a bit to see how I could affect the hysteresis.  The answer is quite a bit, and stochastically.  Some times I would man-handle it and it wouldn't move at all.  Sometimes I would poke it just a bit and it would move by something like a radian.

A couple of other things I noted:

• The eddy current damping blocks are not at all suspended.  The wires are way too think, so they're basically flexures.  They were all pretty cocked, so I repositioned them by just pushing on them so they were all aligned and centered on the mirror mount magnets.
• The mirror mounts are very clearly purposely made to be light.  All mass that could be milled out has been.  This is very confusing to me, since this is basically the entire problem.  Why were they designed to be so light?  What problem was that supposed to solve?

I also investigated the weights that Steve baked.  These won't work at all.  The gap between the bottom of the mirror mount and the base is too small.  Even the smalled "weights" would hit the base.  So that whole solution is a no-go.

What else can we do?

At this point not much.  We're not going to be able to install more masses without re-engineering things, which is going to take too much time.  We could install thinner wires.  The wires that are being used now are all 0.0036", and we could install 0.0017" wires.  The problem is that we would have to mill down the clamps in order to reuse them, which would be time consuming.

The plan

So at this point I say we just install the dichroics, get them nicely suspended, and then VERY CAREFULLY reinstall them.  We have to be careful we don't jostle them too much when we transport them back to the IFO.  They look like they were too jostled when they were transported to the clean room.

My big question right now is: is the plan to install new dichroics in PR2 and SR2 as well, or just in PR3 and SR3, where the green beams are extracted?  I think the answer is no, we only want to install new dichroics in {P,S}R3.

The future

If we're going to stick with these passive tip-tilts, I think we need to consider machining completely new mirror mounts, that are not designed to be so light.  I think that's basically the only way we're going to solve the hysteresis problem.

I also note that the new active tip-tilts that we're going to use for the IO steering mirrors are going to have all the same problems.  The frame is taller, so the suspensions are longer, but everything else, including the mirror mounts are exactly the same.  I can't see that they're not going to suffer the same issues.  Luckily we'll be able to point them so I guess we won't notice.

The thinner wire has a history that it did not improve the hysteresis (ask Jenne). Nevertheless, it's worth to try.

If you flip the clamp upside-down, you can lift the clamping point up. This will make the gravity restoring torque stronger.
(i.e. Equivalent effect to increasing the mass)

Luckily (or unluckily) the clamp has no defined location for the wire as we have no wire fixture.
Therefore the clamp will grab the wire firmly even without milling.

 Why not? The new dichroic mirrors have more transmission of 1064nm than G&H. Thus it will give us more POP beam and will help locking.

 The wire clamps should be taken off at the top and at the mirror holder. They need a mill touch up. It would be nice to have the centering jig from LLO for the 0.0017"

The clamps in this condition are really bad. It can sleep, it is not adjustable.

I stabilized Y arm length by using only I phase coarse signal from the beat(C1:ALS-BEATY_COARSE_I_ERR).
I sweeped the arm length by injecting 0.05Hz sine wave from C1:ALS_OFFSETTER2_EXC.
Below is the plot of TRY and the error signal(ideally, Y arm length) while the sweep.



I couldn't hold the arm length tight, so you can see multiple peaks close to each other.
We need to
  - adjust offsets
  - adjust rotation phase of I-Q mixing
  - adjust servo filters
to hold the length tighter.

Also, I couldn't sweep the Y arm length very much. I need to calibrate, but to do the modescan for many FSRs, we need to
  - introduce automatic phase optimizing system
There were sin/cos function in the CDS_PARTS, so I think we can feedback I_ERR to control rotation phase of I-Q mixing.

 That sounds goofy.

With the delay line technique, you can get a linear signal over 50 MHz with no phase shifting. What is with all this I/Q stuff?

Linear range df of the delay line technique is about df ~ c/(2D). So, the linear range for the fine signal(delay line length D=30m) is about 5 MHz.
Arm cavity FSR = c/(2L) = 3.7 MHz.
So, I think we need phase shifting to do mode scan for more than 2 FSRs by holding the arm length finely with fine servo.
For the coarse (D=1.5m), the linear range is about 100 MHz, so if we can do mode scan using coarse servo, it is OK.

In any case, I think it is nice to have linear signal with fixed slope even if we don't adjust the phase every time.

You can easily calculate whether or not the coarse readout will work by thinking about the scan resolution you need given the ADC dynamic range and the whitening filter that you use.

I am going to try handing off the ALS servo to the IR PDH servo on the Y arm and measure the noise.

 - first I need to investigate why the Y end PDH servo becomes unstable when the ALS is engaged with a high UGF.

(some notes)

 So far I still kept failing to increase the UGF of the ALS servo for some reason (see #6024).

Every time when I increased the UGF more then 50 Hz, the Y arm PDH lock became unlocked. It needs an explanation and a solution.

Another thing: During several trials in this evening I found the ETMY_SUSPOS_GAIN had been set to 1, so I reset it to 20, which gives us the damping Q of about 5.

(Temperature feedback activated)

 As planed in #6024 I have activated the temperature feedback, so that the PZT control signal is offloaded to the temperature. And it seems working fine.

Currently the gain is set to 0.03, which gives us a time constant of ~30 sec for offloading the control signal.

We were not able to open up any test points in the revived c1spx model (dcuid 61).

Looking at the GDS_TP screen we found that every test point was being held open (C1:FEC-61_GDS_MON_?).  Tried closing all test points, awg and otherwise, with the diag comnand line (diag -l), but it would crash when we attempted to look at the test points for node 61.

Rebuild, install, restart of the model had no affect.  As soon as awgtpman came back up all the testpoints were full again.

I called Alex and he said he had seen this issue before as a problem with the mbuf kernel module.  Somehow the mbuf module was holding those memory locations open and not freeing them.

He suggested we reboot the machine or restart mbuf.  I used the following procedure to restart mbuf:

• log into c1iscex as controls
• sudo /etc/init.d/monit stop (needed so that monit doesn't auto-restart the awgtpman processes)
• rtcds stop all
• sudo /etc/init.d/mx_stream stop
• sudo rmmod mbuf
• sudo modprobe mbuf
• sudo /etc/init.d/mx_stream start
• sudo /etc/init.d/monit start
• rtcds start all

Once this was done, all the test points were cleared.

Alex seems to think this issue is fixed in a newer version of mbuf.  I should probably rebuild and install the updated mbuf kernel module at some point soon to prevent this happening again.

Unfortunately this isn't the end of the story, though.  While the test points were cleared, the channels were still not available from c1spx.

I looked in the framebuilder logs to see if I could see anything suspicious.  Grep'ing for the DCUID (61), I found something that looked a little problematic:

...
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=60 HOST=c1lsc DCUID=60
GDS server NODE=61 HOST=c1iscex DCUID=61
...

Note that two nodes, 25 and 61, are associated with the same dcuid.  25 was the old dcuid of c1spx, before I renumbered it.  I tracked this down to the target/gds/param/testpoint.par file which had the following:

[C-node25]
hostname=c1iscex
system=c1spx
...
[C-node61]
hostname=c1iscex
system=c1spx

It appears that this file is just amended with new dcuids, so dcuid changes can show up in duplicate.  I removed the offending old stanza and tried restarting fb again...

Unfortunately this didn't fix the issue either.  We're still not seeing any channels for c1spx.

So I was wrong, the channels are showing up.  I had forgotten that they are showing up under C1SUP, not C1SPX.

[Joe/Kiwamu]

 We found there are some filter names that we can not properly build for some reason.

The following names are not properly going to be built :

 - REFL_DC

 - AUX

If we use the names shown above for filters, it doesn't compile any filter modules.

We took a quick look around the src files including feCodegen.pl, but didn't find any obvious bugs.

For the sake of writing it down: /cvs/cds/caltech/apps/linux64/rockNDS

The upgrade of megatron broke the nds2 service. I have fixed things by

  1) installing the latest version of framecpp (1.19.32) from the lsc debian repository (this was necessary because I couldn't link to the existing version)

  2) built nds2-server-0.5.11 and installed it in the system directories (/usr/bin)

  3) there were a few scripts/links/etc that didn't seem to be set up correctly and I fixed them to correspond with my preious message.

 nds2 is now running and the channel list should be updated regularly and the service restarted as appropriate.

After being unable to fetch data offsite using the nds40 server, I found enlightment here. Our nds2 server is running on megatron and the link before should be sufficient to restore it after any hiccups.

I installed nds2-client-devel on rossa using the following command:

$ sudo yum install nds2-client-devel

I updated the ndscope on rossa to a bleeding edge version (0.7.9+dev0) which has many of the fixes I've requested in recent times (e.g. direct PDF export, see Attachment #1). As usual if you find issue, report it on the issue tracker. The basic functionality for looking at signals seems to be okay so this shouldn't adversely impact locking efforts.

In hindsight - I decided to roll-back to 0.7.9, and have the bleeding edge as a separate binary. So if you call ndscope from the command line, you should still get 0.7.9 and not the bleeding edge.

 [Joe and Kiwamu]

Tonight we noticed that the REFL_DC signal has gone bipolar, even though the whitening gain is 0 dB and the whitening filter is requested to be OFF.

We should check out the switch operation of several ofthe LSC channels in the daytime - where is the procedure for this diagnostic posted?

I did a bunch of cleanup work on the netGPIB stuff:

• Removed extensions from all executable scripts (executables should not have language extensions)
• fixed execution permissions on executables and modules
• committed HP8590.py and HP3563A.py instrument modules, which were there but not included in the svn
• committed NWAG4395A (was AG4395A_Run.py) to svn, and removed old "custom" copies (bad people!)
• cleaned up, modernized, and fixed the netgpibdata program
• removed plotting from netgpibdata, since it was only available for one instrument, there's already a separate program to handle it, and it's just plotting the saved data anyway
• added a netgpibcmd program for sending basic commands to instruments.
• added a README

Probably the most noticeable change is removing the extensions from the executables.   There seems to be this bad habit around here of adding extensions to executables.  It doesn't matter to the person running the program what language it was written in, so don't add extensions.  It only matters for libraries.

I could not understand why 'netgpibdata' scripts are missing in "scripts/general" folder on pianosa... Where did they go???

Also, I found that the PROLOGIX GPIB-LAN controller for crocetta (192.168.113.108) is no longer working. I need to reconfigure it with "telnet"...

The netgpibdata scripts are now under git version control at /opt/rtcds/caltech/c1/scripts/general/labutils/netgpibdata. I think the idea was to make this directory a collection of useful utilities that we could then pull at various labs / at the sites.

crochetta was reconfigured to have 192.168.113.108. It was confirmed that it can be used with netgpibdata.py

Configuration: I have connected my mac with the unit using an Apple USB-Ethernet adapter. The adapter was configured to have a manual IP of 192.168.113.222/255.255.255.0. "netfinder.exe" was run to assign the IP addr to the unit. It seemed that NVRAM of the unit evaporated as it had the IP of 0.0.0.0. Once it was configrued, it could be run with netgpibdata as usual.

I've fixed the gpib scripts for the SR785 and AG4395A to output data in the same format as expected by older scripts when called by them. In addition, there are now some easier modes of operation through the measurement scripts SRmeasure and AGmeasure. These are on the $PATH for the main control room machines, and live in scripts/general/netgpib

Case 1: I manually set up a measurement on the analyzer, and just want to download / plot the data. 

Make sure you have a yellow prologix box plugged in, and can ping the address it is labeled with. (i.e. 'vanna'). Then, in the directory you want to save the data, run:

SRmeasure -i vanna -f mydata --getdata --plot

This saves mydata_(datetime).txt and mydata_(datetime).pdf in the current directory. 

In all cases, AGmeasure has the identical syntax. If the GPIB address is something other than 10, specifiy it with -a, but this is rarely the case.

Case 2: I want to remotely specify a measurement

Rather than a series of command line arguments, which may get lost to the mists of time, I've set the scripts up to use parameter files that serve as arguments to the scripts. 

Get the templates for spectrum and TF measurements in your current directory by running

SRmeasure --template

Set the parameters with your text editor of choice, such as frequency span, filename output, whether to create a plot or not, then run the measurement:

SRmeasure SR785template.yml

Case 3: I want to compare my data with previous measurements

In the template parameter files, there is an option 'plotRefs', that will automatically plot the data from files whose filenames start with the same string as the current measurement.

If, in the "#" commented out header of the data file, there is a line that contains "memo:" or "timestamp:", it will include the text that follows in the plot legend. 

There are also methods to remotely trigger an already configured measurement, or remotely reset an unresponsive instrument. Options can be perused by looking at the help in SRmeasure -h

I've tested, debugged, and used them for a bit, but wrinkles may remain. They've been svn40m committed, and I also set up a separate git repository for them at github.com/e-q/netgpibdata

Now netgpibdata is working again.

Usage:

cd /cvs/cds/rtcds/caltech/c1/scripts/general/netgpibdata   
./netgpibdata -i 192.168.113.108 -d AG4395A -a 10 -f meas01
./netgpibdata -i 192.168.113.105 -d SR785 -a 6 -f meas01   

Jenne witnessed and certified that they were working fine.
Now no one can say "it does not work"!

These weeks I was annoyed by the fact that netgpibdata was messed up by dummies.
A terrible situation was found:

1. Someone pushed the factory reset of one of the wifi bridges (LINKSYS WET54G).
2. Someone gave wrong IPs to the bridges (192.168.1.* instead of 192.168.113.*)
3. Someone left a default IP to the bridges. This means the routers had the same IPs.

-------

I gave the IPs to the bridges. According lines of /etc/hosts in linux1 were updated.

192.168.113.230 WET54G1
192.168.113.231 WET54G2

All of the network settings are taped on the bridge now.
The reset switch of each bridge was covered by a tape so that dummies can't randomly push the button.

The command was tested with each device.

Just wanted to point out that the correct "modern" path to this stuff is:

/opt/rtcds/caltech/c1/scripts/general/netgpibdata

This is, of course, the same directory, but under the correct "/opt/rtcds", instead of the old, incorrect "/cvs/cds".

Not working again. I tried the commands in Koji's elog as well as the ones from my notes, but the AG 4395 hooked up to the yellow box named crocetta doesn't work. It gets to the stage of opening the data files and hangs. I tried it with many variations on pianosa and rossa. Also tried power cycling the analyzer and the Prologix and the bridge.

While hooked up to the MC error point I set the modulation frequency from 137 to 133 Hz to minimize the 3 MHz peak as usual.

Started working tonight. Don't know if anyone did anything to the Martian network or not, so its a mystery...

I also modified the script and SVN'd it. It now correctly takes your plot wants and adjust the linear/log of the axes accordingly

./SPAG4395A.py -i crocetta -A -v 4 --att=0 --start=1kHz --end=10MHz --bw=1kHz --plot --semiy

and also saves the plot as out.pdf

In the attached image I show the MC board TP1A output. The two peaks around 3.7 Mhz are the sideband beats we speak of. The lower one is proportional to the MC length/frequency mistmatch.

I've moved the WB network analyzer to the OMC lab. The 40m network analyzer is not in service for the MC monitoring.
I setup the configuration so that the same command gives us the same spectrum measurement.

 I was going through some old Koji elogs to check them for correctness (as I do weekly). I noticed that back in Dec 2013, he made the above illegal modification of IP numbers. 192.168.113.230 was actually the IP for farfalla. Maybe that's why they were conflicting and farfalla not working and Q observing/imagining wireless GPIB dropouts?

I used the Wiki instructions to update the 2 bind9 files with a new number for farfalla (192.168.113.212) which was previously the number for the long dead op240m. Farfalla is restarted and sort of working. 

 To help development of the data visualization project, we've assigned the .101 and .102 IP to DataVis. This is being used by the iMac in the control room via port 8 of the CDS switch near the Blue Plataeu Tournant.

We tried using one of the free ports, but Jamie realized that we had to use one of the already assigned ones due to some 'Smart' switch management software. So for the moment, please leave the iMac alone so that Bill can use it.

There's, as usual, a disconnect between the real martian host table and the one displayed on the Wiki. Basically, the point is: DO NOT TRUST THE WIKI, because people who update the actual host table only randomly update the wiki table.

The only thing worth trusting is the file

/var/named/chroot/var/named/martian.zone
on linux 1.

You will need to have 'root' or 'sudo' to get into that directory to read the file.

Awesome 5 hrs of locking  Rob!

http://tex.stackexchange.com/questions/2092/which-figure-type-to-use-pdf-or-eps

NDS2 is not designed for non DQ channels - it gets data from the frames, not through NDS1.

For getting the non-DQ stuff, I would just continue using our NDS1 compatible NDS mex files (this is what is used in mDV).

The NDS2 protocol is not for non-DQ, but the NDS2 client is capable of talking both the NDS1 and NDS2 protocols.

fb:8088 is an NDS1 server, so the client is talking NDS1 to fb.  It should therefore be capable of getting online data.

It doesn't seem to be seeing the online channels, though, so I'll work with Leo to figure out what's going on there.

The old mex functions, which like I said are now available, aren't capable of getting online data.

I've installed the new nds2 packages on the control room machines.

These new packages include some new and improved interfaces for python, matlab, and octave that were not previously available. See the documentation in:

  /usr/share/doc/nds2-client-doc/html/index.html

for details on how to use them.  They all work something like:

  conn = nds2.connection('fb', 8088)
  chans = conn.findChannels()
  buffers = conn.fetch(t1, t2, {c1,...})
  data = buffers(1).getData()

NOTE: the new interface for python is distinct from the one provided by pynds.  The old pynds interface should continue to work, though.

To use the new matlab interface, you have to first issue the following command:

   javaaddpath('/usr/lib/java')

I'll try to figure out a way to have that included automatically.

The old Matlab mex functions (NDS*_GetData, NDS*_GetChannel, etc.) are now provided by a new and improved package.  Those should now work "out of the box".

 I've tried new nds2 Java interface in Matlab. Using findChannels method of the connection class I see only slow, DQ and trend channels. I could even download data online using iterate method. When it will be possible to do the same with fast non-DQ channels?

>> conn = nds2.connection('fb', 8088);
>> conn.iterate({'C1:LSC-XARM_OUT'})
??? Java exception occurred:
java.lang.RuntimeException: No such channel.
    at nds2.nds2JNI.connection_iterate__SWIG_0(Native Method)
    at nds2.connection.iterate(connection.java:91)

[Kira, Johannes]

I connected up the channels for the ADC Acromag a while back and we were planning to install it today so that we could set up a new channel for the out of loop sensor. Unfortunately, the Acromag seems to be broken. We connected up a precision 10V voltage to one of the channels, but the Acromag read out ~7V and it kept fluctuating. Even after calibration, we still got the same result. When enabling the legacy support, we got ~11V. But when we measured the voltage at the screw terminals with a multimeter and it showed 10V, so the issue is not with the wiring. All of the channels have this same issue. We will be ordering more Acromags soon, so hopefully we'll be able to set up the channel soon. I've attached a picture of the Acromag along with the front panel with the channels labeled

Based on the evaluation of the error signals, the new servo was designed.

Concept:
- Don't touch the locking filters. (i.e. FM5)
- Sacrifice some phase at 150Hz to increase the gain between 3-20Hz.
- As resonant gains costs the phase without increasing the LF gains, replace them with a poles for the integrators.

FM(:,1) = zero2(f,.5,.7).*pole2(f,0.001,.7)*(0.5/0.001)^2;
FM(:,2) = zero2(f,5,2).*pole2(f,3,3).*pole1(f,1).*zero1(f,5)*5*(5/3)^2;
FM(:,3) = zero2(f,25,.7).*pole2(f,3.2,10)*(25/3.2)^2; % Zero crossing
FM(:,4) = zero2(f,35,2).*pole2(f,3,3).*zero1(f,3000).*pole1(f,1).*pole2(f,3000,1/sqrt(2)).*pole1(f,700).*zero1(f,10).*zero1(f,350).*136e1;
FM(:,5) = zero1(f,1).*pole1(f,4010).*pole2(f,17.3211e3,1.242).*zero2(f,18.865e3,100e3);
FM(:,6) = zero2(f,5,2).*pole2(f,10,2).*pole2(f,16.5,30).*zero2(f,30,2);
FM(:,7) = 1;
FM(:,8) = 1;
FM(:,9) = 1;
FM(:,10) = 1;
dc_gain = 14;

FM1/2/3/5/6 are expected to be used for the control.

FM1: Boost below 0.5Hz. This does not cost the phase margin.
FM2: Increase the gain below 5Hz. This hardly cost the phase margin.
FM3: Boost below 25Hz. This is the main phase cost at UGF. This has a complex pole pair at 3Hz with Q=10 to supress the stack motion.
FM6: zero-pole-pole-zero combination to boost the gain between 5 to 30Hz. This eats the phase margin a little.

Note that the phase tracker gain for the X arm was increased by factor of 2.5.

Comparison of the new and old servo OLTF
The new servo has the same UGF, slightly less phase margin, and more gain between 1.5 and 25Hz.

[Joe, Kiwamu] 

Woooo Yeaaaah ! 

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