I am facing two problems:
I swapped the inputs to the ZHL-3A at the PSL table - so now the X beat RF signals from the beat mouth are going through what was previously the Y arm ALS electronics. From Attachment #1, you can see that the Y arm beat is now noisier than the X. The ~5kHz peak has also vanished.
So I will pursue this strategy of switching to try and isolate where the problem lies...
Somebody had forgotten to turn the HEPA variac on the PSL table down. It was set at 70. I set it at 20, and there is already a huge difference in the ALS spectra
[rana, kevin, udit, gautam]
quick notes of some discussions we had today:
RXA: 0805 size SMD thin film resistors have been ordered from Mouser, to be shipped on Monday. **note that these thin film resistors are black; i.e. it is NOT true that all black SMD resistors are thick film**
I did some work on the PSL table today. Main motivations were to get a pickoff for the BeatMouth PSL beam before any RF modulations are imposed on it, and to improve the mode-matching into the fiber. Currently, we use the IR light reflected by the post doubling oven harmonic separator. This has the PMC modulation sideband on it, and also some green leakage.
So I picked off ~8.5mW of PSL light from the first PBS (pre Faraday rotator), out of the ~40 mW available here, using a BS-80-1064-S. I dumped the 80% reflected light into the large beam dump that was previously being used to dump this PBS reflection. Initially, I used a R=10% BS for S-pol that I found on the SP table, but Koji tipped me off on the fact that these produce multiple reflected beams, so I changed strategy to use the R=80% BS instead.
The transmitted 20% is routed to the West edge of the PSL table via 2 1" Y1-1037-45S optics, towards the rough vicinity of the fiber coupler. For now it is just dumped, tomorrow I will work on the mode matching. We may want to cut the power further - ideally, we want ~2.5mW of power in the fiber - this is then divided by 4 inside the beat mouth before reaching the beat PD, and with other losses, I expect ~500mW of PSL power and comparable AUX light, we will have a strong >0dBm beat.
Attachment #1 is a picture of my modifications. For this work, I
I was looking into the physics of polarization maintaining fibers, and then I was trying to remember whether the fibers we use are actually polarization maintaining. Looking up the photos I put in the elog of the fibers when I cleaned them some months ago, at least the short length of fiber attached to the PD doesn't show any stress elements that I did see in the Thorlabs fibers. I'm pretty sure the fiber beam splitters also don't have any stress elements (see Attached photo). So at least ~1m of fiber length before the PD sensing element is probably not PM - just something to keep in mind when thinking about mode overlap and how much beat we actually get.
I was looking at this a little more closely. As I understand it, the purpose of the audio differential IF amplifier is:
Attachment #1 shows, the changes to the TF of this stage as a result of changing R19->50ohm, R17->500ohm. For the ALS application, we expect the beat signal to be in the range 20-100MHz, so the 2f frequency component of the mixer output will be between 40-200MHz, where the proposed change preserves >50dB attenuation. The Q of the ~500kHz resonance because of the series LCR at the input is increased as a result of reducing R17, so we have slightly more gain there.
At the meeting yesterday, Koji suggested incorporating some whitening in the preamp itself, but I don't see a non-hacky way to use the existing PCB footprint and just replace components to get whitening at audio frequencies. I'm going to try and measure the spectrum of the I and Q demodulated outputs with the actual beat signal to see if the lack of whitening is going to limit the ALS noise in some frequency band of interest.
Does this look okay?
The demod circuit board is configured to have gain of x100 post demod (conversion loss of the mixer is ~-8dB). This works well for the PDH cavity locking type of demod scheme, where the loop squishes the error signal in lock, so most of the time, the RF signal is tiny, and so a gain of x100 is good. For ALS, the application needs are rather different. So we lowered the gain of the "Audio IF amplifier" stage of the circuit from x100 to x10, by effecting the resistor swaps 10ohms->50ohms, 1kohm->500ohms (more details about this later).
I tried to couple the PSL pickoff into the fiber today for several hours, but got nowhere really, achieved a maximum coupling efficiency of ~10%. TBC tomorrow... Work done yesterday and today:
I think part of the problem was that the rejected beam from the PBS was not really very Gaussian - looking at the spot on the beam profiler, I saw at least 3 local maxima in the intensity profile. So I'm now switching strategies to use a leakage beam from one of the PMC input steering optics- this isn't ideal as it already has the PMC modulation sideband on it, and this field won't be attenuated by the PMC transmission - but at least we can use a pre-doubler pickoff. This beam looks beautifully Gaussian with the beam profiler. Pics to follow shortly...
I tried to couple the PSL pickoff into the fiber today for several hours, but got nowhere really, achieved a maximum coupling efficiency of ~10%. TBC tomorrow... Work done yesterday and today
Attachment #1 shows the current situation of the PSL table IR pickoff. It isn't the greatest photo but it's hard to get a good one of this setup. Now there is no need to open the Green PSL shutter for there to be an IR beat note.
All this lead me to conclude that I have reached at least some sort of local maximum. The AR coating of the lens has ~0.5% reflection at 8 degrees AOI according to spec, and EricG mentioned today that the fiber itself probably has ~4% reflection at the interface due to there not being any special AR coating. There is also the fact that the mode of the collimator isn't exactly Gaussian. Anyways I think this is a big improvement from what was the situation before, and I am moving on to debugging the ALS electronics.
There is 3.65mW of power coupled into the fiber - our fiber coupled PDs have a damage threshold of 2mW, and this 3.65mW does get split by 4 before reaching the PDs, but good to keep this number in mind. For a quick measurement of the PMC and X end PDH modulation depth measurements, I used an ND=0.5 filter in the beam path.
Attachment #1 - Photo of the revamped beat setup. The top panel has to be installed. New features include:
Attachment #2 - Power budget inside the box. Some of these FC/APC connectors seem to not offer good coupling between the two fibers. Specifically, the one on the front panel meant to accept the PSL light input fiber seems particularly bad. Right now, the PSL light is entering the box through one of the front panel connectors marked "PSL + X out". I've also indicated the beat amplitude measured with an RF analyzer. Need to do the math now to confirm if these match the expected amplitudes based on the power levels measured.
Attachment #3 - We repeated the measurement detailed here. The X arm (locked to IR) was used for this test. The "X" delay line electronics were connected to the X green beat PD, while the "Y" delay line electronics were connected to the X IR beat PD. I divided the phase tracker Hz calibration factor by 2 to get IR Hz for the Y arm channels. IR beat was at ~38MHz, green beat was at ~76MHz. The broadband excess noise seen in the previous test is no longer present. Indeed, below ~20Hz, the IR beat seems less noisy. So seems like the cleaning / electronics revamp did some good.
Further characterization needs to be done, but the results of this test are encouraging. If we are able to get this kind of out of loop ALS noise with the IR beat, perhaps we can avoid having to frequently fine-tune the green beat alignment on the PSL table. It would also be ideal to mount this whole 1U setup in an electronics rack instead of leaving it on the PSL table.
Photos + power budget + plan of action for using this box to characterize the green PDH locking to follow.
GV Edit: I've added better photos to the 40m Google Photos page. I've also started a wiki page for this box / the proposed IR ALS system. For the moment, all that is there is the datasheet to the Fiber Couplers used, I will populate this more as I further characterize the setup.
Is it better to mount the box in the PSL under the existing shelf, or in a nearby PSL rack?
Further characterization needs to be done, but the results of this test are encouraging. If we are able to get this kind of out of loop ALS noise with the IR beat, perhaps we can avoid having to frequently fine-tune the green beat alignment on the PSL table. It would also be ideal to mount this whole 1U setup in an electronics rack instead of leaving it on the PSL table
It seems like the main contribution to the RMS comes from the high frequency bump. When using the ALS loop to lock the arm to the beat, only the stuff below ~100 Hz will matter. Interesting to see what that noise budget will show. Perhaps the discrepancy between inloop and out of loop will go down.
I was having a chat with EricQ about this today, just noting some points from our discussion down here so that I remember to look into this tomorrow.
Can we make use of the Jetstor raid array for some kind of consolidated 40m CDS backup system? Once we've gotten everything of interest out of it...
I did some work today to see if I could use the IR beat for ALS control. Initial tests were encouraging.
I will now embark on the noise budgeting.
I am leaving the green beat electronics on the PSL table in the switched state for further testing...
The Fiber ALS box has been installed on the existing shelf on the PSL table. We had to re-arrange some existing cabling to make this possible, but the end result seems okay (to me). The box lid was also re-installed.
Some stuff that still needs to be fixed:
Beat spectrum post changes to follow.
To couple the spare NPRO into our Panda PM980 fibers, in order to carry out tests to characterize the fibers, in order to use them in FOL.
Manasa and I spent this morning building the setup to couple NPRO light into the fibers. We used two steering mirrors to precisely guide the beam into the coupler (collimator).
We also attached the lens to a moveable stage (in the z axis), so the setup could be fine tuned to put the beam waist precisely at the photodiode.
The fiber was attached to a fiber-coupled powermeter, so I would be able to tell the coupling efficiency.
During alignment, the NPRO was operating at 1.0 amps, roughly half of nominal current (2.1A).
I first placed the coupler at the distance that I believed the target waist of 231um to be.
Using the steering mirrors and the stage that holds the couple, I aligned the axes of the coupler and the beam.
Finally, I used the variable stage that the lens is attached to to fine tune the location of the target waist.
Once I was getting readings on the powermeter (~0.5nW), the laser was turned up to nominal current of 2.1A.
At this point, I and getting 120nW through the fiber.
While far from "good" coupling, it is enough to start measuring some fiber characteristics.
Tomorrow, I hope to borrow the beam profiler once again so as to measure the fiber mode.
Beyond this, I will be taking further measurements of the Polarization Extinction Ratio, the Frequency Noise within the fiber, and the effects of a temperature gradient upon the fiber.
Once these measurements are completed, the fiber will have been characterized, and will be ready for implementation in FOL.
We wanted to measure the mode coming out of the fibers, so we can later couple it to experimental setups for measuring different noise sources within the fiber. i.e. Polarization Extinction Ratio, Frequency Noise, Temperature Effects.
I used the beamscan mounted on a micrometer stage in order to measure the spot sizes of the fiber coupled light at different points along the optical axis, in much the same way as in the razorblade setup I used earlier in the summer.
I entered my data (z coordinates, spot size in x, spot size in y) into a la mode to obtain the beam profile (waist size, location)
Code is attached in .zip file.
After I took these measurements, Manasa pointed out that I need points over a longer distance. (These were taken over the range of the micrometer stage, which is 0.5 inches.)
I will be coming in to the 40m early on Monday to make these measurements, since precious beamscan time is so elusive.
Eventually, we will use this measurement to design optical setups to characterize Polarization Extinction Ratio, Frequency Noise, and temperature effects of the fibers, for further use in FOL.
The idea was to measure the profile of the light coming out of the fiber, so we could have knowledge of it for further design of measurement apparatuses, for characterization of the fibers' properties.
The method was the same as the last time I tried to measure the fiber mode.
This time I moved the beam profiler in a wider range along the z-axis.
Additionally, I adjusted the coupling until it gave ~1mW through the fiber, so the signal was high enough to be reliably detectable.
Measurements were taken in both X and Y transections of the beam.
The range of movement was limited by the aperture of the beam profiler, which cuts off at 9mm. My measurements stop at 8.3mm, as the next possible measurement was beyond the beam profiler's range.
I entered my data into A La Mode, which gave me a waist of 5um, at a location of z = -0.0071 m, that is to say, 7.1mm inside the fiber.
Note that in the plot, data points and fits overlap, and so are sometimes hard to distinguish from each other.
Code is attached.
Using this data, I will begin designing setups to measure fiber characteristics, the first of which being Polarization Extinction Ratio.
Eventually, the data collected from these measurements will be put to use in the frequency offset locking setup.
The previous data were flawed, in that they were taken in groups of three, as I had to move the micrometer stage which held the beamscan between holes in the optical table.
In order to correct for this, I clamped a straightedge (ruler) to the table, so I could more consistently align the profiler with the beam axis.
These data gave a waist w_o = 4um, located 6mm inside the fiber. While these figures are very close to what I would expect (3.3um at the end of the fiber) the fitting still isn't as good as I would like.
The fit given by ALM is below.
I would like to get a stage//rail so I can align the axes of the beam and profiler more consistently.
I would also like to use an aperture the more precisely align the profiler aperture with the beam axis.
Once these measurements have been made, I can begin assembling the setup to measure the Polarization Extinction Ratio of the fiber.
I repeated this process once more, this time using the computer controlled stage that the beam profiler is designed to be mounted to.
These data//fitting appears to be within error bars. The range of my measurements was limited when the beam width was near the effective aperture of the profiler.
This latest trial yielded a waist of 4um, located 2.9 mm inside the fiber for the X profile, and 3.0mm inside the fiber for the Y profile.
Code is attached in fiberModeMeasurement4.zip. Note that the z=0 point is defined as the end of the fiber.
We want a measurement of the fiber modes at either end, with the collimators, because these will be the modes that we'll be trying to match in order to couple light into the fibers, for FOL and/or future projects.
In order to measure these modes, I used the beam profiler (Thorlabs BP 209-VIS) to take measurements of the beam diameter (cut off at 13.5% of the amplitude) along the optical axis, for each of the fiber ends.
The ends are arbitrarily labelled End 1 and End 2.
For each measurement, the fibers were coupled to roughly 30%, or 25mW at the output.
Regarding the issue of free rotation in the collimator stages: while End 1 was relatively stable, End 2 tended to move away from its optimal coupling position. In order to correct for this, I chose a position where coupling was good, and repositioned the stage to that coordinate (124 degrees) before taking each measurement.
The data were then entered into A La Mode, which gave waist measurements as follows:
End 1--- X Waist: 197um at Z = 4.8mm Y Waist: 190um at Z = 13.6mm
End 2--- X Waist: 192um at Z = 7.4mm Y Waist: 190um at Z = 6.0mm
A La Mode code is attached in .zip file
These are the types of profiles that we will hopefully be matching the PSL and AUX lasers to, for use in frequency offset locking.
More characterization of the fibers is to follow, including Polarization Extinction Ratio.
We also hope to be testing the overall setup soon.
I pulled out the Fiber Optic Module for FOL from the rack inside the PSL table enclosure and modified it. The beat PDs were moved into the box to avoid breaking the fiber pigtail input to the PD.
The box has 3 input FC/APC connectors (PSL and AUX lasers) and 2 output FC/APC connectors (10% of the beatnote for the AUX lasers).
Attachment shows what is inside the box. The box will again go back on the rack inside the PSL enclosure.
Earlier today Q and I somewhat resurrected my old PER measurement setup so I could run the temperature characterization experiment.
Unfortunately, when I tried to use the fiber illuminator, no light came from the other end, causing me to fail my primary goal for the summer of "don't break anything." The fiber has been re-spooled and labeled appropriately. Also sorry.
In addition to this, Q and I scavenged parts from the telescopes on the PSL and Y End tables, which were either not functional, or needed to have their mode matching adjusted, since we're using the non-PM fibers for FOL, which have a different numerical aperture, and thus slightly different output modes.
Specifically, this is involved removing the rotational mounts, and appropriate beam dumping.
My "calorimeter" still remains intact, in case anyone wants to make this measurement in the future, as this is my last day in the lab.
It's also effective at keeping drinks cold, if you'd rather use it for that.
We want to characterize the sort of response the fibers have to temperature gradients along them (potentially altering indices of refraction, etc.)
I have constructed a sort of two chambered "calorimeter" (by which I mean some coolers and other assorted pieces of recycling.)
The idea is that half of the length of PM fiber resides in one chamber, and the other in the other.
One chamber will remain at an uncontrolled, stable temperature (as measured by thermocouple probe) while the other's temperature is varied using a heat gun.
Using this setup, one can measure losses in power, and effects on polarization within the fiber.
This is currently living on the electronics bench until tomorrow morning, and is a little fragile, just in case it needs to be moved.
To maintain PM fibers all the way through to the photodiode, I had ordered some PM versions of the 50/50 fiber beamsplitters from AFW technologies. They arrived some days ago, and today I installed them in the BeatMouth. Before installation, I checked that the ends of the fibers were clean with the fiber microscope. I also did a little cleanup of the NW corner of the PSL table, where the 1um MZ setup was completely disassembled. We now have 4 non-PM fiber beamsplitters which may be useful for non polarizaiton sensitive applications - they are stored in the glass-door cabinet slightly east of the IY chamber along the Y arm, together with all the other fiber-related hardware.
Anjali had changed the coupling of the beam to the slow axis for her experiment but I ordered beamsplitters which have the slow axis blocked (because that was the original config). I need to revert to this config, and then make a measurement of the ALS noise - if things look good, I'll also patch up the Y arm ALS. We made several changes to the proposed timeline for the summer but I'd like to see this ALS thing through to the end while I still have some momentum before embarking on the BHD project. More to follow later in the eve.
Get a fiber BS that is capable of maintaining the beam polarization all the way through to the beat photodiode. I've asked AFW technologies (the company that made our existing fiber BS parts) if they supply such a device, and Andrew is looking into a similar component from Thorlabs.
I looked into this a little more today.
This is a problem - such large shifts in the signal level means we have to leave sufficient headroom in the choice of RF amplifier gain to prevent saturation, whereas we want to boost the signal as much as possible. Moreover, this kind of operation of tweaking the fiber seating to increase the RF signal level is not repeatable/reliable. Options as I see it:
The fibers around the PSL table were shielded to avoid any tampering.
[Aidan, Tara, Joe]
We pulled out what used to be the LSC/ASC fiber from the 1Y3 arm rack, and then redirected it to the 1X1 rack. This will be used as the c1ioo 1PPS timing signal. So c1ioo is using the old c1iovme fiber for RFM communications back to the bypass switch, and the old LSC fiber for 1PPS.
The c1sus machine will be using the former sosvme fiber for communications to the RFM bypass switch. It already had a 1 PPS timing fiber.
The c1iscex machine had a new timing fiber already put in, and will be using the c1iscey vme crate's RFM for communication.
We still need to pull up the extra blue fiber which was used to connect c1iscex directly to c1sus, and reuse it as the 1PPS signal to the new front end on the Y arm.
Alex has said he'll come in tomorrow morning to install the new FB code.
I swapped the EX fiber for the PSL fiber in the polarization monitoring setup. There is a lot more power in this fiber, and one of the PDs was saturated. I should really have put a PBS to cut the power, but I opted for putting an absorptive ND1.0 filter on the PD instead for this test. I want to monitor the stability in this beam and compare it to the EX beam's polarization wandering.
It looks like the drift in polarization content in the PSL pickoff is actually much higher than that in the EX pickoff. Note that to prevent the P-pol diode from saturating, I put an ND filter in front of the PD, so the Y axis actually has to be multiplied by 10 to compare power in S and P polarizations. If this drift is because of the input (linear) polarization being poorly matched to one of the fiber's special axes, then we can improve the situation relatively easily. But if the polarization drift is happening as a result of time-varying stress (due to temp. fluctuations, acoustics etc) on the (PM) fiber from the PSL fiber coupler to the BeatMouth, then I think this is a much more challenging problem to solve.
I'll attempt to quantify the contribution (in Hz/rtHz) of beat amplitude RIN to phase tracker output noise, which will tell us how much of a problem this really is and in which frequency bands. In particular, I'm interested in seeing if the excess noise around 100 Hz is because of beat amplitude fluctuations. But on the evidence thus far, I've seen the beat amplitude drift by ~15 dB (over long timescales) on the control room network analyzer, and this drift seems to be dominated by PSL light amplitude fluctuations.
A follow-up on the discussion from today's lunch meeting - Rana pointed out that rotation of the fiber in the mount by ~5degrees cannot account for such large power fluctuations. Here is a 3 day trend from my polarization monitoring setup. Assuming the output fiber coupler rotates in its mount by 5 degrees, and assuming the input light is aligned to one of the fiber's special axes, then we expect <1% fluctuation in the power. But the attached trend shows much more drastic variations, more like 25% in the p-polarization (which is what I assume we use for the beat, since the majority of light is in this polarization, both for PSL and EX). I want to say that the periodicity in the power fluctuations is ~12hours, and so this fluctuation is somehow being modulated by the lab temperature, but unfortunately, we don't have the PSL enclosure temperature logged in order to compare coherence.
Steve: your plots look like temperature driven
The "beat length" of the fiber is quoted as <=2.7mm. This means that a linearly polarized beam that is not oriented along one of the special axes of the fiber will be rotated through 180 degrees over 2.7mm of propagation through the fiber. I can't find a number for the coefficient of thermal expansion of the fiber, but if temperature driven fluctuations are changing the length of the fiber by 300um, it would account for ~12% power fluctuation between the two polarizations in the monitoring setup, which is in the ballpark we are seeing...
I think the dominant cause for the fact that we were seeing huge swing in the power coupled into the fiber was that the beam being sent in was in fact not linearly polarized, but elliptically polarized. I've rectified this with the help of a PBS. Fiber has been plugged into my polarization monitoring setup. Let's monitor for some long stretch and see if the situation has improved.
What I did today.
1. I tried to align the IR input beam by aligning the two mirrors, to couple input light into the fibre.
2.I was unsuccessful for a long time even though I tried a lot of tricks.
3. I also tried to use the optical fault locator to superpose the IR beam spot onto the beam spot of the other laser to facilitate effective coupling.
4.But the crucial point was to superpose the input beam path in the perfect direction of the output beam path and not just the beam spot.(the input cone and the output cone are perfectly aligned).
5.After one whole day of trial and thought, I managed to couple light into the fibre, and saw the output beam spot on the screen-camera-monitor set-up which we had arranged. Eurekka !!;)
6.I then used a power meter to measure the input beam power and the output beam power.
7.It was a disappointing 2% . I had read in project reports of many students of a 20% success.
8.After a lot of subtle tweaking of the mirrors using the knobs, I managed to increase the percentage of output beam to 12%.
9. This is a workable level.
10.A day of lot of new learning! Pictures of the setup are attached.:)
We decided to use the 1064nm beam reflected from the Y1-1037-45-P mirror after the collimation lens following the doubling crystal for coupling into the optical fiber (ref 3843 and 3847 ).
We replaced a beam dump which was blocking this beam with a Y1-1037-45-P mirror and directed the beam into the fiber coupler with another Y1-1037-45-P. The power in this beam was about 1W. This has been stepped down to 10mW by introducing a reflective ND filter of OD=2. The reflected power has been dumped into a blade-stack beam dump.
Steve has ordered the The Visual Fault Locator from Fluke. It is expected to arrive within a day or two.
The Fluke Visual Fault locator (Visifault) arrived and I used it to couple 1064nm light into the single mode fibre at the south-end-table.
When the output end of the fiber is plugged into the Visifault the light emerges from at the south end (input side for 1064nm). This light is collimated with the fiber coupler at that end and serves as a reference for the optical axis along which the 1064 light must be directed. Once the two beams (red and 1064) are overlapped with the beam steering mirrors, the Visifault was disconnected from the fiber and the fibre output ( 1064 at the PSL table) is maximized by walking the beam at the input end and adjusting the collimation at the input.
The output of the fiber has been collimated with a fiber coupler.
7.5mW are incident on the input end and 1.3mW have been measured at the output. This output power is adequate for the observing the beats with PSL NPRO.
[Annalisa, Jenne, Rana, Steve]
We installed the fibres on cable trays the 1Y2 and the Control Room.
Still to do: find a power supply for the Fiboxes and plug everything in.
One of the things that we had talked about last night was the totally tiny amount of phase margin that we have in the CARM and DARM loops. DARM seemed to be the most obnoxious loop last night, so I focused on that today, although the CARM and DARM loops are pretty much identical.
(Q tells me via email that the phase budget has the same ~14 degree discrepancy between what we expect and what we measure as his estimate last night. However, the Caltech network issues prevented his posting an elog.)
So, we definitely need to figure out where this 14 deg is going, but for now, I wanted to see if I could recover a couple of extra degrees just by modifying the filters.
The original filters do seem to eat a lot of phase:
The short version of the story is that I didn't leave the filters changed at all. I reverted back to the last version of the filter file from Monday night, so currently everything is as it was.
I tried increasing the Q of the zeros on the cyan and brown filters, which would sacrifice some gain at ~20 Hz, but hopefully win us 10+ degrees of phase. This gave me a dip of about a factor of 2 between the new and old filters (all servo filters combined added up to this factor of 2 in magnitude) between ~20Hz - 70Hz.
When we were locked using DARM for just the Yarm (for the UGF servo commissioning), I took a spectra of the error signal (which was POY) as a reference, then loaded in my new filters. For the most part, the spectra didn't change (which is good, since the magnitude of the filter didn't change much.). The spectra was bigger though between 50-70Hz, in kind of a sharp bandpass-looking shape that I wasn't expecting. I don't know exactly why that's happening.
Anyhow, we tried the new filters once or twice with the full IFO, but kept losing lock. Since I clearly haven't put in enough thought yet for these (particularly, how much suppression do we really need? what are our requirements???), I reverted back to the filter file from last night. We continued locking, and checking out the new UGF servo that Diego is elogging about.
For the beam spot position tracking, I am wondering if there is any benefit to going for a wider field of view and getting the OSEMs in the frame? It may provide some "anchor points" against which whatever algorithm can calibrate the spot position against. But there are also several point scatterers visible in the current view, and perhaps the Gaussiam beam profile moving over them and tracking the scattered intensity from these point scatterers serves the same function? I don't know of a good solution to have a "switchable" field of view configuration in the already cramped camera enclosure though.
Also, I think it may be useful to have a cron job take a picture of MC2 and archive it (once a week? or daily?) to have some long term diagnostic of how the scattered light received by the camera changes over several months.
The GigE is focused now and I have closed the lid. I'm attaching a picture of the MC2 beam spot, captured using GigE at an exposure time of 400µs
This afternoon, after Q and Manasa finished recovering from the activities of the morning, I aligned the IFO, and went to the Yend to touch up the alignment of the green to the arm. I don't know if it was the alignment (I didn't do the PSL table), or I happened to have a good combination of laser temperatures, or what, but the Yend ALS noise was super good. After that, the low frequency noise contribution is different lock-to-lock, and I haven't discerned a pattern yet.
One thing that we want to try is to get DARM to AS55 so that we're entirely off of ALS (assuming we've already gotten CARM to sqrtInvTrans). However, according to Q's simulations, we have to get past arm power of a few before we are within the AS55 linewidth. I have a DTT running showing me the phase between AS55 and ALSdiff as I reduce the CARM offset, but I haven't been able to get close enough to see the sign flip when CARM is on sqrtInvTrans. If I just sweep through with both CARM and DARM on ALS, I see the sign flip. I've tried a few different things, but I have not successfully gotten a transition to AS55 while the arm powers were above 1. Empirically, I think I want them at at least 3 or 4.
Koji suggested locking the DRMI rather than PRMI, to widen the AS55 linewidth, but I haven't tried that tonight. Maybe tomorrow night.
I have made a ruidimentary lockloss plotting script, that I have put in ..../scripts/LSC/LockLossData, but I'm not satisfied with it yet. Somehow it's not catching the lockloss, even though it's supposed to run when the ALS watch/down scripts run. I'll need to look into this when I'm not so sleepy.
Q, can you please work on figuring out the phase tracker gain tracker? It will be nice to have that functional so we don't have to fret about the phase tracker gains.
Manasa, can you please estimate what kind of mode matching we have on the PSL table between the arm greens and the PSL green? We *do not* want to touch any optics at this point. Just stick in a power meter to see how much power we're getting from each beam, and then think about the peak height we see, and what that might tell us about our mode overlap. If we determine it is total crap, we can think about measuring the beams that go either toward the camera, or the DC PDs, since neither of those paths require careful alignment, and they are already picked off from the main beatnote path. But first, what is our current efficiency? Yarm is first, then Xarm, since Yarm seems worse (peak height is larger for non-00 modes!)
We developed a fairly sophisticated lockloss script at the sites, which you could try using as well. It's at:
It requires a reasonably up-to-date install of cdsutils, and the tconvert utility. It uses guardian at the sites to determine when locklosses happen, but you can use it without guardian by just feeding it a specific time to plot. It also accepts a list of channels to plot, one per line.
Just a reminder that a film crew will be here Monday morning, filming Christian Ott for some Discovery channel show.
They are slated to be here from 8am to 12:30pm or so. They will take a couple of shots inside the lab, and the rest of the filming should be of Christian in the control room (which they will "clean up" and fit with "sexy lighting"). I will try to be here the whole time to oversee everything.
I was trying to load some filters into the ASS so that I can try it out, but for some reason the filter banks aren't working - clicking the on/off buttons doesn't do anything, filters (which exist in the .txt file generated by foton) don't load.
I've emailed cds-announce to see if anyone has any ideas.
When the network / fb went bad this afternoon, I had been working on the ASS model, shortening the names of the filter banks to fix the problem from elog 7092. I wanted to finish working on that, so the ASS model is now rebuilt with slightly shorter names in the filterbanks (which fixes the problem of the filter banks not working).
I mentioned this to Jamie the other day, but here's the error that you get when the GoTo/From tags aren't working:
>>rtcds make c1ass
### building c1ass...
Parsing the model c1ass...
IPC 9 8 is C1:LSC-ASS_LSC
IPC 9 8 is ISHME
IPC 10 9 is C1:RFM-LSC_TRX
IPC 10 9 is IPCIE
IPC 11 10 is C1:RFM-LSC_TRY
IPC 11 10 is IPCIE
INPUT XARM_LSC_in is NOT connected
INPUT YARM_LSC_in is NOT connected
***ERROR: Found total of ** 2 ** INPUT parts not connected
make: *** [c1ass] Error 255
make: *** [c1ass] Error 1
I don't know why these tags weren't working, but there was a GoTo tag on the output of the LSC shmem block, and then Froms on each of the XARM_LSC_in and YARM_LSC_in. The other day I played around with a bunch of different things (grounding inputs, terminating outputs, whatever), but finally replacing the tags with identical ones freshly taken from CDS_PARTS made it happy.
Toyed around some more with the adaptive filters.
nTaps Downsampling factor Execution time average / max in ca. 3 min [us], (480 us available)
1000 16 110 / 150
2000 16 280 / 340
3000 16 380 / 470
4000 16 Over limit
Now we are running with Downsampling 32, 4000 Taps => max 410us execution time.
I tried to desynchronize the downsampled operations of the filters of the different DOFs. That however increased execution time by about 10%. So I undid that.
[Rana and Kevin]
I made a low pass filter for the piezo driver for the 2W laser that is now installed. The filter has a pole at 2.9 Hz. The transfer function is shown in attachment 1.
Attachment 2 shows the outside of the filter with the circuit diagram and attachment 2 shows the inside of the filter.
The missing filter files for ULPOS, URPOS, and so forth for the mode cleaner optics was due to the length of the names of the filters.
This was not a problem for the c1sus model because it was using its own name as the first 3 letters of its designation. A filter for the sus model would be called something like BS_TO_COIL_MTRX_0_0, while for the mcs it would be called SUS_MC1_TO_COIL_MTRX_0_0, an extra 4 characters.
However, the c1mcs model used the "top_name" feature which uses a subsystem box within the simlink model to rename all the channels. Apparently in the filter file, this means it has to add the top name to the front of everything, adding an additional 3 characters. This pushed things over the length limit.
A hard cap of 18 characters has been added to the FiltMuxMatrix.pm file (located in /cvs/cds/caltech/c1/, so that it will prevent this type of problem in the future by stopping at compile time and presenting a helpful error message.
I also fixed a bug with too many spaces in the feCodeGen.pl file when dealing with top_names and the filtMuxMatrix.pm preventing some .adl files from being generated.
Also of interest, MC3 appears to never have had F2A filters. For the moment we're running without them, but since they're just a fine tuning it shouldn't affect locking tonight.
Improbability factor of mode cleaner suspensions working tonight: ~20