40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
 40m Log, Page 19 of 335 Not logged in
ID Date Author Type Category Subject
13123   Mon Jul 17 16:22:01 2017 SteveUpdateSUSruby wire standoff pictures

Bluebean Optical Tech Limited of Shanghai delivered 50 pieces red ruby prisms with radius.  The first prism pictures were taken at June 5

and it was retaken again as BB#1 later

More samples were selected randomly as one from each bag of 5 and labeled as BB#2.......6

The R10 mm radius can be seen agains the  ruler edge.  The v-groove edge was labeled with blue marker and pictures were taken

from both side of this ridge. The top view is shown as the wire laying across on it.

SOS sus wire of 43 micron OD used as calibration as it was placed close to the side that it was focused on.

The V-groove ridge surface quality was evaluated based on as scale of 1 – 10 with 10 being the most positive.

 BB# Edge quality score 1 4 2 8 3 3 4 9.5 5 2 6 9

Remaining thing to examin, take picture of the contacting ridge to SOS from the side.

Attachment 1: contacting_ridge.bmp
Attachment 2: contacting_ridge.png
6270   Fri Feb 10 15:46:59 2012 steveUpdateSUSruby wire standoff

Finally I found a company who can do Koji's improved  -hard to make-  specification on ruby or sapphire wire standoff.

NOT POLISHED excimer laser cut, wire groove radius R 0.0005" + - 0.0002"

