40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 12 of 341  Not logged in ELOG logo
ID Date Authorup Type Category Subject
  8862   Wed Jul 17 11:13:36 2013 Alex ColeConfigurationElectronicsAS Table Additions

[Eric, Alex]

For the RFPD frequency response project, we routed the fiber that will connect our REF DET (on the AS table) to our 1x16 optical splitter (in the OMC_North rack), as pictured. (The new fiber is the main one in the picture, which ends at the right edge near REF DET) Note that we secured the fiber to the table in two places to ensure the fiber would remain immobile and out of other optical paths already in place.

At 2:00 we plan to run fiber from our laser module (in rack 1Y1) to our 1x16 optical splitter (in the OMC_North rack) and measure the power output at one of the splitter's output ports. We plan to keep the output power limited to less than 0.5 mW per optical splitter output.

  8863   Wed Jul 17 16:15:42 2013 Alex ColeConfigurationElectronicsAS Table Additions

[Eric, Alex]

We decided that the POY Table would be a better home for our REF DET (Newport 1611 FC-AC) than the AS Table. We moved the PD to the POY Table (1st attachment) and routed a fiber from our 1x16 Optical Splitter in the OMC_North rack to the POY Table. REF DET's power supply is now located under the POY table (2nd attachment). We left the fiber described in the previous post on the AS Table.

Afterwards, we hooked a fiber up to our laser module to test it (3rd attachment). The laser was not being distributed, just going to one fiber with a power meter at its end. Everything turns out, but we realized we need to read the power supply's manual before continuing. 

 

 

  8870   Thu Jul 18 15:34:15 2013 Alex ColeUpdateElectronicsPD Frequency Response Update

 [Eric, Alex]

Our RF Switch arrived today, and we mounted it in rack 1Y1 (1st attachment). 

We connect our input fiber and all of our output fibers to our 1x16 optical splitter (2nd attachment). Note that the 75 meter fiber we are using for the splitter's input is in a very temporary position (3rd attachment - it's the spool).

We successfully turned our laser on and tested the optical splitter by measuring output power at each fiber using our Thorlabs PM20 power meter. Data was taken with the laser running at 67.5 mA and 24 degrees Celsius:

Detector name                  Power

REF DET 192 µW
AS55 146 µW
REFL55 180 µW
REFL11 172 µW
MCREFL 133 µW
REFL33 146 µW
REFL165 180 µW
POP22/POP110 182 µW
POP55 193 µW
POX11 123 µW

 

 

  8940   Tue Jul 30 16:21:46 2013 Alex ColeUpdateElectronicsPhotodetector Input Modulation

 [Eric, Alex]

We successfully used our system to modulate the input to a single photodetector. The RF Out of the network analyzer went to the Mod In of our laser, which was operating at 98 mA. The laser's output was sent to our 1x16 optical splitter. This provided input signals for both our reference detector and AS55. Our reference detector's output was sent to the network analyzer's R input, while the AS55's output was sent to the network analyzer's A input. 

We still need to work out the specifics of how the modulation works. Specifically, we want to look at the amplitude of the network analyzer's output. Additionally, we may have been saturating our reference detector, causing noise problems.

  8947   Wed Jul 31 17:02:17 2013 Alex ColeUpdateElectronicsPreliminary Photodetector Frequency Reponse Measurements

[Eric, Alex]

