100 Sapphire prizms arrived.

The 3 pieces of Sapphire v-groove test cuts are back. They look good. The suspension wire 0.0017" ( 43 micron ) is show on some of the pictures.

Very nice! I got excited.

• Don't you ask Calum and co to check the groove size with their microscopes? Just give the samples and the wire.
• Do we want to make a simple "guitar" setup to measure the vibration Qs with Al piece, glass prism, ungrooved Sapphire, this grooved sapphire, grooved ruby, etc?

Kyle took high quality images of  the three sapphire prisms using the microscope @Downs. He analyzed the images to see the radius of the groove.

They all look sufficiently sharp for a 46um steel wire. Thumbs up.
I am curious to see how the wire Q is with grooved sapphires, ungrooved sapphires, grooved ruby, grooved aluminum stand off, and so on.

Ruby wire standoff received from China. I looked one of them with our small USB camera.  They did a good job. The  long edges of the prism are chipped.

The v-groove cutter must avoid them. Pictures will follow.

The power supply of a lock-in amp, which is on the Y-arm side of PSL clean room, was pulled out by my mistake.

Then I reconnected it, but I don't know whether it is re-adjusted properly.

I'm sorry about this. If you are using that amp, it should be checked.

Whenever you modify any of the front-end code in /opt/rtds/caltech/c1/userapps, such as models, scripts or medm screens, REMEMBER TO COMMIT YOUR CHANGES, WITH A LOG MESSAGE!!!

cd /opt/rtcds/caltech/c1/userapps/trunk
svn commit path/to/modified/file

If you forget to commit things, they may be purged and you will loose your work.  ALWAYS COMMIT!

Things to note and watch out for:

• When you commit, make sure you specify explicitly the path to the file that you are committing.  This repository is shared by all LIGO sites, including the sites (LHO and LLO) so you really want to make sure you're not committing anything that affects anything other than "c1" (ie. the 40m)
• Only commit one file at a time, unless the changes to multiple files are tightly coupled.
• Never commit without specifying the path to the file that you are committing.  Other people may be working on other files in the repository, and you don't want to commit their work with yours.
• YOU MUST LEAVE A LOG MESSAGE.  Your log message should be specific to the file you have modified, and should be clear and verbose to explain exactly what you have done.
• Use the "svn status" command to give you an overview of what is going on in the working directory.  This will tell you which files have been modified.  See "svn help status" for more information.

If you have questions ASK.  Don't force things.

Also, remember to update the svn working copy before you begin doing any work, to make sure you're working on the most recent version:

cd /opt/rtcds/caltech/c1/userapps/trunk
svn update

!!!CHECK IN MODEL CHANGES!!!

Today I found three models that were modified, but not checked in to the SVN repository:

M       sus/c1/models/lib/sus_single.mdl
M       isc/c1/models/c1lsc.mdl
M       isc/c1/models/c1mcp.mdl

I checked in the c1lsc model, since I think it was just the change that Kiwamu made in http://nodus.ligo.caltech.edu:8080/40m/4749.  I left the others, since I have no idea what they are or who made them.

Please please please remember to commit your model changes to the SVN after you're done.  This is particularly important for important models, such as c1lsc.  If you don't check in your changes I can pretty much guarantee that at some point you will loose them.

 "Alberto"NPRO laser has been moved again on PSL table in order to make a measurement of the beat note varying also the PSL temperature.

It is useful because if the PSL temperature would drift  we have to know which is the NPRO temperature that returns the beat.

I'm going to measure it tomorrow.

EDIT: Ran Jamie's NDS2 reset method and it's still not serving up MC data.

I am debugging the SUS input matrix diagonalization code (which I have affectionately termed "Dr. SUS") offline by running everything except the actual writing of the matrices (%writeSUSinmat()) in a sandbox directory. Some notes:

• nodus doesn't know NDS2, but this isn't a problem given Kiwamu's reply, since we don't want to push results to the elog. I will still have the script push "optics kicked---don't touch" alerts to the elog, but I realized this can be done easily from a remote computer via in-script SSH commands. My next choice was pianosa, but even though she knows NDS2, she spits out MEX errors when I try to get data. Third stop was allegra, and she plays nice 
• NDS2 is unable to read the MC mirror sensor data. Data from all other optics are retrieved without a problem. I verified that raw data was being written by plotting playback data in dataviewer, and I tried various times and the problem persisted. I suspect the problem is on the NDS2 server side:

The most recent entry in .../users/jzweizig/nds2-mafalda/channel_history shows nothing for MC1 2 or 3

Now that NDS2 is working, I was able to run all parts of diagAllSUS (except for the matrix writing) without errors. Barring issues with standard commands (freeswing, turnOnWatchDogs.csh, caput, etc.), Dr. SUS should be ready to go.

As requested, I have suppressed the generation of an elog post containing the results of the diagonalization.

Dr. SUS will run on allegra as a cron job at 8:00am on Sundays:

allegra:peakFit>crontab -l

PATH=/bin/:/usr/bin/:/cvs/cds/caltech/apps/linux64/matlab/bin/:/cvs/cds/caltech/apps/linux/gds/bin/:/cvs/cds/caltech/apps/linux/tds/bin/

PWD=/cvs/cds/caltech/apps/linux/gds/lib/

LD_LIBRARY_PATH=/cvs/cds/caltech/apps/linux/gds/lib

01 05 * * 0 cat /cvs/cds/caltech/users/kiwamu/work/20091026_OMC-LSC-diag/src/OMC_LSC_timing.m | matlab -nosplash -nodesktop > /dev/null

0 8 * * 0 /cvs/cds/rtcds/caltech/c1/scripts/SUS/peakFit/runDrSUS

Also: should these variable definitions really be here?

Cron starts with only a very minimal PATH.  However, this shouldn't be an issue if you specify the full path to the commands.

The rest of the env vars should probably not be there.

Also, Zach:  using /cvs/cds is now forbidden.  We need to put this script in the right place.

[Paco, Yehonathan]

I took over the finesse calculations Yehonathan had set up for BHD. The notebook is here and for this post I focused on simulating what we might expect from our single RF vs dual RF sensors (55 MHz and 44 MHz respectively) in terms of LO phase control.

The configuration is simple, only MICH is included (no ETMs, no PRC, no SRC). The LO phase is changed by scanning LO1, the differential loss is changed by scanning the ITMXHR loss parameter (nominally at 25 ppm), and the microscopic DARM offset is changed by scanning the BS position by +- 6 nm.

Finesse estimates the sensor response by taking the demodulated sideband magnitude (BH55, BH44) with respect to a 1 Hz LO1 signal modulation. This can be done for a set of LO phase angles so as to get the nominal LO phase angle where the response is maximized.

I first replicated the plots from [elog17170] for the two sensors in question. This is just done as a sanity check and is shown in Attachment #1. This plot summarizes our expectation that the single RF sideband sensor should have a peak response to the LO phase around 90 deg away from the nominal BHD readout phase angle (0 deg in this plot). In contrast, the double RF demodulation scheme has a peak response around the nominal LO phase angle.

Attachment #2 looks at a family of similar plots representing differential loss changes between the two MICH arms. We tune this by changing the ITMX loss in finesse, and then repeat the calculation as described above. It seems that for the simple MICH, differential loss of ~ 10000 ppm does not impact the nominal LO phase angle where the responses are maximized for either sensor (note however that the response magnitude maybe changes for single RF sideband sensing at extremely high differential loss).

Finally, and most interestingly Attachment #3 looks at a family of similar plots representing a set of microscopic DARM offsets (+- 6 nm). This is tuned by changing the BS position ever so slightly, and the same calculation is repeated. In this case, the nominal LO phase angle does change, and it changes quite a lot for the single RF demod. It looks like this might be enough to explain how we can sense the LO phase angle with a single RF sideband, but I think the next interesting point would be to simulate the effect of contrast defect by changing the ITM RoCs (to scatter into HOMs) or the non-thermal ITM lenses (to probe the TEM00 contrast defect effect). Any comments / feedback at this point are welcome, as we move forward into other configurations where more serious thermal effects might be introduced (PRMI).

This is interesting. With the FPMI, the DARM phase shift is enhanced by the cavity. Therefore, I suppose the effect on the BH55 is also going to be enhanced (i.e. a much smaller displacement offset causes a similar LO phase rotation).

