After fixing the PRM tonight, all of the oplevs look okay.
.....except ITMX, which looks like it's power dropped significantly after the CDS upgrade. To be investigated tomorrow.
I had a look-see at ITMX's oplev. I can't see any clipping, so maybe the power is just low? One thing that was funny though is the beam coming directly from the laser. There is the main, regular beam, and then there is a thin horizontal line of red light also coming straight out of the laser. I don't know what to do about that, except perhaps put an iris right after the HeNe, to block the horizontal part? I'm not sure that it's doing anything bad to the optic though, since the horizontal part gets clipped by other optics before the beam enters the vacuum, so there is no real irregularity on the beam incident on the QPD.
I realigned the oplev on the QPD, using last night's ITMX alignment + whatever drift it picked up over night, so it may need re-recentering after Xarm is nicely aligned.
While walking past the PSL, I noticed that the PSL's doubling oven's heater was still disabled from the power outage. As with the ETMY heater, I hit the Enable button, and it started warming up (according to the front panel at least).
I'm still not super happy with the low power level of the ETMX oplev, so I went to investigate.
This is a 3-year plot. The first ~year in the plot, the oplev sum is ~15000 cts, and in the most recent year, it's ~1000 cts. A new HeNe was installed in May 2011 (elog 4686), with an output of 2.6mW, after the old one had died. When the new one was installed, Steve said that it was giving ~1400 counts, so maybe 1000 isn't too, too embarrassing. There is, however, a lens on the injection side, which is AR coated for 1064. The power before this lens (measured with the Ophir, set to 632nm) was ~2.6mW. The power after this lens was ~1.5mW. Now THAT is embarrassing. I'm adding replacing that lens to the to-do list (elog 6595), although I don't want to do it until such a time (maybe in an hour, maybe in a few days?) when I've got the Xarm locked / aligned, so I can nicely re-center the oplev. UPDATE: The lens is a KBC 037 (-100) lens, and the sticker on the lens mount says coated for 1064. We don't have any KBC037's in the visible lens kits, so we need to get one before I can do this replacement (PURCHASED 10pm).
There is an elog (elog 5004) from July 2011, which mentions that these channels have not been saved for a long time, so that's why there's the year-long gap.
Since Den wasn't able to fix c1sus (make it talk to the framebuilder) before he left a few hours ago, I decided to do some housekeeping rather than actual locking.
I wrote new save / misalign / restore scripts for all of the suspended optics on the C1IFO_ALIGN screen. Adding save / restore versions for the mode cleaner optics should be quick and easy. Now when you use the ! button for each optic, it points you to the new scripts. I still have the burt capabilities there, but the restore script has the burt-restore line commented out.
SAVE: burt-save the PIT_COMM and YAW_COMM values, as well as write those values and the date to a text file.
MISALIGN: Turn off oplevs, move 100 steps of 0.01 in the "+" direction.
RESTORE: Move ~100 steps toward the saved value, until you're within 0.001 of the saved value (step size is "saved val" minus "current val" divided by 100). Then just write the saved value to the slider (otherwise if the slider were touched between the last "save" and the restore, we might not be able to step precisely to the value we want). Turn oplevs back on.
Scripts are in the same place the old ones used to live: ...../caltech/c1/medm/c1ifo/cmd/ New scripts are C1IFO_OPTIC(save/restore/misalign)_soft.cmd
I'm checking this one off of the to-do list.
Good things: (a) I remembered / re-learned / just plain learned a lot about scripting. (b) the optics are now walked slowly over to their misaligned state, and slowly walked back. The past regime had the optics suddenly kicked over by a lot, sometimes enough to trip / come close to tripping watchdogs, which was never good.
Bad things: it took a long time. Now it's bedtime.
We officially are *failures* at svn-ing our scripts and screens. This is NOT OKAY. I checked in a few things, since there were already folders on the svn, but many things don't have folders created. It's a hot mess. We need to get our shit together, and become as disciplined about MEDM and scripts as we have been (under Jamie's watchful eye) of the simulink models.
I'm not going to start fixing it all right now. It might not even happen at this point until after GWADW, but it needs to happen.
Rana theorized that we're having problems with the MC error signal in the OAF model (separate elog by Den to follow) because we've named a channel "C1:IOO-MC_F", and such a channel already used to exist. So, Rana and I went out to do some brief cable tracing.
MC Servo Board has 3 outputs that are interesting: "DAQ OUT" which is a 4-pin LEMO, "SERVO OUT" which is a 2-pin LEMO, and "OUT1", which is a BNC->2pin LEMO right now.
DAQ OUT should have the actal MC_F signal, which goes through to the laser's PZT. This is the signal that we want to be using for the OAF model.
SERVO OUT should be a copy of this actual MC_F signal going to the laser's PZT. This is also acceptable for use with the OAF model.
OUT1 is a monitor of the slow(er) MC_L signal, which used to be fed back to the MC2 suspension. We want to keep this naming convention, in case we ever decide to go back and feed back to the suspensions for freq. stabilization.
Right now, OUT1 is going to the first channel of ADC0 on c1ioo. SERVOout is going to the 7th channel on ADC0. DAQout is going to the ~12th channel of ADC1 on c1ioo. OUT1 and SERVOout both go to the 2-pin LEMO whitening board, which goes to some new aLIGO-style ADC breakout boards with ribbon cables, which then goes to ADC0. DAQout goes to the 4pin LEMO ADC breakout, (J7 connector) which then directly goes to ADC1 on c1ioo.
So, to sum up, OUT1 should be "adc0_0" in the simulink model, SERVOout should be "adc0_6" on the simulink model, and DAQout should be "adc1_12" (or something....I always get mixed up with the channel counting on 4pin ADC breakout / AA boards).
In the current simulink setup, OUT1 (adc0_0) is given the channel name C1:IOO-MC_F, and is fed to the OAF model. We need to change it to C1:IOO-MC_L to be consistent with the old regime.
In the current simulink setup, SERVOout (adc0_6) is given the channel name C1:IOO-MC_SERVO. It should be called C1:IOO-MC_F, and should go to the OAF model.
In the current simulink setup,DAQout (~adc1_12) doesn't go anywhere. It's completely not in the system. Since the cable in the back of this AA / ADC breakout board box goes directly to the c1ioo I/O chassis, I don't think we have a degenerate MC_F naming situation. We've incorrectly labeled MC_L as MC_F, but we don't currently have 2 signals both called MC_F.
Okay, that doesn't explain precisely why we see funny business with the OAF model's version of MCL, but I think it goes in the direction of ruling out a degenerate MC_F name.
Problem: If you look at the screen cap, both simulink models are running on the same computer (c1ioo), so when they both refer to ADC0, they're really referring to the same physical card. Both of these models have adc0_6 defined, but they're defined as completely different things. Since we can trace / see the cable going from the MC Servo Board to the whitening card, I think the MC_SERVO definition is correct. Which means that this Green_PH_ADC is not really what it claims to be. I'm not sure what this channel is used for, but I think we should be very cautious and look into this before doing any more green locking. It would be dumb to fail because we're using the wrong signals.
Den noticed this, and will write more later, I just wanted to sum up what Alex said / did while he was here a few minutes ago....
Errors are probably really happening.... c1oaf computer status 4-bit thing: GRGG. The Red bit is indicating receiving errors. Probably the oaf model is doing a sample-and-hold thing, sampling every time (~1 or 2 times per sec) it gets a successful receive, and then holding that value until it gets another successful receive.
Den is adding EPICS channels to record the ERR out of the PCIE dolphin memory CDS_PART, so that we can see what the error is, not just that one happened.
Alex restarted oaf model: sudo rmmod c1oaf.ko, sudo insmod c1oaf.ko . Clicked "diag reset" on oaf cds screen several times, nothing changed. Restarted c1oaf again, same rmmod, insmod commands.
Den, Alex and I went into the IFO room, and looked at the LSC computer, SUS computer, SUS I/O chassis, LSC I/O chassis and the dolphin switch that is on the back of the rack, behind the SUS IO chassis. All were blinking happily, none showed symptoms of errors.
Alex restarted the IOP process: sudo rmmod c1x04, sudo insmod c1x04. Chans on dataviewer still bad, so this didn't help, i.e. it wasn't just a synchronization problem. oaf status: RRGG. lsc status: RGGG. ass status: RGGG.
sudo insmod c1lsc.ko, sudo insmod c1ass.ko, sudo insmod c1oaf.ko . oaf status: GRGG. lsc status: GGGG. ass status: GGGG. This means probably lsc needs to send something to oaf, so that works now that lsc is restarted, although oaf still not receiving happily.
Alex left to go talk to Rolf again, because he's still confused.
Comment, while writing elog later: c1rfm status is RRRG, c1sus status is RRGG, c1oaf status is GRGG, both c1scy and c1scx are RGRG. All others are GGGG.
Upgrades suck. Or at least making everything work again after the upgrade.
On the to-do list tonight: look at OSEM sensor and OpLev spectra for PRM, when PRMI is locked and unlocked. Goal is to see if the PRM is really moving wildly ("crazy" as Kiwamu always described it) when it's nicely aligned and PRMI is locked, or if it's an artifact of lever arm between PRM and the cameras (REFL and AS).
However, I can't get signals on DTT. So far I've checked a bunch of signals for SUS-PRM, and they all either (a) are just digital 0 or (b) are ADC noise. Lame.
Steve's elog 5630 shows what reasonable OpLev spectra should look like: exactly what you'd expect.
Attached below is a small sampling of different SUS-PRM signals. I'm going to check some other optics, other models on c1sus, etc, to see if I can narrow down where the problem is. LSC signals are fine (I checked AS55Q, for example).
UPDATE: SRM channels are same ADC noise. MC1 channels are totally fine. And Den had been looking at channels on the RFM model earlier today, which were fine.
ETMY channels - C1:SUS-ETMY_LLCOIL_IN1 and C1:SUS-ETMY_SUSPOS_IN1 both returned "unable to obtain measurement data". OSEM sensor channels and OpLev _PERROR channel were digital zeros.
ETMX channels were fine
UPDATE UPDATE: Genius me just checked the FE status screen again. It was fine ~an hour ago when I sat down to start interferometer-izing for the night, but now the SUS model and both of the ETMY computer models are having problems connecting to the fb. *sigh*
Restarted SUS model - it's now happy.
c1iscey is much less happy - neither the IOP nor the scy model are willing to talk to fb. I might give up on them after another few minutes, and wait for some daytime support, since I wanted to do DRMI stuff tonight.
Yeah, giving up now on c1iscey (Jamie....ideas are welcome). I can lock just fine, including the Yarm, I just can't save data or see data about ETMY specifically. But I can see LSC data, so I can lock, and I can now take spectra of corner optics.
A few things tonight. Locked both arms simultaneously (IR only). Locked MICH, Locked PRMI, although it doesn't like staying locked for more than a minute or so, and not always that long.
Locking PRCL was possible by getting rid of the power normalization. We need to get some triggering going on for the power norm. I think it's a good idea for after the cavity is locked, but when PRCL is not locked, POP22 is ~0, so Refl33/Pop22 is ~inf. The PRCL loop kept railing at the Limit that was set. Getting rid of the power normalization fixed this railing.
I took some spectra of PRM's oplev, while PRMI was locked, and unlocked. The PRM is definitely moving more when the cavity is locked. I'm not sure yet what to do about this, but the result was repeatable many times (~6 or 7 over an hour or so). The OpLev spectra when PRMI was locked didn't depend too strongly on the PRM's alignment, although I think that's partly because I wasn't able to really get the PRM to optimal alignment. I think POP22I is supposed to get to 7 or so...last week with Koji it was at least flashing that high. But tonight I couldn't get POP22I above 4, and most of the time it wouldn't go above 3. As I was aligning PRM and the circulating SB power increased, POP22I fluctuations increased significantly, then the cavity unlocked. So maybe this is because as I get closer, PRM gets more wiggly. I tried playing 'chicken' with it, and took spectra as I was aligning PRM (align, get some improvement, stop to take spectra, then align more, stop to take spectra....) but usually it would fall out of lock after 1-2 iterations of this incremental alignment and I'd have to start over. When it relocked, it usually wouldn't come back to the same level of POP22I, which was kind of disappointing.
In the PDF attached, pink and light blue are when the PRMI is locked, and red and dark blue are no PRCL feedback. The effect is more pronounced with Pitch, but it's there for both Pitch and Yaw.
Also, I need to relook at my new restore/misalign scripts. They were acting funny tonight, so I'm taking back my "they're awesome, use them without thinking about it" certification.
Den and Alex left things not-burt restored, and Den mentioned to me that it might need doing.
I burt restored all of our epics.snaps to the 1am today snapshot. We lost a few hours of striptool trends on the projector, but now they're back (things like the BLRMS don't work if the filters aren't engaged on the PEM model, so it makes sense).
I'm combining the IFO check-up list (elog 6595) and last week's action items list (elog 6597). I thought about making it a wiki page, but this way everyone has to at least scroll past the list ~1/week.
Feel free to cross things out as you complete them, but don't delete them. Also, if there's a WHO?? and you feel inspired, just do it!
Dither-align arm to get IR on actuation nodes, align green beam - JENNE
Arm cavity sweeps, mode scan - JENNE
ASS doesn't run on Ubuntu! or CentOS Fix it! - JENNE, JAMIE's help
Input matricies, output filters to tune SUS. check after upgrade. - JENNE
POX11 whitening is not toggling the analog whitening??? - JAMIE, JENNE, KOJI
OAF comparison plot, both online and offline, comparing static, adaptive and static+adaptive - DEN
THE FULL LIST:
cd /opt/rtcds/caltech/c1/burt/autoburt/today/ -
No leaving the OAF running until you're sure (sure-sure, not kind of sure, not pretty sure, but I've enabled guardians to make sure nothing bad can happen, and I've been sitting here watching it for 24+ hours and it is fine) that it works okay.
OAF (both adaptive and static paths) were left enabled, which was kicking MC2 a lot. Not quite enough that the watchdog tripped, but close. The LSCPOS output for MC2 was in the 10's or 100's of thousands of counts. Not okay.
This brings up the point though, which I hadn't actively thought through before, that we need an OAF watchdog. An OAF ogre? But a benevolent ogre. If the OAF gets out of control, it's output should be shut off. Eventually we can make it more sophisticated, so that it resets the adaptive filter, and lets things start over, or something.
But until we have a reliable OAF ogre, no leaving the adaptive path enabled if you're not sitting in the control room. The static path should be fine, since it can't get out of control on it's own.
Especially no leaving things like this enabled without a "I'm leaving this enabled, I'll be back in a few hours to check on it" elog!
It doesn't look all that different, but the first image didn't have that much lit up in it to begin with.
This is totally cool! You can see that the OSEM lights are almost entirely gone in the subtracted image.
Can you switch to trying with one of the *TM*F cameras? (ITMXF, ITMYF, ETMYF, ETMXF) They tend to have more background, so there should be a more dramatic subtraction. Den or Suresh should be able to lock one of the arms for you.
I just sat down in the control room, and discovered the PMC (and everything else) unlocked. I relocked the PMC, but the MC wasn't coming back. After a moment of looking around, I discovered that the WFS were on, and railing. I ran the "turn WFS off" script, and the MC came back right away, and the WFS came on as they should.
We need to relook at the WFS script, or the MC down script, to make sure that any time the MC is unlocked, no matter why it unlocked, the WFS output is off and the filter histories are cleared.
Align Ygreen beam - JENNE, YUTA
Arm cavity sweeps, mode scan - JENNE, YUTA
ASS doesn't run on Ubuntu! or CentOS Fix it! - YUTA, JENNE, JAMIE's help
Decide on plots for 40m Summary page - DEN, STEVE, JENNE, KOJI, JAMIE, YUTA, SURESH, RANA, DUNCAN from Cardiff/AEI
Look into PMC PZT drift - PZT failing? Real MC length change? - JENNE, KOJI, YUTA
...will be helpful for acquiring lock after the vent. We should install a camera at ETMX.
PMC and MC alignment are both shit, although with the WFS on, the MC is pretty good. We're leaving it for now, so that (a) we don't mess up Koji's work, and (b) we can work on the Xarm. Steve is doing Yarm oplev stuff, so we'll do Yarm later.
[Yuta, Jenne, Suresh]
We pushed on the MC SUS connectors at the back of the rack, and that helped bring MC3 back to where it should be. Then we looked at MC RFPD DC, and adjusted the optics with the WFS off, so that the refl is ~0.56. Then when we turn the WFS on, the alignment doesn't really change, so we have offloaded the WFS.
Now we're measuring the spot positions to check where the MC is. Then we'll align the arms, and align the green to the arms.
The followings are a kind of daily check. Do this without any notice:
- Align PMC.
PMC aligned. Suresh is fixing the measure MC spot positions script, then we'll remeasure MC spot positions.
The typical sign of a dying gas laser is that it glows for a few minutes only. The power supplies are fine.
Two new JDS - Uniphase 1103P lasers ( NT64-104 ) arriving on Monday, May 21
Yesterday I swapped in new He/Ne laser with output power 3.5 mW The return spot on qpd is large ~6mm in diameter and 20,500 counts
The spot size reduction require similar layout as ETMX oplev.
The oplev path is relayed and the spot size on the qpd is reduced. I still have to clean up and replace "Miki Mouse" lens holder.
Flipped the sign on the ETMY oplev servo gain, since it was wrong. (It was "-" for both, now it is "+" for both)
The ~16Hz bounce mode of some optic is showing up in the Yarm error signal.
MC is kind of 'windy' looking, so maybe it's from that? (Yuta's guess).
We need to make sure that the SUS damping and oplev paths both have notches at the correct bounce mode, not the old, old MOS frequency. If that doesn't work, may need to put a resgain in Yarm path.
Made the Bounce notch in the BounceRoll filter (ITMY OLPIT, ITMY OLYAW) wider, so it actually spans the peak we see in the error spectra. When we next lock the arm later today, I'll retake this spectra to see if the ETMY oplev fix (Koji, Yuta) and this notch fix both helped.
fix Q of Vio2 filter in SUS. - JENNE
Switch power source for beatnote PD's amplifiers from temporary power supplies under PSL table to permanent taking the power from a rack.
I was looking a little at ASS, while Yuta was doing some Green transmitted DC PD work, and I find that the output of some filters is totally insane with no deliberate input or excitation signals.
Note in the figure that the filter (which is a 2nd order butter bandpass in the C1:ASS-LOCKIN29_SIG filter bank) is ringing a lot - this needs fixing. But, more disconcertingly, sometimes (not every time) the arm flashes, the input to the filter bank gets a ~1 sample long spike that is ~9,000,000 counts. 9 million is a lot of counts. This is then making the filter go crazy.
Any ideas on how this can happen, and how we can stop / fix it? It's certainly a CDS issue, but I'm not sure where or how.
Because I keep taking a long time to search for these, since I can't remember the keywords in the different entries, here are the links:
elog 3759 : Green X end aux laser temperature setting vs. PSL laser temperature setting
elog 4439 : Green Y end aux laser temperature setting vs. PSL laser temperature setting
More words: beat note, doubling, second harmonic.
T_Xend = 8.31 + 0.9293*T_PSL
T_Yend = 6.9825 + 0.87326*T_PSL
Also, C1:GCY-SLOW_SERVO2_OFFSET was 29725 (twenty nine thousand seven hundred twenty five) cts when we sat down to start today.
C1:GCX-SLOW_SERVO2_OFFSET was 80 (eighty) cts when we sat down to start today. Why the offsets are so different, I don't know. But I was able to find the X green beatnote with this small number offset, so it is approximately correct.
I modified the lsc model (after Jamie finished) to use a new triggering scheme. It HAS NOT yet been compiled and tested, since it's way past time for us to start beatnote-ing. I will compile, test, debug, etc. tomorrow. Don't compile the LSC model tonight.
Now we also have (assuming no bugs.....) triggering capability for the filter modules in the filter banks. Yay! Testing, etc will commence tomorrow.
We tried to find the Ygreen beat note, with no success yet. We calculate from Bryan's formula that the Yend laser should be ~34.68C. But Katrin has an elog saying that she was looking around 19C. I don't know why the discrepancy, but maybe this is part of our problem? Kiwamu elog-responded that the epics output had to be high (~9V) when the temp was 19C. So maybe we need a smaller offset setting in the slow servo with the 34C temperature?
We set the "T+" on the Ygreen laser controller to 34.68C using the dial, and then tried a few large steps with the offset in the Ygreen slow servo. The idea was to see if we could swing past the beat, so we would know vaguely where it was. But we never saw a resonance on the spectrum analyzer, even with a "hold max" trace.
We confirmed that there is signal going to the SLOW input of the laser controller's front panel. Yuta watched a voltmeter while I changed the epics value, and we successfully changed the signal. However, after plugging the SLOW cable back in, we noticed that no matter what we set the epics value to, we don't see any temperature change reported on the front panel display. There is something in the manual( according to Katrin) that the "LT" display is not accurate when a cable is plugged in. But none of the display values changed. I think there is a measured temp output on the back that Bryan mentioned that we could use to see if something is really changing inside.
Anyhow, no beatnote found yet tonight. We confirmed before starting that the alignment onto the beat PD was good, so that's not the problem.
Something bad happened to c1sus and c1iscex ~20 min ago. They both have "0x2bad" 's. I restarted the daqd on the framebuilder, and then rebooted c1sus, and nothing changed. The SUS screens are all zeros (the gains seem to be set correctly, but all of the signals are 0's).
If it's not fixed when I get in tomorrow, I'll keep poking at it to make it better.
As of now, the regular LSC DoF triggers work, just as they used to. There is a problem with the filter module triggers that I haven't figured out yet.
We can't send integers (like control words for the filter banks) through Choice blocks, since those pass doubles by default. I fixed that by removing the choice block, but the triggering still isn't happening properly.
Vaguely chronological order:
Found a beat peak, thought it was puny, went to realign Ygreen at end table.
Noticed that beam out of faraday was clipping on the last lens before the steering optics. We adjusted the mirror directly before the faraday, making sure the power transmitted (measured by the Ophir) didn't go down. Now we're roughly centered on both the lens directly after the faraday, and the lens before the steering optics.
This, of course, meant that we had to completely realign the Ygreen beam to find the TEM00 resonance. We did that. Actually, this took us a really long time. We ended up putting a temporary CCD camera on the PSL table to look at the transmitted green light. This helped a lot, but the resonant modes were just totally wacky. We finally were able (after 30+ minutes, using the camera) to get to TEM01. Then Yuta adjusted ITMY a teeny bit, and green was happy to resonate. We then removed the CCD camera so that we could move on to beat stuff.
Yuta decided it's faster to sweep the PSL temp, rather than the end laser temp, since we don't have to watch that the arm maintains lock. So we set the end laser temp (T+) to 34.049C, which gave a measured temperature at the back of 34.68C (with an offset of 29425)
We then swept the SLOW adjust on the FSS screen to change the PSL temp. We went all the way, starting at 0, to +10, back to 0, then on to -10, in steps of 0.01 .
We found a puny peak at -0.96, and pretty good peak at -9.48. Height of the pretty good peak, after optimizing PSL table beat alignment was -50dBm. At this time, the PSL temp is 33.81C, while the Yend is still measured at 34.68C.
I checked the cabling, and it looks like the beat setup is still as it should be, using the old-school, non-beatbox stuff. We plugged the beat PD into the beat detection setup, removing it from the spectrum analyzer. As mentioned in my self-reminder elog, I changed the gains on the top 2 SR560's down by a factor of 2 so they weren't overloading.
We aren't really sure that we're getting any real signals into the ALS model though. C1:ALS-BEATY_COARSE_I_MON seems to be the same whether or not the arm is locked on green, therefore it seems to be the same ~500 or 600 counts whether or not there is a beat. Hmmmm. We used the offset option of the OFFSETTER2 to send an offset to the beat signal that gets sent to the ETMY. We confirmed that signals are going out to ETMY from the ALS model, but we're not sure if they are correct / non-insane signals. One symptom that we're seeing is even though we have the Yarm locked on green, and the ALS system engaged, the arm is still flashing in IR, which means the green is mostly just following the arm. We're not actually holding the arm in place.
Also, TRY and TRX are not recorded channels, so I went into the .ini file to have them acquire (uncommented them, set acquire=1, set the data rate to 2048), saved the ini file, and restarted the fb's daqd process. The new TRY_OUT_DQ channel is digital zeros, and is red in dataviewer. Also, the lsc model is no longer happily connected to the framebuilder. I then decided to try Joe's old .daqconfig script (in the scripts directory) which provides a gui for acquiring channels. Restarted the daqd process, same story. I then went back to comment out the TRY_OUT_DQ lines, set acquire=0, set data rate back to 16384. Joe's program put a bunch of spaces into the .ini file, but I don't think they do anything bad. Except that now when I restart daqd, lsc still won't connect to the framebuilder. Yuta setup pynds to save the data, if we were able to get anything useful.
We couldn't make awg, tdssine, or DTT write anything to the OFFSETTER2_EXC. This is annoying, because this is how (once we figure everything else out) we need to sweep (with a ramp or triangle) the beat signal.
Moral of the night: we learned some stuff, but ultimately failed.
Yuta is going to bring this up at the 40m meeting so it can be argued over, but we (I) want a permanent IR beat setup at the PSL table. This isn't a novel idea or anything, I just think it will save us time if we can quickly re-acquire the beat signal, so I'm bringing it up again. Eventually, as Koji suggested to me, we can make the IR beat part of a servo, so that the green beat is always within the bandwidth of the green beat PD. But for Phase 1, it's enough to just see the Ir beat on a ~1GHz PD. Suresh tells me most of the bits and pieces are around, we just have to gather them all in one place.
2 questions (so far) regarding your diagram / doc:
We are using 3 of the feed-throughs on the BS chamber, and 1 on the OMC chamber, even though we have 2 TTs on the BS table, 1 on the OMC table, and 1 on the IMC table? Just wanted to check.
Does your list / table at the bottom include all of the cables we already have, as well as the ones we need? (Or maybe we just have nothing so far, so this is a moot question).
We have too much crap in the rfm model. CPU time for the rfm model is regularly above 60us, and sometimes in the mid-70's (but sometimes jumps down briefly to ~47us, which is where I think it "used" to sit, but I don't remember when I last thought about that number)
This is potentially causing lots of asynchronous grief.
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).
There is an intermittent rattling sound coming from the HEPA in the NE corner of the PSL table (right above the PMC, all of our input optics).
Steve says it might be a bad bearing, but he'll check it out in the morning and get it fixed.
MC was having a hard time staying locked, with no discernable reason from the control room (i.e. no big seismic, no PMC PZT railing). The HEPA was on 100%, so I turned it down to 50% to hopefully reduce the rattling, if that was what was wrong.
tdsavg isn't working:
controls@rossa:/opt/rtcds/caltech/c1/scripts/LSC 6$ tdsavg 10 C1:LSC-ASDC_IN1
ERROR: LDAQ - Unable to find NDS host "fb0"
ERROR: LDAQ - Unable to find NDS host "fb1"
ERROR: LDAQ - Unable to open socket to NDS.
When this command is executed inside a script, it doesn't return anything. eg:
set offset = `tdsavg 10 C1:LSC_ASDC_IN1`
returns a blank line.
Past elog research said lots of things about test points. I didn't suspect that, since there aren't many test points occupied (according to the CDS status screens), but I cleared the test points anyway (elog 6319). Didn't change anything, still broken.
LSCoffsets script, and any others depending on tdsavg will not work until this is fixed.
We can't compile any changes to the LSC or the GCV models since Jamie's new script / program isn't found. I don't know where it is (I can't find it either), so I can't do the compiling by hand, or point explicitly to the script. The old way of compiling models in the wiki is obsolete, and didn't work :(
This means we can't (a) record TRY or (b) add the Q quadrature of the beat PD to the real time system tonight.
We're going to try just using Yuta's pynds script to capture data in real time, so we can keep working for tonight.
As usual, we noticed the frame builder wasn't connecting happily with the rest of the computers just as we were about to lock some stuff (we never notice it being bad when we're not trying to use the frame builder....)
All the big rectangles by each computer were white. I restarted daqd, and that brought most things back. c1lsc and c1sus needed their mx_streams restarted manually to get everything green again.
I've had about enough whine with my computers for tonight.
Yuta claims he fixed the PRM oplev by centering it the other day, but no one has left it on and watched it for a long while, to make sure it's okay. We watched it now for ~2 min, and it was good, but we're leaving the oplevs off anyway for the night. Tomorrow we should restore PRM (it's currently restored), turn on the oplevs, and let it sit to make sure it doesn't go crazy.
I'm starting to feel like a wine-o here. Yuta wanted to glance at the PRM oplev dataviewer, and lo and behold, the fb lost connection just as he decided to do that. We had checked the front end status screen not 1 minute beforehand, and everything was green. Lame.
Yuta added channels so we can get the Q phase of all the beat PDs to the c1gcv model. I showed him how to recompile/install/start.
During the install, it couldn't find: Unable to find the following file in CDS_MEDM_PATH: LOCKIN_FILTER.adl
Unable to find the following file in CDS_MEDM_PATH: LOCKIN_FILTER.adl
On all the screens (ALS and SUS), lockin parts are white. Someone changed something, then didn't go back to fix the screens.
Otherwise, things look to be working fine.
Sorry about that. I had modified the path environment that pointed to the rtcds util. The rtcds util is now in /opt/rtcds/caltech/c1/scripts/rtcds, which is in the path. Starting a new shell should make it available again.
Added TRX and TRY and POY11_I_ERR and POX11_I_ERR to the c1lsc.mdl using a new-style DAQ Channels block, recompiled, installed, started the model, all good. Restarted the daqd on the framebuilder, and everything is green. I can go back and get recorded data using dataviewer (for the last few minutes since I started fb), so it all looks good.
Note on the new DAQ Channels block: Put the text block (from CDS_PARTS) at the same level as the channel you want to save, and name it exactly as it is in the model. The code-generator will add the _DQ for you. i.e. if you define a channel "TRY_OUT_DQ" in the lsc model, you'll end up with a channel "C1:LSC-TRY_OUT_DQ_DQ".
The LSC triggers for the individual filter modules in a filter bank now works. This is handy so that boosts can come on as soon as a cavity is locked, but will turn off when the cavity unlocks.
You choose which filter modules you want to be triggered, and which ones you want to be manually controlled.
Example: LSC-YARM FM4 and FM5 should always be on, but FM2 and FM3 are controlled by the trigger. You can set the trigger thresholds for the filter modules independently of the main DoF enable trigger thresholds.
Since the .ini files get overwritten every time a model is compiled now, we need to put all channels we want saved to frames in the DAQ Channels list inside the model.
I added the _ERR channels for all RFPDs (I and Q for each), as well as the _OUT channels for the DCPDs. I also added the _OUT channels for the DoF servos (ex. C1:LSC-DARM_OUT). I don't remember off the top of my head what else we used to save from the LSC model, but those all seemed like ones we'll possibly want access to later.
We need to go through and do this to all the models we use regularly.
Since SUS hasn't been recompiled in a while, all those channels are saved (until such time as someone does a recompile). Den has gone through and edited the PEM and OAF .ini files by hand each time he recompiles, so we have that data, although we need to put it into the model (which is the new proper way to acquire channels).
Jenne and Yuta's Summer Plan
These are the things that we'd like to accomplish, hopefully before Yuta leaves in mid-July
* Yarm mode scan
~ Measure residual motion of Yarm cavity when ALS is engaged
* Xarm mode scan
~ Align Xarm IR
~ Align Xarm green to cavity
~ Do mode scan (similar to Yarm)
~ Measure residual motion of Xarm cavity when ALS is engaged
* Hold both arms on IR resonance simultaneously (quick proof that we can)
~ Modify beatbox so we can use both X and Y at the same time (Jamie will do this Wednesday morning - we've already discussed)
* PRMI + Arms
~ Lock the PRMI (which we already know we can do) holding arms off resonance, bring both arms into resonance using ALS
* PRC mode matching - figure out what the deal is
~ Look at POP camera with video capture - use software that Eric the Tall wrote with JoeB to measure spot size
* DRMI glitches
~ Why can't we keep the DRMI locked stably?
* DRMI + Arms
~ Full lock!!
~ Make lots of useful diagnostics for aLIGO, measure sensing matricies, etc.
We have measured the out of loop residual motion of the Yarm while locked with the ALS. We see ~70pm RMS, as compared to Kiwamu's best of ~24pm RMS. So we're not yet meeting Kiwamu's best measurement, but we're certainly not in crazy-land.
The Yarm ALS was locked, I took a spectrum of POY11_I_ERR, and used the calibration that we determined earlier this evening. For reference, I attach a screenshot of our ALS loop filters - we had on all the boosts, and both resonant gain filters (~3Hz and ~16Hz).
A large part of the RMS is coming from the 60Hz power line and the 180Hz harmonic....if we could get rid of these (how were they eliminated from the measurement that Kiwamu used in the paper?? - plotted elog 6780) we would be closer.
Also, it looks like the hump (in our measurementf ~100Hz, in Kiwamu's ~200Hz) is not quite an order of magnitude higher in amplitude in our measurement vs. Kiwamu's. We have ~5e-11 m/rtHz, Kiwamu had ~7e-12 m/rtHz. This increase in noise could be coming from the fact that Yuta and Koji decreased the gain in the Ygreen PDH loop to prevent the PDH box from oscillating.
While we should still think about why we can't use the same gain that Kiwamu was able to ~6 months ago, we think that we're good enough that we can move on to doing mode scans and residual motion measurements of the Xarm.
[Yuta, Koji, Jenne]
Lots of small things happened tonight, in preparation for having both arms' ALS working simultaneously.
1. Xarm aligned in IR
1.1 ETMX oplev centered
2. Xgreen coarsely aligned to Xarm
3. X beat setup on PSL table resurrected.
3.1 Steering optics for both X and Y green (before PBS) were touched to fix clipping Xgreen on some of the first mirrors after the light exits the chambers.
3.2 Xgreen aligned to beat PD
3.3 PSL green waveplate rotated so ~half of the light goes to X beat, other ~half goes to Y beat (recall we had rotated the polarization so we had max light on the Y beat PD a few weeks ago).
3.3.1 Now we have ~80uW of PSL green going to each beat PD.
3.4 PSL green aligned to X beat PD
3.4.1 Replaced mount for mirror between PBS (which splits PSL green light) and BS (which combines PSL green and X green) so that I could get the alignment correct without having to use the full range of the knobs on the mount.
3.5 Realigned (coarsely) Ygreen to Y beat PD - the mirrors just after the chambers had been touched, so Y green was no longer directly on the PD. This will need to be done more finely when we're ready to lock the Yarm again.
3.6 Dedicated cables for the DC of each beat PD were put in place, so we have those in addition to the DC transmission PDs which we are putting in temporarily each time we align the green to the cavities. Some mystery unused cables that were running under the PSL table were removed. The power for the X beat PD was rerouted so that it's much closer to the actual diode, and out of the way.
4. Better alignment of X green to X arm.
4.1 Put Green Transmission camera into place
4.2 Noticed that the X green spot on the transmission camera is not nearly as steady as the Y green. Increased the gain of the X green refl PD on the end table to see if it helped the spot be more steady, but it's still very wiggly. We reverted the gain to what it was. We need to fix this!!!!
4.3 Removed camera, looked at X transmission DC (PD is temporarily in front of the beat PD), tried to increase the transmission.
4.4 Aligning the green to the X arm has been really tough - there were a few more iterations of camera then DC PD.
4.5 Measured X green power on the PSL table - 02 mode was ~150uW. The 00 mode is still not very stable, which is frustrating, although we have a reasonable amount of power transmitted.
4.6 The X end green shutter was moved out of the beam path since the green beam was clipping while going through the shutter. We need to put it back now that the beam is pretty much aligned. The beam size and the aperture are roughly the same, so we should look to see if there is a different place on the table where the beam is a little smaller, where we can put the shutter.
5. Whitening filters (Pomona box-style) made for the Xarm I and Q channels - these are the same as the whitening for the Y arm.
6. 30m SMA cable made to be used for 2nd delay line.
6.1 Steve reminded me this morning that we returned one of the fancy spools of cable that was purchased for the delay lines, since it was defective. We didn't get it replaced because there was debate as to what is the best kind of cable to use. We need to come to a conclusion, but for now we have a regular RG-405 cable.
7. Jamie has started work on modifying the beatbox so that we can have 2-arm ALS. Hopefully that will be done soon-ish, because we're otherwise pretty close to being ready.
ASS doesn't run on Ubuntu!
Put beatbox back, simultaneous arm ALS
Input matricies, output filters to tune SUS. check after upgrade.
POX11 whitening is not toggling the analog whitening???
Look into PMC PZT drift - PZT failing? Real MC length change?
Vent planning / organization
THE FULL LIST:
Audio system for the signals!!!! Even a crappy one!
Input matricies, output filters to tune SUS. Check after upgrade.
Fix occasional common-mode power transient in the arm transmissions. Probably an alignment thing. Would ISS help?
Drift of the green incident axis -> Assess the amount of the drift / replace the mount
Calibration of POP22 / AS110
PMC/IMC/ARM characterization (loss, finesse, reflectivity, etc)
Arm cavity sweeps, mode scan
Align AS OSA (others?)
Investigate PRMI glitches, instability
PZT or Picomotor mounts for PSL/ALS beams
ALS on the both arm simultaneously / common / diff ALS scripts
Measure green locking (Aux laser to arm) transfer functions, residual spectra
Measure oplev spectra while locking Xgreen - see if the optics are particularly noisy
Measure Xarm residual motion using POX while ALS is engaged.
Fix Vio2 filter modules on SUS
Switch power supply for amplifiers of beatnote signal to rack power
Add temp sensors for end lasers to CDS slow channels
Put windows / pickoffs on PSL table for (a) green trans camera, (b) GTRY, (c) GTRX
Capture OSA signals in CDS (the 'scope TDS1001B has a USB port in the back for connecting to the computer)
Transmon (arms) for high and low power
POX11 whitening is not toggling the analog whitening???
Install guardians to monitor EPICS values
Actuator noise level characterization (coil driver response in V/m & coil driver noise level V/rtHz)
Improvement of POP22/110/AS110 RF circuits?
Complete 40m overview screen - everything should be clickable with pseudo 3D icons
Script to generate a MEDM tree
Resurrect MEDM snapshots
New ! buttons on every screen, include wiki page
Add all screens to svn
Daily diagnosis of the MC spot positions (there must be something already...)
Daily/occasional adjustment of the incident axis on the MC
Panic button on Watchdog screen isn't working on Ubuntu
OPLEV/OSEM trending script before the IFO work for diagnosis. Put into 40m summary screen.
Auto-locker for arms
Auto-locker for PSL things
Diagnostic script for CDS - mx_stream, other stuff.
Make sure scripts are all svn-ed
If each video screen has a caption, that would be great
GUI interface of "videoswitch"
Ubuntu vs. CentOS
Upgrade Ottavia to Ubuntu, make sure connect to DTT, Dataviewer, AWG.
IPPOS beam measurement
AS beam measurement (if beam is bright enough)
Mode matching calculations, sensitivity to MC waist measurement errors, PRM position
Think up diagnostic measurement to determine mode matching to PRC while chambers are open, while we tweak MMT
Use sensoray to capture, measure beam mode at AS, POP
Scattered light measurement at the end stations: design / confirmation of the mechanical parts/optics/cameras
Align AUX laser into dark port
Assemble in-vac beam dumps - how many do we need?
OAF comparison plot, both online and offline, comparing static, adaptive and static+adaptive
Static-only OAF noise budget (Adaptive noise budget as next step)
Script for daily / weekly re-calculation of Wiener, post to elog if need changing
Prepare electronics for TTs (coil drivers)
In-air TT testing to confirm we can control / move TTs before we vent
Connect TTs to digital system and controls, lay cables if needed
Determine whether we need to add a new flange to OMC chamber
Opto Energy diode laser - purchase
Set everything up
Demod board for AS110 - so we can also have POP110?