We used our setup from yesterday (elog #8940) to measure transimpedance measurements for AS55, REFL11, REFL33, and REFL55, using our Newport 1611 FC-AC as reference. We connected the fibers to their respective telescopes such that the beams focused on their photodetectors, using a multimeter to maximize photodetector DC output. Plots are attached. At first glance, the poles seem to be where they're supposed to be.

Note that the procedure used today is similar to what the eventual automated procedure will be. The main differences are (1) The RF Switch will be used rather than manual switching (2) NWAG4395A will be used to collect data rather than netgpibdata (3) Data will be fit using vectfit4.m and compared to some canonical set.

  8955   Thu Aug 1 18:55:20 2013 Alex ColeUpdateElectronicsPreliminary Photodetector Frequency Reponse Measurements

Quote:

[Eric, Alex]

We used our setup from yesterday (elog #8940) to measure transimpedance measurements for AS55, REFL11, REFL33, and REFL55, using our Newport 1611 FC-AC as reference. We connected the fibers to their respective telescopes such that the beams focused on their photodetectors, using a multimeter to maximize photodetector DC output. Plots are attached. At first glance, the poles seem to be where they're supposed to be.

Note that the procedure used today is similar to what the eventual automated procedure will be. The main differences are (1) The RF Switch will be used rather than manual switching (2) NWAG4395A will be used to collect data rather than netgpibdata (3) Data will be fit using vectfit4.m and compared to some canonical set.

 [Alex, Eric]

Today I spent some time mounting the launcher and performing the same data collection for POX11. I think I still need to focus the launcher so the photodetector gets a good signal, but the data from today wasn't too bad.  Additionally, I worked on matlab scripts to improve PDFR data analysis.

This time I collected data from the network analyzer using NWAG4395A in the netgpibdata directory. The advantage of this is that the computer tells the network analyzer to perform the sweep as well as retrieving the data.

For analysis, I improved my implementation of vectfit4.m so that it focuses in on the particular photodetector's predicted peaks and thus ignores much of the noise, giving a better fit. The raw data is the red circles in the 2nd attachment, while the fit is the blue line. I also had the program return the frequency value of the peak. For POX11, this was 1.106e+07 Hz.

I also finagled copies of existing programs to enable one to plot multiple transfer functions on the same axes. This function is /users/alex.cole/plottwo.m. I will eventually use this to compare new data to some canonical data so that we may monitor photodetector performance over time.

The eventual plan is to generate two plots per photodetector, one of which will compare new data to the canonical set, the other of which will show the fit of the data. Both will have subplots that zoom in around regions of interest (known peaks and notches), and the plot which displays the canonical set will also have Q's of peaks and their locations.

  8971   Tue Aug 6 12:43:23 2013 Alex ColeConfigurationElectronicsAS Table and Rack 1Y1 Additions

For the photodetector frequency response project, I finished the construction of our baluns chassis and mounted it in rack 1Y1 (1st picture).

After consulting with Jenne, I mounted the fiber launcher for REFL165 on the AS table such that it would not cause an obstruction. I aligned the launcher using a multimeter to monitor the DC output of REFL165, but looking at the data I got, it seems I need to do a better alignment/focusing job to get rid of a bunch of noise.

  8979   Wed Aug 7 15:51:53 2013 Alex ColeConfigurationElectronicsRF Switch Change

For the photodetector frequency response project, our new RF Switch Chassis (NI pxie-1071) arrived today. I took the switches out of the old chassis (Note for future generations: you have to yank pretty darn hard) and put them in the new chassis, which I mounted in rack 1Y1 as pictured. 

The point of this new chassis is that its controller is compatible with our control room computer setup. We will be able to switch the chassis using TCP/IP or telnet, aiding in our automation of the measurement of photodetector frequency response.

  9004   Tue Aug 13 11:40:19 2013 Alex ColeSummaryElectronicsRFPD Demod Filter Frequency Response Measurement

 For the RF PD Frequency Response Measurement project, we get each PD signal from the "PD RF Mon" output of each demodulator board corresponding to our PD under test. Therefore we can't neglect the frequency response of various filters inside the demodulator board. I used our Agilent 4395 Network Analyzer to gather frequency response data for each demodulator board being considered for the RFPD frequency response project (AS55, REFL11, REFL33, REFL55, REFL165, POX11, POP22, POP110).

The NA swept over a frequency range of 1-500 MHz. Data was collected using NWAG4395A (from the netgpibdata directory). It should be noted that the command line options -a 16 -x 15 (averaging=16 and excitation amplitude=15 dBm[the max]), in addition to the usual command line options described in the help file, were used to minimize noise. 

The data is located in /users/alex.cole. The file names are in the format [PDNAME]DemodFilt_1000000.dat (e.g. REFL11DemodFilt_1000000.dat). Results for POP110 are shown below.

  9005   Tue Aug 13 11:54:40 2013 Alex ColeHowToElectronicsRF PD Fiber-Coupled Laser Operation

This post pertains to the fiber-coupled diode laser mounted in rack 1Y1.

To turn the laser on, first turn the power supply's key (red) to the clockwise. Then make sure that the laser is in "current" mode by checking that the LED next to "I" in the "Laser Mode" box in lit up. If the light is not on, press the button to the right of the "I" light until it is. Now press the output button (green). This is like removing the safety for the laser. Then turn the dial (blue) until you have your desired current. Presently, the current limit is set to around 92 mA.

To turn the laser off, dial the current back down to 0mA and turn the key (red) counterclockwise.

  9006   Tue Aug 13 13:30:41 2013 Alex ColeConfigurationElectronicsCable Routing

 I routed cables (RG405 SMA-SMA) from several demodulator boards in rack 1Y2 to the RF Switch in rack 1Y1 using the overhead track. Our switch chassis contains two 8x1 switches. The COM of the "right" switch goes to channel 7 of the "left" switch to effectively form a 16x1 switch. The following is a table of correspondences between PD and RF Switch input.

 

PD Left/Right Switch Channel Number
REFL11

R

0
POX11 L 0
AS55 R 1
REFL55 R 7
POP22 R 6
REFL165 R 5
REFL33 L 7

 

ThePOP110 demod board has not yet had a cable routed from it to the switch because I ran out of RG405.

We should also consider how important it is to include MCREFL in our setup. Doing so would require fabrication of a ~70 ft RG405 cable. 

  9059   Fri Aug 23 21:01:38 2013 Alex ColeHowToElectronicsAutomated Photodetector Frequency Response System

 This post describes how to use the Automated Photodetector Frequency Response System.

On the mechanical side, turn on:

-the diode laser (in rack 1Y1)

-the RF Switch (in rack 1Y1)

-the reference PD (under the POY table)

-the AG4395A Network Analyzer

The NA’s RF output should go to the laser’s modulation input, the reference PD’s output should go to the NA’s R input, and the RF Switch Chassis’s output (which is the combination of the two switches’ COM channels using a splitter) should go to the NA’s A input.

Once this is done, navigate into /users/alex.cole and run PDFR.sh. This script collects data for each photodetector under consideration by switching using a python script and communicating with the NA via GPIB. It then sends all the data to RF.m, which fits the functions, plots the latest data against canonical data, and saves the plots to file.

The fitting function, fit.m, also outputs peak frequency to the command line. This function uses PD name data (e.g. ‘REFL33’) to choose an interval with minimal noise to fit.

The main script prompts the user to press enter after each NA sweep to make sure that measurements don’t get interrupted/put out of order by RF switching.

Once you're done, you should turn off the laser, NA, RF Switch, and reference PD.

Troubleshooting

Sometimes, the NA throws up and doesn’t feel like running a particular sweep. If this happens, it’s a good idea to keep the matlab script from trying to analyze this PD’s data. Do this by opening up RF.m and commenting out the calls to ‘fit’ and ‘canonical’ for that PD.

If fit.m complains about a particular set of data, it is often the case that the N/P ratio (where N is order of approximation and P is number of points in the interval) is too high. You can fix this by reducing N or making the PD’s frequency range (chosen in the fnew_idx line) larger.

Choosing a single PD

If you only want to grab the transfer function for one PD, first look up which switch input it belongs to. This information is contained in /users/alex.cole/switchList. To turn the switch to a particular input, type something like:

python rf.py “ch7”

This command uses TCP/IP to tell the switch to look at channel 7. Switch input numbers range from 1 to 16, though not all of them are in use.

Once the switch is looking at the correct input, you can run a sweep and download the data by typing /opt/rtcds/caltech/c1/scripts/general/netgpibdata/NWAG4395A -s 1000000 -e 500000000 -c 499000000 -f [filestem for output] -d [path of directory for output] -i 192.168.113.108 -g 10 -x 15. 

  2075   Fri Oct 9 14:23:53 2009 Alex IvanovConfigurationDAQtpchn mystery

"Yes. This master file is used."

Quote:

Does anyone know if this master file is the real thing that's in use now? Are we really using a file called tpchn_C1_new.par? If anyone sees Alex, please get to the bottom of this.

allegra:daq>pwd
/cvs/cds/caltech/chans/daq
allegra:daq>more master
/cvs/cds/caltech/chans/daq/C1ADCU_PEM.ini
#/cvs/cds/caltech/chans/daq/C1ADCU_SUS.ini
/cvs/cds/caltech/chans/daq/C1LSC.ini
/cvs/cds/caltech/chans/daq/C1ASC.ini
/cvs/cds/caltech/chans/daq/C1SOS.ini
/cvs/cds/caltech/chans/daq/C1SUS_EX.ini
/cvs/cds/caltech/chans/daq/C1SUS_EY.ini
/cvs/cds/caltech/chans/daq/C1SUS1.ini
/cvs/cds/caltech/chans/daq/C1SUS2.ini
#/cvs/cds/caltech/chans/daq/C1SUS4.ini
/cvs/cds/caltech/chans/daq/C1IOOF.ini
/cvs/cds/caltech/chans/daq/C1IOO.ini
/cvs/cds/caltech/chans/daq/C0GDS.ini
/cvs/cds/caltech/chans/daq/C0EDCU.ini
/cvs/cds/caltech/chans/daq/C1OMC.ini
/cvs/cds/caltech/chans/daq/C1ASS.ini
/cvs/cds/gds/param/tpchn_C1_new.par
/cvs/cds/gds/param/tpchn_C2.par
/cvs/cds/gds/param/tpchn_C3.par

 

  4779   Thu Jun 2 10:19:37 2011 Alex IvanovSummaryDAQinstalled new daqd (frame builder) program on fb (target/fb/daqd)

I hope that new daqd code will fix the problem with non-aligned at 16 seconds frame file GPS times.

I have compiled new daqd program under /opt/rtcds/caltech/c1/core/release/build/mx and installed it under

target/fb/daqd, then restarted daqd process on "fb" computer. It was installed with the ownership of user root

and I did chmod +s on it (set UID on execution bit). This was done in order to turn on some code to renice daqd process

to the value of -20 on the startup. Currently it runs as the lowest nice value (high priority).

 

controls@fb /opt/rtcds/caltech/c1/target/fb $ ls -alt daqd
-rwsr-sr-x 1 root controls 6592694 Jun  2 10:00 daqd

 

Backup daqd is here:

 

controls@fb /opt/rtcds/caltech/c1/target/fb $ ls -alt daqd.02jun11
-rwxr-xr-x 1 controls controls 6768158 Feb 21 11:30 daqd.02jun11

 

 

  6094   Fri Dec 9 14:33:16 2011 Alex IvanovUpdateAdaptive FilteringC1OAF

Quote:

I tried to figure out why red NO SYNC label became present in the C1OAF_GDS_TP screen after I added AA filters to the C1OAF model.

C1OAF model contains 8 libraries C1OAF_ADAPT for 8 DOF. I changed C1OAF_ADAPT library to C1OAF_ADAPT_AA library where I added 28 AA filters for 28 witness channels. It turns out that if I use this library for all 8 DOF then I see NO SYNC label, if only for one DOF (MCL) then I see green IOP label. This means that using AA filters for each DOF too much channels of filters are created for online system to operate. I think there is some number inside the code that one can not exceed. Analyzing compilation output after "make c1oaf" I figured out that without using AA filters we have 632 filters and using AA we have 856 filters.

For now I'll use AA filters for MCL only.

 I have a feeling we are not fitting into pre-allocated memory space in the shared memory between the front-end process and the epics process. Filter module data is overwriting some other data and that's why we are not getting a sync light. I suggest we upgrade to 2.4 code first and then we will figure out a way to expand memory areas to fit 856 filters.

  7146   Fri Aug 10 17:17:41 2012 Alex Masha DenUpdatePEMclassify seismic c code

Den and I installed a module in the c1pem model which has a feedforward neural network to classify seismic disturbance (10 means quiet, 20 truck, 30 earthquake). There is a channel SEIS_CLASS which should specify the class of the seismic signal. The code works for signals sampled at 256 Hz, so an anti-aliasing filter must be installed in order to decimate from the 2048 model.

The models were compiling slowly, so Alex removed the archiving feature (gzip and tar were taking a lot of time).

Den and I also had trouble with a simple for loop in our model, so we talked to Alex who noted that the -O3 compiler unravels for loops in a buggy way. Thus, we have compiled c1pem using the -O compiler.

PS: the Trilium seismometer now has legs.

  5249   Tue Aug 16 16:59:20 2011 AnamariaUpdateRF SystemAM in the PM

Kiwamu, Keiko, Anamaria

Looking at the I and Q signals coming from REFL11 and REFL55 we saw large offsets, which would mean we have amplitude modulation, especially at 11MHz. We checked the PD themselves with RF spectrum analyzer, and at their frequencies we see stationary peaks (even if we look only at direct reflection from PRM). We changed the attenuation of the PSL EOM, and saw the peak go down. So first check is beam out of PSL EOM, to make sure the input beam is aligned to the crystal axis and is not giving AM modulation in adition to PM.

  5255   Wed Aug 17 15:47:18 2011 AnamariaUpdateSUSETMX Side Sensor slow channel down for a long time

Jenne, Anamaria

We aligned the ETMX OSEMs and ran into this issue. Looking at the SENSOR_SIDE channel, we pulled out the OSEM and determined that the open light voltage is 874 counts, so we centered it around 440 as well as we could. This is same channel as its slow counterpart SDSEN_OUTPUT (grey number immediately to the right on SUS medms).

 

 

Quote:

The slow signal from the side sensor on ETMX was last seen in action sometime in May 2010!  And then the frame builder has no data for a while on this channel.  After that the channel shows some bistability starting Sept 2010 but has not been working.  The fast channel of this sensor  (C1:SUS-ETMX_SDSEN_OUTPUT) does work so the sensor is working.  Probably is a loose contact... needs to be fixed.

 

 

  5278   Mon Aug 22 20:37:43 2011 AnamariaConfigurationRF SystemPlan for install of 3f PDs

I made a quick sketch of how to include two more RF PDs on the REFL beam, given the space we have on the table. We want to install REFL33 and REFL165, 3f signals for the the two modulation frequencies we are using. The point is to make the distance from first beam splitter the same to all PDs so that we can use only one lens before this BS to make the beam the right size. Currently there are 2 PDs on the refl beam, REFL11 and REFL55, predictably. So the drawing shows 4 PDs. Drawing is to scale but is a bit coarse. Hopefully we'll take pictures once we're done.

Reference from current BS splitting beam to the existing PDs.

  5284   Tue Aug 23 06:49:24 2011 AnamariaUpdateGeneralmore in-vac work : AS clipping fixed and OSEM/oplev adjustment

Where was the AS clipping?! Ah, the suspense...

Quote:

  + fixed the AS clipping issue

 

Quote from #5275

We need to check/fix the AS beam clipping and once it's done we will readjust the OSEM mid range and the oplevs.

 

 

 

  5389   Mon Sep 12 18:45:04 2011 AnamariaConfigurationLSCAP table current layout

Before we install the REFL 3f PDs I made a drawing of the current table layout, since there has been no update lately. Once I've incorporated the two extra PDs (now seen sitting bottom left), I will update the drawing and post in the wiki as well.

  5401   Wed Sep 14 01:19:20 2011 AnamariaConfigurationLSC3f PD Install in Progress

I have reconfigured the refl beam path on the AP table to include REFL33 and REFL165. Would be done if we hadn't prepared P BSs instead of S, which required some serious digging to find two others. And if someone hadn't stolen our two 3m SMA cables that Keiko and I made on our previous visit and I had left with the 3f PDs. I don't expect them to reappear but if they do, it would be grand.

Note: Refl beam from ifo looks a bit high, ~1cm on the lens 20'' from output port. Not sure what that means about ifo alignment change, I've left it as is. When we know we have a good alignment, we should be able to easily realign the beam path if necessary. If it remains the same, we might want to change the lens height.

Done:

1) REFL11 and REFL55 are now hooked up and aligned in a low power beam. (I set the power as low as I could by eye to not risk burning the PDs during alignment)

2) The required BSs and REFL33 and REFL165 are in place, powered.

