40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 324 of 344  Not logged in ELOG logo
ID Date Author Type Category Subjectdown
  13987   Tue Jun 19 18:56:55 2018 JonUpdateGeneralAUX beam alignment issues

Not much progress today with the AUX cavity scans. I've determined there still are some alignment issues.

At the start of today a large AUX/PSL beat note was visible on the AS110 sensor, at a similar power as where we left off last night (-60 dBm). Proceeding from there, I attempted to reproduce Johannes' measurement of the cavity transmission resonances. I misaligned the X-arm, locked the Y-arm cavity, and scanned the AUX RF offset approximately 8 MHz in 2 kHz steps. This should have swept through two FSRs, but nothing was visible.

Further inspection revealed that none of the PSL light was making it back to through the AUX fiber to the PSL table. I take this to mean that the beam seen earlier on AS110 was the ITMY reflection, and that the AUX injection axis was no longer reaching ETMY. I also found that the AUX beam size just after the 90/10 beasmsplitter looks anomolously large. Maybe a lens was recently changed? In any case, the mode-matching looks like it is going to need to be readjusted.

  13989   Wed Jun 20 00:57:04 2018 johannesUpdateGeneralAUX beam alignment issues

We did swap a lens as discussed in elog 13968, but they both had f=100mm specified, the difference being one was AR-coated for 1064 and bi-convex, while the other one was plano-convex and had a different coating. The reason for the large beam spot was something else: The fiber wasn't sitting in the coupler properly. When reconnecting the fiber after taking it out make sure to align the key on the fiber end with the notch in the coupler before tightening. After discovering this the following was done:

  • Fixed fiber mounting situation
  • Tested AUX alignment into fiber on PSL table, was still good
  • The AUX polarization was aligned to the wrong fiber axis. I fixed this. The coupler on the PSL table has it's noth oriented vertically since we're using s-polarized light. The AS-table coupler is rotated by 90 degrees, such that the notch points to the side. This way we technically don't need any halfwaveplates for rotation. However, there are still current HWPs installed.
  • Locked both arms and ran dither alignment until satisfactory
  • Misaligned ITMX and ETMX, and further set the ITMX pitch offset to 0.0
  • Started overlapping the expectedly misaligned beams by eye. For this I turned the power of the deflected beam down to 50mV bias voltage, which gives the PSL and AUX lasers similar card-brightness on the shared path
  • Misaligned SRM more because there was still the strong prompt reflection coming out the AS port.
  • Restored phaselock between AUX and PSL, with beat at 30MHz between 1st-order diffracted in fiber and PSL
  • Immediately saw STRONG 30MHz RF signal on AG4395. Disappeared when blocking AUX, and optimized alignment brought the signal up to -10dBm, as shown in attachment #1
  • Checked YEND PDA10CF and saw a -80dBm RF signal at 30 MHz (#2), compatible with earlier observations.

Before leaving I restored the XARM alignment. SRM remains misaligned, LSC off. Alignment shouldn't change drastically over night, so I suggest when picking this work up tomorrow to directly look for the beats after phaselocking AUX and PSL

Attachment 1: as110_rf_30MHz.pdf
as110_rf_30MHz.pdf
Attachment 2: yend_rf_30MHz.pdf
yend_rf_30MHz.pdf
  14013   Sun Jun 24 23:13:46 2018 johannesUpdateGeneralAUX beam alignment issues

At some point we want to change the AUX injection on the AS table to interfere less with the normal interferometer path, and avoid 10/90 beamsplitters which produce a fair amount of ghosting. The plan is to replace the 99/1 BS whose reflection goes to AS110 and AS55, while the transmission goes to the AS camera, with a 90/10 BS as shown in the attachment. This results in ~10% less light on the PDs compared to the pre-AUX era. Between this BS and the AS camera there will be a second 90/10 BS that sends the AUX light into the IFO, so we end up with marginally less AUX power into the IFO and the same PSL power on the AS cam. We're short optics, so this has to wait until two new beamsplitters arrive from CVI.

Attachment 1: AS_AUX_SETUP.pdf
AS_AUX_SETUP.pdf
  13968   Thu Jun 14 22:45:05 2018 johannesUpdateGeneralAUX beam SRC alignment

[Jon, Gautam, Johannes]

Jon spent some time trying to align the AUX beam to the SRC today, I got to the game kind of late so maybe others can add more detail.

The AUX beam that is reflected by the SRM looks terribly misshapen - it is quite elongated in vertical direction. Unfortunately I didn't snap a picture of it - anybody? It seemed at first as if this could be clipping - but after confirming the alignment of the AUX beam with the PSL output beam with aligned SRM, a slow dither of the SRM just moved the ugly pattern on the AS camera with no change to its shape - so clipping is unlikely. I'm now thinking that this is just the output beam of the fiber coupler after propagating ~15 meters to the SRM and back - even though this aspheric lens triplet coupler is supposed to be super-duper. I found that if I loosen the fiber slightly and pull it back just a bit at least the spot on the AS camera becomes nice and round - so maybe the fiber just doesn't sit well in this collimator? Not sure why that would be. I checked the fiber tip with the microscope, and while there was some gunk present, the central region and the core were clear (still cleaned using the fiber cleaning kit, which got rid of the debris). Either way, before switching to a different collimator I think we should give the Guoy phase measurement a shot - after all there was plenty of RF signal present on both AS110 and the PDA10CF placed at the YEND.

Looking for rogue beams on the AS table, I started placing some beam dumps. There was one particularly strong source of stray beams - a lens that was labeled with KPX094AR.33_F100. It became apparent after alignment efforts to the IFO had moved the AUX beam signifcantly off-center on this lens. According to the label it should have an AR coating for 1064nm, however judging by the amount of reflected light, it was certainly NOT AR-coated for 1064nm. I replaced it with a bi-convex f=100mm lens with confirmed AR-behavior.

The AUX laser is currently shuttered.


Per our Wednesday meeting, some items to work on are

  • Align the zero-order AUX beam into a second collimator on the PSL table, so we can switch the fiber output and look for RF signals at the offset-phaselock frequency without the additional frequency shift from the AOM. This will simpligy the mode spectroscopy scheme significantly
  • Abandon the R10/T90 beamsplitters in favor of R90/T10 beamsplitters. We'll swap the large mirror in front of the AS camera with an R90/T10 BS, and follow it up with a second R90/T10 BS that sends the AUX beam to the IFO. This way we'll have identical power levels on AS110 and AS55, and still 90% of the current AUX light going into the IFO, but without strong secondary beams from R10/T90 optics.
  10299   Wed Jul 30 18:09:08 2014 HarryUpdateGeneralAUX and PSL Coupling Telescopes

 Purpose

These telescopes will be used to mode match//couple the dumped SHG light from both PSL and AUX (Y-Arm) lasers into PM fibers for use in FOL.

Methods

Using the waist measurements I made yesterday (29/7/14) as seed waists, I used a la mode to design coupling telescopes.

These are designed to match the output mode of the fibers with collimators.

AUXTelescope.m    PSLTelescope.png

 

 

ALM files are attached in .zip file.

AUXTelescopePlot.png PSLTelescopePlot.png

Moving Forward

Once the fibers are coupled, I will continue in assembling the Y-Arm FOL setup, using fiber coupled beam combiner and photodiodes.

I will also do the same procedure for the X-Arm, access permitting.

Attachment 2: AUXTelescope.png
AUXTelescope.png
Attachment 3: telescopes.zip
  11924   Sat Jan 9 00:39:15 2016 gautamUpdateLSCAUX Y Freq Noise re-measured
Quote:

With the Y end laser, I was able to lock the PLL with a lower actuation range (1.6MHz/V), and with the PSL in both the free-running and MCL locked configurations.

I took spectra (attached) with the same actuation range (3.2 MHz/V) for the AUX X+PSL and AUX Y+PSL combinations (PSL shutter closed) just to keep things consistent. It looks like there is hardly any difference between the two combinations - could the apparent factor of 3 worse performance of the X end laser have been due to different actuation ranges on the Marconi? 

I've not managed to take a spectrum for the proposed replacement Lightwave laser on the PSL table, though with Eric's help, I've managed to find the beatnote (at a temperature of 53.0195 degrees). I had to do some minor alignment tweaking for this purpose on the PSL table - the only optics I touched were the ones in the pink beam path in attachments 1 and 2 in this elog (the setup used to make the measurement is also qualitatively similar to attachment 3 in the same elog, except for the fact that we are feeding back to the Marconi and not the laser - a detailed sketch with specific components used will be put up later). I'll try and measure the frequency noise of this laser as well over the weekend and put up some spectra. 

With regards to possibly switching out the Lightwave on the PSL table for the (faulty?) Innolight at the X end, I've verified the following:

  • The beam-height from the Lightwave on the mount it is currently sitting on is the same as that from the Innolight on the X end table.
  • There is sufficient space on the X end table to house the Lightwave laser+mount

It remains to characterize the beam coming out from the Lightwave laser and do a mode matching calculation to see if we can use the same optics currently in place (with slight rearrangement) to realize a satisfactory mode-matching solution - I've obtained a beam profiler to do this from Liyuan and have the software setup, but have yet to do the beam scan - the plan is to do this on the SP table, but we've put off moving the Lightwave laser off the PSL table until we (i) establish conclusively that the X end laser is malfunctioning and (ii) check the frequency nosie of the Lightwave relative to the Aux lasers currently at the ends. 

The area around the Marconi is in a little disarray at the moment with a bunch of cables, SR560s, analyzers etc - I didn't want to disconnect the measurement setup till we're done with it. I have however turned both IR beat PDs on the PSL table off, and have reconnected the Marconi output to the Frequency Generation Unit and have set the carrier back to 11.066209MHz, +13dBm. 

Attachment 1: AuxPLL.pdf
AuxPLL.pdf
  11921   Fri Jan 8 14:47:33 2016 ericqUpdateLSCAUX Y Freq Noise measured

Here are some results from measuring the PSL / AUX Y beat. 

With the Y end laser, I was able to lock the PLL with a lower actuation range (1.6MHz/V), and with the PSL in both the free-running and MCL locked configurations. (In the latter, I had to do a bit of human-turning-knob servo to keep the control signal from running away). I also took a spectrum with the marconi detuned from the beat frequency, to estimate the noise from the PD+mixer+SR560. 

It looks like the AUX X laser is about 3 times noisier than the Y, though the Y laser looks more like a 10^5 noise-frequency product, whereas I thought we needed 10^4. 

Gautam is investigating the PSL / AUX PSL beat with Koji's setup now. 

Attachment 1: AUX_freqnoises.pdf
AUX_freqnoises.pdf
Attachment 2: AUXY_Jan8.zip
  11922   Fri Jan 8 20:02:49 2016 ranaUpdateLSCAUX Y Freq Noise measured

Unless this is the limit from the way you guys set up the PLL, it seems like there's no difference between the two lasers that's of any import. So then the locking problem has been something else all along - perhaps its noise in the X-PDF lock somehow? PDH box oscillations?

  10894   Tue Jan 13 13:22:54 2015 JenneUpdateGeneralAUX Y + PSL beat note at 1064nm: needs work

I'm super excited about this new frequency readbacklaugh, but I'm not sure that it's reliable yetfrown.  Without touching any settings, the readback is currently saying 78.6MHz, and is changing slightly (as is the FSS Slow Temp), so something is working.  However, the beatnote as measured on the spectrum analyzer is 158.2MHz.  So, either the calibration or the tracking or something isn't quite finished being tuned yet.cheeky

It's going to be super awesome when we have this though!!cool

  10895   Tue Jan 13 14:01:20 2015 manasaUpdateGeneralAUX Y + PSL beat note at 1064nm: needs work
Quote:

I'm super excited about this new frequency readback, but I'm not sure that it's reliable yet.  Without touching any settings, the readback is currently saying 78.6MHz, and is changing slightly (as is the FSS Slow Temp), so something is working.  However, the beatnote as measured on the spectrum analyzer is 158.2MHz.  So, either the calibration or the tracking or something isn't quite finished being tuned yet.

It's going to be super awesome when we have this though!!

As Jenne pointed out, this is still not fully tuned. 

For example, I found today that the frequency counter requires more power at the input >= -20dBm to measure frequency inputs < 40 MHz. Since the RFPD gives ~ -40dBm at its output, the ~20dB gain amplifier will not be enough to measure low frequencies in case the beat power at the PD drops (which is very much possible when the alignment drifts or things move around on the PSL table).  So I am shopping for an RF amplifier with higher gain to replace the current one. In the meantime, I will test the PID loop for set point frequency > 40MHz.

I have also observed the frequency difference between the measured frequencies on FC and the spectrum analyzer. I am not sure where this comes from as yet. 

At this point, the FC readout is only reliable enough to find a beatnote that is lost on the spectrum analyzer.

  10883   Fri Jan 9 14:01:17 2015 manasaUpdateGeneralAUX Y + PSL beat note at 1064nm

I worked around the PSL table today.

The Y+PSL output from the optical fiber module for FOL was fed to the input of the Thorlabs FPD310
200uW of incident light on the RFPD gave an RF signal of -70dBm as measured on a spectrum analyzer.

I swapped the beam splitter along the PSL path so that the incident power on the RFPD is ~1.5mW (Maximum incident power that the PD can tolerate is ~2mW).
This RF signal generated was - 43dBm which is still small for the input to the frequency counter module.

I checked this with a function generator and found that the frequency counter requires around -25 to -30 dBm at the input.

I plan to use the Minicircuits ZFL-1000ln that is on the IOO rack but not being used (This was used for green beatnote amplification but is not required/used anymore) to amplify the RF signal to the frequency counter.
If anyone has any objections to using this amplifier for the frequency counter, let me know.

 

  10893   Tue Jan 13 10:28:02 2015 manasaUpdateGeneralAUX Y + PSL beat note at 1064nm
Quote:
 

I plan to use the Minicircuits ZFL-1000ln that is on the IOO rack but not being used (This was used for green beatnote amplification but is not required/used anymore) to amplify the RF signal to the frequency counter.
If anyone has any objections to using this amplifier for the frequency counter, let me know.

The above mentioned amplifier has been used to amplify the input to the frequency counter. The frequency counter is now getting an input that it can read.

I have done an edit to the ALS medm screen and the PSL and AUX Y laser beat frequency is now readable.

  11936   Tue Jan 19 17:27:58 2016 gautamUpdateGreen LockingAUX X power investigations

Last week, Eric and I noticed that the green transmission levels at the PSL table seem much lower now than they did a month or two ago. To investigate this, I attempted to reproduce a power budget for the X endtable setup - see the attached figure (IR powers measured with calorimeter, green powers measured with Ophir power meter). A summary of my observations:

  • The measurements were all made at an AUX-X laser diode current of 1.90A, and laser crystal temperature of 47.41 degrees. The current was chosen on the basis of the AUX-X frequency noise investigations. The temperature was chosen as this is the middle of three end-laser temperatures at wich a beat-note can be found now. Why should this temperature have changed by almost 5 degrees from the value reported here? I checked on the PSL laser controller that the PSL temperature is 33.43 degrees. Turning up the diode current to 2A does not change the situation significantly. Also, on the Innolight datasheet, the tuning geometry graphs' X-axes only runs to 45 degrees. Not sure of what to make of this. I tried looking at the trend of the offset to the slow temperature servo to see if there has been some sort of long-term drift, but was unable to do so...
  • The IR power from the laser seems to have halved, compared to the value in Feb 2014. Is this normal deterioration over two years? Changing the laser diode current to 2A and the laser crystal temperature to ~42 degrees (the conditions under which the Feb 2014 measurements were taken) do not alter these numbers radically.
  • The green power seems to have become 1/4 its value in Feb 2014, which seems to be consistent with the fact that the IR power has halved.

It is worth noting that two years ago, the IR power from the AUX-Y laser was ~280 mW, so we should still be getting "enough" green power for ALS?

 

Attachment 1: X_END_POWER_BUDGET.JPG
X_END_POWER_BUDGET.JPG
  10996   Tue Feb 10 16:01:21 2015 manasaUpdateGeneralAUX X fiber coupled 72%

Plan C finally worked. We have 1.454mW of AUX X light at the PSL table (2mW incident on the fiber coupler). 

Attached is the layout of the telescope.

What I did:

I stuck in Lens 1 (f=200mm) and measured the beam width after the focus of the lens at several points. I fit the data and calculated the beam waist and its position after this lens. 

I used the calculated waist and matched it with an appropriate lens and target (fiber coupler) distance. I calculated the maximum coupling efficiency to be 77% for Lens 2 with f=50mm and the fiber coupler placed at 20cm from the waist of Lens1. I was able to obtain 72% coupling after putting the telescope together.

I locked the arms, ran ASS and brought back GTRX to its usual optimum value of ~0.5 counts after closing. We also have the X arm beatnote on the spectrum analyzer.

Notes:

There are still a couple of things to fix. The rejected beam from the beam sampler has to be dumped using a razor blade.

 

  11894   Mon Dec 21 02:29:49 2015 ericqUpdateLSCAUX X RIN measurements

I'll finish up the beat / frequency noise parts of the diagnosis tomorrow later, but I've done some investigation of the AUX X laser RIN. 

I placed a PDA255 at one of the rejected beams from the PBS on the downstream side of the IR faraday, making sure the power didn't saturate the PD. I measured the RIN on a SR785, and simultaneously looked at the signal on a 100MHz scope. 

The RIN has a very strong dependence on the laser diode current, and no noticable dependence on the crystal temperature or the presence of the PDH modulation / temperature control cables. Here are some traces, note that "nominal" current up until recently was 2.0A. 

When adjusting the diode current, a peak beings to appear in the tens of kHz, eventually noticible in the DC power trace on the scope. The point at which this occurs is not fixed.

At all times, I saw a strong intensity fluctuation at around 380-400kHz on the scope whose amplitude fluctuated a fair amount (at least 75mVrms over Vdc=6.5V, but would often be 2 or 3 times that).

I didn't look at the frequency noise while doing this, because the WiFi at the X end was too slow, I'll do more tomorrow in the daytime. 

Attachment 1: auxXRIN.pdf
auxXRIN.pdf
  11619   Fri Sep 18 11:59:08 2015 ericqUpdateLSCAUX X Laser Current Reverted

Once again, the transmitted X green beam was showing enormous intensity fluctuations (50x higher than normal). Last month, I reduced the AUX X laser current from 2.0A to 1.9A, which I thought had fixed it somehow.

However, when I sent to the end to check it out today, I found the SR560 which is there to amplify the green PDH error signal before being sent to the AA board was overloading. Not so surprising, since the error signal was similarly noisy as the transmitted light. 

I turned the SR560 gain down, and, after relocking, the transmitted light was stable. I've turned the AUX X laser current back up to 2.0A, it's previous nominal value, and the green transmitted light is still stable. 

I'm a little mystified that the 560 could intefere with the loop, since it is not in the feedback path. Could it be that when it is overloading, it sends garbage backwards out of the inputs? But even then, its input is not connected to the real error point, but the buffered monitor port. Could it be interfering via the power line?

Before, I had hesitated adding gain to the PDH board's monitor point for DAQ purposes, because the motivation of the port is to provide a 1:1 version of the real error signal, and I didn't want to add gain to the AA board, because we normally don't have gain in those boards, and I didn't want to surprise future people. The SR560 was meant to be temporary, but as often happens, it was forgotten. Now, I think I will add gain to the error monitor buffer stage of the PDH boards. 

  11533   Thu Aug 27 02:09:14 2015 ericqUpdateLSCAUX X Laser Current Changed

I spent some time tonight chasing down the cause of huge RIN in the X green PDH transmitted light, which I had started seeing on Monday. This was preventing robust locking, since the ALS sensing noise was ~10x worse above 50Hz, thus making the AO transition much flakier (though, impressively, not impossible!)

I went down to the X end, and found that turning the laser diode current down by 0.1A (from 2.0 to 1.9) smoothed things out completely. Unfortunately, this causes the power to drop, from GTRX of 0.45 to 0.3, but the ALSX sensitivity is unchanged, as compared with the recenent "out of loop" template. 

This also seems to have changed the temperatures of the good modes, as no beat was evident at the previously good temperature. Beats were found at +5400 and +10500 counts on the slow servo offset slider; I suspect the third lies around the edge of the DAC range which is why I couldn't uncover it. In any case, I've parked it at 10500 for now, and will continue locking; nailing it down more precisely and offloading the slider offset to the laser controller will happen during daytime work...

  13325   Thu Sep 21 01:32:00 2017 gautamUpdateALSAUX X Innolight AM measurement running

[rana,gautam]

We set up a measurement of the AUX X laser AM today. Some notes:

  • PDA 55 that was installed as a power monitor for the AUX X laser has been moved into the main green beam path - it is just upstream of the green shutter for this measurement.
  • AUX X laser power into the doubling crystal was adjusted by rotating HWP upstream of IR Faraday (original angle was 100, now it is 120), until the DC level of the PDA 55 output was ~2.5V on a scope (high impedance).
  • BNC-T was installed at the PZT input of the Innolight - one arm of the T is terminated to ground via 50 ohms. The purpose of this is to always have the output of the power splitter from the network analyzer RF source drive a 50 ohm load.
  • The output of the Green PDH servo to the Innolight PZT was disconnected downstream of the summing Pomona box - it is now connected to one output of a power splitter (borrowed from SR function generator used to drive the PZT) connected to the RF source output of the AG4395.
  • Other output of power splitter connected to input R of AG4395.
  • PDA55 output has been disconnected from CH5 of the AA board. It is connected to input A of the AG4395 via DC block.

Attachment #1 shows a preliminary scan from tonight - we looked at the region 10kHz-10MHz, with an IF bandwidth of 100Hz, 16 averages, and 801 log-spaced frequencies. The idea was to get an idea of where some promising notches in the AM lie, and do more fine-bandwidth scans around those points. Data + code used to generate this plot in Attachment #2.

Rana points out that some of the AM could also be coming from beam jitter - so to put this hypothesis to test, we will put a lens to focus the spot more tightly onto the PD, repeat the measurement, and see if we get different results.

There were a whole bunch of little illegal things Rana spotted on the EX table which he will make a separate post about.

I am running 40 more scans with the same params for some statistics - should be done by the morning.

Quote:

I borrowed the HP impedance test kit from Rich Abbott today. The purpose is to profile the impedance of the NPRO PZTs, as part of the AUX PDH servo investigations. It is presently at the X-end. I will do the test in the coming days.
 


Update 12:00 21 Sep: Attachment #3 shows schematically the arrangement we use for the AM measurement. A similar sketch for the proposed PM measurement strategy to follow. After lunch, Steve and I will lay out a longish BNC cable from the LSC rack to the IOO rack, from where there is already a long cable running to the X end. This is to facilitate the PM measurement.

Update 18:30 21 Sep: Attachment #4 was generated using Craig's nice plotting utility. The TF magnitude plot was converted to RIN/V by dividing by the DC voltage of the PDA 55 of ~2.3V (assumption is that there isn't significant difference between the DC gain and RF transimpedance gain of the PDA 55 in the measurement band) The right-hand columns are generated by calculating the deviation of individual measurements from the mean value. We're working on improving this utility and aesthetics - specifically use these statistics to compute coherence, this is a work in progress. Git repo details to follow.

There are only 23 measurements (I was aiming for 40) because of some network connectivity issue due to which the script stalled - this is also something to look into. But this sample already suggests that these measurement parameters give consistent results on repeated measurements above 100kHz.

TO CHECK: PDA 55 is in 0dB gain setting, at which it has a BW of 10MHz (claimed in datasheet).


Some math about relation between coherence \gamma_{xy}(f) and standard deviation of transfer function measurements:

\mathrm{SNR}(f) = \sqrt{\frac{\gamma_{xy}^{2}(f)}{1-\gamma_{xy}^{2}(f)}}

\sigma_{xy}^{2} = \frac{1-\gamma_{xy}^{2}(f)}{2N\gamma_{xy}^{2}(f)}|H(f)|^2  --- relation to variance in TF magnitude. We estimate the variance using the usual variance estimator, and can then back out the coherence using this relation.

\sigma_{\theta_{xy}} = \mathrm{tan}^{-1}\left [ \sqrt{\frac{1-\gamma_{xy}^{2}(f)}{2N\gamma_{xy}^{2}(f)}} \right ] --- relation to variance in TF phase. Should give a coherence profile that is consistent with that obtained using the preceeding equation.

It remains to code all of this up into Craig's plotting utility.

Attachment 1: Innolight_AM.pdf
Innolight_AM.pdf
Attachment 2: Innolight_AM.tar.gz
Attachment 3: IMG_7599.JPG
IMG_7599.JPG
Attachment 4: 20170921_203741_TFAG4395A_21-09-2017_115547_FourSquare.pdf
20170921_203741_TFAG4395A_21-09-2017_115547_FourSquare.pdf
  11917   Thu Jan 7 04:28:39 2016 ericqUpdateLSCAUX X Freq Noise measured

[ericq, Gautam]

Brief summary of tonights work:

  • Locked Marconi to AUX X vs PSL beat at around 320MHz, PSL shutter closed (i.e. both lasers free running)
  • Measured control signal spectrum at various laser diode currents, crystal temperatures. Oddly, spectra remained consistent across these variables. 
  • Measured OLG of PLL to calibrate into open-loop frequency noise of the beat, found UGF ~30kHz

Our "requirement" for the end laser is as follows: We expect to (and have in the past) achieved ALS sensitivity of 1Hz/rtHz at 100 Hz. If the end PDH loop is 1/f from 100Hz-10kHz, then we have 40dB of supression at 100Hz, meaning the free running AUX laser noise should be no more than 100Hz/rtHz at 100Hz.

So, if we expect both the PSL and AUX lasers to have this performance when free running, we would get the green curve below. We do not. frown


I'll post more details about the exact currents, temperatures and include calibrated plots for the >30kHz range later. Here's the OLG for kicks. 

Attachment 1: PLLspec.pdf
PLLspec.pdf
Attachment 2: PLL_OLG.pdf
PLL_OLG.pdf
  11919   Thu Jan 7 16:52:32 2016 ericqUpdateLSCAUX X Freq Noise measured

Here is some of the promised data. As mentioned, changing diode current and crystal temperature didn't have much effect on the frequency noise spectrum; but the spectrum itself does seem too high for our needs. 

At each temperature, we started measuring the spectrum at 1.8A, and stepped the current up, hoping to reach 2.0 A.

At 47.5 C, we were able to scan the current from 1.8 to 2.0 A without much problem. At 49.0C, the laser mode would hop away above 1.95A. At 50.4C it would hop away above 1.85A. The spectra were not seen to change when physically disconnecting the PZT actuation BNC from the rear of the laser. 

The flattening out at the upper end is likely due to the SR560 output noise. I foolishly neglected to record the output spectrum of it, but with the marconi external modulation set to 3.2MHz/V, the few Hz/rtHz above 20k translates to a signal on the order of uV/rtHz, which seems reasonable. 

Data and code attached. 

Attachment 1: AUXfreqnoise.pdf
AUXfreqnoise.pdf
Attachment 2: auxXmeasurements.zip
  11920   Thu Jan 7 19:04:25 2016 KojiUpdateLSCAUX X Freq Noise measured

The next step is to compare this data with the same measurement with the PSL and the AUX laser on the PSL table (or the end Y laser). If these show a lot lower noise level, we can say 1) the x-end laser is malfunctioning and 2) the y-end and AUX laser on the PSL are well low noise.

  11908   Tue Jan 5 02:54:38 2016 ericqUpdateLSCAUX X Freq Noise attempt