Yuta pointed out that the BH55 signal was weirdly never going to zero, so I actually tuned the demod angle and made sure I was reading the right (Q) quadrature. This doesn't affect our previous qualitative conclusion about DARM offsets, but here's an updated gif which also makes visualization easier (?).

but what about including the DC reflectivity imbalance of the arms? there would be another BH55 term from that field maybe.

I repeated the calculations but with FPMI (last case was all MICH). The qualitative behavior is the same, the BH55 sensing is mostly affected by residual darm offset. If the darm offset is of a couple of nm, the single RF sideband may sense the LO phase at as much as > 20 deg away from the nominal phase angle. This is not too different from the MICH case; so maybe I overlooked something about how I define FPMI in the calculation.

Attachments #1-3 show the plots of the BH55 (single RF sideband) and BH44 (double RF sideband) sensitivity to LO phase fluctuations around various nominal LO phase angles. Attachment #1 looks at the effect of differential loss, Attachment #2 looks at the effect of differential dc reflectivity (of the ITMs), and Attachment #3 looks at the effect of residual darm offsets. Dashed lines show the orthogonal quadrature (I) of the demodulated RF signals (always minimized).

Manasa and I have been wondering why the low frequency seismic noise has been different in the last few days/weeks.  I went over to visit the Rock Monster, a.k.a. the Earth Surface Dynamics Laboratory next door, and the grad student turned it up for me (increased water flow significantly) for a few minutes.  Then I came back to look at the BLRMS, and you can see the low frequency increase a few minutes ago, when he turned it up on high.  He said that they run it on low almost all the time, 9am-5pm ish, and on high for an hour or so at a time periodically during the day.

[Jenne, Yuta, Rana, Steve, Manasa]

We have taken stock of the lab "temporary" power supply situation, and things look much better.

This morning, I removed 2 unused power supplies and a function generator from the PSL table - these had been used for MC ringdown things.

I also removed the non-connected cables that had been used for the RAMMON setup, and the EOM temperature controller circuit.

This afternoon, Yuta removed the 2 HV power supplies that were used to keep PZT2 working near the end of its life.  Since we now have the active TTs, these have been turned off for a while, and just needed to be removed.

Manasa removed the power supply under the POP/POX table that was powering the amplifier for POP22.  If we are going to continue using a Thorlabs PD for POP22, then we need to make a twisted pair of wires (~20 feet) to get power from 1X1.  If we are going to (finally) install a gold RF PD, then that will not be necessary.

I removed the power supply sitting near the bottom of the LSC rack, for another amplifier for POP22 (with minicircuits filters attached).  Again, if we get a gold RF PD, we can remove the filters and amplifier.  If not, we can use the existing twisted pair of wires, and plug them into the rack rather than a power supply. 

The power supply under the NE corner of the PSL table was no longer in use.  It was most recently used for amplifiers for the green beat PDs, as Yuta mentioned in elog 6862, those were moved over to 1X2.  In elog 8008 I mentioned that Yuta and I moved those amplifiers over to rack power.

The HV supply, the function generator and the OSA controllers that were on top of the short OMC rack next to the AS table have all been removed.  We need to come up with a better place for the OSAs, since we need to re-install them.  The power supply and the function generator (which was used just for a voltage offset) were formerly used for the output steering PZTs, but lately we have just been using those mirrors as fixed mirrors, since we don't need to steer into the OMC.  Some day, we will replace those mirrors with the output steering active tip tilts, and re-commission the OMC....someday.

The power supply for the amplifier set (that goes with the set of minicircuits filters) for the RAMMON PD (which took light from the IPPOS path) has been removed.  If we determine that we need RAMMON back, we will have to make a twisted pair to power those amplifiers.

SUMMARY:

* If we don't install a gold RF PD for POP22, we need a 20ft twisted pair for +15/GND.

* Also, if we don't install a gold RF PD for POP22, we need to plug the amplifier at the LSC rack into the rack power (twisted pair already exists).

* If we need RAMMON back, we will need a twisted pair to power those amplifiers.

* All other power supplies have been removed, and put away.  We currently have 0 "temporary" power supplies in use in the lab!