3) I have set them in a configuration such that the beam is the same distance from the main beam, to adjust beam size easily for all 4.

4) Camera has been moved from main beam to behind a steering mirror, ND filters removed, centered on camera.

To Do:

1) Find one more longish SMA cable.

2) Align beam on REFL33 and REFL165.

3) Check beam size carefully. (I get a plateau on the scope, and I can "hide" the beam on the PD, but it could be better. The path has become longer by ~5-8inches.)

4) Adjust power.

5) Redo layout diagram, post in wiki.

  5414   Thu Sep 15 02:18:19 2011 AnamariaUpdateLSCMICH locked and attempt to lock PRCL

Kiwamu, Keiko, Anamaria

 

We were able to lock PRC using REFL11I after improving the MICH dark fringe a bit (moving BS) and rotating AS55 and REFL11 such that the signal was maximized in the phases we were using. The dark port is not so dark... but the lock is stable.

I had finished the whole REFL path alignment, but I didn't have a good input beam reference at the time, which is why we had to realign the PDs and the camera. We only had strength to realign 11 and 55. Otherwise, we just need to tweak and center beam on 33 and 165, figure out what's up with 55 and be done with the AP table mods. I hope.

 

Quote:

 Anamaria, Keiko

- We aligned MICH and were successfully locked MICH using AS55Q. The other mirrors were misaligned so that the other degrees of freedom didn't exist. AS55 was fed back to BS. The f2a filters on BS suspension were required to lock, because the pos feedback was unbalanced to angle degrees of freedom.