[ericq, Gautam]

We set out to lock a marconi to the IR fiber beat of PSL + AUX X to measure some frequency noise, and failed.

In short, the Marconi's 1.6MHz max external FM isn't enough oomph to stabilize the PLL error signal. It's actually evident on the Agilent that the beat moves around a few times more than that, which I should've noticed sooner... We could briefly "lock" the PLL for a few tenths of a second, but weren't able to get a spectrum from this.

We also tried using the digital phase tracker temperature servo for some help at ~DC; this worked to the extent that we didn't have to twiddle the Marconi carrier frequency to stay on top of the fringes as the beat wandered, but it didn't otherwise stabilize the beat enough to make a difference in locking the PLL.

I suppose one more thing to try is to lock the PSL laser itself to each AUX laser in turn via PLL, and look for different / excess noise.

The Green and IR beat electronics are a in a little bit of disarray at the moment, but it's not like anyone else is going to be using them for the time being...

  11910   Tue Jan 5 13:17:06 2016 ranaUpdateLSCAUX X Freq Noise attempt

The problem here is that the MC displacement noise is leading to large frequency excursions of the PSL beam. Options

  1. Feed back the low frequency PLL control signal to the MC2 length to suppress the excursion required by the Marconi. This is better than driving the laser, since the drive to the laser would be squashed by the MC locking loop.
  2. Put the beat signal through a divider? Don't know if this makes the Marconi more able to handle it.
  3. Turn on the MCL path. this will make the low frequency MC error signal go to the MC length, thereby reducing the low frequency feedback to the NPRO.
  11912   Tue Jan 5 16:33:45 2016 ericqUpdateLSCAUX X Freq Noise attempt