I installed 'glue' on Rossa, Allegra, and Rosalba.  This is a Python module that includes a facility for LIGO_LW XML files.  Oddly, I couldn't find the glue package on Pianosa.

As Jenne's Elog we want to see Spectrum and time series of REFL 165 (our PRMI LSC locking PD) to see if the signal is saturated while bring the arms into resonance.
I started to connect the spectrum analyser and the 'scope to REFL165 output.

Directional coupler (Mini=-circuits ZMDC-10-2 ZMDC-20-3) was connected just before the dimod boad input. The main output of coupler is plugged into demod board's input.The other output of the coupler is connected to AG4395A using BNC cable.

The spectrum analyser output can be read using netgpibdata in control room. The IP address is 192.168.113.108 and the GPIB address is 17. For this I dissconected the network hub from another AG4395A, which is at the front of 1X2 lack.

I didn't connected the 300 MHz 'scope right now, but tomorrow it will be connected using power splitter and also be able to get data by internet. For connect 'scope to network, I disconected the network hub from SR785.

[Jenne, Masayuki]

We changed the Directional coupler from ZMDC-20-3 to ZMDC-20-5-S+ because that coupler seemed to introduce some high frequency noise.

 I connected the 'scope between REFL165 output and demod board input. I split the signal from coupler using the splitter (Mini-Circuits ZFSC-2-5). One signal is going to 'scope CH1 and the other is going to spectrum analyzer. I connected the 'scope to 40MARS. The IP adress is 192.168.113.25. I connected that by cabling from 1X2.

Recorded transfer functions for the 1cm Si-PD as described on p. 2708

for different biases. I put the plots in there, to keep the info in one place,

where the label on the PD case (which Steve made without asking him) points

to.

I talked to some people recently about the fact that the responsivity (A/W) of the PD

changes even at DC for different biases. I tested this again and should be more precise about this:

The first time I observed this was in the transfer functions as shown on p. 2708.

With 'DC' I meant 'low frequency' there, as you can still see an effect of the bias as low as 100kHz.

Then at one point I saw the responsivity changing with bias also at true DC.

However, it turned out that this is only the case if the photocurrent is too high.

If the photocurrent is 4mA, you need 400mV bias to get the max. responsivity.

For 2mA photocurrent, the responsivity is already maximal for 0V bias.

An effect for relative low frequencies remains however.

The DC check of responsivity was done with white light from a bulb.

I modified C1LSC.mdl to use the CDSphase blocks, which automatically calculate the R and D phase rotation for us.  Now each of the RFPDs has 2 channels in place of the old IQ_MTRX channels:  C1:LSC-RFPD_PHASE_R and C1:LSC-RFPD_PHASE_D.

I have not yet compiled / rebooted / done CDS magic to actually make these installed.  So far the change is only in the simulink model.

I was going to wait until morning to compile/reboot/magic, so I can do it under Joe's supervision.

In the meantime, I also modified the RFPD screens.  They have white boxes for the _R and _D channels just now, but that's because the new model hasn't been put in.  They now look like phase rotators, instead of Koji's temporary matrix.

Still to do:  Find the EPICS database where the phase rotation calculation is done (you give it an angle, it gives you sin(angle) and cos(angle) ).  I want to put a "90-angle" in the database so that we can type in the measured relative phase between I and Q, and it will calculate how many more degrees it needs to get to 90deg. 

 I spiffed up the order of the cables / sensors plugged into the PEM ADCU.  Now all of the seismometers are labeled as Rana left them, and the 2 Guralp's have their sets of 3 channels next to eachother in channel-number-land.  None of the accelerometer names/cabling have changed recently.  In the table, Cable-label refers to the physical tag tied to the end of the cables plugged into the ADCU...they are meant to be descriptive of what seismometer channels they are hooked up to, and then the names change to something useful for us when they come into the DAQ system.  Also, the labels of input channels on the ASS_TOP_PEM screen have been updated accordingly.

I went to WB and found the last spare module of D990399 revB. We need to thank Frank for his foresight.

The original (=broken) board had various modifications from this revB.
I had to check the schemaric diagram and the difference between the boards and migrate some of the SMD components from left to right.