- We tried to lock PRCL next, however, because we aligned the MICH and the REFL beam paths were changed, REFL PDs didn't have the light anymore. The REFL paths were modified now, so we will try the PRCL locking next.

- We couldn't confirm REFL55 signals although we alined the REFL paths to REFL55 PD.

 

  5430   Fri Sep 16 03:22:11 2011 AnamariaUpdateLSCMore Refl PDs Work and Attempt at DRMI

Kiwamu, Keiko, Anamaria

I started today with a different input beam, so I had to realign the REFL path again. Then we measured the RF signal out of the 4 REFL PDs and found them to be too low. We increased the power to around 10mA for each diode, and we can see the right modulation frequency on each diode, though REFL165 is way too weak so we might need an RF amplifier on it. We will measure demod board noise tomorrow.

We had an issue with REFL165 not giving the right DC level, low by a factor of 10, even though it was receiving the same optical power as the others. We fifteen-checked clipping and alignment, then pulled it out and measured it on the test stand - found it to be ok. So I uplugged its power cable at the rack and connected it to the AS165 slot. Problem sloved. Not sure what was wrong with the other power slot.

Then we found REFL55 to be clipping on its black glass, we fixed that. But the REFL55 DC power still changes a lot with seemingly not huge motions of the PRM. We'll investigate more tomorrow.

We added a lens in the path to REFL165 because unlike the others it is a 1mm diode. All diodes have about half a turn to a full turn flatness of maximum (on tiny steering mirror).

We set the whitening gain on all four diodes to 21 db.

Not sure if we should set the power to be different on these diodes since their sensitivity is different to RF, and now REFL11 sees huge signal.

We continued the DRMI locking attempt and brought in the SRC, using AS55I to control it. It kind of works/stays locked. We did manage to get MICH and PRC better controlled than last night, but with SRC in the mix, something is wrong. We have to redo f2a filters on SRM and hopefully things will be better after Jenne's suspension work tomorrow. Oplevs not optimized yet either.

We intend to realign POY beam path so we can monitor power in cavities.

  5475   Tue Sep 20 03:12:14 2011 AnamariaUpdateSUSJenne's Scripts started

I followed Jenne's instructions, ran the matrix filler script and then set the optics to freeswing. Someone has to burt resture and damp them in the morning.

  5489   Tue Sep 20 20:58:35 2011 AnamariaConfigurationLSCNew AP Table Drawing

As promised, I have made a final AP table drawing, including the MC camera relocation changes by Kiwamu. I have posted it in the wiki on the tables list, and on the AP table page I've attached the inkscape .svg I used to make it, if someone needs to do small modifications.

Attached is a pdf version of it.

Big changes:

1) REFL beam has been split into 4, to go in equal powers and equal beam size to the now 4 REFL RFPDs, 11, 33, 55 and 165. A lens had to be added for REFL165 because it's a 1mm PD instead of 2mm like the other 3.

2) MC camera has moved.

3) I've cleaned up most of the random components on the table, put them away, and tidied up the cabling.

 

  5513   Thu Sep 22 04:49:14 2011 AnamariaUpdateLSCLocking status update - Some Scripts, No Louck

The scripts I wrote can be found in /users/anamaria/scripts/sensemat/

]There are two of them:

- one that sets all the switches, gains, frequencies, etc, then cycles through the various RFPDs I and Q into the LOCKIN signal, so as to see the sensing matrix.

- the second one is a matlab script that takes the crappy file tdsavg outputs and makes it into a cute mag/phase matrix.

They're quite primitive at this point, I've forgotten a lot of tcsh... may improve later. But could be useful later to someone else at least.

I don't think it's particularly the fault of the script that we can't measure the sensing matrix. We can slam on the excitation by hand, and it holds for a little while. I set a wait time for lock to adjust, and most times it just oscillates a bit for a few seconds. Also, the script turns on the excitation and it's done, the rest is just measurement, then turns it off at the end. So during the script, there's not much to deal with, except keeping the lowpass filters quiet when switching the signal to demod; but that doesn't go anywhere, so it definitely doesn't disturb the ifo. Turns out pressing the RSET clear history button needs a 2 to make it happen.

I think I might prefer to set the excitation to run, and then do the old retrieve-data-later-nds-matlab thing. I do not trust these measurements without coherence and a bit of variance study, given instabilities.

Point is... Even on carrier, the PRC lock is not stable by any means. Can barely turn on low freq boosts, every other lock. Until we fix the lock stability issue, there's not much to measure I guess.

Unfortunately, I don't know how to make that happen. Before we leave on Friday we could do a few sanity checks such as measuring the noise of the RFPDs vs ADC+whitening, which I may have said I would do; and perhaps setting up a couple OSAs, one on REFL, one on AS, to make sure we know what the sidebands are doing. Both of which Rana suggested at some point.

(There used to be a quote here from Keiko here but I got mad when it reformated my entire log to be one cluster- hence the look)

  5525   Thu Sep 22 22:55:01 2011 AnamariaUpdateLSCPOX channel = POY PD connected + Bad Rack

Keiko, Anamaria

We decided we needed a DC channel to sense the gain in the PRC, so we set to align POY55. It took a while because the beam was very weak, and it comes in upwards, so we used a couple of mirrors to bring to a reasonable flat level, and put it on the PD. Then we went to read the DC out and we got 1.3V stationary! Nonsense. We also realized there is no LO for this PD, or any other 55MHz PD, aside from REFL55. Oh well, we only wanted the DC for now. POY55 is aligned (decently).

Koji told me to try swapping the power cable, so I unplugged it at the rack and plugged it in another power card. And it worked! I then moved the DC out (back of rack) to follow the front, and it turns out POY55 diode is read on the POXDC channel. I plugged and unplugged it in disbelief, but it is what it is. At least we have a readout on the power level in PRC.