Turning on the MCL path (in addition to the MCL FF we always have on) let me lock the PLL for multiple seconds, but low frequency excursions still break it in the end. I was able to briefly observe a level of ~50Hz/rtHz at 1kHz, which may or may not be real. Tomorrow we'll send the PLL control signal to MC2, which should lock it up just fine and give us time to twiddle laser diode current, measure the PLL loop shape, etc. 

  16933   Tue Jun 21 14:59:22 2022 CiciSummaryGeneralAUX Transfer Function Loop Exploration

[Deeksha, Cici]

We learned about the auxillary laser control loop, and then went into the lab to identify the components and cables represented by our transfer functions. We connected to the SR785 inside the lab so that we can use it to insert noise next time, and measure the output in various parts of the control loop.

  17243   Tue Nov 8 11:18:39 2022 RadhikaUpdateAUXAUX PZT transfer function fitting + filtering

Here I describe efforts to cancel the AUX laser PZT mechanical resonances from ~200 kHz-400kHz. While these may not be the resonances we end up wanting to suppress, I chose this region as an exercise because it contains the most significant peaks.

The PZT transfer measurement was taken on 09/06 by myself and Anchal. The Moku:Go outputted a swept-sine (1kHz - 1MHz) I sent to the AUX laser PZT. The beat note between the AUX and frequency-doubled PSL was sent to the DFD, and the I and Q channels were routed back as input to the Moku:Go. We also took a calibration transfer function of the Moku:Go, sending output 1 to inputs 1 and 2. 