Here is the deciphered features of the QPD whitening board:
- The input stage is a VGA amp (AD602). It has the internal input impedance of 100 Ohm. The series resister
  of 909 Ohm gives us 1/10 voltage division! It is more tricky as the QPD (D990272) has the output impedances of 50Ohm
  (for the both side of the differential out) and on resistance of MAX333A. So it could have been deviated by ~10% from the nominal.

- Variable gain control: The input has 1/10 voltage division. The gain is fixed at the unity. In total the gain of the variable control stage is 1/10.
  This gives us the gain range of +42dB/-22dB for +10V/-10V. The actual range is limited to be -10~30dB.

- Whitening stages. Each channel has two sets of the whitening path and the bypass path.
  They could be switched by binary control inputs but I permanently enabled the whitening by pulling the MAX333 control inputs to the ground.
  The whitening zero and pole are at 4.02Hz and 40.6Hz.

  Each bypass path has an additional cap of 220pF in parallel to 35.7kOhm (R101 and R103 for CH1), resulting in the pole at 20.2kHz.
  Each whitening paths had a 5.6nF cap (C53 and C64). This cap was replaced with 350pF, resulting in the move of the pole freq from 800Hz to 12.7kHz.

- There are two anti-aliasing stages which were designed for 2kHz sampling rate. They are identical sallen key 2nd-order LPFs with fc=766Hz and Q=0.74 (~ butterworth).
  As all of these caps were removed, they are just voltage followers now.

- The final stage (AD620) has the gain resister of 16.5k. The gain is 1+(49.4k/16.5k) = 3.99.

- The 4pin lemo connector (J8) was removed from the board. We instead installed an isolated BNC connector on the panel for the thorlabs PD serving as the high gain PD.

- There is a daughter board for the high gain PD. This seems to be the butterworth low pass filter with fc=~30kHz.
  The differential output of the daughter board is connected to pin 17 and 18 of J10 (S5 Out and Rtn).

- The input of the daughter board is differential (AD620). Therefore the LEMO connectros next to the BNC were wrapped with Kapton tapes for isolation.

Board test at the workbench.

- The test required two dual power supply as the unit requires +/-5V and +/-15V.

- The four channels were tested with the signal injection. 1kHz input yielded 20mVpp across the AD602 input. The output of the 1st whitening stage was
  60mVpp. This makes sense as the gain of the AD620 is -10dB (1/10 and 10dB). The output of the 2nd whitening stage was 600mVpp.
  Finally the output of the output stage was confirmed to be 2400mVpp. This was confirmed for four channels.

- The daughter board output was also checked. The gain is the unity and flat upto ~10kHz.

Board installation

- Jenne installed the module. This time there was no smoke.

Gain mystery

- It was not sure how the whitening gains have been given.

- The corresponding database entry was found in /cvs/cds/caltech/target/c1auxey/ETMYaux.db as

grecord(ao,"C1:ASC-QPDY_S1WhiteGain")
grecord(ao,"C1:ASC-QPDY_S2WhiteGain")
grecord(ao,"C1:ASC-QPDY_S3WhiteGain")
grecord(ao,"C1:ASC-QPDY_S4WhiteGain")

- The gains for S2-S4 were set to be 30. However, C1:ASC-QPDY_S1WhiteGain was set to be 8.62068.
And it was not writable.

- After some investigation, it was found that the database was wrong. The DAC channel was changed from S100 to S0.
The corrected entry is shown here.

grecord(ao,"C1:ASC-QPDY_S1WhiteGain")
{
        field(DESC,"Whitening gain for QPDY Seg 1")
        field(DTYP,"VMIVME-4116")
        field(OUT,"#C0 S0 @")
        field(PREC,"1")
        field(EGUF,"42")
        field(EGUL,"-22")
        field(EGU,"dB")
        field(LINR,"LINEAR")
        field(DRVH,"30")
        field(DRVL,"-10")
        field(HOPR,"30")
        field(LOPR,"-10")
}

- Once c1auxey was rebooted, the S1 whitening gain became writable. Now all of the channels were set to be +30dB (max).

This exact situation was happening at ETMX. I did the exact same change to the database, now I can read and write all four gain segments.