I attach a picture of the power cards for the LSC RFPDs, with the 3 I found to be bad, and showing current config. I had to move REFL11 and POY55 from their assigned spot.

The two on the lower left are bad in the sense that they put an offset on the PD and make the DC readout be 1.3V for no reason (when working, for example, POY55 read 60mV). The one on the lower right I had trouble with some time ago, it made the PD not read any voltage at all (when working it would read at least 100mV). Beyond that I have not investigated what is up, since I could find working plugins.

  5545   Mon Sep 26 15:15:45 2011 AnamariaUpdateLSCRealignment of REFL / Some 3f PRMI locking / Recycling Gain

A few comments on REFL table alignment and REFL165.

Last time we realigned the table was after the PZT work by Koji/Kiwamu; we made sure that the beam was going through optics satisfactorily and that we were reading reasonable numbers. I did use primarily a viewer to align onto PD, after which we used the voltage reading to center better around that spot. As desired, I could not see the beam once it was centered on the PD. I never touched the PBS unfortunately, so I never noticed it was not fixed. Sad.

I am very surprised to hear the reading from REFL165, since I was reading around 400mV from it a few days before. Something strange happened in the mean time. I hope not when I was plugging and unplugging at the power rack for the POY work. But I would not have needed to touch REFL165. Those cables should get some strain relief at the rack, by the way.

I thought about it, and I must admit that after we centered camera on REFL (paired with an alignment), we did not check the beam path later, even after we saw that the REFL beam had moved. We only did a quick by-viewer check that the beams were not off of the PDs.

Quote:

[Koji Suresh]

- The REFL path has been thoroughly aligned
Many optics had the spots not on the middle of the optic, including the PBS whose post was not fixed on the post holder.
We aligned the optical paths, the RF PDs, and the CCD. The alignment of the PD required the use of the IR viewer.
One should not trust the DC output as a reference of the PD alignment as it is not enough sensitive to the clipping.

We aligned the optical paths again after the reasonable alignment of PRM is established with the interferometer.
"Next time when you see REFL spot is not at the center of the camera, think what is moved!"

- The REFL165 PD is disconnected from the power supply
I found that the REFL165 PD is producing 7.5V output at the DC monitor no matter how the beam is blocked.
As I could not recover this issue by swapping the power connector at the LSC rack, I disconnected the cable
at the RFL165 PD side. I need to go through the PD power supply circuit next week.

 

  5243   Mon Aug 15 21:43:29 2011 Anamaria and KeikoSummaryLockingcentral part ifo locking project

 REFL33 and REFL165 cables were connected from the AP table to the rack.  Cables on the rack for REFL33I, 33Q, 165I, 165Q ports were connected, too. Connections were confirmed by the data viewer. Two SMA cables which will be used for the two PDs on the AP tabl were built. We will be able to place the two PDs tomorrow. The beamsplitters to split the laser to REFL33 and REFL165 ports were mounted and ready to be placed.

  15762   Wed Jan 13 16:09:29 2021 AnchalHowToCDSAcromag wiring investigation

I'm working on a better wiring diagram that takes into account multiple power supplies, how their GND is passed forward to the circuits or sensors using those power supplies and what possible wiring configurations on Acromag would give low noise. I think I have two configurations in mind which I will test and update here with data and better diagrams.


I took some striptool images earlier yesterday. So I'm dumping them here for further comments or inferences.

  15774   Wed Jan 20 18:07:09 2021 AnchalSummaryBHDHAM-A Coil Driver measurements before modifications

I have taken transfer functions and noise measurements of the two HAM-A coil driver boxes D1100687 #S2100027 and #S2100028. All transfer functions look as expected. I'm not sure about the noise measurements. If anyone sees flaw in my measurement method, please let me know. I'm not sure why in some channels I got 10Hz harmoni peaks in the noise. That was very strange. Also let me know if my current noise estimate is wrong.

Transfer Function Measurement details

  • SR785 source out was connected to the differential amplifier input of D1900068.
  • The one pair of two BNC outputs of this differential amplifier goes directly to the SR785 Input 1 A and B.
  • The DB9 output of the differential amplifier goes to the Coil Input DB9 connector J3.
  • Header W2 was shorted to provide ground to the incoming signal.
  • Header P4 was shorted to enable all the channels manually.
  • Normal operation is the Acquisition mode (Acq) while when pins of header P3 are shorted, we go into the Run mode for respective channel.
  • The “To Satellite Box” DB25 port at the read side was conencted to a DB25 breakout circuit and pins 1-9, 3-11, 5-13 and 7-15 were connected to 36 Ohm resistor to simulate Coil load.
  • The “Output Monitor” on the rear side is then connected to the test switch DB9 port on D1900068.
  • The the pair of BNCs from the test switch is connected to SR785 Input 2 A and B.
  • Measurements are taken with file D1100687_TF.yml and D1100687_TF_LF.yml.
  • A measurement of just cables without the DUT is taken as well.
  • Commands.txt list all the commands used.
  • All data is compiled and plotted in Plotting.ipynb
  • D1100117_S2100027_TF.pdf and D1100117_S2100028_TF.pdf shows all the transfer functions measured.

Spectrum Measurements

  • All channels were kept in disabled mode (Not shorting P4) to ensure their inputs are grounded on the board.
  • I ran two BNC cables with their centers connected to output monitors V2+ and V2- and one of their shields connected to board GND.
  • in SR785, A-B differential mode always runs with grounded shields mode, so effectively the board GND got grounded to SR785 GND through internal 50 Ohm resistor. But all ground loops have been evaded.
  • The two BNC cables were twisted together to minimize the area between the two center cores of the cables as that is the remaining pickoff possible in this measurement.
  • Instrument noise with cables was measured first but shorting the clips of the center cores and one of the shields of the two BNC cables together.
  • Measurements were taken with file D1100687_SP.yml and D1100687_SP_LF.yml.
  • D1100117_S2100027_Voltage_Noise_Spectrum.pdf and D1100117_S2100028_Voltage_Noise_Spectrum.pdf shows the measured voltage noise spectrum at the output monitors when loaded with 36 Ohms.
  • D1100117_S2100027_Current_Noise_Spectrum.pdf and D1100117_S2100028_Current_Noise_Spectrum.pdf shows the esitmate current noise through the coil calculated by dividing the measured voltage noise by 2436 Ohms.
  15776   Mon Jan 25 18:18:04 2021 AnchalSummaryBHDSatellite Amplifier Transfer Functions and noise

 

I took transfer function and noise measurement of satellite amplifier box's photodiode transimpedance circuit. For the measurement, I created a makeshift connector to convert backside DB25 into DB9 with the 4 channels for PDA input. The output was taken in differential form at the front PD Output port. To feed current to the circuit, I put in 12 kOhm resistors in series at the inputs, so the V/V transfer function measured was multiplied by 12 kOhm to get the transimpedance of the circuit.