Almost all of the signal was present in the I channel, so I proceeded to use the I data for fitting/next steps. After normalizing the measured frequency response by the calibration measurement (and adjusting for the calculated time delays in the loop - see [17131]), I fit the resulting data using vectfit [Attachment 1]. I supplied the function with n_poles=16, which in reality fit for 16 complex pairs of poles. This complexity of fit was not necessary to capture the 3 prominent peaks, but would likely be needed to fit any of the more heavily-damped resonances. 

I chose to invert all fitted poles between 200 kHz and 367 kHz and the corresponding fitted zeros. The result of this filter applied to the original frequency response data can be seen in Attachment 2, where the blue-shaded region contains the inverted poles/zeros. In total, 9 pairs of poles and 9 pairs of zeros were inverted. 

Next steps:

- Determine which resonances we want to suppress
- Send filter coefficients to Moku:Go (write scripts to streamline)
- Set up Moku:Go in series in loop; take TF measurement
Attachment 1: AUX_PZT_TF_vectfit.pdf
AUX_PZT_TF_vectfit.pdf
Attachment 2: AUX_PZT_TF_filtered.pdf
AUX_PZT_TF_filtered.pdf
  17244   Tue Nov 8 16:56:33 2022 ranaUpdateAUXAUX PZT transfer function fitting + filtering

