I did at trial run at pumping down the vacuum today. While doing this I monitored the transmission power. The graph of this is attached.
You can see the start, where therer is good transmission. Then there's noise where I put the lids on the chambers, and then a locked section in the middle. You can see that just putting the tops on the chambers and clamping them down has caused some misalignment. Then there is noise where the pumping happens, and the last section is after the valve is closed and the pump turned off. Clearly there is significant reduction in transmission power.
Maybe we can improve this with better clamps to hold down the vacuum chambers? At least the cavity is still locking, so the overall effect is pretty small.
Also, I haven't tried to maximise the transmitted light by playing with the input mirrors. This may improve things a bit.
I have been saying things like "the new PD is lower-noise than the PDA255". This is not true; the output noise is actually a bit higher even. The way we win is thus because the transimpedance is a little bit better and more importantly because the dynamic range is much higher. Here is the demod noise analysis akin to that from this post for the PDA255.
In my post about the shot-noise-limited locking scheme, I claimed that the input-referred noise of the RFPD was well below our requirement curve. This is not true at the moment because of (still) poor optical gain. I calculated that based on the theoretical maximum optical gain in V/Hz we could obtain, assuming that we could at least do as well as a sizable fraction of that. More on this later, but it appears that the purely optical component ([W/Hz]) is orders of magnitude lower than it could be, despite the fact that we are getting ~50% transmission through the cavity.
Since residual common mode noise ("spillover noise") has been our main obstacle to date, I decided to do some analysis of the primary loop error signal before bothering to put together the rest of the gyro. Here is a busy plot, followed by a wordy explanation:
Note: all traces are calibrated to units of (rad/s)/rHz by dividing the error signal noise level by the appropriate optical gain in V/Hz and then multiplying by (lambda S / 4 A) to get rad/s. Also note that the overall OLTF of the primary loop is roughly the same for all the plots (not entirely true, as I was only able to get our UGF up to about 10 kHz as opposed to the ~15 kHz we had before).
So, the low-frequency spillover noise is now ~30x better than it was in the previous setup. I would put on a party hat and dance in a circle, but this is shit: we are still something like a factor of 200 away from the sensing requirement from 200 mHz - 1 Hz, and worse at 100 mHz since the requirement drops down there. We cannot fix this by adding servo gain as we were planning to do for noise here caused by mirror motion, etc; this is sensor noise, so we need to improve SNR up front.
This is why, in my last post, I suggested we do away with the Cougar---it takes away SNR where we are dying for it, while in the current case we are just attenuating the signal downstream. We also need to improve our modulation depth. Right now, we are at < 0.3 rad, whereas we want something like 1 rad for best signal.
Here's the confusing thing: right now, we have a pure optical gain (cavity response) of ~4 nW/Hz, whereas the theoretical maximum is something like 1 uW/Hz for our power level and cavity parameters. Why is our cavity response so piss-poor? Increasing the modulation depth could improve this by a factor of 4 or so, but that still leaves us at around 1% of the available response. This would seem to fit with my observation that coupling our astigmatic beam to a non-astigmatic-but-elliptical cavity mode should lead to ~1% overlap with the solution that gives 99% coupling for an ideal input beam, but the fact remains that we are still coupling ~50% through the cavity! It is as though this light is not contributing to the error signal but still fits in the cavity mode at the same frequency and just comes along for the ride! What?!
Yes, I have considered that there could be something going on with the demodulation (mixer starvation, non-optimized phase angle, etc.), but this won't account for it because any attenuation there should also attenuate the noise level out of the PD, which appears in the error signal exactly as predicted.
I took a transfer function of RFPD S/N 02 tonight with the Jenne Laser. It was much easier to calibrate this one because I didn't have to worry about what the Cougar was doing (since I didn't put one on this board). I also noticed that for some reason the power leaving each port of the beamsplitter was not equal---there was about 2x the power going to the reference PD as to the DUT---this explains why I was getting less gain than expected by about this factor with the last PD.
Here is a transfer function:
Okie dokie. I wasn't going to lose much sleep over it anyway, as we won't see it at this level. Just pointing it out.
Bah! The input referred noise is plenty good enough at low frequencies. Sometimes reality is just not the same as theory on the long time scales (c.f. Hope and Yes We Can). Move On and get gyro noise!
As for the noise level, the agreement isn't quite as great. Here is the input-referred spectrum along with the LISO prediction:
I spent the afternoon/evening finishing building the temporary breadboard version of the PDH2 and testing it. As a reminder, this is necessary because we want to get a new, low gyro noise spectrum before the LV meeting for the poster/talk and we won't have time to get the PCB done before then.
Here she is in all her glory:
I spared no expense; she's equipped with all four (DIP-switchable) boosts, as well as an invert and a switch-engaged SWEEP input.
I originally built it with all AD829s as we are planning (?) on doing for the final servo, but I had problems with oscillations. I followed the instructions for shunt compensation capacitors in the datasheet, but Frank and I found that there were unavoidable problems from stray capacitances and inductances in the push-in components and the board. We systematically replaced each stage with an OP27 from the input to the output until we had no more issues. We don't expect to see the electronics noise floor at the moment, so the difference between 1.7 nV/rHz and 3 nV/rHz isn't a big one in our case, though we would like to keep as few slower parts in there as possible to retain phase. In any case, we were able to keep two of the AD829s without a problem.
Taking a transfer function was a big pain in the ass because of the 105-dB DC gain (i.e. without the boost). I have a trimpot to adjust the offset of the input stage, but the way the Agilent makes swept-sine measurements causes a small change in offset over the course of the sweep that is enough to rail the servo. I ended up avoiding the problem by taking the transfer function with random-noise excitation. I used an SR560 immediately after the source with a 2nd-order HPF so that I had enough at high frequencies where there is much attenuation. Here is the experimental setup and the SR560 settings (for one of the span settings):
I got a good measurement in the end; you can see that it agrees very well with the model:
Note: this says "LISO estimate", but that's a mistake; it's actually an ideal model of a TF with the same poles and zeros. This shows that the phase lag introduced by the OP27s is negligible in our region of (current) interest.
As for the noise level, the agreement isn't quite as great. Here is the input-referred spectrum along with the LISO prediction:
It converges in the middle frequencies but doesn't at either end. I was suspicious that the analyzer noise was the culprit at higher frequencies---you can see that the input range is different over the higher three measurements---so I looked at how the output noise compared:
I would be willing to bet that the high-frequency divergence is indeed caused by the analyzer noise, and I will retake these measurements tomorrow. As for the low-frequency part, I am not quite so sure. It could be that one or more of the stages has a higher-than-quoted noise corner frequency, but this doesn't seem all that likely.
Since the transfer function looked right, I tried very briefly to lock the cavity with it. It didn't work right away (I got some audio-band oscillations), but I had to take off so I didn't mess with it too much. I think that if I adjust the gain by adjusting the input power to the experiment I can get it to lock. This is first on the docket tomorrow. In the meantime, I am taking a low-frequency measurement of the servo noise overnight for inclusion in the noise model. Hopefully this will help to identify the low-frequency noise culprit.
I made some more progress on the gyro upgrade today:
Signals -- Yellow: REFL DC, Blue: ERR, Magenta: CTRL, Green: TRANS DC
OK, never mind. It's only that about five people didn't see it this morning and i checked the the drawer and the desks and couldn't find it. Anyway, there is no 35W laser SOP, not in the lab, not on the wiki and i can't find it in the DCC either. Who wrote it and where is it?
Not true; ours has been sitting next to the laser all night. We will find a permanent place for it in the lab, in case we forget how to use the laser (just kidding..).
none of the SOP's exists in a printed form posted in or outside of the lab.
We finally got all the parts together to properly mount the RFPD board to the box, so we did that today. We aligned the cavity mirrors and injected the primary beam in the CCW direction. I used the mode matching solution that I came up with last week, but there is a problem with it in that one of the mirrors has to occupy the same space as a turning mirror for the other beam. I will have to come up with a different solution, but I put the lenses as close to the right place as possible for right now.
Another issue is that---like before---it is going to be very tough to have the faraday isolators so close to the cavities while still having the beam small enough to fit through the center. We have a little more space on the table now, so we could conceivably move them further upstream in the MMT, but this makes the REFL extraction a bit messier. I think someone said that getting new enclosures with larger apertures for the polarizers flanking the rotator is just as difficult as getting a whole new FI, but we may have to figure a way to get the beam through, or else deal with clipping. Since there is no CW beam yet and I have to fix the mode matching of the CCW beam, I have not installed either faraday yet.
In any case, once I got some good TEM00 flashes, I distributed the LO signal from the Tektronix FG as before:
I then installed RFPD S/N 01 and put the ~80 mW reflection from the cavity onto it. The DC output was consistent with the design, and dips were evident in conjunction with the spikes in the TRANS signal. I then connected the RF out to the RF IN of the mixer and swept the cavity to see the error signal. At first, I thought what i was getting was some distorted junk, but then I realized that the signal was just so huge that it was saturating the INPUT MON. Turning down the optical power resulted in the classic PDH signal sweep. Nevertheless, I was able to lock the cavity with the full 80 mW, though some UGF instability was evident at this level, so I had to turn it down to about 40 mW.
With the cavity locked, I iteratively adjusted both the cavity mirrors and the input steering mirrors to maximize transmission. I was able to get about 50% after quite a bit of trying, but I'm not convinced I can't do better even with the suboptimal mode matching.
Here are a couple shots of the PD doing its thing. The backplate is not on the box because I did not have a d-sub breakout board to power the thing.
The plan for the immediate future is the following:
We now have access control lists for the wiki, which means we can choose who has access to what pages. At the moment I've set the front page to being non-password protected, along with the main experiments page. I've also made an LVC account, though at the moment this has no different access than the non-password pages.
We should decide how we want the wiki set up. Here are a couple of options:
1) We could make dedicated "public" pages, and have these non-password protected. Then we could have LVC access to basically all or most of the wiki, but without any editing rights. Then we can have our own accounts that can edit. The downside to this approach is that it is unlikely any public pages will ever be updated.
2) Another option is to allow public access to as many pages as we feel comfortable with, but for these to be the same regular pages that make up the wiki. This has some advantages because the public pages get updated with everything else. The downside here is that there will be many frustrating links on public pages that come up with "you do not have enough rights to continue" when you click them.
3) Option 3 is to just have no public access at all. We just keep the whole thing private, and choose what pages to give the LVC account access to. Again LVC doesn't need to have editing rights.
I should point out that the LVC account will only have one password (rather than using albert.einstein accounts) so people will have to know the password to get in.
I added some Hartmann Sensor channels to the frames and restarted DAQD on fb1 to include them.
See here for details ...
According to your schematic the bias is 5V. If that is the case the capacitance is usually much less than 150pF!
If you check the typical graph in the datasheet the capacitance is ~120pF@5V.
According to the data i measured i expect it to be below 120pF @5V.
Old LIGO diodes had about 105pF@ 7V. The diode you are using is one of those old batches.
If you like we can measure it tomorrow with my pulsing setup. Doesn't take longer than 5 minutes including setting everything up and getting the data
I chose the "final" component values for the first RFPD as follows. Consult the schematic here.
I have taken a transfer function with the Jenne Laser setup and the result is reasonable but not exactly what we expect. Below is a comparison of the measured transfer function with the prediction from LISO. To get these in a comparable form, I took the raw output of the spectrum analyzer (the ratio of the responses of the DUT and the New Focus 1611 reference PD), multiplied by the flat AC transimpedance of the reference PD (700 V/A), and subtracted the 10 dB of gain from the Cougar (AP1053).
I have a suspicion that just subtracting 10 dB does not accurately negate the effect of having the Cougar on the end. Though it says nothing about it on the datasheet, I have heard that they have some sort of internal AC coupling, and so this odd behavior could be explained by that somehow. I think I will take the transfer function again, this time using a probe to sense before the Cougar instead of after it, and hopefully then it will conform with the model. In the end, all we care is that it behaves as expected near where we expect to have appreciable input signals (e.g. 33 MHz and 66 MHz), but it;s nice to be able to say that we know what's going on everywhere.
Another thing I noticed on the Cougar datasheet is that the noise figure goes up pretty quickly as you go below ~50 MHz. Using naked-eye extrapolation, I estimate that it is about 3.7 dB @ 33 MHz. I have taken a noise spectrum of the PD, but I am not comfortable enough with the TF calibration to trust the analysis yet. Stay tuned.
The input noise of the spectrum analyzer at the lowest range is ~20 nV/rHz. Subtracting this from the measured output noise spectrum of the PDH box before referring to the input, I get a noise spectrum that matches closely the estimated noise from LISO. This box is ready to go. Note that simply subtracting the noise off the way I did does not lead to a large systematic error because the true servo noise is of just about the same level.
I corrected the mistakes to the PDH box. The LISO estimate of the noise from the previous post is no longer quite right, however, as I had to reduce the gain at different points than I had originally intended (originally I was going to do at least part of the reduction at the output stage, but this proves difficult because doing so without being very careful results in a different gain for the inverted and non-inverted modes the way the output stage is designed). The result is that the high-frequency noise is higher than anticipated. Taking the increase in optical gain into consideration, though, the high-frequency contribution to the gyro noise is still lower than before.
Here is a transfer function, showing an overall gain decrease of about 35 dB from the previous case (this post, about halfway down):
Here is the input-referred noise spectrum, along with the LISO estimate for this circuit. The excess low-frequency noise is now absent, but the noise at high frequencies is higher than estimated. It looks as though this might actually be the noise of the spectrum analyzer (the output noise level here is on the order of 20 nV/rHz, and though I had it auto-ranging it could have gotten hung up). I will check this in the AM. Either way, there is a big improvement in broadband and the servo's contribution to the gyro noise is below requirement in a big chunk of our operational band (see previous post).
As I outlined in this post, the primary PDH box needed some modifying if we are to see any significant improvement from the new setup. I made these changes:
The input-referred noise is now at the level explained by the LISO model---unlike it was before---though this calls for a funny story:
When I plotted the noise and divided by the transfer function I measured, I got a noise level that was exactly 10x higher than predicted by LISO. After quite a while of scratching my head and checking my code, I realized that I mistakenly changed the gain of the wrong stage (despite writing down the right one in my notes), causing the noise from the nasty LF356 switchable stage to have 10x the influence. I will correct it and re-measure tomorrow, but the important thing is that we have removed the noisy 8336 from near the input.
Here is a picture of the modified portion of the board and a LISO prediction of the noise when I've corrected the mistake. You can compare with the plot in the link above, but this corresponds to a true low-frequency voltage noise betterment of 20 dB at low frequency, which adds to the 40 dB improvement in the servo's contribution from the expected optical gain increase. This actually puts the servo noise below the aLIGO requirement between about 100-350 mHz.
The PD boxes arrived today, and with the exception of a few minor issues they look great!! Here are a few shots. Here one box is shown assembled and mounted to the brass base and insulator that Alastair designed. The dimensions for these were chosen so that the PD is at 4" from the table.
The issues were/are as follows:
I agree, but that is what the calculation gives. I haven't plotted this yet, but it could be that in this case there are two coupling maxima (i.e. one where the X solution is closest to the cavity mode and one where the Y one is), and right in between---where the "average" solution is---there is a local minimum. Then, we could easily have adjusted the lenses slightly to get to one of the maxima and have something like 10-20% coupling like we saw, despite the fact that the other axis was way off.
I will do some crunching.
I think this 1% is a lot less than we have already seen coupling into the cavity - it doesn't seem quite right to me.
I think that you're correct that is the way we did the calculation, taking some average of the x and y parameters we measured for the beam. I'd have to go back and check though.
This afternoon I measured the distances required to calculate the mode matching, and then I came up with a solution using code that I wrote. In doing so, I realized that there is a problem with the way we have been calculating the overlap in the past.
Last summer, Jenna used the overlap function to show that an overlap of > 99% could be achieved with a non-astigmatic beam injected into a cavity with an elliptical eigenmode (like our gyro cavity, whose mode has a waist twice as big in one direction as in the other). This is fine, but there are two things to note:
Jenna calculated such a nice overlap because she assumed that our input beam was not astigmatic. The coupling is far more sensitive to curvature match at the input (i.e. making the beam flat at the flat mirror) than it is to the area of the beam cross section, and a non-astigmatic beam allows you to do that arbitrarily well.
If I take the solution I calculated for the average of the X and Y components of our input beams and apply it to both components individually, the overlap I get with the cavity eigenmode is < 1%, despite the fact that it is >99% if we assume that the average is a real, physical, circular beam.
I think we may need to do the cylindrical mode matching after all.
Probably ought to put a thermistor on the can to see if the temperature noise is big enough to cause the low frequency MZ noise.
By pushing on the table to force the MZ output through full swings, I have determined the amplitude of the beat and therefore the calibration. The peak-to-peak amplitude is ~3400 cts, so the calibration is:
(1 / 1700 cts) * (1064 x10-9 m) / (2 * pi) = 9.96 x 10-11 m/ct
Here is the calibrated spectrum:
Comparing it with the spectrum I linked to in the previous post shows that the noise below 1 Hz has gone down significantly (a factor of ~8 at 100 mHz), while the high frequency noise has suspiciously gone up. For the resonances, this could be due to Q enhancement from going into vacuum, but it is also noteworthy that there was a possible calibration issue in the old spectrum, while this time I have used the full swing of the beat in counts to do the calibration without having to multiply by other conversion factors. I will always do it this way in the future so that there is no ambiguity. No matter how you look at it, though, the low-frequency noise is better.
It is also worth noting that this MZ-type noise is expected only to couple in as phase noise at the gyro output beat signal. As such, its influence will be rotated away by a factor of f at low frequencies, where we will instead be dominated by the "FSR modulation noise". Hopefully, the low frequency improvement we see here will have a counterpart in that, as well.
This is the output of the MZ for the first couple hours after we set it up. Since we only watched the first few minutes on the scope, it appeared as though some transient from the slow influx of gas into the chamber was causing it to swing through fringes. This longer time series seems to paint a different picture. It shows something that looks like a damped oscillation that is also increasing in period.
An increase in period alone would be consistent with a slowing differential drift while the vacuum system reached its steady-state pressure, but the change in amplitude doesn't make sense (we have the output going onto a large-area PD using a lens, so even if we were just losing contrast the maximum power on the PD---bottom of the plot here---would stay roughly the same). Instead, this looks like something was actually causing it to oscillate between the maximum and minimum values of the output.
Not long after this, the large oscillation seemed to have gone away, leaving a more stochastic looking time series (see below). The abrupt jumps and subsequent slow drifts are probably coincident with the lab temperature control system turning on.
I chose a small chunk of time during which the time series looked relatively flat and near mid-range (~13:00:00 2/19/11) to take a spectrum. Since I now realize that we probably don't know the contrast for sure, I have to postpone the calibration until I can verify the full-swing amplitude tomorrow morning. Still, a few things can be learned by looking at how the spectrum compares qualitatively with the one I took in air. The main thing to notice is that the low-frequency hill is markedly shallower with respect to the higher-frequency mechanical resonances. There also appears to be a new family of resonances between 10-20 Hz, which might originate in the vacuum system itself.
We will have more information of how much better the low-frequency noise is once we've calibrated this.
"Inter-Spacecraft Clock Transfer Phase Stability for LISA (Diploma Thesis)"
"Computation of phase-stability over temperature - Thermal testing of microwave cables for the Laser Interferometer Space Antenna"
"Phase noise contribution of EOMs and HF cables"
"Inter-Spacecraft Clock Transfer Phase Stability for LISA"
One of the companies which is selling some good stuff
We finished cleaning the in-vac stuff, installed the mirrors in the MZ configuration, injected a beam, aligned it for best contrast, put the output on a PD, and then pumped down. We disconnected the pump once we got down to the level that Alastair had achieved previously (~a few x 10-4 torr) and the pressure rose to a few hundredths of a torr.
The output of the interferometer throughout the process was a slow sine wave, which we figured was due to the small changes in cavity length from the pumping/leaking.
The channel is being acquired. More analysis and a better explanation of the setup to come.
A while ago I posted an entry with an outline of what needs to be done for the gyro upgrade. Here is an updated2 version. Completed items are in green, items in progress in magenta, stricken items are deemed unnecessary, and comments in blue.
A few things have been somewhat glossed over in the above:
The bases for our PDs arrived today, which enabled us to finalize the table layout for the new gyro. Alastair has been mounting the cavity mirrors to the new bases and cleaning them for placement into the vacuum system. Here is a shot of the table with rays traced. The (sturdy!) brass PD bases are clearly visible. Note that the MMT lenses shown here are just placeholders; I still need to work out a solution now that the layout is done.
The fact that the "viewports" on the IO box are very close to the edge of it (from when they were used to inject to the gyro cavity) makes the injection setup a little awkward. We originally thought we would have to cross the beams just before the cavity, but I figured out a way to do it without that. Here is a closeup of the injection/REFL isolation setup, and a slightly-less-close-up shot of it to highlight how the beams are directed into the vacuum system. I have only shown the input beams (blue and yellow) in the second one to avoid confusion.
The PD boxes are scheduled to arrive on Monday afternoon. Before they do, I will have two RFPDs ready to go so that we can assemble them and begin open-tank locking immediately. I think we should be able to have an in-vac gyro spectrum by the end of next week if all goes smoothly. Science at work.
I profiled the primary and secondary beams so that we have this information when we go to do the modematching. I have started calling them strictly the "primary" and "secondary" beams because geometry might dictate that we switch which one is CW and which is CCW in the new scheme. It is best to keep the names unambiguous so that we don't run into the trouble that they have at the 40m.
This evening, I set up the AOM double-pass and balanced the two beams going to the injection/extraction optics. This wasn't as simple as last time because I had to re-profile the beam and come up with a modematching solution. I've updated my recent "status" post to reflect the current status.
Here is the profile after the mirror leading into the AOM:
The beam was slightly elliptical and somewhat astigmatic (|z0x - z0y| ~ 10 cm). Using the average of x and y, I came up with a simple matching solution using an f = 100mm lens and the R = 30cm mirror we were using before. It puts the mirror roughly 30cm from the AOM, and the waist of about 124um near the center of the crystal. Here is the ABCD screenshot:
I was able to isolate the double-passed 1st-order beam with an overall efficiency of ~45% (i.e. single-pass efficiency of ~67%). This is slightly worse than before, but the output beams are very close together so it is difficult to know whether we actually had it better before at all. In any case, I balanced the beams heading toward the injection optics at about 80 mW apiece, which is more than what we were counting on already. There is still some power dumped just after the laser, so there is still room to step up the power a bit more should we need it. Here's a picture of the setup as it stands---I am holding an IR card to show where the two beams are going:
I realize that now. The plot you mention was supposed to be and is now in my last post.
For the record, I did mention that the AD8336 could be the problem when I first did the measurement, and no one jumped up to say THAT IS A SHITTY PART! Of course, I am to blame for not looking at the data sheet.
I thought you guys know that, as it's clearly mentioned in the datasheet, in the table on page 2 and in graphs where noise is plotted vs gain setting voltage some pages later. Nobody ever said that this is a low-noise part.
It seems that the main issue was a design flaw. The AD8336 has a preamp stage, and if the gain is too low there the noise performance of the whole thing is bad no matter what you choose as the "variable gain". The universal box has this preamp set to unity gain. As seen in the plot, if you extrapolate the "preamp gain = 4x" gain line up by a factor of four, and assume we were using a reasonable gain setting of ("G" = 5) on the dial---corresponding to Vgain = 0---the input noise is 100 nV/rHz. This is bush league.
Also, I don't see a single reference to any frequencies lower than ~100 kHz, and I suspect that the low-frequency behavior is not a priority for them. We should avoid this part.
Yes, I am happy about that. For the new box, we confirm the noise levels of the boxes with various gains before they are in use.
Second, Koji will be pleased to hear that I think I have traced the excess low-frequency noise seen in this measurement to the AD8336 variable gain stage.
Since we will not have the new PDH servos ready by the time we are locking the mGyro, it is important for us to think about how we can minimize the gyro noise with the old boxes.
First of all, we will not be able to capitalize on the improved optical gain (from increased power on the new diodes) unless we can decrease the overall gain of the servo; otherwise, the loop will become unstable. We should figure out the best way to reduce the gain by an overall factor of ~40-50 dB, which is the expected enhancement from the new PDs.
Second, Koji will be pleased to hear that I think I have traced the excess low-frequency noise seen in this measurement to the AD8336 variable gain stage. It turns out that they have poor performance when used in low-gain configurations, leading to a likely input noise of greater than 400 nV/rHz in our current configuration, with an apparently high 1/f corner frequency of >10 Hz. By playing with the parameters a bit in LISO (the noise specifications in the data sheet are a bit esoteric), I am able to produce a noise plot that is quite like the one we measured in the above linked post.
I propose that we temporarily circumvent the variable gain stage altogether and reduce the gain of some or all of the stages, leaving a trimpot somewhere so that we can tune it as necessary. The box will of course be reverted for universal use once we get our new boxes. This combination should allow us to reach our estimated unavoidable displacement noise level in broadband above ~10 Hz. The hope is that this unavoidable displacement noise level is actually lower than we think at low frequencies (assuming that most of the low-frequency noise is caused by the air), so that using the new boxes to juice up our gain at low frequencies will put us below the requirement in the operational band. For reference, the most recent gyro noise budget is here.
A while ago I posted an entry with an outline of what needs to be done for the gyro upgrade. Here is an updated version. Completed items are in green, items in progress in magenta, stricken items are deemed unnecessary, and comments in blue.
I didn't say that they are out of limits, but they are not normal compared to other disks which indicates that they WILL FAIL NEXT. So we should be prepared and replace e.g. sdd now BEFORE it fails and all data is gone. Same for the boot disk. If you compare the raw values for all disks in fb1 and fb2 (psl lab) you see that for all disks, even for five year old disks those numbers are zero.
Both "Raw_Read_Error_Rate" and "Seek_Error_Rate" are super high for sda and sdc on fb0. If you compare that with other disks you see that this is not normal.
For sdd the "Load_Cycle_Count" is more than 200k, max lifetime is 300k. A good value is a few hundred to thousand. The count for all disks in fb1 and fb2 is less than 50!
The problems with the disk you showed me were not really problems at all:
I do think it's a good idea to get a mirror for sda though.
Some more problems:
This time we should replace the disks BEFORE they fail
Out of interest, what does ndsd do?
I'd like to update the wiki with info on how inittab should be set up.
[Alex, Joe, Zach]
[Alastair, Steve, Zach]
I finalized the dimensions of the RFPD boxes this morning. This afternoon, Alastair and I went over them and made sure they jived with the base dimensions.
Steve let me use his P-card to order them. The grand total was $700 ($175/box).
Lead time is 5 days from order to shipping, then UPS ground.
With Koji's help, I was able to get the PD working today. Yesterday, I was having trouble getting the DC readout to work. We traced it back to the conical inductor to ground from the PD anode, which was open for some reason (I later broke it when removing it from the board, but it wasn't obviously broken before that --- I am trying to fix it). I replaced it with a normal coil for the moment.
After this, things worked fine. There was a strange ~75 kHz oscillation in the DC signal, but Rana postulated that this could be from the less-than-stellar lab supplies. I decided to move on to the RF output. I hooked it up to the Jenne Laser rig and swept it. Below is a log-scale plot and a linear close-up. I am still working on the calibration and making it match up with the model, but I have to have another look at the measurement setup and measure some component values tomorrow.
Essentially, though, it looks like what we expect:
More details and comparison with the model to follow.
Disk sdc was full. See below list of files, showing that it stopped at 05:43:
-rw-r--r-- 1 controls controls 19126210 Feb 8 05:40 C-R-981207616-32.gwf
-rw-r--r-- 1 controls controls 19126385 Feb 8 05:41 C-R-981207648-32.gwf
-rw-r--r-- 1 controls controls 19104189 Feb 8 05:41 C-R-981207680-32.gwf
-rw-r--r-- 1 controls controls 2629632 Feb 8 05:42 .C-R-981207712-32.gwf
-rw-r--r-- 1 controls controls 0 Feb 8 05:43 .C-R-981207776-32.gwf
-rw-r--r-- 1 controls controls 0 Feb 8 05:44 .C-R-981207840-32.gwf
-rw-r--r-- 1 controls controls 0 Feb 8 05:45 .C-R-981207904-32.gwf
-rw-r--r-- 1 controls controls 0 Feb 8 05:46 .C-R-981207968-32.gwf
The wiper was running, and was set to 95%:
[controls@fb0 fb]# more wiper.log
Tue Feb 8 20:27:01 PST 2011
Directory disk usage:
Combined 912389612k or 891005m or 870Gb
/frames/full size 961432072k at 94.90%
/frames/full is below keep value of 95.00%
Will not delete any files
df reported usage 94.92%
However the disk was full:
[controls@fb0 fb]# df
Filesystem 1K-blocks Used Available Use% Mounted on
234476168 24758300 197615008 12% /
/dev/sda1 101086 28296 67571 30% /boot
tmpfs 1029676 0 1029676 0% /dev/shm
/dev/sdd1 1442145212 149825928 1292319284 11% /frames/trend
/dev/sdc1 961432072 912594164 0 100% /frames/full
fb1:/cvs 961432032 108480608 852951424 12% /cvs
Something is screwed up with the way that wiper calculates how full the disk is. We changed the value down to 90%, and the disk is now at 91%. The wiper script says it's at 85%, so it's still getting the wrong value, but the disk is no longer full and we are recording frames again.
Now that the frame data is being taken again, we can see the realtime data in dataviewer. However, we cannot get any frame data from the past. Dataviewer throws up the following error. The frame data is definitely there, is owned by controls, and we are definitely acquiring the channel whose data we are trying to retrieve. There is something wrong here that I cannot work out.
Connecting to NDS Server fb0 (TCP port 8088)
LONG: DataRead = -1
No data found
T0=11-02-08-04-59-52; Length=60 (s)
No data output.
I think this is going to be a problem we need to get Alex to take a look at.
To clarify what was done, I actually changed some boot up settings for the ethernet on fb0.
I went to /etc/sysconfig/network-scripts/ and modified the ifcfg-eth1 and ifcfg-eth3 files. I basically changed "ONBOOT=yes" to "ONBOOT=no" in each file. This was in addition to the "sudo ifconfig eth1 down" for shutting them down while the computer was running.
Similar results can be achieved with the network GUI, which can be run with "sudo system-config-network"