Transfer Function Measurement details

  • SR785 source out was fed into PDA input pins using a makeshift BNC-DB9-DB25 converter.
  • The output from PDOut DB9 port was fed to test switch in D1900068 to separate differential signal.
  • This differential signal was fed back to SR785 at input 2 in A-B configuration.
  • Measurements are taken with file D1002818_TF.yml and D1002818_TF_LF.yml.
  • A measurement of just cables without the DUT is taken as well.
  • Commands.txt list all the commands used.
  • All data is compiled and plotted in Plotting.ipynb
  • D1100117_S2100029_TFandNoiseSpectrum.pdf shows all the transfer functions measured.

Spectrum Measurements

  • Two pair of BNC cables were twisted together and clips were added at ends.
  • One of the GND was connected to board GND. Rest were left unconnected to avoid ground loops.
  • Each pair of signal was connected to PDOutP/N.
  • The PDA inputs were shorted together to make zero input current to the board.
  • Instrument noise with cables was measured by shorting the clips of the center cores and one of the shields of the two BNC cables together.
  • Measurements were taken with file D1002818_SP.yml and D1002818_SP_LF.yml.
  • Input referred current noise spectrum was calculated by dividing the output voltage noise spectrum by the measured transfer function.
  • D1100117_S2100029_TFandNoiseSpectrum.pdf shows all the output votlage noise spectrum and input referred current noise spectrum measured.

Edit Wed Feb 10 15:14:13 2021 :

THE NOISE MEASUREMENT WAS WRONG HERE. SEE 40m/15799.

  15778   Tue Jan 26 12:59:51 2021 AnchalHowToCDSAcromag wiring investigation

Taking inspiration from SR785 on how it reads differential signal, I figured that acromag too always need a way to return current through RTN ports always. That must be the reason why everything goes haywire when RTN is not connected to IN-. Now for single ended signals, we can always short RTN to IN- and keep same GND but then we need to be careful in avoiding ground loops. I'm gonna post a wiring diagram in next post to show how if two signal sources connect to each other separately, a GND loop can be formed if we tie each IN- port to RTN on an acromag.
Coming to the issue of reading a differential signal, what SR785 does is that it connects 50 Ohm resistance between Earth GND and differential signal shields (which are supposed to signal GND). In a floating GND setting, SR785 connects a 1 MOhm resistor between input shield and Earth GND. This can be used to read a differential signal through a single BNC cable since the shiled can take arbitrary voltages thanks ti the 1 MOhm resistor.

We can do the same in acromag. Instead of shorting RTN to IN- ports, we can connect them through a large resistor which would let IN- float but will give a path for current to return through RTN ports. Attached here are few scenarios where I connected IN- to RTN throguh wire, 820 Ohms, 10kOhms and 1MOhms in two sub cases where RTN was left open or was shorted to Earth GND. In all cases, the signal was produced by a 9V battery outputing roughly 8.16V. It seems that 10kOhm resistor between RTN and IN- with RTN connected to Earth GND is the best scenario noise wise. I'll post more results and a wiring diagram soon.

  15779   Tue Jan 26 15:37:25 2021 AnchalHowToCDSAcromag wiring investigation

Here I present few wiring diagrams when using Acromag to avoid noisy behavior and ground loops.


Case 1: Only single-ended sources

  • Attachment 1 gives a functioning wiring diagram when all sources are single ended.
  • One should always short the RTN to IN- pin if the particular GND carried by that signal has not been shorted before to RTN for some other signal.
  • So care is required to mark different GNDs of different powersupply separately and follow where they inadvertently get shorted, for example when a photodiode output is connected to FSS Box.
  • Acromag should serve as the node of all GNDs concerned and all these grounds must not be connected to Earth GND at power supply ends or in any of the signal sources.
  • I think this is a bit complicated thing to do.

Case 2: Some single and some differential sources

  • Connect all single ended sources same as above keeping care of not building any ground loops.
  • The differential source can be connected to IN+ and IN- pins, but there should be a high resistance path between IN- and RTN. See Attachment 2.
  • Why this is the case, I'm not sure since I could not get access to internal wiring of Acromag (no response from them). But I have empirically found this.
  • This helps IN- to float with respect to RTN according to the negative signal value. I've found that 10kOhm resistance works good. See 40m/15778.
  • If RTN is shorted to nearby Earth GND (assuming none of the other power supply GNDs have been shorted to Earth GND) shows a reduction in noise for differential input. So this is recommended.
  • This wiring diagram carries all complexity of previous case along with the fact that RTN and anything connected to it is at Earth GND now.

Case 3: Signal agnostic wiring

  • Attachment 3 gives a wiring diagram which mimics the high resistance shorting of RTN to IN- in all ports regardless of the kind of signal it is used for reading.
  • In this case, instead of being the node of the star configuration for GND, acromag gets detached from any ground loops.
  • All differences in various GNDs would be kept by the power supplies driving small amounts of current through the 10 kOhm resistors.
  • This is a much simpler wiring diagram as it avoids shorting various signal sources or their GNDs with each other, avoiding some of the ground loops.

Edit Wed Jan 27 13:38:19 2021 :

This solution is not acceptable as well. Even if it is successfull in reading the value, connecting resistor between IN- and RTN will not break the ground loops and the issue of ground loops will persist. Further, IN- connection to RTN breaks the symmetry between IN-  and IN+, and hence reduces the common mode rejection which is the intended purpose of differential signal anyways. I'll work more on this to find a way to read differential signals without connecitng IN- and RTN. My first guess is that it would need the GND on the source end to be connected to EarthGND and RTN on acromag end to be connected to EarthGND as well.

 

  15780   Thu Jan 28 12:53:14 2021 AnchalSummaryBHDHAM-A Coil Driver measurements before modifications

I took some steps to reduce the coupling of 60 Hz harmonics in noise measurement. The box was transferred to the floor instead of on top of another instrument. Measurement was immediately converted into single-ended using SR560 in battery mode with a gain of 10. All of the setups was covered in aluminum foil to increase isolation.

Spectrum measurement details

 

  15781   Thu Jan 28 18:04:55 2021 AnchalSummaryBHDHAM-A Coil Driver measurements After modifications

I did the recommended modifications on of the boards with serial number S2100028. These included:

  • R13, R27: 160 -> 75
  • C11, C21: 470 nF -> 68nF
  • C19: 4.7 uF -> 470 nF
  • R15: 3.23 kOhm -> 1.82 kOhm

I took transfer function measurements with same method as in 40m/15774 and I'm presenting it here to ensure the modifications are correct and if I should proceed to the next board as well. I didn't have the data used to make plots in here but I think the poles and zeros have landed in the right spot. I'll wait for comments until tomorrow to proceed with changes in the other board as well. I'll do noise measurements tomorrow.

  15784   Fri Jan 29 15:39:30 2021 AnchalSummaryBHDHAM-A Coil Driver measurements After modifications TF and Noise S2100027