This looks really good to me. Rather than fully invert the plant, what we would like to do is now design a filter which allow this loop to have a high UGF and a high gain below 1 kHz. Anchal and Paco probably have gain requirements for this loop in the ALS-CAL paper they are writing. The loop would have the cavity transfer function, as well as the demod electronics for the green PDH loop.

In addition to the gain requirements, we would also like to have a phase margin > 30 deg, and a gain margin of > 10 dB.

 

  16152   Fri May 21 12:12:11 2021 PacoUpdateNoiseBudgetAUX PDH loop identification

[Anchal, Paco]

We went into 40m to identify where XARM PDH loop control elements are. We didn't touch anything, but this is to note we went in there twice at 10 AM and 11:10 AM.

  11715   Mon Oct 26 19:10:59 2015 gautamUpdateGreen LockingAUX PDH loop characterization

I began my attempts to characterize the PDH loops at the X end today. My goal was to make the following measurements:

  • Dark noise and shot noise of the PD
  • Mixer noise
  • Servo electronics noise 

which I can then put into my simulink noise-budget scheme for the proposed IR beat setup.

I've made an Optickle model of a simple FP cavity and intend to match the measured PDH error signal from the X end to the simulated error signal to get the Hz/V calibration. I'll put the plots up for these shortly.

With regards to the other measurements, I was slowed down by remote data-acquisition from the SR785 - I've only managed to collect the analyzer noise floor data, and I plan to continue these measurements during the day tomorrow. 

  11351   Wed Jun 10 03:19:58 2015 ericqUpdateLSCAUX PDH error measured in CDS