I moved the Hartmut Green PD to the Jenne laser bench to try to determine if the response at RF was reasonable or somehow very much smaller than it should be. It was set up as shown in the attached diagram. The first pass at this was by comparing the ratio of the RF photocurrent of the green PD to the RF photocurrent of the New Focus 1611 InGaAs PD. That ratio (at a sufficiently low frequency) should be the same as the ratio the DC photocurrents of the two PDs.

Using the network analyzer I measured the ratio of the voltages of the two RF signals (and then scaled each of these by the respective transimpedances of the PDs: 700 Ohms for the 1611 and 240 Ohms for the Harmut PD). The resulting ratio is shown in the attached plot.

I measured the DC voltages from each PD and scaled those by the transimpedances to get the photocurrent (10 kOhm for the 1611 and 80 Ohm effective for the Harmut PD). The ratio of the DC photocurrents was 0.37. This is roughly 3x the ratio of the RF photocurrents at 500kHz (=0.14). This discrepancy is uncomfortably large.

 The full set of measurements is given in the table below:

There is one other troubling point: using the estimate of responsivity on the Harmut PD * incident power * transimpedance at DC = (0.02A/W) * (0.28mW) * (80 V/A) = 0.45 mV.

But the measured DC voltage is 6.5mV = inconsistent.