I fitted zeros and poles in the measured transfer function of D1100687 S2100027 and got zeros at 130 Hz and 234 Hz and poles at 10Hz and 2845 Hz. These values are different from the aimed values in this doc, particularly the 234Hz zero which was aimed at 530 Hz in the doc.

I also took the noise measurement using the same method as described in 40m/15780. The noise in Acquisition mode seems to have gone up in 10 Hz - 500 Hz region compared to the measurement in 40m/15780 before the modifications.

All channels are consistent with each other.


Edit Mon Feb 1 12:24:14 2021:
Added zero model prediction after the changes. The measurements match with the predictions.


Edit Wed Feb 3 16:46:59 2021:

Added zero modeled noise in the noise spectrum curves. The acquisition mode curves are in agreement with the model. The noise in Run mode is weirdly lower than predicted by zero.

  15785   Fri Jan 29 17:57:17 2021 AnchalHowToCDSAcromag wiring investigation

I found a white paper  from Acromag which discusses how to read differential signal using Acromag units. The document categorically says that differential signals are always supposed to be transmitted in three wires. I provides the two options of either using the RTN to connect to the signal ground (as done in Attachment 3) or locally place 10k-100k resistors between return and IN+ and IN- both (Attachment 2).

I have provided possible scenarios for these.

Using two wires to carry differential signal (Attachment 1):

  • I assume this is our preferential way to connect.
  • We can also assume all single-ended inputs as differential and do a signal condition agnostic wiring.
  • Attachment 3 show what were the results for different values of resistors when a 2Hz 0.5V amplitude signal from SR785 which as converted to differential signal using D1900068 was measured by acromag.
  • The connection to RTN is symmetrical for both inputs.

Using three wires to carry differential signal (Attachment 2):

  • This is recommended method by the document in which it asks to carry the GND from signal source and connect it to RTN.
  • If we use this, we'll have to be very cautious on what GND has been shorted through the acromag RTN terminals.
  • This would probably create a lot of opportunities for ground loops to form.

Using an acromag card without making any connection with RTN is basically not allowed as per this document.

  15787   Tue Feb 2 11:57:46 2021 AnchalSummaryBHDHAM-A Coil Driver measurements After modifications TF and Noise S2100028

I have made the modifications on the other board D1100687 S2100028 as well. The measurements were taken as mentioned in 40m/15784. All conclusions remain the same as 40m/15784. The attached zip file contains all measurement data, before and after the modifications.


Edit Wed Feb 3 16:44:51 2021 :

Added zero modeled noise in the noise spectrum curves. The acquisition mode curves are in agreement with the model. The noise in Run mode is weirdly lower than predicted by zero.

  15793   Wed Feb 3 16:27:19 2021 AnchalSummaryBHDSatellite Amplifier Transfer Functions and noise After modifications

I have made modifications recommended in this doc. The changes made are:

  • R24: 19.6k to 4.99k Ohms
  • R20: 19.6k to 4.99k Ohms
  • R23: 787 to 499 Ohms
  • Removed C16.

I took transfer function measurements, fitted them with zeros and poles and plotted it against the zero model of the circuit. The zeros and poles we intended to shift are matching well with 3Hz zero and 30 Hz pole. The later pole at 1500 Hz is at a higher value from what is predicted by zero.

I also took noise measurements and they are in good agreement with the noise predicted by zero.


Edit Wed Feb 10 15:14:13 2021 :

THE NOISE MEASUREMENT WAS WRONG HERE. SEE 40m/15799.

  15797   Wed Feb 10 11:45:59 2021 AnchalSummaryBHDSatellite Amplifier Very Low frequency noise After modifications

As suggested, I wrapped the satellite amplifier box D10028128 S2100029 in blanket and foam and took very low frequency spectrum starting from 32 mHz to 3 Hz. The results are attached along with stiched high frequency measurements from 40m/15793.

Very Low Frequency Spectrum Measurement

  • D1002818 S2100029 box was powered and covered in a foam blanket.
  • Additionally, it was covered from all sides with foam to reduce wind and temperature effects on it.
  • The rear panel DB25 connector was connected to a breakout board where pins od PDA input and GND were shorted, shorting the transimpedance circuit input.
  • The output was read from PDMon DB9 output at front panel which was converted to 4 BNC channels using breakout board.
  • Two channel noise was measured at once using D1002818_SP.yml parameter file.
  • Instrument noise at all the used input ranges were measured separately by shorting the input of the BNC cables.

Edit Wed Feb 10 15:14:13 2021 :

THIS MEASUREMENT WAS WRONG. SEE 40m/15799.

  15799   Wed Feb 10 15:07:50 2021 AnchalSummaryBHDSatellite Amplifier Output Offset measurements

I measured the output DC voltage of the satellite amplifier box at PDMon port when the PDA input was shorted and got following offsets:
 

CH Output Offset (mV) CH Output Offset (mV)
1 6 5 750
2 140 6 120
3 350 7 537
4 40 8 670

However, I think I'm making a mistake while measuring this offset as well as all the noise measurements of this satellite amplifier box so far. Since it is a current input, transimpedance circuit, the noise of the circuit should be measured with open input, not closed. Infact, by shorting the PDA input, I'm giving DC path to input bias current of AD833 transimpedance amplifier to create this huge DC offset. This won't be the case when a photodiode is connected at the input which is a capacitor and hence no DC path is allowed. So my issue of offset was bogus and past two noise measurements in 40m/15797 and 40m/15793 are wrong.

  15803   Thu Feb 11 11:10:05 2021 AnchalSummaryBHDSatellite Amplifier Very Low frequency noise After modifications

Here is a proper measurement for PD transimpedance amplifier circuit in the Satellite amplifier box D1002818 S2100029. The input from rear DB25 connector was left open and measurement was taken with AC coupling with correction by the AC coupling transfer function (Zero at 0, pole at 160 mHz). I have calculated the input referred displacement noise by calculating the conversion factor of OSEM in A/m. From 40m/12470, old conversion factor of OSEM to output of sat amplifier was 1.6 V/mm. then, the transimpedance was 39.2 kOhm, so that must mean a conversion factor of 1.6e3/39.2 A/m. This I scaled with increased drive current by factor of 35/25 as mentioned in this document. The final conversion factor turned out to be around 57 mA / m. If someone finds error in this, please let me know.

There is excess noise in the low-frequency region below 5-6 Hz. If people think I should make a measurement of amplified noise to go further away from the instrument noise floor, let me know.

  15876   Sun Mar 7 19:56:27 2021 AnchalUpdateLSCSensing matrix settings messed with