Looking over the old noise budget in the green locking paper, it seems the main technical noise sources were the AUX PDH error and DFD noise. I'm working on quantifying the current state of these noises. 

Rather than lugging out the analyzers every time I wanted to make a measurement of the AUX PDH error signals, I set out to make the existing digitized channels (ALS-[X/Y]_ERR_MON) usable for easier, and continuous, monitoring. Sadly, up until now the signals were poorly conditioned, and drowning in ADC noise. (When locked, the Y error signal was only +-10 counts!)

Of course, given the bandwidth of the green servos (10kHz), this won't tell us the full story of the what the green PDH lock is doing, but does indicate how much residual frequency noise exists in the ALS control band. 

I'm currently using SR560s at G=20 at each end to amplify the ERR MON outputs of the uPDH boards before sending them to the ADCs; now that I've found a gain that works, I'll modify the error point monitor buffer opamps inside the uPDH boards themselves during the daytime. 

The AUX Y error signal was going into an AA board with some funky filtering going on that I didn't want to mess with. Instead, I've moved the signal to the pentek generic board whose first four channels are used for the oplev segments, and the second quartet are unused, save for the TST channel I hooked up yesterday. 

On the pentek board, I changed the 4th order 800Hz lowpass to a 4th order 8kHz lowpass on the last three channels through some resistor swapping. (At first it was just the last two, but I found I was getting weird signals in the 32nd channel; and if I recall correctly from my cymac work, the 32 ADC channel is used for some timing signal or something...). I also turned off the 1:10 whitening filters on the last four channels via PCB jumper. 

I then unhooked the PZT drive and let the PDH error signals swing around, to calibrate the ADC counts into HZ. Now, the ALS-[X/Y]_ERR_MON_OUT_DQ are calibrated in green Hz! Here are the spectra.

As we've seen in the past (ELOG 10464), the X green is limited by the dark noise of the PD from 10-100Hz. This isn't so great. The RMS noise from 300Hz downwards (which is maybe the band where the ALS control would inject noise into the mirror motion) is about Y:10Hz X:40Hz.

During this time, the test masses were not under any longnitudinal control, so I'm not sure why there is such a difference in the height of the suspension resonance peaks, unless there's some differene in the low frequency PDH TFs that I've forgotten about. 

Now, with these references, we can easily check if the PDH loops change qualitatively over longer time periods.

I'll be including the effect of these noises in the upcoming revised ALS noise budget.

Attachment 1: AUXspectra.png
AUXspectra.png
  13994   Thu Jun 21 09:33:02 2018 JonUpdate AUX Mode Scans of YARM, PRC cavities

[Jon, Keerthana, Sandrina]

Yesterday we carried out preliminary proof-of-concept measurements using the new AS-port-injected AUX laser to resolve cavity mode resonances.

At the time we started, I found the beat note levels consistent with what Johannes had reported the night before post-realignment. Hence we did not change the AUX alignment.

Test 1: YARM Mode Scan

  • IFO locked in YARM configuration on carrier.
  • Confirmed the presence of a -80 dBm beat note on the temporary YEND broadband PD (i.e., at the cavity transmission).
  • Slowly canned the RF offset of the AUX laser from 50 MHz (nominal) to 60 MHz in 10 kHz steps.
  • Attachment 1 shows the measured scan in "max hold" mode. The bottom panel is the transmission spectrum and the top panel is the reflection, with the AUX/PSL carrier-carrier beat note visible to the far left. In addition to the FSR, it looks to me like the scan resolves at least two HOMs.

Test 2: PRC Mode Scan

  • IFO locked in PRMI configuration on carrier.
  • Moved the temporary 150 MHz PDA10CF from the YEND to an unused pickoff of the REFL33 beam (i.e., the PRC transmission of the AUX beam). There was an existing 50-50 beamsplitter just before REFL33 whose reflected beam was directed onto a beam dump. The PD is now placed in that location. The modification to the AS table is shown in Attachment 2.
  • We made a similar slow scan of the AUX RF offset over ~35 MHz in 10 kHz steps.
  • We resolve the 22 MHz FSR, but it is apparent that an incoherent "max-hold" analyzer measurement is inadequate. The problem is that in max-hold mode, because the 11 MHz-spaced PSL sidebands also beat with the AUX subcarrier, we measure a messy superposition of the PSLcarrier-AUXcarrier beat AND all of the PSLsideband-AUXcarrier beats. The next step is to use the AOM to make a coherent measurement at only the frequency of PSL/AUX carrier-carrier beat.

The SURFs have the data from last night's scans and will be separately posting plots of these measurements. We'll continue today with mode scans using AM sidebands rather than the AUX RF offset.

Attachment 1: YARM_AUX_RF-offset_scan.pdf
YARM_AUX_RF-offset_scan.pdf
Attachment 2: temp_broadband_refl33.pdf
temp_broadband_refl33.pdf
  10349   Thu Aug 7 17:09:53 2014 HarryUpdateGeneralAUX Coupling In Progress

 I'm currently in the process of coupling dumped SHG light from the Y arm end table into fibers for FOL.

The main point is that the NPRO at that end in shuttered, because I wasn't sure whether or not leaving it open would've set anything on fire.

  10360   Sun Aug 10 00:54:54 2014 HarryUpdateGeneralAUX Couping

The Y End laser dumped SHG light has been coupled into the yellow fiber that terminates at the PSL table.

It's not super stably coupled, and only at 5mW. I'll be interested to see what it is on monday.

  14035   Tue Jul 3 11:59:10 2018 JonUpdateAUXAUX Carrier Scan of Y-Arm Cavity

I made the first successful AUX laser scan of a 40m cavity last night.

Attachment #1 shows the measured Y-end transmission signal w.r.t. the Agilent drive signal, which was used to sweep the AUX carrier frequency. This is a distinct approach from before, where the carrier was locked at a fixed offset from the PSL carrier and the frequency of AM sidebands was swept instead. This AUX carrier-only technique appears to be advantageous.