I think I had underestimated the responsivity of the Silicon PD at 1064nm. The previous value was based on a rough search online for the responsivity of Silicon (I couldn't find the product number of the actual PD we are using). For instance, the PDA100A Si detector from Thorlabs has a responsivity of 0.35-0.4A/W at 1064nm. 

If we calculate the responsivity of the Hartmut PD from the measurements I made today (input power = 0.300mW, output voltage = 5.56mV, effective transimpedance = 80 Ohms), then the responsivity at 1064nm is 0.23 A/W which is not an unreasonable number given the response of the Thorlabs detector.

Responsivity of SGD-444A

I reran the FDA in COMSOL on the MC1/MC3 Stack and produced the following Displacement-Displacement Transfer Functions:

X-Translational Drive has a blue background

Y-Translational Drive has a red background

Z-Translational Drive has a green background

Obtaining the Displacement-to-Phase part of the Transfer Function still produces difficulties -- I'm still working on the COMSOL-Matlab interface to perhaps better facilitate this.

RA: I have deleted those plots because they weren't transfer functions. Transfer functions must always be the ratio of something to something. For example: if I had a nickel for every bad plot I see, I would be a millionaire. In that example, the transfer function would have the units of nickels/plots. For the stacks, it should be meters/meter.

My apologies for the mislabeled axes on my previous plots. They have been corrected to a ratio (in./in.), as Rana so kindly suggested in his helpful, not-at-all-condescending response.

I have chosen to stay in the English system because all of the original stack drawings are in inches as well.

wonder if its possible to do variable finesse locking

Gabriele mentioned that Virgo used arm trans PDH for this, but I guess we could possibly use POX/POY to start and bring in the PRM with 50% MICH trans

We replaced the +15V sorensen at 1X1, and brought the power supplies back up symmetrically, and everything seems fine. I noted that a quarter turn counter-clockwise took the current limit down by one amp, so I set the knob to just letting 2.8A (the nominal current), and then added one half turn, shooting for ~4A current limit. 

In doing so, we had to cut power to the c1psl VME box. It didn't come back happily. We had to do the chiara /etc/hosts things, like we did for c1auxexx, to get it back.

I have setup a shared .bashrc for all the workstations that is symlinked to the normal location on all machines:

controls@rossa:~ 0$ ls -al /home/controls/.bashrc 
lrwxrwxrwx 1 controls controls 23 2012-05-25 15:37 /home/controls/.bashrc -> /users/controls/.bashrc
controls@rossa:~ 0$ 

This should help simplify maintenance considerably.  Editing that file on one machine will edit it for all.  Just edit this one file!  Don't try to get fancy and add extra files!

I also added a bunch of aliases that had previously been missing.  This should help with some of the problems that people had been having.

NOTE: PLEASE DO NOT CHANGE THE DEFAULT SHELL!  We are using bash, because that's what the sites are now using and we want to be as compatible as possible.

You can of course still write scripts in csh/tcsh or use tcsh in a shell if you wish.   Just don't change the default shell for the controls user.

In /cvs/cds/caltech


1.6M    2008-8-15.pdf
2.9M    40mUpgradeOpticalLayoutPlan01.pdf
2.4M    alh
19M     apache
18G     apps
11M     archive
4.0K    authorized_keys2
8.0K    backup.notes
8.0K    backup.notes~
1.9G    build
62G     burt
47M     cds
13M     cds40m
37M     chans
70G     conlog
52K     crontab
12K     cshrc.40m
12K     cshrc.40m~
36M     diag
1.4G    dmt
8.2M    framecpp-0.2.0
1.7M    free_080730.pdf
57M     gds
9.8G    home
60K     hooks
8.0K    hosts.40m
4.0K    id_rsa
10M     iscmodeling
110M    ldg-4.7
648M    libs
4.0K    log2.txt
224K    logs
0       log.txt
238M    medm
344M    NB
148M    NB_080304
211M    NB_080307
401M    NB40
1.2G    noisebudget.071109
837M    noisebudget.bak.20060623
3.5M    oldtarget
123M    root
5.7M    savesets
208K    schematics
655M    scripts
13G     scripts_archive
1.1M    state
3.7G    svn
4.0K    svn-commit.tmp
7.3G    target
295M    target_archive
6.7M    test
72K     test.png
4.0K    tmp
8.0K    typescript
35G     users
205M    wind


Local backup on chiara seems not working since Nov 19, 2017.
/opt/rtcds/caltech/c1/scripts/backup/localbackup.log

2017-11-18 07:00:01,504 INFO       Updating backup image of /cvs/cds
2017-11-18 07:03:00,113 INFO       Backup rsync job ran successfully, transferred 1954 files.
2017-11-19 07:00:02,564 INFO       Updating backup image of /cvs/cds
2017-11-19 07:00:02,592 ERROR      External drive not mounted!!!

I think this is because /cvs/cds is getting too big. lsblk reveals:

I believe one of sdc or sdd is connected via SATA while the other is an external USB drive. Maybe we have to get bigger backup disks, but this may be a huge pain to setup as it will involve taking chiara down. Actually, now that I check the backup log, seems like backup is executing successfully - not sure if this is due to my unelogged mounting of sdc (using sudo mount /dev/sdc1 /media/40mBackup) last week, or if this is some LDAS backup. But in any case, seems undesirable that sdb1 is larger than sdc1 or sdd1.

I was able to bring back svn 1.6 formatting to /cvs/cds/caltech/chans by doing the following on nodus:

Note that I used the http address for the repository. The svn repository doesn't live at file:///cvs/cds/caltech/svn anymore; all of our checkouts (e.g. in the scripts directory) use http to get the one true repo location, regardless of where it lives on nodus' filesystem. (I suppose we could also use https://nodus.martian:30889/svn to stick to the local network, but I don't think we're that limited by the caltech network speed)

Presumably, at some point we will want to introduce a newer operating system into the 40m, as ubuntu 12.04 hits end-of-life in April 2017. Ubuntu 16.04 includes svn 1.8, so we'll also hit this issue if we choose that OS. 

Aside from the svn issues, this directory (/cvs/cds/caltech/chans) only contains pre-2010 channels. Filters and DAQ ini files currently live in /opt/rtcds/caltech/c1/chans, which is not under version control. It's also not clear to me why summary page configurations should be kept in this /cvs/cds place.

True - its an issue. Koji and I are updating zita into Ubuntu16 LTS. If it looks like its OK with various tools we'll swap over the others into it. Until then I figure we're best off turning allegra back into Ubuntu12 to avoid a repeat of this kind of conflict. Once the workstations in the LLO control room are running smoothly on a new OS for a year, we can transfer into that. I don't think any of us wants to be the CDS beta tester for DV or DTT.

Just to be clear, since there seems to be some confusion, the SVN issue has nothing to do with Debian vs. Ubuntu.  SVN made non-backwards compatible changes to their working copy data format that breaks newer checkouts with older clients.  You will run into the exact same problem with newer Ubuntu versions.

I recommend the 40m start moving towards the reference operating systems (Debian 8 or SL7) as that's where CDS is moving.  By moving to newer Ubuntu versions you're moving away from CDS support, not towards it.