I understand this mst be frustrating for you. But we did not change these settings, knowingly atleast. We have documented all the things we did there. The only thing I can think of which could possibly change any of those channels are the scripts that we ran that are mentioned and the burt restore that we did on all channels (which wasn't really necessary). We promise to be more vigilant of changes that occur when we are present in future.

Quote:

To my dismay, I found today that somebody had changed the oscillator frequencies for the sensing matrix infrastructure we have. The change happened 2 days and 2 hours ago (I write this at ~1230 on Saturday, 3/6), i.e. ~1030am on Thursday. According to the elog, this is when Anchal and Paco were working on the interferometer, but I can find no mention of these settings being changed. Not cool guys 😒 .

This was relatively easy to track down but I don't know what else may have been messed with. I don't understand how anything that was documented in the elog can lead to this weird doubling of the frequencies.

I have now restored the correct settings. The "sensing matrix" I posted last night is obviously useless.

 

  15896   Wed Mar 10 15:29:58 2021 AnchalSummaryIMCIMC free swinging prep

No we didn't fix the issue. We'll post some screenshots tomorrow. From "sitemap>Shutter>PSL" we meant in Shutter medm window, we clicked on the PSL close button. As pointed later, it switches C1:AUX-PSL_ShutterRqst while the PSL shutter switch on Lock MC medm screen switches C1:PSL-PSL_ShutterRqst. We were not sure if this was intentional, so we didn't change anything.

  15916   Fri Mar 12 18:10:01 2021 AnchalSummaryComputer Scripts / ProgramsInstalled cds-workstation on allegra

allegra had fresh Debian 10 installed on it already. I installed cds-workstation packages (with the help of Erik von Reis). I checked that command line caget, caput etc were working. I'll see if medm and other things are working next time we visit the lab.

  15934   Wed Mar 17 16:30:46 2021 AnchalUpdateSUSNormalized Input Matrices plotted better than SURF students

Here, I present the same input matrices now normalized row by row to have same norm as current matrices rows. These now I plotted better than last time. Other comments same as 15902. Please let us know what you think.


Thu Mar 18 09:11:10 2021 :

Note: The comparison of butterfly dof in the two cases is bit bogus. The reason is that we know what the butterfly vector is in sensing matrix (N_osems x (N_dof +1)) and that is the last column being (1, -1, 1, -1, 0) corresponding to (UL, UR, LR, LL, Side). However, the matrix we multiply with the OSEM data is the inverse of this matrix (which becomes the input matrix) which has dimensions ((N_dof + 1) x N_osem) and has the last row corresponding to the butterfly dof. This row was not stored for old calculation of the input matrix (which is currently in use) and can not be recovered (mathematically not possible) with the existing 5x4 part of that input matrix. We just added (1, -1, 1, -1, 0) row in the bottom of this matrix (as was done in the matlab codes) but that is wrong and hence the butterfly vector looks so bad for the existing input matrix.

Proposal: We should store the last row of generated input matrix somewhere for such calculations. Ideally, another row in the epics channels for the input matrix would be the best place to store them but I guess that would be too destructive to implement. Other options are to store this 5 number information in wiki or just elogs. For this post, the buttefly row for the generated input matrix is present in the attached files (for future references).

  15971   Sun Mar 28 14:16:25 2021 AnchalSummarySUSMC3 new Input Matrix not providing stable loop

Rana asked us to write out here the new MC3 input matrix we have calculated along with the old one. The new matrix is not working out for us as it can't keep the suspension loops stable.


Matrices:

Old (Current) MC3 Input Matrix (C1:SUS-MC3_INMATRIX_ii_jj)
  UL UR LR LL SD
POS 0.288 0.284 0.212 0.216 -0.406
PIT 2.658 0.041 -3.291 -0.674 -0.721
YAW 0.605 -2.714 0.014 3.332 0.666
SIDE 0.166 0.197 0.105 0.074 1

 

New MC3 Input Matrix (C1:SUS-MC3_INMATRIX_ii_jj)
  UL UR LR LL SIDE
POS 0.144 0.182 0.124 0.086 0.586
PIT 2.328 0.059 -3.399 -1.13 -0.786
YAW 0.552 -2.591 0.263 3.406 0.768
SIDE -0.287 -0.304 -0.282 -0.265 0.871

Note that the new matrix has been made so that the norm of each row is the same as the norm of the corresponding row in the old (current) input matrix.


Peak finding results:

  Guess Values Fittted Values
PIT Resonant Freq. (Hz) 0.771 0.771
YAW Resonant Freq. (Hz) 0.841 0.846
POS Resonant Freq. (Hz) 0.969 0.969
SIDE Resonant Freq. (Hz) 0.978 0.978
PIT Resonance Q 600 345
YAW Resonance Q 230 120
POS Resonance Q 200 436
SIDE Resonance Q 460 282
PIT Resonance Amplitude 500 750
YAW Resonance Amplitude 1500 3872
POS Resonance Amplitude 3800 363
SIDE Resonance Amplitude 170 282

Note: The highest peak on SIDE OSEM sensor free swinging data as well as the DOF basis data created using existing input matrix, comes at 0.978 Hz. Ideally, this should be 1 Hz and in MC1 and MC2, we see the resonance on SIDE DOF to show near 0.99 Hz. If you look closely, there is a small peak present near 1 Hz actually, but it is too small to be the SIDE DOF eigenfrequency. And if it is indeed that, then which of the other 4 peaks is not the DOF we are interested in?

On possiblity is that the POS eigenfrequency which is supposed to be around 0.97 Hz is split off in two peaks due to some sideways vibration and hence these peaks get strongly coupled to SIDE OSEM as well.

P.S. I think something is wrong and out limited experience is not enough to pinpoint it. I can show up more data or plots if required to understand this issue. Let us know what you all think.

  15988   Thu Apr 1 21:13:54 2021 AnchalUpdateSUSMatrix results, new measurement set to trigger
New Input matrix used for MC2 (C1:SUS-MC2_INMATRIX_ii_jj
  UL UR LR LL SIDE
POS 0.2464 0.2591 0.2676 0.2548 -0.1312
PIT 1.7342 0.7594 -2.494 -1.5192 -0.0905
YAW 1.2672 -2.0309 -0.9625 2.3356 -0.2926
SIDE 0.1243 -0.1512 -0.1691 0.1064 0.9962

New output matrix for MC2 (C1:SUS-MC2_TO_COIL_ii_jj_GAIN)
  POS PIT YAW
UL 1 1.022 0.6554
UR 1 0.9776 -1.2532
LL 1 -0.9775 1.2532
LR 1 -1.0219 -0.6554

Measured Sensing Matrix (Cross Coupling) (Sensed DOF x Excited DOF)
  Excited POS Excited PIT Excited YAW
Sensed POS 1 1.9750e-5 -3.5615e-6
Sensed PIT 0 1 -6.93550e-2
Sensed YAW 0 -2.4429e-4 1

A longer measurement is set to trigger at 5:00 tomorrow on April 2nd, 2021. This measurement will run for 35 iterations with an excitation duration of 120s and bandwidth for CSD measurement set to 0.1 Hz. The script is set to trigger in a tmux session named 'cB' on pianosa.

ELOG V3.1.3-