This 6-15 MHz scan resolves three FSR peaks (TEM00 resonances) and at least six other higher-order modes. The raw data are also enclosed (attachment #2). I'll leave it as an excercise for the SURFs to compute the Y-arm cavity Gouy phase.

Attachment 1: yarm_carrier_trans.pdf
yarm_carrier_trans.pdf
Attachment 2: AG4395A_02-07-2018_185504.txt
# AG4395A Measurement - Timestamp: Jul 02 2018 - 18:55:04
#---------- Measurement Parameters ------------
# Start Frequency (Hz): 6000000.0, 6000000.0
# Stop Frequency (Hz): 15000000.0, 15000000.0
# Frequency Points: 801, 801
# Measurement Format: LOGM, PHAS
# Measuremed Input: AR, AR
#---------- Analyzer Settings ----------
# Number of Averages: 16
# Auto Bandwidth: Off, Off
... 807 more lines ...
  3442   Thu Aug 19 11:38:48 2010 AlastairUpdateComputersATF wiki

The ATF wiki page doesn't seem to be working any more.  Does anyone know where this is held so we can try to get it back online?  Thanks

  3443   Thu Aug 19 12:06:07 2010 AlastairUpdateComputersATF wiki

Quote:

The ATF wiki page doesn't seem to be working any more.  Does anyone know where this is held so we can try to get it back online?  Thanks

 I phoned Phil Ehrens and found out that all these wikis have been moved to a new wiki site

The ATF wiki can now be found here

I have updated the link from the 40m wiki to reflect this

  8495   Fri Apr 26 10:50:07 2013 AnnalisaUpdateABSLATF laser on PSL

The ATF NPRO auxiliary laser has been moved on the PSL table. All the optics for beat note measurement are in place and alignment has been done.

The setup for this measurement is the same as described in elog 8333.

  15315   Fri May 1 01:49:55 2020 gautamUpdateALSASY commissioning

Summary:

It appears that the EY green steering PZTs have somehow lost their bipolar actuation range. I will check on them the next time I go to the lab for an N2 switch.

Details:

  • Yuki installed the EY green PZTs and did some initial setup of the RTCDS model. 
  • But we don't have a functional dither alignment servo yet, which is mildly annoying. So I thought I'll finally finish my SURF project.
  • There were several problems with the signal flow, MEDM screens etc.
  • I rectified these, and set up some operational scripts, burt snapshots etc in $SCRIPTS/ASY. The c1asy and c1als models were also modified, recompiled and restarted, everything appears to have come back online smoothly.
  • The LO frequencies/amplitudes, demod filter gains and demod phases were chosen to have a signal mostly in the _I quadrature of the demodulated signal when the alignment is slightly disturbed from optimal (monitored after the post-demod LPF).
  • While trying to close the integrator loops, I found that I appear to only have monopolar actuation ability (positive DAC output changes the alignment, negative DAC output does nothing).

Could be that the power outage busted something in the drive electronics. 

  15316   Fri May 1 22:44:17 2020 gautamUpdateALSASY M2 PZT damaged

I went to EY and saw that the HV power supply was only putting out 50 V and had hit the current limit of 10 mA (nominally, it should be 100 V, drawing ~7mA). This is definitely a problem that has come up after the power shutdown event, as when I re-energized the HV power supply at EY, I had confirmed that it was putting out the nominal values (the supply was not labelled with these nominal numbers so I had to label it). Or maybe I broke it while running the dither alignment tests yesterday, even though I never drove the PZTs above 50 Hz with more than 1000cts (= 300 mV * gain 5 in the HV amplifier = 1.5 V ) amplitude.

The problem was confirmed to be with the M2 PZT (YAW channel) and not the electronics by driving the M2 PZT with the M1 channels. Separately, the M1 PZT could be driven by the M2 channels. I also measured the capacitance of the YAW channels and found it to be nearly twice (~7 uF) of the expected 3 uF - this particular PZT is different from the three others in use by the ASX and ASY system, it is an older vintage, so maybe it just failed? 😔 

I don't want to leave 100 V on in this state, so the HV supply at EY was turned off. Good GTRY was recovered by manual alignment of the mirror mounts. If someone has a spare PZT, we can replace it, but for now, we just have to live with manually aligning the green beam often.

Quote:

Could be that the power outage busted something in the drive electronics. 

  15317   Sat May 2 02:35:18 2020 KojiUpdateALSASY M2 PZT damaged

Yes, we are supposed to have a few spare PI PZTs.

  14716   Mon Jul 1 20:27:44 2019 gautamUpdateASCASX tuning

Summary:

To practise the dither alignment servo tuning, I decided to make the ASX system work again (mainly because it has fewer DoFs and so I thought it'd be easier to manage). Setup is: dither PZT mirrors on EX table-->demodulate green transmission at the dither frequencies-->Servo the error signals to 0 by an integrator.

Details:

  1. Started by checking the dither lines are showing up with good SNR in GTRX. They are, see Attachment #1. The dither lines are at 18.23 Hz, 27.13 Hz, 53.49 Hz and 41.68 Hz, and all of them show up with SNR ~100.
  2. Hand-aligned the beam till I got a maximum of GTRX ~ 0.35. This is lower than the usual ~0.5 I am used to - possibilities are (i) in the process of plugging in the BNC cable to the rear of the EX laser for my PLL investigations, I disturbed the alignment into the SHG crystal ever so slightly and I now have less green light going into the cavity or (ii) there is an iris on the EX table just before the green beam goes into the vacuum on which it is getting clipped. IIRC, I had centered the GTRX camera view such that the spot was well centered in the field of view, but now I see substantial mis-centering in pitch. So the cavity alignment for IR could also be sub-optimal (although I saw TRX ~1.15). Anyways, I decided to push on.
  3. Introduced a deliberate offset in a given DoF, e.g. M1 PIT. Then I looked at the demodulated error signals (filtered through an RLP0.5 filter post demodulation, so the 2f component should be attenuated by 100 dB at least), and tuned the demod phase until most of the signal appeared in the I-phase, which is what is used for servoing. The Q-phase signals were ~x10 lower than their I-phase counterparts after the tuning.
  4. Checked the linearity of the error signal in response to misalignment of a given DoF. I judged it to be sufficiently linear for all four DoFs about the quadratic part of the GTRX variation.
  5. Tweaked the overall servo gains to have the error signals be driven to 0 in ~10 seconds.
  6. There was quite significant cross-coupling between the DoFs - why should this be? I can understand the PIT->YAW coupling because of imperfect mounting of the PZT mounted mirror in a rotational sense, but I don't really understand the M1->M2 coupling.
  7. Nevertheless, the servo appears to work - see Attachment #2.

The adjusted demod phases, servo gains were saved to the .snap file which gets called when we run the "DITHER ON" script. Also updated the StripTool template.

I plan to repeat similar characterization on the IR dither alignment servos. I think the tuning of the ASS settings can be done independently of figuring out the mystery of why the TRY level is so low.

Attachment 1: ASX_ditherlines.pdf
ASX_ditherlines.pdf
Attachment 2: ASX.png
ASX.png
  9018   Fri Aug 16 13:25:50 2013 KojiUpdateASSASX model/screen cleaning up

[Koji Manasa]

Yesterday we cleaned up the ASX model and screens to have more straight forward structure of the screen
and the channel names, and to correct mistakes in the model/screens.

The true motivation is that I suspect the excess LF noise of the X arm ALS can be caused by misalignment
and beam jitter coupling to the intensity noise of the beat. I wanted to see how the noise is affected by the alignment.
Currently X-end green is highly misaligned in pitch.

- Any string "XEND" was replaced by "XARM", as many components in the system is not localized at the end table.

- The name like "XARM-ITMX" was changed to "XARM-ITM". This makes easier to create the corresponding model for the other arm.

- There was some inconsistency between the MEDM screens and the ASX model. This was fixed.

- A template StripTool screen was created. It is currently saved in users/koji/template as ASX.stp.
  It will be moved to the script directory once it's usefulness is confirmed.


The next step is to go to the end table and manually adjust M2 mirror while M1 is controlled by the ASX.
The test mass dithering provides the error signal for this adjustment but the range of the PZT is not enough
to make the input spot position to be controlled. In the end, we need different kind of matching optics
in order to control the spot position. (But is that what we want? That makes any PZT drift significantly moves the beam.)

  8982   Wed Aug 7 22:18:43 2013 KojiUpdateASCASS update

While Gautam is working on the Xarm green ASS...

The EPICS monitor points for the ASS actuators were added to the ASS model.

This will be used for the offloading the ASS actuations to the alignment biases.
As this modification allowed us to monitor the actuation apart from the dithering,
now we can migrate the ASS actuation to the fast alignment offset on the suspension.
This modification to the offset moving scripts were also done.

Screenshot-Untitled_Window.png

  7100   Tue Aug 7 03:20:56 2012 JenneUpdateASSASS setup, on, off scripts written

I wrote new setup, on and off scripts for the arm ass.  They take the arm as an argument, so it's the same script for both arms.  Scripts are in ...../scripts/ASS/ , and have been checked in to the 40m svn.

So far the on script doesn't really do anything, since I haven't chosen values for the CLKGAINs of the lockins.  The old values were 30 for lockins 12, 14, 27, 29 and 250 for lockins 7, 9, 22, 24.  Unfortunately, I have no memory of which lockin means what in the old numbered system.  I'll have to look that up somehow.  Or, just dither the optics using some value and look at the spectrum to see the resulting SNR and just pick something that gives me reasonable SNR.

I modified the ASS model slightly:

* Added an overall gain to the ASS_DOF2 library part, between the matrix and the servo inputs so we can do soft startups.  Self - remember that the main ASS screen needs to be modified to reflect this!

* Rearranged the order that the demodulated signals go into the matrix.  I hadn't paid attention, and the old ordering had the transmission (TRX/TRY) demod signals interleaved with the LSC demod signals.  I've changed it to be all the TR signals, then all the LSC signals.  I think this makes more sense, since we will use these inputs separately, so now they're on different halves of the matrix.

  8980   Wed Aug 7 19:16:20 2013 JenneUpdateASCASS setting up accelerated more

I have furthered Koji's work, and moved the filter on/off state for all the filter banks also to the burt snapshot.  

Turning on the ASS is now much faster than it was originally, with the ezcawrites in series.

  8977   Wed Aug 7 15:32:37 2013 KojiUpdateASCASS setting up accelerated (slightly)

I moved bunch of ezcawrite from the ASS Dither On script to a snapshot file.

This accelerated a half of the "up" time but still switching part is not in the snapshot.

If you find anything wrong with ASS, please notify me.

  6677   Thu May 24 16:13:05 2012 yutaUpdateComputersASS scripts on new ubuntu machines

[Den, Yuta]

Background:
 ASS and many other scripts don't work on new ubuntu machines.

What we did:
1. Installed C-shell on rossa and rosalba(Ubuntu machine).
  sudo apt-get insall csh

2. Find out that
  /opt/rtcds/caltech/c1/scripts/AutoDither/alignY

runs, but
  /opt/rtcds/caltech/c1/scripts/medmrun /opt/rtcds/caltech/c1/scripts/AutoDither/alignY

doesn't run. It gives us the following error messages.

ezcawrite: error while loading shared libraries: libca.so: cannot open shared object file: No such file or directory
ezcaswitch: error while loading shared libraries: libca.so: cannot open shared object file: No such file or directory

Result:
 ASS scripts run on rossa and rosalba, but not with medmrun.
 At least ASS scripts run on pianosa(ubuntu machine) with medmrun. So we decided to wait for JAMIE to fix it.

  6684   Fri May 25 17:50:38 2012 JamieUpdateComputersASS scripts on new ubuntu machines

Quote:

[Den, Yuta]

Background:
 ASS and many other scripts don't work on new ubuntu machines.

What we did:
1. Installed C-shell on rossa and rosalba(Ubuntu machine).
  sudo apt-get insall csh

2. Find out that
  /opt/rtcds/caltech/c1/scripts/AutoDither/alignY

runs, but
  /opt/rtcds/caltech/c1/scripts/medmrun /opt/rtcds/caltech/c1/scripts/AutoDither/alignY

doesn't run. It gives us the following error messages.

ezcawrite: error while loading shared libraries: libca.so: cannot open shared object file: No such file or directory
ezcaswitch: error while loading shared libraries: libca.so: cannot open shared object file: No such file or directory

Result:
 ASS scripts run on rossa and rosalba, but not with medmrun.
 At least ASS scripts run on pianosa(ubuntu machine) with medmrun. So we decided to wait for JAMIE to fix it.

Apparently the environment was not being properly inherited by the scripts launched from medmrun.  We modified the medmrum script so that it executes things with an interactive shell ("bash -i -c ...") and this fixed the problem (by assuring that it sources all the interactive environment configs (i.e. ~/.bashrc)).  I'm still not sure why we were seeing different behavior on pianosa, but at least the solution we have now should be robust.

As a reminder, all scripts launched from MEDM should use medmrun:

/opt/rtcds/caltech/c1/scripts/medmrun
  5817   Sat Nov 5 00:04:23 2011 kiwamuUpdateASCASS scripts gone

Did somebody delete all the scripts in /opt/rtcds/caltech/c1/scripts/ASS ?

  5818   Sat Nov 5 00:24:13 2011 SureshUpdateASCASS scripts gone

Quote:

Did somebody delete all the scripts in /opt/rtcds/caltech/c1/scripts/ASS ?

 I have moved all the MC_ASS scripts to a directory called MC under ASS

 

ELOG V3.1.3-