250 ea at 50 pieces of order 6796 Tue Jun 12 00:15:51 2012 JenneUpdateComputersrtcds: command not found We can't compile any changes to the LSC or the GCV models since Jamie's new script / program isn't found. I don't know where it is (I can't find it either), so I can't do the compiling by hand, or point explicitly to the script. The old way of compiling models in the wiki is obsolete, and didn't work :( This means we can't (a) record TRY or (b) add the Q quadrature of the beat PD to the real time system tonight. We're going to try just using Yuta's pynds script to capture data in real time, so we can keep working for tonight. 6801 Tue Jun 12 11:25:05 2012 JamieUpdateComputersrtcds: command not found  Quote: We can't compile any changes to the LSC or the GCV models since Jamie's new script / program isn't found. I don't know where it is (I can't find it either), so I can't do the compiling by hand, or point explicitly to the script. The old way of compiling models in the wiki is obsolete, and didn't work :( Sorry about that. I had modified the path environment that pointed to the rtcds util. The rtcds util is now in /opt/rtcds/caltech/c1/scripts/rtcds, which is in the path. Starting a new shell should make it available again. 6807 Tue Jun 12 17:46:09 2012 JenneUpdateComputersrtcds: command found Quote:  Quote: We can't compile any changes to the LSC or the GCV models since Jamie's new script / program isn't found. I don't know where it is (I can't find it either), so I can't do the compiling by hand, or point explicitly to the script. The old way of compiling models in the wiki is obsolete, and didn't work :( Sorry about that. I had modified the path environment that pointed to the rtcds util. The rtcds util is now in /opt/rtcds/caltech/c1/scripts/rtcds, which is in the path. Starting a new shell should make it available again. Added TRX and TRY and POY11_I_ERR and POX11_I_ERR to the c1lsc.mdl using a new-style DAQ Channels block, recompiled, installed, started the model, all good. Restarted the daqd on the framebuilder, and everything is green. I can go back and get recorded data using dataviewer (for the last few minutes since I started fb), so it all looks good. Note on the new DAQ Channels block: Put the text block (from CDS_PARTS) at the same level as the channel you want to save, and name it exactly as it is in the model. The code-generator will add the _DQ for you. i.e. if you define a channel "TRY_OUT_DQ" in the lsc model, you'll end up with a channel "C1:LSC-TRY_OUT_DQ_DQ". 4247 Thu Feb 3 17:25:03 2011 josephbUpdateComputersrsync script was not really backing up /cvs/cds So today, after an "rm" error while working with the autoburt.pl script and burt restores in general, I asked Dan Kozak how to actually look at the backup data. He said there's no way to actually look at it at the moment. You can reverse the rsync command or ask him to grab the data/file if you know what you want. However, in the course of this, we realized there was no /cvs/cds data backup. Turns out, the rsync command line in the script had a "-n" option. This means do a dry run. Everything *but* the actual final copying. I have removed the -n from the script and started it on nodus, so we're backing up as of 5:22pm today. I'm thinking we should have a better way of viewing the backup data, so I may ask Dan and Stewart about a better setup where we can login and actually look at the backed up files. In addition, tomorrow I'm planning to add cron jobs which will put changes to files in the /chans and /scripts directories into the SVN on a daily basis, since the backup procedure doesn't really provide a history for those, just a 1 day back backup. 11161 Mon Mar 23 19:30:36 2015 ranaUpdateComputer Scripts / Programsrsync frames to LDAS cluster The rsync job to sync our frames over to the cluster has been on a 20 MB/s BW limit for awhile now. Dan Kozak has now set up a cronjob to do this at 10 min after the hour, every hour. Let's see how this goes. You can find the script and its logfile name by doing 'crontab -l' on nodus. 11288 Wed May 13 09:17:28 2015 ranaUpdateComputer Scripts / Programsrsync frames to LDAS cluster Still seems to be running without causing FB issues. One thought is that we could look through the FB status channel trends and see if there is some excess of FB problems at 10 min after the hour to see if its causing problems. I also looked into our minute trend situation. Looks like the files are comrpessed and have checksum enabled. The size changes sometimes, but its roughly 35 MB per hour. So 840 MB per day. According to the wiper.pl script, its trying to keep the minute-trend directory to below some fixed fraction of the total /frames disk. The comment in the scripts says 0.005%, but I'm dubious since that's only 13TB*5e-5 = 600 MB, and that would only keep us for a day. Maybe the comment should read 0.5% instead...  Quote: The rsync job to sync our frames over to the cluster has been on a 20 MB/s BW limit for awhile now. Dan Kozak has now set up a cronjob to do this at 10 min after the hour, every hour. Let's see how this goes. You can find the script and its logfile name by doing 'crontab -l' on nodus. 11299 Mon May 18 14:22:05 2015 ericqUpdateComputer Scripts / Programsrsync frames to LDAS cluster  Quote: Still seems to be running without causing FB issues. I'm not so sure. I just was experiencing some severe network latency / EPICS channel freezes that was alleviated by killing the rsync job on nodus. It started a few minutes after ten past the hour, when the rysnc job started. Unrelated to this, for some odd reason, there is some weirdness going on with ssh'ing to martian machines from the control room computers. I.e. on pianosa, ssh nodus fails with a failure to resolve hostaname message, but ssh nodus.martian succeeds. 375 Thu Mar 13 12:11:58 2008 aivanovUpdateComputer Scripts / Programsrouting PEM -> ASS -> SUS_MCL on ASS RFM 1 has PEM signals at float at 0x100000 has c0dcu1 first ICS110B chan 1 float at 0x100004 has chan 2 etc. ASS sends to RFM 0 float at 0x100000 goes to PRM MCL 0x100004 to BS MCL 0x100008 to IMTX MCL 0x10000c to ITMY MCL 0x100010 to SRM MCL 0x100018 to MC1 MCL 0x10001c to MC3 MCL 0x100020 to ETMX MCL 0x100024 to ETMY MCL 380 Fri Mar 14 15:06:24 2008 robUpdateComputer Scripts / Programsrouting PEM -> ASS -> SUS_MCL  Quote: on ASS RFM 1 has PEM signals at float at 0x100000 has c0dcu1 first ICS110B chan 1 float at 0x100004 has chan 2 etc. ASS sends to RFM 0 float at 0x100000 goes to PRM MCL 0x100004 to BS MCL 0x100008 to IMTX MCL 0x10000c to ITMY MCL 0x100010 to SRM MCL 0x100018 to MC1 MCL 0x10001c to MC3 MCL 0x100020 to ETMX MCL 0x100024 to ETMY MCL You can differentiate between RFM 0 and RFM 1 in the simulink model by adding 0x4000000 to the offsets for RFM 1. 11810 Wed Nov 25 16:40:32 2015 yutaroUpdateLSCround trip loss of Y arm I measured round trip loss of Y arm. The alignment of relevant mirrors was set ideal with dithering (no offset). Summary: round trip loss of Y arm: 166.2 +/- 9.3 ppm (In the error, only statistic error is included.) How I measured it: I compared the power of light reflected by Y arm (measured at AS) when the arm was locked (P_L) and when ETMY was misaligned (P_M). P_L and P_M can be described as $P_M=P_0(1-T_\mathrm{ITM})$ $P_L=P_0\left[1-(1-\alpha)\frac{4T_\mathrm{ITM}}{T_\mathrm{tot}^2}T_\mathrm{loss}\right]$. The reason why P_L takes this form is: (1-alpha)*4T_ITM/(T_tot)^2 is intracavity power and then product of intracavity power and loss describes the power of light that is not reflected back. Here, alpha is power ratio of light that does not resonate in the arm (power of mismatched mode and modulated sideband), and T_tot is T_ITM+T_loss. Transmissivity of ETM is included in T_loss. I assumed alpha = 7%(mode mismatch) + 2 % (modulation) (elog 11745) After some calculation we get $1-P_L/P_M\simeq \frac{4(1-\alpha) T_\mathrm{loss}}{T_\mathrm{ITM}}-T_\mathrm{ITM}$. Here, higher order terms of T_ITM and (T_loss/T_ITM) are ignored. Then we get $(1-\alpha) T_\mathrm{loss}=\frac{T_\mathrm{ITM}}{4}(1-P_L/P_M+T_\mathrm{ITM})$. Using this formula, I calculated T_loss. P_L and P_M were measured 100 times (each measurement consisted of 1.5 sec ave.) each and I took average of them. T_ETM =13.7 ppm is used. Discussion: -- This value is not so different from the value ericq reported in July (elog 10248). -- This method of measuring arm loss is NOT sensitive to T_ITM. In contrast, the method in which loss is obtained from finesse (for example, elog 11740) is sensitive to T_ITM. In the method I'm now reporting, $\Delta T_\mathrm{loss}/T_\mathrm{loss}\simeq\Delta T_\mathrm{ITM}/T_\mathrm{ITM}$, but in the method with finesse, $\Delta T_\mathrm{loss}\simeq\Delta T_\mathrm{ITM}$. In the latter case, if relative error of T_ITM is 10%, error of T_loss would be 1000 ppm. So it would be better to use power of reflected light when you want to measure arm loss. 11816 Wed Nov 25 23:34:52 2015 yutaroUpdateLSCround trip loss of Y arm [yutaro, Koji] Due to the strange behavior (elog 11815) of ASDC level, we checked if it is possible to use POYDC instead of ASDC to measure the power of reflected light of YARM. Attached below is the spectrum of them when the arm is locked. This spectrum shows that it is not bad to use POYDC, in terms of noise. The spectrum of them when ETMY is misaligned looked similar. So I am going to use POYDC instead of ASDC to measure arm loss of YARM. Ed by KA: The spectra of POYDC and ASDC were measured. We foudn that they have coherence at around 1Hz (good). It told us that POYDC is about 1/50 smaller than ASDC. Therefore in the attached plot, POYDC x50 is shown. That's the meaning of the vertical axis unit "ASDC". Attachment 1: 14.png 11818 Fri Nov 27 03:38:23 2015 yutaroSummaryLSCround trip loss of Y arm Tonight I measured "loss map" of ETMY. The method to calculate round trip loss is same as written in elog 11810, except that I used POYDC instead of ASDC this time. How I changed beam spot on ETMY is: elog 11779. I measured round trip loss for 5 x 5 points. The result is below. (unit: ppm) 494.9 +/- 7.6 356.8 +/- 6.0 253.9 +/- 7.9 250.3 +/- 8.2 290.6 +/- 5.1 215.7 +/- 4.8 225.6 +/- 5.7 235.1 +/- 7.0 284.4 +/- 5.4 294.7 +/- 4.5 205.2 +/- 6.0 227.9 +/- 5.8 229.4 +/- 7.2 280.5 +/- 6.3 320.9 +/- 4.3 227.9 +/- 5.7 230.5 +/- 5.5 262.1 +/- 5.9 315.3 +/- 4.7 346.8 +/- 4.2 239.7 +/- 4.5 260.7 +/- 5.3 281.2 +/- 5.8 333.7 +/- 5.0 373.8 +/- 4.9 The correspondence between the loss shown above and the beam spot on ETMY is shown in the following figure. In the figure, "downward" and "left" indicate direction of shift of the beam spot when you watch it via the camera (ex. 494.9 ppm corresponds to the lowest and rightest point). Edited below on 28th Nov. To shift the beam spot on ETMY, I added offset in YARM dither loop. The offset was [-30,-15,0,15,30]x[-10,-5,0,5,10] for pitch and yaw, respectively. How I calibrated the beam spot is basically based on elog 11779, but I multiplied 5.3922 for vertical direction and 4.6205 for horizontal direction which I had obtained by caliblation of oplev (elog 11785). Edited above on 28 th Nov. I will report the detail later. 11819 Fri Nov 27 22:20:24 2015 yutaroUpdateLSCround trip loss of Y arm Here, I upload data I took last night, including the power of reflected power (locked/misaligned) and transmitted power for each point (attachement 1). And I would like to write about possible reason why the loss I measured with POYDC and the loss I measured with ASDC are different by about 60 - 70 ppm (elog 11810 and 11818). The conclusion I have reached is: It could be due to the strange bahavior of ASDC level. This difference corresponds to the error of ~2% in the value of P_L/P_M. As reported in elog 11815, ASDC level changes when angle of the light reflected by ITMY changes, and 2% change of ASDC level corresponds to 10 urad change of the angle of the light according to my rough estimation with the figure shown in elog 11815 and attachment 2. This means that 2% error in P_L/P_M could occur if the angle of the light incident to YARM and that of resonant light in YARM differ by 10 urad. Since the waist width $w_0$ of the beam is ~3 mm, with the 10 urad difference, the ratio of the power of TEM10 mode is $(10\,\mu \mathrm{rad}/ \theta_0)^2\sim0.01$, where $\theta_0=\lambda/\pi w_0$. This value is reasonable; in elog 11743 Gautam reported that the ratio of the power of TEM10 was ~ 0.03, from the result of cavity scan. Therefore it is possible that the angle of the light incident to YARM and that of resonant light in YARM differ by 10 urad and this difference causes the error of ~2% in P_L/P_M, which could exlain the 60 - 70 ppm difference. Attachment 1: log.txt.zip Attachment 2: 17.png 11857 Mon Dec 7 11:11:25 2015 yutaroSummaryLSCround trip loss of X arm On the day before yesterday and in this morning, I measured loss map of ETMX. I reported the method I used to change the beam spot on ETMX below. Round trip loss was measured for 5 x 5 points. The result is below. (unit: ppm) 455.4 +/- 21.1 437.1 +/- 21.8 482.3 +/- 21.8 461.6 +/- 22.5 507.9 +/- 20.1 448.4 +/- 20.7 457.3 +/- 21.2 495.6 +/- 20.2 483.1 +/- 20.8 472.2 +/- 19.8 436.9 +/- 19.3 444.6 +/- 19.7 483.0 +/- 19.5 474.9 +/- 20.9 498.3 +/- 18.7 454.4 +/- 18.7 474.4 +/- 20.6 487.7 +/- 21.4 482.6 +/- 20.7 487.0 +/- 19.9 443.7 +/- 18.6 469.9 +/- 20.2 482.8 +/- 18.7 480.9 +/- 19.5 486.1 +/- 19.2 The correspondence between the loss shown above and the beam spot on ETMX is shown in the attached figure. In the figure, "up" and "right" indicate direction of shift of the beam spot when you watch it via the camera (ex. 455.4 ppm corresponds to the highest and rightest point in the view via the camera). This result is consistent withe previous result of 561.19 +/- 14.57 ppm ericq got with ASDC and reported in elog 10248 if the discussion I reported in 11819 is taken into account. Elog 11819 says in short that the strange behavior of ASDC could give us 60-70 ppm error. The reason why the error is larger than that of the measurement for ETMY is that the noise of POX is larger than that of POY. But I am not sure to what extent the statistical error needs to be reduced. How I shifted the beam spot on ETMX: Basically, the method was same as one used for Y arm. Different point is: for Y arm we have two steering mirrors TT1&2, but for X arm we have only one steering mirror BS. Then in order to shift incident beam so that the beam spot on ITMX does not change, I ran the dithering of X arm as well as that of Y arm and added offsets to both dither loops that caused same amount of shift on ETMX and ETMX. Thanks to the symmetry between X arm and Y arm, the dithering of Y arm ensured that the beam spot on ITMX was unchanged as well as that of ITMY. The idea of this method is schematically shown in Attachment 2. The calibration of how much the beam spot shifted is based on the results of elog 11846 . The offset was [-15,-7.5,0,7.5,15]x[-5,-2.5,0,2.5,5] for pitch and yaw, respectively. Attachment 1: image1-2.JPG Attachment 2: symmetry.png 7990 Mon Feb 4 10:45:51 2013 JamieSummaryGeneralrough analysis of aligned PRM-PR2 mode scan Here's a sort of rough analysis of the aligned PRM-PR2 cavity mode scan. On Friday we took some mode scan measurements of the PRM-PR2 cavity by pushing PRM (C1:SUS-PRM_LSC_EXT) with a 0.01 Hz, 300 count sine wave. We looked at the transmitted power on the POP DC PD and the error signal on REFL11_I. Below is a detail of the scan, chosen because the actuation was in its linear region and there were three relatively ok looking transmission peaks with nice PDH response curves: The vertical green lines on the bottom plot indicate the rough averaged separation of the 11 MHz side-band resonances from the carrier, at +- 0.0275 s. If we take this for our calibration, we get roughly 400 MHz / second. The three peaks in top plot have an average FWHM of 0.00381 s. Given the calibration above, the average FWHM = ~1.52 MHz. If we assume a cavity length of 1.91 m, FSR = 78.5 MHz. Putting this together we get a finesse = ~51.6. Analysis of misaligned mode scans to follow. 7991 Mon Feb 4 11:10:59 2013 KojiSummaryGeneralrough analysis of aligned PRM-PR2 mode scan The expected finesse is 100ish. How much can we beleive the measured number of 50? From the number we need to assume PR2 has ~93% reflectivity. This does not agree with my feeling that the cavity is overcoupled. Another way is to reduce the reflectivity of the PRM but that is also unlikely from the data sheet. The scan passed the peak in 4ms according to the fitting. How do the analog and digital antialiasing filters affect this number? 7994 Mon Feb 4 19:33:19 2013 yutaSummaryGeneralrough analysis of aligned PRM-PR2 mode scan [Jenne, Yuta] We redid PRM-PR2 cavity scan because last one (elog #7990) was taken with the sampling frequency of 2 KHz. We have also done TMS measurement. Method: 1. Align input TTs and PRM to align PRM-PR2 cavity. 2. Sweep cavity length using C1:SUS-PRM_LSC_EXC. 3. Get data using Jamie's getdata and fitted peaks using /users/jrollins/modescan/prc-pr2_aligned/run.py 4. Calculated cavity parameters Results: Below is the figure containing peaks used to do the calculation. From 11 MHz sidebands, calibration factor is 462 +/- 22 MHz/sec (supposing linear scan around peaks) FWHM is 1.45 +/- 0.03 MHz. TMS is 2.64 +/- 0.05 MHz. Error bars are statistical errors of the average over 3 TEM00 peaks. If we believe cavity length L to be 1.91 m, FSR is 78.5 MHz. So, Finesse will be 54 +/- 1 and cavity g-factor will be 0.9944 +/- 0.0002. 0.9889 +/- 0.0004 (Edited by YM; see elog #8056) If we believe RoC of PRM is exactly +122.1 m, measured g-factor insists RoC of PR2 to be -187 +/- 4. If we believe RoC of PR2 is exactly -600 m, measured g-factor insists RoC of PRM to be 218 +/- 6. Discussion: 1. Finesse is too small (expected to be ~100). This time, data was taken 16 KHz. Cut-off frequency of the digital antialiasing filter is ~ 5 kHz (see /opt/rtcds/rtscore/release/src/fe/controller.c). FWHM is about 0.003 sec, so it should not effect much according to my simulation. 2. I don't know why FWHM measurement from the last one is similar to this one. The last one was taken 2 KHz, this means anti-aliasing filter of 600 Hz. This should double FWHM. 3. Oscilloscope measurement may clear anti-aliasing suspicion. 7997 Tue Feb 5 02:04:44 2013 yutaSummaryGeneralrough analysis of aligned PRM-PR2 mode scan I redid PRM-PR2 cavity scan using oscilloscope to avoid anti-aliasing effect. Measured Finesse was 104 +/- 1. Method: 1. Splitted POP DC output into three and plugged two into oscilloscope TDS 3034B. Ch1 and Ch2 was set to 1 V/div and 20 mV/div respectively to take the whole signal and higer resolution one at the same time (Koji's suggestion). Sampling frequency was 50 kHz. Sweeping time through FWHM was about 0.001 sec, which is slow enough. 2. Took mode scan data from the oscilloscope via network. Preliminary results: Below is the plot of the data for one TEM00 peak. The data was taken twice. Measured FWHM was 0.764 MHz and 0.751 MHz. By taking the average, FWHM = 0.757 +/- 0.005 MHz. This gives you Finesse = 104 +/- 1, which is OK compared with the expectation. What I need: I need better oscilloscope so that we can take longer data (~1 sec) with higher resolution (~0.004 V/count, ~50kHz). TDS 3034B can take data only for 10 ksamples, one channel by one! I prefer Yokogawa DL750 or later. 7998 Tue Feb 5 03:16:51 2013 KojiSummaryGeneralrough analysis of aligned PRM-PR2 mode scan 0.764 and 0.751 do not give us the stdev of 0.005. I have never seen any Yokogawa in vicinity.  Quote: Measured FWHM was 0.764 MHz and 0.751 MHz. By taking the average, FWHM = 0.757 +/- 0.005 MHz. This gives you Finesse = 104 +/- 1, which is OK compared with the expectation. What I need I need better oscilloscope so that we can take longer data (~1 sec) with higher resolution (~0.004 V/count, ~50kHz). TDS 3034B can take data only for 10 ksamples, one channel by one! I prefer Yokogawa DL750 or later. 8000 Tue Feb 5 10:09:08 2013 yutaSummaryGeneralrough analysis of aligned PRM-PR2 mode scan stdev of [0.764, 0.751] is 0.007, but what we need is the error of the averaged number. Statistical error of the averaged number is stdev/sqrt(n).  Quote: 0.764 and 0.751 do not give us the stdev of 0.005. 8002 Tue Feb 5 11:30:19 2013 KojiSummaryGeneralrough analysis of aligned PRM-PR2 mode scan Makes sense. I mixed up n and n-1 Probability function: X = (x1 + x2 + ... + xn)/n, where xi = xavg +/- dx Xavg = xavg*n/n = xavg dXavg^2 = n*dx^2/n^2 => dXavg = dx/sqrt(n) Xavg +/- dXavg = xavg +/- dx/sqrt(n) 8074 Wed Feb 13 01:26:08 2013 yutaSummaryGeneralrough analysis of aligned PRM-PR2 mode scan Koji was correct. When you estimate the variance of the population, you have to use unbiased variance (not sample variance). So, the estimate to dx in the equations Koji wrote is dx = sqrt(sum(xi-xavg)/(n-1)) = stdev*sqrt(n/(n-1)) It is interesting because when n=2, statistical error of the averaged value will be the same as the standard deviation. dXavg = dx/sqrt(n) = stdev/sqrt(n-1) In most cases, I think you don't need 10 % precision for statistical error estimation (you should better do correlation analysis if you want to go further). You can simply use dx = stdev if n is sufficiently large (n > 6 from plot below).  Quote: Makes sense. I mixed up n and n-1 Probability function: X = (x1 + x2 + ... + xn)/n, where xi = xavg +/- dx Xavg = xavg*n/n = xavg dXavg^2 = n*dx^2/n^2 => dXavg = dx/sqrt(n) Xavg +/- dXavg = xavg +/- dx/sqrt(n) 6205 Tue Jan 17 03:10:27 2012 kiwamuConfigurationIOOrotated lambda/2 plate I have slightly rotated the lambda/2 plate, which is used for attenuating the REFL beam's power on the AS table because the plate had been at an unusual angle for investigation of the glitches since last Thursday. It means the laser power going to the coating thermal noise setup has also changed. Just keep it in mind.  Quote from #6198 So today we set up the Jenny RC temperature setup to lock the LWE NPRO to the RC and then set up the beat note with the IFO REFL beam on the AS table. By using the 2 laser beat, we are avoiding the VCO phase noise issue which used to limit the PSL frequency noise at ~0.01 Hz/rHz. To do this we have reworked some of the optics on the PSL and AS tables, but I think its been done without disturbing the beams for the regular locking. Beat note has been found, but the NPRO has still not been locked to the RC - next we setup the lockin amp, dither the PZT, and then use the New Focus lock box to lock it to the RC. 13044 Mon Jun 5 21:53:55 2017 ranaUpdateComputersrossa: ubuntu 16.04 With the network config, mounting, and symlinks setup, rossa is able to be used as a workstation for dataviewer and MEDM. For DTT, no luck since there is so far no lscsoft support past the Ubuntu14 stage. 15455 Mon Jul 6 12:51:41 2020 gautamUpdateComputersrossa: resolvconf installed Indeed, this is now fixed by following instructions from here. I rebooted rossa at ~1250 PDT and confirmed that resolv.conf didn't get overwritten. The resolv.conf file also now has the following useful lines at the head: ~>cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN  Quote: yes, I rebooted yesterday to fix the 'steaking white lines' problem in the video/display maybe we're supposed to edit something besides resolv.conf since that gets over-written on boot for some linux OS 15451 Sun Jul 5 18:39:57 2020 ranaUpdateComputersrossa: printer I did sudo usermod -a -G lpadmin controls and then was able to add Grazia to the list of printers for Rossa by following the instructions on the 40m Wiki. I installed color syntax highlighting on Rossa using the internet (https://superuser.com/questions/71588/how-to-syntax-highlight-via-less). Now if you do 'less genius_code.py', it will be highlighting the python syntax. when I try 'sitemap' on rossa I get: medm: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory 15460 Wed Jul 8 22:50:33 2020 gautamUpdateComputersrossa: more symlinks I wanted to try using rossa as my locking workstation today. However, a few problems became quickly evident. Basically, any of our scripts that rely on the cdsutils package (there are MANY) will not work on rossa, because of some library error. This machine is running Debian 10, while the cdsutils package is being loaded from a pre-compiled install on the shared drive, so perhaps this isn't surprising? Digging a little more, I found that actually, a version of cdsutils that actually works with python3 is actually shipped with the standard cds-workstation meta-package. This is great news, and we should try and use this where possible I guess. Deferring further debugging for daytime work. Anyway, I added a symlink: sudo ln -s /usr/lib/x86_64-linux-gnu/libncurses.so.6 /usr/lib/x86_64-linux-gnu/libncurses.so.5, and installed wmctrl using sudo apt install wmctrl 15469 Sat Jul 11 00:10:22 2020 gautamUpdateComputersrossa: more developmental work After some consultation with Erik von Reis at LHO, this workstation is progressing towards being usable for most commissioning tasks. DTT, awggui, foton, and MEDM are all now working well. The main limitation now comes from the fact that many of our python scripts are written for python2, and rossa doesn't have many dependencies installed for python2. I see no reason to build these dependencies on rossa for python2, we should not have to work with an unsupported language. But at the same time, I don't want to completely wipe all our python2 scripts, and make them python3, because this would involve a lot of tedious testing that I'm not prepared to undertake at the moment (the problem is compounded by the fact that pianosa does not have many dependencies installed for python3). So what I have done in the interim is make python3 versions of the most important scripts I need to get the PRFPMI locking working - they are in the scripts directory and have the same names as their python2 counterparts, but have a 3 appended to their names. So when working on rossa, these are the scripts that are called. Eventually, after a lot more testing, we can depracate the old scripts. Currently, where applicable, the MEDM screens allow for either the python2 or python3 version of the script to be called. Please, for the time being, do not try and install any new packages on rossa unless you are prepared to debug any problems caused and return the machine to a workable state. If you find some issue with a missing package on rossa, (i) make a note of it on the elog, and (ii) if possible, set up your own conda environment for testing and install dependencies to that environment only. 15473 Mon Jul 13 11:33:18 2020 ranaUpdateComputersrossa: more developmental work I too, would prefer py3 for everything, but aren't all the cdsutils / gaurdian things still python2? Is it possible to just make a python2 conda environment on rossa? I would guess that its simple and won't interfere with the regular operation of that machine. 15475 Mon Jul 13 12:37:05 2020 gautamUpdateComputersrossa: more developmental work In fact, all these utilities are now available in python3. There may be some bugs (e.g. this), but I've checked basic functionality and things look usable enough for development to proceed. While we can have a python2 env on rossa, I think it's unnecessary.  Quote: I too, would prefer py3 for everything, but aren't all the cdsutils / gaurdian things still python2? 15452 Mon Jul 6 00:37:28 2020 gautamUpdateComputersrossa: lib symlink This is strange - I was definitely able to launch medm when I was working on this machine remotely on Friday. But now, there does seem to be a problem with this shared library being missing. First of all, I installed mlocate to find where the shared library files are installed. Then I made the symlink, and now sitemap seems to work again. Weirdly, my changes to /etc/resolv.conf got overwritten somehow. Was this machine rebooted? Uptime suggests it's only been running for ~6 hours at the time of writing of this elog. sudo apt install mlocate sudo updatedb sudo ln -s /usr/lib/x86_64-linux-gnu/libreadline.so.7 /usr/lib/x86_64-linux-gnu/libreadline.so.6  Quote: when I try 'sitemap' on rossa I get: medm: error while loading shared libraries: libreadline.so.6: cannot open shared object file: No such file or directory 15454 Mon Jul 6 12:43:02 2020 ranaUpdateComputersrossa: lib symlink yes, I rebooted yesterday to fix the 'steaking white lines' problem in the video/display maybe we're supposed to edit something besides resolv.conf since that gets over-written on boot for some linux OS 15463 Thu Jul 9 16:16:20 2020 gautamUpdateComputersrossa: graphics driver issues? I noticed these streaky lines again today (but they were not a problem last night). It is annoying if we have to reboot this machine all the time. I wonder if this has something to do with missing drivers. When I ran sudo apt update && sudo apt upgrade, I got several lines like (this isn't the whole stack trace) W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/bl.bin for module nouveau Is this indicative of the graphics drivers being installed incorrectly? I am hesitant to mess with this because I think in the past, it was always trying to update some graphics driver that crashed the whole machine into some weird state where we have to wipe the drive and do a fresh re-install of the OS. Should we just follow these instructions? The graphics card is apparently Quadro P400, which is one of the supported ones according to the list of supported devices. Or just swap donatella and rossa monitors and defer the problem for later?  Quote: yes, I rebooted yesterday to fix the 'steaking white lines' problem in the video/display 14023 Tue Jun 26 22:06:33 2018 ranaUpdateComputersrossa: SL7.3 upgrade continues: DTT is back I used the following commands to get diaggui to run on rossa/SL7: controls@rossa|lib64> ls -lrt libsasl* -rwxr-xr-x. 1 root root 121296 Feb 16 2016 libsasl2.so.3.0.0 lrwxrwxrwx. 1 root root 17 Dec 18 2017 libsasl2.so -> libsasl2.so.3.0.0 lrwxrwxrwx. 1 root root 17 Dec 18 2017 libsasl2.so.3 -> libsasl2.so.3.0.0 controls@rossa|lib64> sudo ln -s libsasl2.so.3.0.0 libsasl2.so.2 controls@rossa|lib64> ls -lrt libsasl* -rwxr-xr-x. 1 root root 121296 Feb 16 2016 libsasl2.so.3.0.0 lrwxrwxrwx. 1 root root 17 Dec 18 2017 libsasl2.so -> libsasl2.so.3.0.0 lrwxrwxrwx. 1 root root 17 Dec 18 2017 libsasl2.so.3 -> libsasl2.so.3.0.0 lrwxrwxrwx. 1 root root 17 Jun 26 22:02 libsasl2.so.2 -> libsasl2.so.3.0.0 Basically, I have set up a symbolic link to point sasl2.so.2 to sasl2.so.3.0.0. I've asked LLO again for some guidance on whether or not to find some backport in a non-standard SL7 repo. IF they reply, we may later replace this link with a regular file. For the nonce, diaggui runs and is able to show us the spectra. We also got swept sine to work. But the FOTON launched from inside of AWGGUI doesn't inherit the sample frequency of the excitation channel so we can't filter noise injections from awggui yet. 14025 Wed Jun 27 19:05:20 2018 ranaUpdateComputersrossa: SL7.3 upgrade continues: DTT is back UNELOGGED: someone has changed Pianosa from Ubuntu/Dumbian into SL7. Might be hackers. Donatella is now the only Ubuntu machine in the control room. I propose we keep it this way for another month and then go fully SL7 if we find no bugs with Pianosa/Rossa. 13487 Mon Dec 18 17:48:09 2017 ranaUpdateComputersrossa: SL7.3 upgrade continues Following instructions from LLO-CDS fo the rossa upgrade. Last time there were some issues with not being to access the LLO EPEL repos, but this time it seems to be working fine. After adding font aliases, need to run 'sudo xset fp rehash' to get the new aliases to take hold. Afterwards, am able to use MEDM and sitemap just fine. But diaggui won't run because of a lib-sasl error. Try 'sudo yum install gds-all'. diaggui: error while loading shared libraries: libsasl2.so.2: cannot open shared object file: No such file or directory (have contacted LLO CDS admins) X-windows keeps crashing with SL7 and this big monitor. Followed instructions on the internet to remove the generic 'Nouveau' driver and install the proprietary NVDIA drivers by dropping to run level 3 and runnning some command line hoodoo to modify the X-files. Now I can even put the mouse on the left side of the screen and it doesn't crash. 14925 Wed Oct 2 20:45:18 2019 ranaUpdateComputersrossa revival Formatted and re-installing OS on rossa for the 3rd or 4th time this year. I suggest that whoever is installing software and adjusting video settings please stop. If you feel you need to tinker deeply, use ottavia or zita and then be prepared to show up and fix it. While I was moving the UPS around, the network lights went out for Rossa, so I may have damaged the network interface or cable. Debugging continues. 14935 Thu Oct 3 21:50:22 2019 ranaUpdateComputersrossa revival Got the network to work again just by unplugging the power cord and letting it sit for awhile. But corrupted OS by trying to install Nvidia drivers. https://www.advancedclustering.com/act_kb/installing-nvidia-drivers-rhel-centos-7/ 14994 Mon Oct 28 18:55:06 2019 ranaUpdateComputersrossa revival back on new Rossa from Xi computing 1. switched to using Display Port for video; this works. The DVi, HDMI, VGA ports are connected to the motherboard rather than the video card, so they are not active. 2. runs super slow w/ SL 7.6; maybe some service is running after startup? 3. install repos and update according to LLO CDS wiki 4. add controls user and group according to LLO wiki 5. remove gstreamer ugly because it breaks yum update 6. run 'yum update --skip-broken' because GDS doesn't work 7. turn off old selinux stuff 8. modify fstab to get NFS Next: 1. finish mounting 2. xfce 3. figure out why the LLO install instructions can't install any CDS software (e.g. root, DTT, etc) Update: Sun Nov 3 18:08:48 2019 1. moved the SL7 fresh install repos back into etc/yum.repos.d/. The LLO instructions has me remove them, but the LLO supplied repos are no good for standard apps. After putting these back was able to install standard apps (terminator, root, diaggui) 2. copied over /etc/fstab lines from pianosa sothat the NFS mounts work correctly 3. added symlinks so that the NFS dirs mount in the right dirs 4. symlink libsasl2.so.3 -> libsasl2.so.2 and now DTT runs and can get data now and in the past 5. install XFCE 6. sitemap / MEDM works 7. Did "sudo ln -s /usr/lib64/libXm.so.4 /usr/lib64/libXm.so.3" to enable StripTool. Update: Fri Nov 15 00:00:26 2019: 1. random hanging of machine while doing various window moving or workspace switching 2. turned off power management in XFCE 3. turned off power management on monitor 4. disabled SELINUX 5. firewalld was already off 6. installed most, pdftk, htop, glances, qtgrace, lesstif 7. dataviewer now works and QTgrace is much nicer than XMGrace 15141 Wed Jan 22 16:38:01 2020 ranaUpdateComputersrossa revival wiped and install Debian 10 on rossa today still to be done: config it as CDS workstation please don't try to "fix" it in the meantime 15447 Wed Jul 1 18:16:09 2020 gautamUpdateComputersrossa re-re-revival In an effort to make a second usable workstation, I did the following (remotely) on rossa today (not necessarily in this order, I wasn't maintaining a live log so I forgot): 1. Fixed /etc/resolv.conf, so that the other martian machines can be found. 2. Copied over .bashrc file, and the appropriate lines from /etc/fstab from pianosa to rossa. 3. Ran sudo apt install nfs-common. Then ran sudo mount -a to get /cvs/cds mounted. 4. Made symlinks for /users and /opt/rtcds , and /ligo. All of these are used by various environment-setting scripts and I chose to preserve the structure, though why we need so many symlinks, I don't know... 5. Set up the shell variableNDSSERVER using export NDSSERVER=fb:8088. I'm not sure how, but I believe DTT, awggui etc use this on startup to get the channel list (any
6. Followed instructions from Erik von Reis at LHO to install the cds workstation packages and dependencies. Worked like a charm 🎃
7. As a test, I plotted the accelerometer spectra in DTT, see Attachment #1. I also launched foton from inside awggui, and confirmed that the sample rate is inherited and I could designate a filter. But I haven't yet run the noise injection to test it, I'll do that the next time I'm in the lab.
8. Also checked that medm, StripTool and ndscope, and anaconda python all seem to work 👍🏾.

So, in summary, rossa is now all set up for use during lock acquisition. However, until this machine has undergone a few months of testing, we should freeze the pianosa config and not mess with it.

Note that this version of the "crtools" is rather new. Please, use them and if there is an issue, report the errors! I am going to occassionally try lock acquisition using rossa.

 Quote: wiped and install Debian 10 on rossa today still to be done: config it as CDS workstation please don't try to "fix" it in the meantime
Attachment 1: MCacc.pdf
15449   Sun Jul 5 16:14:41 2020 ranaUpdateComputersrossa re-re-revival

maybe we should make a "dd" copy of pianosa in case rossa has issues and someone destroys pianosa by accidentally spilling coffee on it.

 So, in summary, rossa is now all set up for use during lock acquisition. However, until this machine has undergone a few months of testing, we should freeze the pianosa config and not mess with it.
3517   Thu Sep 2 21:22:31 2010 Sanjit, KojiConfigurationComputersrossa nvidia driver and dual monitor configuration

Simple steps (but don't try these on a working computer without getting some experience on a spare one, you may find it difficult to restore the system if something goes wrong):

• we did: NVIDIA GeForce 310 64bit Linux, version: 256.53, release date 2010.08.31
2. keep/move the driver in /root (use "sudo" or "su")
3. reboot the computer in "single user" mode
• in the GRUB screen edit the boot command by pressing the appropriate key listed in the screen
• in the boot command-line put " single" in the end (no other change is normally needed), don't save
• press ENTER and the system will reboot to a root shell (# prompt)
4. cd /root
5. run the NVIDIA driver script
6. exit the shell (ctrl-d), let the system reboot
• it should flash (mostly green) "nvidia" screen before starting X
• in case of problems run system-config-display and revert to vesa driver

3518   Thu Sep 2 23:35:33 2010 ranaConfigurationComputersrossa nvidia driver and dual monitor configuration

Why are we running CentOS 4.8 instead of 5.5 ?    What runs at LLO?     What runs in Downs?

3521   Fri Sep 3 11:23:16 2010 josephbConfigurationComputersrossa nvidia driver and dual monitor configuration
At LLO the machines are running Centos 5.5. A quick login confirms this. Specifically the release is 2.6.18-194.3.1.el5.

 Quote: Why are we running CentOS 4.8 instead of 5.5 ?    What runs at LLO?     What runs in Downs?

3524   Sun Sep 5 21:35:41 2010 ranaConfigurationComputersrossa notes

**** Deleted
apps/emacs
apps/linux64/firefoxold
apps/linux64/comsol      (old v. 3.5)

* running up2date on rossa

* rossa needs to be able move windows between monitors: Xinerama?

* there are permissions problems: controls on rossa can't
make and delete directories made by 'controls' elsewhere.
Some sort of user# or group issue?

3531   Tue Sep 7 10:50:53 2010 josephbConfigurationComputersrossa notes

The controls group is user id 500 by default on most new machines. Unfortunately, the user ID used across the already existing machines is 1001. One method of doing this switch is in this elog.  You can also do the change of the controls ID by becoming root and using the graphical command system-config-users.  This will  let you change the user ID and group ID for controls to 1001.  This graphical interface also lets you change the login shell.

Unfortunately, I had some minor difficulty and I ended up removing the old controls and creating a new controls account with the correct values and using tcsh.  The .cshrc file has been recreated to source cshrc.40m.  The controls account now has correct permissions, although some of the preferences such as background will need to be reset.

 Quote: **** Deleted apps/emacs apps/linux64/firefoxold apps/linux64/comsol      (old v. 3.5) * running up2date on rossa * rossa needs to be able move windows between monitors: Xinerama? * there are permissions problems: controls on rossa can't make and delete directories made by 'controls' elsewhere. Some sort of user# or group issue?

3539   Tue Sep 7 23:17:45 2010 sanjitConfigurationComputersrossa notes

 Quote: * rossa needs to be able move windows between monitors: Xinerama?

Xinerama support has been enabled on rossa using nvidia-settings.

ELOG V3.1.3-