ID |
Date |
Author |
Type |
Category |
Subject |
1531
|
Wed Apr 29 04:03:51 2009 |
Yoichi | Update | Locking | CARM RF changed to REFL_2I |
Yoichi, Peter
As Rob suggested, the optimal demodulation phase is easier to find for REFL_2I than POX_1I.
Moreover, for 166MHz LO, we have a phase shifter (delay line) already installed. So we can easily change the demodulation phase of REFL_2I.
Tonight, we switched the RF CARM signal to REFL_2I.
To do so, I changed the signal going to the REFL1 input of the common mode board from POX_1I to REFL_2I.
I moved a BNC-T installed at the output of POX_1I to the REFL_2I output to split the REFL_2I signal and send it to the CM board.
Since the gain of the REFL_2I was about 20dB lower than that of POX_1I, I increased the gain of the SR560, which is installed between the REFL_2 demodulation board and the CM board, from 1 to 10.
With some gain tweaks, we were able to hand off the CARM from REFL_DC to REFL_2I. We also succeeded in switching the REFL_2I ADC channel from PD11 to PD2_DC (the output of the length path from the CM board). This switching is necessary in order to engage the boost on the CM board.
There remains some offset in the CARM when the arm power is maximized. This is expected because the REFL_2I demodulation phase is probably not exactly right.
I will optimize the demodulation phase tomorrow. |
1530
|
Tue Apr 28 17:51:13 2009 |
rob | HowTo | Locking | setting the RF CARM demod phase |
Quote: |
To set the demod phase for RF CARM, sensed at REFL2 (REFL 166I), it suffices to set the demod phase for REFL2 to be the optimal phase for controlling SRCL in a no-arm state.
|
For POX33, the ideal phase for single arm locking does not yield a zero-offset CARM signal. So the offset needs to be manipulated digitally. |
Attachment 1: XARM_phases_POX.pdf
|
|
Attachment 2: CARM_phases_POX.pdf
|
|
1529
|
Tue Apr 28 16:36:24 2009 |
rob | HowTo | Locking | setting the RF CARM demod phase |
To set the demod phase for RF CARM, sensed at REFL2 (REFL 166I), it suffices to set the demod phase for REFL2 to be the optimal phase for controlling SRCL in a no-arm state. |
Attachment 1: CARM_phases_REFL.pdf
|
|
Attachment 2: SRCL_phases_REFL.pdf
|
|
1528
|
Tue Apr 28 12:55:57 2009 |
Caryn | DAQ | PEM | Unplugged Guralp channels |
For the purpose of testing out the temperature sensors, I stole the PEM-SEIS_MC1X,Y,Z channels.
I unplugged Guralp NS1b, Guralp Vert1b, Guralp EW1b cables from the PEM ADCU(#10,#11,#12) near 1Y7 and put temp sensors in their place (temporarily). |
1527
|
Tue Apr 28 09:27:32 2009 |
steve | Configuration | VAC | cryopump deserves some credit |
Congratulation Yoichi and Peter for full rf locking at night. Let's remember that the cryopump was shaking the hole vac envelope and ifo during this full lock. |
Attachment 1: cryfl.jpg
|
|
Attachment 2: seiscryofl.jpg
|
|
1526
|
Tue Apr 28 04:30:16 2009 |
Yoichi | Update | Locking | RF full lock |
Yoichi, Peter
I believe we have succeeded in the full lock of the interferometer with the RF signals.
The lock process is reasonably robust and repeatable.
I did a scan of the RF CARM offset and plotted the arm power as a function of the CARM offset (see the attachment).
The arm power goes maximum at non-zero CARM offset. I guess the RF CARM error signal has some offset.
Maybe the demodulation phase is wrong ? I will tweak this tomorrow.
The script to do this scan can be found at /cvs/cds/caltech/scripts/CM/CARMSweep.
I haven't tried DC readout yet. |
Attachment 1: Sweep1.png
|
|
1525
|
Tue Apr 28 01:48:45 2009 |
pete | Configuration | VAC | VC1 open |
At about 1am or so Yoichi and I opened VC1. CC1 had fallen to about 5e-5 torr. |
1524
|
Mon Apr 27 18:31:44 2009 |
steve | Configuration | VAC | VC1 closed |
CC1 5e-7 Torr, VC1 closed at 18:25, IFO is not pumped, RGA is in bg-mode
|
1523
|
Sun Apr 26 02:13:18 2009 |
Yoichi | Update | Locking | Two more successes of RF CARM handoff |
Tonight, the RF CARM hand off (mostly) succeeded twice.
But still, the IFO lost lock when I reduced the REFL_DC gain in the AO path to zero.
At the beginning of tonight's work, MICH DD hand off failed several times. This was because the the PD9 gains were set to zero.
I found that the offset script, which I called before starting the locking, fails to restore the gain values sometimes.
This happens when ezcaread fails to read the current gain. We have to be careful when running the LSCoffsets script. |
1522
|
Sat Apr 25 03:27:34 2009 |
Yoichi | Update | Locking | Locking status |
Yoichi, Peter,
We are working on the final step of the lock acquisition, RF CARM hand off.
I was able to hand off the CARM error signal to RF once, but lost lock when decreasing the CARM offset to zero (it was too rapid).
I will try to make the process more robust tomorrow. |
1521
|
Sat Apr 25 02:54:25 2009 |
Yoichi | Configuration | VAC | Reflector for the cryopump temperature monitor changed |
Quote: | The temperature of the cryopump head is monitored by a photo switch looking at an aluminum foil reflector attached to the needle of the temperature gauge.
If the needle moves out of the 14K position, the photo switch will be triggered to close the cryopump gate valve.
However, this photo switch system has been touchy.
Tonight, the switch falsely tripped several times and closed the gate valve, which caused lock losses as the motion of the valve generates a lot of vibrations.
Seems to me, it was caused by the poor/irregular reflection from the wrinkled aluminum foil on the needle.
So I replaced the aluminum foil with a brand-new shiny one. |
The photo switch still trips randomly. We need a better interlock. |
1520
|
Sat Apr 25 00:45:31 2009 |
Yoichi | Configuration | VAC | Reflector for the cryopump temperature monitor changed |
The temperature of the cryopump head is monitored by a photo switch looking at an aluminum foil reflector attached to the needle of the temperature gauge.
If the needle moves out of the 14K position, the photo switch will be triggered to close the cryopump gate valve.
However, this photo switch system has been touchy.
Tonight, the switch falsely tripped several times and closed the gate valve, which caused lock losses as the motion of the valve generates a lot of vibrations.
Seems to me, it was caused by the poor/irregular reflection from the wrinkled aluminum foil on the needle.
So I replaced the aluminum foil with a brand-new shiny one. |
1519
|
Fri Apr 24 17:26:57 2009 |
Yoichi | Update | Locking | DARM demod phase |
Quote: |
There's actually code in place in the LSC to dynamically adjust the demod phase for AS1. I've never made much use of it, because it's possible to get around the problem with some gain tweaking if you start at the right phase, or because I did the DC readout handoff earlier.
Attached is a cartoon showing how the demod phase at the dark port changes as the CARM offset is decreased. |
The cartoon is very nice.
I actually changed the demod phase continuously as the CARM offset was reduced to get up to arm power = 70.
As the CARM offset is changed, not only the DARM signal gain but also the phase margin around 100Hz changes if you use a fixed demodulation phase.
So it was necessary to change the demodulation phase to keep the DARM loop stable. |
1518
|
Fri Apr 24 16:24:25 2009 |
rob | Omnistructure | VAC | Paschen |
In response to Steve's elog entry, and for 40m posterity, I provide the Paschen Curve. |
Attachment 1: paschens.png
|
|
Attachment 2: paschenplot.m
|
% Paschen Curve plotting
% From http://home.earthlink.net/~jimlux/hv/paschen.htm
% Breakdown voltage:
% Vbreakdown = B * p * d / (C + ln( p * d))
%
% Breakdown field strength:
% Ebreakdown = p * ( B / ( C + ln ( p * d)))
%
... 38 more lines ...
|
1517
|
Fri Apr 24 16:02:31 2009 |
steve | HowTo | VAC | cryo pump interlock rule |
I tested the cryopump interlock today. It is touchy. I do not have full confidence in it.
I'm proposing that VC1 gate valve should be kept closed while nobody is working in the 40m lab.
How to open gate valve:
1, confirm temp of 12K on the gauge at the bottom of the cryopump
2, if medm screen cryo reads OFF( meaning warm) hit reset will result reading ON (meaning cold 12K )
3, open VC1 gate valve if P1 is not higher than 20 mTorr
VC1 was closed at 18:25,
IFO condition: not pumped,
expected leak plus out gassing should be less than 5 mTorr/day
The RGA is in bg-mode, annuloses are closed off |
Attachment 1: cryo.png
|
|
1516
|
Fri Apr 24 11:34:32 2009 |
rob | Update | Locking | DARM demod phase |
Quote: |
Quote: | Tonight, I was able to go up to arm power = 40 by tweaking the DARM demodulation phase.
I think the DARM loop became unstable because the demodulation phase was not right and the error signal contained some junk from I-phase.
I did not do any sophisticated demodulation phase optimization. Rather I just tweaked the phase so that the dark port image becomes stable.
I will do more careful demodulation phase tuning next time. |
In the next try, I was actually able to go up to arm power = 70 stably.
At this power level we are ready for the RF CARM hand off. |
There's actually code in place in the LSC to dynamically adjust the demod phase for AS1. I've never made much use of it, because it's possible to get around the problem with some gain tweaking if you start at the right phase, or because I did the DC readout handoff earlier.
Attached is a cartoon showing how the demod phase at the dark port changes as the CARM offset is decreased. |
Attachment 1: darm_phase_rotate.png
|
|
1515
|
Fri Apr 24 04:38:49 2009 |
Yoichi | Update | Locking | DARM demod phase |
Quote: | Tonight, I was able to go up to arm power = 40 by tweaking the DARM demodulation phase.
I think the DARM loop became unstable because the demodulation phase was not right and the error signal contained some junk from I-phase.
I did not do any sophisticated demodulation phase optimization. Rather I just tweaked the phase so that the dark port image becomes stable.
I will do more careful demodulation phase tuning next time. |
In the next try, I was actually able to go up to arm power = 70 stably.
At this power level we are ready for the RF CARM hand off. |
1514
|
Fri Apr 24 03:57:30 2009 |
Yoichi | Update | Locking | DARM demod phase |
Tonight, I was able to go up to arm power = 40 by tweaking the DARM demodulation phase.
I think the DARM loop became unstable because the demodulation phase was not right and the error signal contained some junk from I-phase.
I did not do any sophisticated demodulation phase optimization. Rather I just tweaked the phase so that the dark port image becomes stable.
I will do more careful demodulation phase tuning next time. |
1513
|
Thu Apr 23 21:13:37 2009 |
Yoichi | Summary | Environment | Mag. 4 earthquake in LA tripped the watchdogs of the most optics |
So far, no damage is noticeable.
restoreWatchdog script was useful 
-------------------------------------------------------
Magnitude 4.0
Date-Time * Friday, April 24, 2009 at 03:27:50 UTC
* Thursday, April 23, 2009 at 08:27:50 PM at epicenter
Location 33.910°N, 117.767°W
Depth 0 km (~0 mile) (poorly constrained)
Region GREATER LOS ANGELES AREA, CALIFORNIA
-------------------------------------------------------
|
1512
|
Thu Apr 23 18:09:11 2009 |
Yoichi | Update | Environment | Effect of cryopump |
The attached is the trend plot of the MC1 accelerometer for 3 days.
It is evident that the seismic level increased by a factor of two on Wednesday morning (when Steve started the cryopump). |
Attachment 1: SeisTrend.pdf
|
|
1511
|
Thu Apr 23 16:38:33 2009 |
steve | Update | VAC | vac valve relay box is shorting |
Ben and I found this vacuum valve relay box intermittently shorthing yesterday.
It effects V4, V5, VA6 and VM1........ Please do not touch this box under the beam pipe next to the vac rack!
The function of this box to send 120VAC to the vacuum valve to move. |
Attachment 1: vacrel.png
|
|
1510
|
Thu Apr 23 16:35:23 2009 |
Yoichi | Summary | Computer Scripts / Programs | restoreWatchdog script |
When the IFO loses lock during the lock acquisition steps, it often kicks the MC2 (through the CM servo) and trips the watchdog.
I wrote a script to restore the tripped watchdog (/cvs/cds/caltech/scripts/SUS/restoreWatchdog).
The script takes the name of a mirror (such as MC2) as an argument.
It will enable the coils and temporarily increase the watchdog threshold to a value higher than the current OSEM RMS signals.
Then it will bring the watchdog back to the normal state and wait for the mirror to be damped. After the mirror is damped enough, the
watchdog threshold will be restored to the original value.
The script will do nothing if the watchdog is not tripped.
I put this script in the drdown_bang so that the MC2 watchdog will be automatically restored when a lock loss kicks out the MC2. |
1509
|
Thu Apr 23 16:27:24 2009 |
Yoichi | Update | Locking | Locking with the cryo-pump |
The last night, the IFO was unstabler than usual and the locking script often failed before reaching the power up stage.
The failure happened at random points.
I'm not sure if this is related to the operation of the cryo-pump.
The mode cleaner reflection image seemed to move around more than usual. Maybe it was just a high seismic night.
|
1508
|
Thu Apr 23 13:55:43 2009 |
josephb, peter | Update | Computers | RCG example |
We successfully compiled and installed the Real time Code Generator "Hello World" example (which is a skeleton for the ETMX suspension controller) on megatron. In order to get it to compile, we had to add a flag indicating the computer is stand alone, and not using a myrinet card at the moment. This was done by adding the shmem_daq = 1 flag to the cdsParameters module. The symptom was it was unable to find gm.h (and there is no installed /opt/gm directory).
It is called "sam". It was installed to /cvs/cds/caltech/target/sam, and produced medm screens in /cvs/cds/caltech/medm/c1/sam. As nothing points to these, I figure it won't harm any of the current configuration, but lets us play around a bit. If by some strange reason, these do cause problems, feel free to remove them. |
1507
|
Wed Apr 22 11:16:26 2009 |
steve | Configuration | VAC | Cryo pump is ON and the Maglev is dead |
The CRYO pump cooled down and VC1 was opened. This valve configuration is Cryo-only
PSL output shutter opened at 4pm
PZT HV power supplies turned on for OMC and IOO steering mirrors.
There positions were not corrected to strain gauge values.
Ben helped us to conclude that the FAILURE led indicator is working correctly and
has nothing to do with the one lose, dangling wire#258 in the side connects of the vac rack.
I reset the CSB switch inside the Maglev controller and tried to start accelerating.
It fails after 2-3 sec and failure led light comes on.
Now we can say the MAGLEV 360 is DEAD and the new OSAKA TG420M can be swapped in.
However it requires new interface with our epics based MEDM or better...?
|
Attachment 1: cryoOn.jpg
|
|
1506
|
Tue Apr 21 18:18:27 2009 |
steve | Update | VAC | maglev failed |
Our Osaka TG360MB maglev failed with CSB error message. This means that the dry emergency landing bearing has to be replaced.
I will consalt with Osaka about the choice of replacing bearing or installing new spare tomorrow.
Mean while V1 is closed and the vac envelope is not pumped.
Valve configuration: BG -background, pumping on the RGA-only
High voltage to IOO PZT steering mirrors and OMC are turned off.
PSL output shutter is closed and manual block is in place.
I will start cooling the CYO pump in the morning, so the IFO will be pumped by noon.
Outgassing plus leakrate after 10 hrs the pressure is 2.3 mTorr
This rate of rise is normal and it is safe to work with the ifo.
|
Attachment 1: nopumping10h.jpg
|
|
1505
|
Mon Apr 20 23:27:59 2009 |
rana | Summary | VAC | c1vac2 rebooted: non-functional for several months |
We found several problems with the framebuilder tonight. The first symptom was that it was totally out of
disk space. The latest daqd log file had gone up to 500 MB and filled the space. The log file was full of
a lot of requests from my seisBLRMS.m code, but what was really making it so big was that it couldn't
connect to c1vac2 (aka scipe4) to make connections for some channels.
We looked into the daqd log files and this has been going on since at least December. There were several
'whited out' records for TP2 and TP3 in the Vacuum overview as well as the Checklist screen! Why did no
one notice this and fix it?? WE cannot function if we just ignore any non-functioning displays and say
"Oh, that never worked."
For sure, we know that it was working in 2005. Jay and Steve and Alan looked at it.
Today it was responding to ping and telnet, but not allowing any new connections. I hit the RESET button
on it. Several lights went RED and then it came back up. The readbacks on the EPICS screens are OK too.
I went into fb0 and deleted many of the GB size log files from the past several months. There is now
19GB free out of its local 33GB disk. |
1504
|
Mon Apr 20 20:45:25 2009 |
rana | Configuration | General | SVN: project area added |
I added the /cvs/cds/project/ directory to the SVN. I've noticed that we've been using target/ for code which is not
being targeted for any IOCs. This is out of line with the intention of separating real time FE code from just regular
code that we use for diagnostics or otherwise.
So please move all of your non-FE code over to project from target. And if you didn't have it in SVN at all, you
should experience level 3 shame and then import it. |
1503
|
Mon Apr 20 20:00:44 2009 |
rana | Configuration | IOO | McWFS gains re-allocated |
Since it looks like the night time people have been running with a WFS gain of 0.05 and I like the slider
to be at 1.0, I lowered all of the WFS1/2_P/Y gains by 10 and increased the overall slider from 0.05 to 1.0.
So the loop gains are now 2x higher; with it like this I guess the UGFs are in the ~0.2-0.5 Hz range. |
1502
|
Mon Apr 20 19:51:51 2009 |
Jenne | Configuration | PSL | PMC has new Level 13 Mixer installed |
The new Level 13 mixer on the PMC servo board is installed (minicircuits SRA-3MH). Since the RF output of the LO board was ~16dBm, I put a 3dB attenuator between the LO board and the LO input on the servo board. Since the previous cable was *just* the right length, this required adding a tiny bit of cable. I found a very short cable, which worked out nicely, and didin't leave bunches of extra cable between the two boards. One of these days if I have time (i.e. if it is necessary), I'll make a new cable for this purpose, so that we don't have 2 cables daisy-chained.
A note on the Mixer-replacement: The mixer on the PMC servo board is soldered in a set of 8 through-holes, not stuck in a socket. So I had to desolder the old Level 23 Mixer (minicircuits RAY-3) which was a total pain. Unfortunately, in this process, I lifted one of the pads off the back side of the board. Once the old mixer was removed, it became clear that the pin for the pad I had lifted was shorted via a trace on the front side of the board to the pin directly across from it. So when installing the new mixer, I did my best to get some solder into the through-hole for the lifted-pad-pin, and then tied it using a jumper wire to the pin that it's shorted to on the front of the board. You can't see the trace that shorts the two pins because it's underneath the mixer, when the mixer is installed. (Sidenote: after talking with Rana, this should be okie-dokie, especially if these are ground pins).
The PMC and MC locked nice and happily after I replaced the board and turned all the HV supplies back on, so I call this a success!
I also measured the OLG of the PMC servo after today's adventures in mixer-land. I get a UGF of 1.4kHz, with 66 degrees of phase margin. The method for this is in elog 924.
I checked the phase slider setting of the PMC phase screen by putting 30kHz at 100mV into the Ext DC input of the servo board, and looking at the 30kHz peak output of the Mixer Out. I fiddled with the phase slider, and chose the value for which the 30kHz peak was maximized. The phase slider is now set to 5.0V. |
Attachment 1: PMColg20Apr2009.png
|
|
1501
|
Mon Apr 20 18:36:37 2009 |
rana | Update | Cameras | Mafalda may need an update |
Sadly, the sensoray crap doesn't seem to build on CentOS. I too would prefer a homogenous solution,
but I don't know how to make this happen without punishing Joe with sensoray driver development on CentOS. |
1500
|
Mon Apr 20 18:17:44 2009 |
rob | Summary | Locking | CARM offset/Power rubric |
Plotted assuming the average arm power goes up to ~80. No DARM offset. |
Attachment 1: ARMpowersCARM.png
|
|
1499
|
Mon Apr 20 11:57:27 2009 |
rob | Update | Cameras | Mafalda may need an update |
Quote: |
I tried installing libusb-dev on mafalda in order to try getting the usb frame grabber to work on it, but could not as it could not download the package.
I then tried to do a sudo apt-get update, which failed completely, as the repository seems to have ceased existing. Basically I had all 404 Not Found errors.
Turns out Mafalda is still running Ubuntu 7.04, whose support ended late 2008. So there's a couple things that can be done:
1) Ignore it, and simply not update Mafalda anymore. This also means some newer software and hardware simply won't work with it (like the usb frame grabber)
2) Try to find another, unofficial repository which still has all of the Ubuntu 7.04 packages.
3) Upgrade to a newer, still supported Ubuntu, such as 7.10, 8.04, or 8.10.
I'd personally lean towards the 3rd option, and go to the 8.04 long term support version. If people agree with it, I could do the upgrade sometime Monday or Tuesday.
|
I don't see a reason to proliferate operating systems. Is there any reason we actually need Ubuntu? Can we put CentOS on it? |
1498
|
Mon Apr 20 05:18:42 2009 |
Yoichi | Configuration | Locking | FM6 and FM10 of LSC-MC were restored |
During tonight's locking work, I realized that FM6 and FM10 (both resonant gains around 20Hz) were actually activated by cm_step.
So I restored those filters from the svn history.
Instead, I removed a bunch of unused filters from LSC-DEMOD and LSC-DEMOD_A (moving zero filters) to off load c1lsc.
As for the locking itself, the DARM loop becomes unstable at around arm power = 30. I may have to add a filter to give a broader phase bubble. |
1497
|
Sun Apr 19 11:51:05 2009 |
josephb | Update | Cameras | Mafalda may need an update |
I tried installing libusb-dev on mafalda in order to try getting the usb frame grabber to work on it, but could not as it could not download the package.
I then tried to do a sudo apt-get update, which failed completely, as the repository seems to have ceased existing. Basically I had all 404 Not Found errors.
Turns out Mafalda is still running Ubuntu 7.04, whose support ended late 2008. So there's a couple things that can be done:
1) Ignore it, and simply not update Mafalda anymore. This also means some newer software and hardware simply won't work with it (like the usb frame grabber)
2) Try to find another, unofficial repository which still has all of the Ubuntu 7.04 packages.
3) Upgrade to a newer, still supported Ubuntu, such as 7.10, 8.04, or 8.10.
I'd personally lean towards the 3rd option, and go to the 8.04 long term support version. If people agree with it, I could do the upgrade sometime Monday or Tuesday.
|
1496
|
Sun Apr 19 11:34:33 2009 |
josephb | HowTo | Cameras | USB Frame Grabber - How to |
To use the Sensoray 2250 USB frame grabber:
Ensure you have the following packages installed: build-essential, libusb-dev
Download the Linux manual and linux SDK from the Sensoray website at:
http://www.sensoray.com/products/2250data.htm
Go to the Software and Manual tab near the bottom to find the links. The software can also be found on the 40m computers at /cvs/cds/caltech/users/josephb/sensoray/
The files are Manual2250LinuxV120.pdf and s2250_v120.tar.gz
Run the following commands in the directory where you have the files.
tar -xvf s2250_v120.tar.gz
cd s2250_v120
make
cd ezloader
make
sudo make modules_install
cd ..
At this point plug in the 2250 frame grabber.
sudo modprobe s2250_ezloader
Now you can run the demo with
./sraydemo or ./sraydemo64
Options will show up on screen. A simple set to start with is "encode 0", which sets the recording type, "recvid test.mpg", which starts the recording in file test.mpg, and "stop", which stops recording. Note there is no on screen playback. One needs an installed mpeg player to view the saved file, such as Totem (which can screen cap to .png format) or mplayer.
All these instructions are on the first few pages of the Manual2250LinuxV120 pdf.
|
1495
|
Sun Apr 19 03:34:05 2009 |
Yoichi | Update | Locking | Saturday night lock |
Tonight I was able to go up to arm power = 33, by mainly tweaking the DARM gain. A small progress.
In order to give more phase margin to the CARM MC_L path, I added a 300:100 filter to C1:LSC-MC.
To reduce the load to the lsc computer I deleted several filters from the filter bank, which were not used in the locking scripts.
Before I deleted the filters, I checked in the current chans directory into the svn repository.
If you want to restore the deleted filters, go back to the revision 36142. |
1494
|
Fri Apr 17 11:37:32 2009 |
Yoichi | Configuration | Computer Scripts / Programs | AutoDTT |
In order to get test point data with AutoDTT, you have to pre-trigger test points you want to use.
This is done by starting a DTT measurement with necessary test points for a few second, then stop it but keep the DTT opened.
I made prepTP script which does this job.
It takes a file name of an XML file, which should include a DTT measurement setup with test point channels you want to open and the trigger time set to "now".
The script will open an xterm and run diag with the XML file. Unlike restoreRunSave script, it does not save the result nor quit diag. Therefore, you can keep the test points as long as you keep the xterm opened. You can manually exit the diag (Ctrl-D) when you no longer need the test points.
watchLockLoss script now calls prepTP at the beginning. Therefore, you have to be able to open an xterm. If you run the script through SSH, make sure that you give -X option to ssh. |
1493
|
Fri Apr 17 11:05:22 2009 |
Yoichi | Update | Locking | Thursday night locking status |
The last night, it was sort of robust to go up until arm power = 26.
The REFL_DC gain seems to change a lot around this region. So I did fine adjustments of the gain with small incremental steps of the arm power.
This work will continue.
The AutoDTT shows that the lock loss happens with an oscillation of CARM at around 100Hz. This indicates that the cross-over is the culprit.
I was also able to increase the CM UGF up to 10kHz. |
1492
|
Thu Apr 16 17:48:00 2009 |
Yoichi | Configuration | Computer Scripts / Programs | AutoDTT |
As Peter mentioned in his entry on the last night's locking, I imported AutoDTT from Hanford.
It resides in /cvs/cds/caltech/scripts/AutoDTT/.
The main script is restoreRunSave, which takes three arguments, templete_file_name, result_file_name and log_file_name.
This script opens a template xml file and execute it. Then saves the result in the result file.
You can open the result file in a normal DTT.
You can call restoreRunSave from watch scripts, such as c1_watch_dr_bang.
watchLockLoss is a standalone watch script to detect a lock loss and call restoreRunSave.
It runs both on Linux and Solaris. However on Linux, diag fails 50% of the time with some glibc error.
So it is probably better to run it on op440m. |
1491
|
Thu Apr 16 17:19:44 2009 |
Alberto | Update | Auxiliary locking | the zipper |
Quote: |
It takes 18 months to double the computational power of microprocessors but it took man thousands of years to invent the zipper. I never really understood that till these days.
Here is a sample of my latest results from Optickle simulations of the locking signal for the Power Recycling Cavity.
Thanks also to Rob's revolutionary bidimensional rotating matrix idea (I can see entire books of linear algebra going to be rewritten now because of that) I could find the way to determine the optimal demodulation phases for the demod signals.
There were also an other couple of missing details. But that came easily along.
The parfor function for the parallel computation in Matlab sped up some loops by a factor of 100.
In these particular plots there's still no CARM offset scan. That's what I'm going to post next on the elog, together with the signals for the other degrees of freedom.
|
Just to show that I'm confident I'm getting reasonable results, I'll post two PRC scans for different CARM. One set of plots is for the current 40m with -19.78 deg of SRM detuning phase, the other is for the Old Upgrade (9 Mhz vs the 11 currently planned) with no detuning phase.
I'm going to put together the results and get some conclusion about the 3f locking scheme for the current 40m and the upgrade. |
Attachment 1: 04_3f_Current_40m_plots.pdf
|
|
Attachment 2: 11_3f_40mUpgrade_plots.pdf
|
|
1490
|
Thu Apr 16 16:37:42 2009 |
Alberto | Update | Auxiliary locking | the zipper |
It takes 18 months to double the computational power of microprocessors but it took man thousands of years to invent the zipper. I never really understood that till these days.
Here is a sample of my latest results from Optickle simulations of the locking signal for the Power Recycling Cavity.
Thanks also to Rob's revolutionary bidimensional rotating matrix idea (I can see entire books of linear algebra going to be rewritten now because of that) I could find the way to determine the optimal demodulation phases for the demod signals.
There were also an other couple of missing details. But that came easily along.
The parfor function for the parallel computation in Matlab sped up some loops by a factor of 100.
In these particular plots there's still no CARM offset scan. That's what I'm going to post next on the elog, together with the signals for the other degrees of freedom. |
Attachment 1: 19_3f_Current_40m_plots_SUCCESS.pdf
|
|
1489
|
Thu Apr 16 16:26:57 2009 |
pete | Update | Locking | Wed. night locking |
yoichi, pete
We installed the watchLockLoss script in scripts/AutoDTT/. This script monitors arm power and uses command line
DTT to save 5 s snapshot of the interferometer when it senses loss of lock. We ran it on linux and it seemed to
save an xml file about half the time; we'll try it on solaris.
I managed to get up to arm power of about 20 a couple of times. IFO lost lock a couple of times after turning
off moving zero. MC2 would often get tripped by lock loss and need resetting. Maybe we will try to stiffen the
op levs. |
1488
|
Thu Apr 16 11:17:56 2009 |
Jenne | Update | PSL | Edited c1psl.db to calibrate PMC's LO mon |
Quote: |
I edited c1psl.db to include the following:
grecord(calc, "C1:PSL-PMC_LOCALC")
{
field(INPB,"C1:PSL-PMC_LODET")
field(SCAN,".1 second")
field(PREC,"4")
field(CALC,".955*LOGE(B)-17.11")
}
|
As it turns out, I apparently can't tell X from Y when fitting a function in a rush. The real calibration stuff which is now in c1psl.db is:
grecord(calc, "C1:PSL-PMC_LOCALC")
{
field(INPB,"C1:PSL-PMC_LODET")
field(SCAN,".1 second")
field(PREC,"4")
field(CALC,"1.004*LOGE(B)+17.76")
}
I restarted c1psl (again, had to go hit the physical reset button since it didn't come back after a telnet-reboot) to have it take in the changes. The psl.db file that was in place before yesterday (before I touched it) is saved as psl.db.15Apr2009 just in case.
I edited the PMC EPICS screen to have the LO mon look at C1:PSL-PMC_LOCALC, which is the calibrated channel in dBm. I also stuck a little label on the screen saying what units it's in, because everyone likes to know what units they're looking at.
|
1487
|
Wed Apr 15 17:11:37 2009 |
Jenne | Update | PSL | Edited c1psl.db to calibrate PMC's LO mon |
Following the method in Peter's Elog,
I edited c1psl.db to include the following:
grecord(calc, "C1:PSL-PMC_LOCALC")
{
field(INPB,"C1:PSL-PMC_LODET")
field(SCAN,".1 second")
field(PREC,"4")
field(CALC,".955*LOGE(B)-17.11")
}
I restarted c1psl (had to go hit the physical reset button since it didn't come back after telnet-ing and "reboot"ing) to make this take effect.
Next step is to tell the PMC screen to look at this _LOCALC rather than _LODET, and the screen will be calibrated into dBm.
Right now, the screen is as it always has been, because after relooking at the calibration, I no longer believe it. This calibration claimes -19dBm for an LOmon value of 0.1200, when I actually measured +16dBm for this LOmon value. So I've screwed something up in doing my MatLAB calibration. I'll fix it tomorrow, and put in the correct calibration before I change the PMC screen.
RefCav, PMC, MC are all back and locked after my shenanigans. |
1486
|
Wed Apr 15 11:25:21 2009 |
steve | Configuration | VAC | RGA cal completed |
Quote: |
Vacuum normal valve condition was changed to accommodate SRS-RGA calibration.
The annulus valves were closed to free TP3 to pump on the RGA
VM1 was closed to isolate the RGA from the IFO.
VM3 opened to TP3.
This condition is called back ground (BG) mode. It is where we can calibrate and see the RGA background without the IFO.
|
Vacuum valve configuration is back to VACUUM NORMAL condition. RGA calibration completed.
RGA scan attached is the backgroud of the rga with std cal leak open, sn 08581
Krypton at amu 84 and Argon at amu 40 are the cal signals.
|
Attachment 1: rga-090415-bg-d7-cald2.png
|
|
1485
|
Wed Apr 15 03:52:27 2009 |
rana | Update | DMF | NDS client32 updated for DMF |
Since our seisBLRMS.m complains about 'can't find hostname' after a few hours, even though matlab is able to ping fb40m,
I have recompiled the NDS mex client for 32-bit linux on mafalda and stuck it into the nds_mexs/ directory. This time I
compiled using the 'gcc' compiler instead of the 'ANSI C' compiler that is recommended in the README (which, I notice,
is now missing from Ben Johnsons web page!). Let's see how long this runs.
|
1484
|
Wed Apr 15 02:20:46 2009 |
rana, yoichi | Update | DMF | DMF now working copy |
We found that DMF/ was not an SVN working copy, so I wiped out the SVN version, imported the on-disk copy, moved it to DMFold/ and then checked out the SVN version.
We can delete DMFold/ whenever we are happy with the SVN copy. |
1483
|
Wed Apr 15 02:18:42 2009 |
rana | Configuration | Computers | nodus vfstab changed for rigel |
nodus was hanging because it was trying to mount the cit40m account from rigel and rigel was not responding.
Neither I nor Yoichi can recall what the cit40m account does for us on nodus anymore and so I commented it out of the nodus /etc/vfstab.
nodus may still need a boot to make it pay attention. I was unable to do a 'umount' to get rid of the rigel parasite. But mainly I don't want anything in
the 40m to depend on the LIGO GC system if at all possible. |
1482
|
Tue Apr 14 17:20:36 2009 |
Yoichi | Update | Computer Scripts / Programs | Parallel Optickle |
I wrote a parallel version of tickle() function for Optickle.
The attached ptickle.m, which provides ptickle() command, can be used as a drop-in replacement of tickle() command.
Just download it and place it in the @Optickle directory.
This command will run multiple instances of Matlab to calculate the frequency responses in parallel.
The speed gain is roughly proportional to the number of CPU cores you use.
To use multiple cores, you have to run matlabpool() command first. See the comment at the beginning of ptickle.m for more detail.
The progress bar is disabled at this moment because it is not clear for me how to make a single progress bar from multiple instances of Matlab.
I sent the code to Matt, so this may be included in the next release of Optickle. |
Attachment 1: ptickle.m
|
% Compute DC fields, and DC signals, and AC transfer functions
%
% This is a parallelized version of tickle. You have to run matlabpool(n)
% command before using this command. matlabpool(n) will invoke n instances
% of matlab workers in your computer. Once you have started those workers,
% you can reuse them many times (i.e. you don't have to run matlabpoo(n)
% every time you use ptickle). Usually n should be equal to the number of
% CPU cores in your computer, but the Matlab parallel computing toolbox has
% the limit of maximum 4 workers for a local computer. If you use a cluster
% of computers across a network, this limit does not apply. But I haven't
... 393 more lines ...
|