This disturbance in the MC ASC channels were fixed.
This craziness happened ~10pm last night. Was there any action at the time? >> Sunday-night workers? (RXA: No, Nakano-kun and I left before 9:30 PM)
We found that the signals came from c1ioo. However, restarting, recompiling c1ioo and c1mcs didn't help
to clean up this issue. Just in case we cleaned up the corresponding entries in the ipc file /opt/rtcds/caltech/c1/chans/ipc/C1.ipc
and recomplied c1ioo and c1mcs because these are the channels we touched last week to mitigate the timing out issue of c1rfm.
Incidentally, we fell into a strange mode of the RCG: IOPs could not restart. We ended up running "sudo shutdown -r now"
on each machine (except for c1lsc which was not affected by this issue). This solved the issue.
Even now c1oaf could not be running properly. This is not affecting the IFO operation right now, but we need to look into this issue again
in order to utilize OAF.
When I came in this morning, I noticed that the Mode Cleaner had not been locked for at least the past 8 hours. We moved the MC SUS sliders until the MC SUSPIT and SUSYAW values for each mirror were back to approximately the place they were the last time the MC was nicely locked (~12 hours ago). This got the MC flashing TEM00, so we thought we were doing well.
However, if the servo was enabled, any time the cavity flashed a small-order mode (especially 00), the mirrors would get super kicked. Not good.
We went to investigate, and discovered that the RFPD aux laser was left on again. We turned that off, however that didn't fix the situation.
Manasa suggested checking that the WFS were really, really off. When we looked at the WFS master screen, we noticed that although the WFS servos were off, the MC mirrors' ASC filter banks had non-zero inputs. We checked, and this is not from the MCASS, nor is it from the MC WFS lockins. At this point, I have no idea where these signals are coming from. I have turned off the ASC outputs for all the MC mirrors (which means that we cannot turn on the WFS), and the MC locks fine.
So, we need to know where the ASC signals are coming from. There isn't anything that I can see, from any screen that I can find, that indicates some signals being sent over there. Has anyone done anything lately? I know Koji was working on IPC stuff the other day, but the MC was locking fine over the weekend until yesterday afternoon, so I suspect that's not the culprit.
I have turned off the outputs of the WFS lockins, as part of my turning things off, so if whatever script needs them doesn't enable them, they should be turned back on by hand.
We can not leave cables connected like this. This is a burned toast award.
Masayuki Nakano, a student of Seiji's from ICRR / U Tokyo, is visiting us here at the 40m lab for the next couple months.
He received 40m specific basic safety training this morning.
This is an elog about the activity on Friday night.
- The X arm green beam was aligned with assist of the ASX system.
- M1 PZT alignment was swept while M2 PZT was under the control of ASX.
- Everytime M1 was touched, M2 was restored by manual alignment so that the REFL beam hits the center of the REFL PD.
This way we could recover the lock of TEM00. Once TEM00 is recovered, ASX took care of the alignment of M2
- The error signal used by the cavity dither did not give us a good indication where the optimal alignment is.
- Thus the best alignment of M1 had to be manually scanned. The resulting maximum green transmission was ~0.88
- Once the beam was aligned, the out-of-loop stability of the Xarm was measured.
There has been no indication of the improvement compared to Manasa's measurement taken before our beam alignment.
ETMX sus damping restored
JoeB and JamieR are working somewhat coherently on a set of python libraries to fulfill all of our command line CDS wants. This is being done mostly to satisfy The Guardian and the SkunkTools project.
I did an 'svn up' in /opt/rtcds/userapps (it might finish in ~1000 years) to get the things that they have so far (in particular, Joe's 'pyavg'). There's going to be some issues since the pylib stuff written by Yuta/Kiwamu has never been integrated with anything and is imported as 'epics' in many python scripts. As we move over to the new stuff there will be a lot of broken script functions since the new libraries are also used in that way.
I noticed at LLO (?) that the LSC screen there uses up ~25-30% of the CPU time on a single core for the control room iMac workstations - this seems excessive.
Here is an accounting of CPU usage percentages for some of our screens:
These were measured using the program 'glances' on rosalba. MEDM running with only the sitemap used up 0.9% of a CPU. With the screens running, the fluctuation from sample to sample could be ~ +/- 0.5%. While the LSC screen seems to be the biggest pig, it is only big in comparison to small pigs. Certainly this pig has gotten bigger after getting sent to Louisiana.
Sun Aug 18 15:52:50 2013
Found the FB lights (C1:FEC-NN_FB_NET_STATUS and C1:DAQ-DC0_C1XXX_STATUS) RED for everything on the CDS_FE_STATUS screen.
I used the (! mxstream restart) button ro restart the mxstreams. Everything is green now.
PMC was out of lock- relocked it and the IMC locked itself as did the X & Y arms on IR. X was already green locked.
I took the "aso-laptop" and made it into Ubuntu a couple months ago. Today I added it to the Martian network and then moved it to the X End.
I followed the instructions in (https://wiki-40m.ligo.caltech.edu/Network) and added it to the files in /var/named/chroot/var/named on linux1 and did the "service named restart".
The router already had his MAC address in its list (because Yoichi was illegally using his personal laptop on the Martian). The new laptop's name is 'asia'. This is a legal name according to our computer naming conventions and this Wikipedia page (http://en.wiktionary.org/wiki/Category:Italian_female_given_names). It has been added to the Name Pool on the wiki.
The terminal on the laptop still calls itself 'aso-laptop' so I need some help in fixing that. It successfully connects to 40MARS and displays a MEDM sitemap after sshing in to pianosa.
I use 'ssh -X -C' since I find that compression actually helps when the laptops are so far from the router.
Rana and I connected the PMC_trans output to the BNC connector board on the west end of the PSL table (the channel is labeled). I took a few spectra off of PMC_trans and the SR785 was connected directly to the PMC_trans output for about an hour.
Data will follow.
Yesterday we cleaned up the ASX model and screens to have more straight forward structure of the screen
and the channel names, and to correct mistakes in the model/screens.
The true motivation is that I suspect the excess LF noise of the X arm ALS can be caused by misalignment
and beam jitter coupling to the intensity noise of the beat. I wanted to see how the noise is affected by the alignment.
Currently X-end green is highly misaligned in pitch.
- Any string "XEND" was replaced by "XARM", as many components in the system is not localized at the end table.
- The name like "XARM-ITMX" was changed to "XARM-ITM". This makes easier to create the corresponding model for the other arm.
- There was some inconsistency between the MEDM screens and the ASX model. This was fixed.
- A template StripTool screen was created. It is currently saved in users/koji/template as ASX.stp.
It will be moved to the script directory once it's usefulness is confirmed.
The next step is to go to the end table and manually adjust M2 mirror while M1 is controlled by the ASX.
The test mass dithering provides the error signal for this adjustment but the range of the PZT is not enough
to make the input spot position to be controlled. In the end, we need different kind of matching optics
in order to control the spot position. (But is that what we want? That makes any PZT drift significantly moves the beam.)
Apparently all of the ION pump valves (VIPEE, VIPEV, VIPSV, VIPSE) opened, which vented the main volume up to 62 mTorr. All of the annulus valves (VAVSE, VAVSV, VAVBS, VAVEV, VAVEE) also appeared to be open. One of the roughing pumps was also turned on. Other stuff we didn't notice? Bad.
Several of the suspensions were kicked pretty hard (600+ mV on some sensors) as a result of this quick vent wind. All of the suspensions are damped now, so it doesn't look like we suffered any damage to suspensions.
CLOSE CALL on the vacuum system:
Jamie and I disabled V1, VM2 and VM3 gate valves by disconnecting their 120V solenoid actuator before the swap of the VME crate.
The vacuum controller unexpectedly lost control over the swap as Jamie described it. We were lucky not to do any damage! The ion pumps were cold and clean. We have not used them for years so their outgassing possibly accumulated to reach ~10-50 Torr
I disconnected_ immobilized and labelled the following 6 valves: the 4 large ion pump gate valves and VC1, VC2 of the cryo pump. Note: the valves on the cryo pump stayed closed. It is crucial that a warm cry pump is kept closed!
This will not allow the same thing to happen again and protect the IFO from warm cryo contamination.
The down side of this that the computer can not identify vacuum states any longer.
This vacuum system badly needs an upgrade. I will make a list.
While I was doing the oil change of the roughing pumps I accidentally touched the 24 V adjustment knob on the power supply.
All valve closed to default condition. I realized that the current indicator was red at 0.2A and the voltage fluctuated from 3-13V
Increased current limiter to 0.4A and set voltage to 24V I think this was the reason for the caos of valve switching during the VME swap.
Based on the facts above I reconnected VC1 and VC2 valves. State recognition is working. Ion pumps are turned off and their gate valves are disabled.
We learned that even with closed off gate valves while at atmosphere ion pumps outgass hydrocarbons at 1e-6 Torr level. We have not used them for this reason in the passed 9 rears.
I need help with implementing V1 interlock triggered by Maglev failure signal and-or P2 pressure.
MEDM screen agrees with vacuum rack signs.
After many, many moons of getting to know exactly how frustrating Altium can be, I have completed the PCB layout for my ISS board (final page of ISS_v3.pdf).
Before I get into detail about the PCB, there is one significant schematic change to note: the comparator circuit was changed (with significant help from Koji) so that the voltage reference for boost triggering is established in a more logical way. Instead of the somewhat convoluted topology I had before, now there are only two feedback resistors, R82 and R83. Because their resistances (500k and 50k respectively) are so much larger than the total resistance of the 1k potentiometer (used to establish a tunable threshold voltage), the current flowing through the feedback loop is negligible compared to the 5 mA current flowing through the potentiometer (the pot is rated for 2 W and with 5 mA -> 25 mW dissapation). This allows one to set the threshold voltage for my schmitt trigger, at pin 2 of both the pot and the comparator, entirely with the pot. This trigger also has hysteresis given by the relation deltaV ~ (R83/R82) * (Voh - Vol) where deltaV is the separation between threshold voltages, Voh is the high-level comparator ouput and Vol is the low-level comparator output. Koji simulated this using CircuitLab and I plan to verify the behavior by making a quick prototype circuit.
Now, on to the PCB. The board itself is of a 'standard' LIGO size (11" x 6") has 3 routing layers and 3 internal planes, one for +15 V, one for -15 V and one for GND. In the attached pdf, red is the top routing layer, blue is the bottom layer and brown is the middle routing layer (used for ±5 V exclusively). The grey circles are pads and vias (drilled through) and anything in black is silkscreen overlay. I placed each component and track by hand, attempting to minimize the signal path and following the general rules below,
Sections of the board have been partitioned and labeled with silkscreen overlay to help in both signal pathway recognition as well as eventual troubleshooting.
On the board, I have also included holes so that it can be mounted inside of an enclosure. There is a DCC number printed as well as a 'barcode' (TrueType font: IDAutomationC39S), although they both contain filler asterisks as I haven't published this to the DCC and thus do not have a number.
Beat notes were recovered for both the arms.
I locked the arms to IR using PDH and measured the ALS out of loop noise at the phase tracker output.
The Y arm has the same 300Hz/rtHz rms. The X arm rms noise measures nearly the same as the Y arm in the 5-500Hz region (X arm has improved nearly 10 times after the last whitening filter stage change old elog ).
The noise in the ALSX error signals could be related to the bad alignment and conditions at the X end.
[Koji, Nic, Manasa]
Update from last night.
Koji and I realigned the green optics on the PSL to start working on the ALS.
We set on a beat note search. We couldn't find the beat note between any of the arm green transmission and the PSL green. All we could see was the beat between the X arm and the Y arm green leakage.
Since we had the beatnote between the 2 green transmission beams, we decided to scan the PSl temperature. We scanned the SLOW actuator adjust of PSL; but couldn't locate any beat note. The search will continue again today.
Eric and Steve,
We removed Wilcoxon Accelerometer PS and Amplifier unit under the BS optical tabel yesterday. The six cabels going to DAQ were labeled and left in place. Gain setting were 100, except channel 3 was 10.
The ~ 40 m long 2 sets of 3 cables were very happy to get their kinks out. Especially the set going just south of ITMX optical table.
We have to take better care of these cables! Your data will be useless this way.
Since the RFM-Dolphin bridges for the ASX model was added to the c1rfm model, c1rfm kept timing-out from the single sample time of 60us.
The model had 19 dolphin accesses, 21 RFM accesses, and 9 shared memory (SHM) accesses.
At the beginning 2 RFM and 2 SHM accesses were moved to c1sus (i.e. they were mistakenly placed on c1rfm).
But this actually made the c1sus model timed out. So the model was reverted.
The current configuration is that the WFS related bridges were accommdated in the c1mcs model.
This made the timing of c1rfm ~40us. So it is safe now.
On the other hand, the c1mcs model has the time consumption of ~59us. This is marginal now.
We need to understand why any RFM access takes such huge delay.
As a part of the network analyzer test in the previous entry, the transfer functions of Mini-Circuits filters we have at the 40m were measured.
<<List of the filters>>
- LPF (SMA): SLP1.9, SLP5, SLP21.4, SLP30, SLP50, SLP100, SLP150, SLP750
- LPF (BNC): BLP1.9, BLP2_5, BLP5, BLP30
- BPF (SMA): SBP10.7, SBP21.4, SBP70
- HPF (SMA): SHP25, SHP100, SHP150, SHP200, SHP500
New AG4395, sn MY41101114 for West Bridge Labs was delivered. For the test purpose it is at the 40m now.
I made a series of tests in order to find anything broken.
Network analyzer test
- RF out / Rch test
RF out directly connected to R input channel.
The received power at the R-ch was measured while the output was swept from 10Hz to 500MHz.
The RF power was changed from -50dBm to +15dBm with +10dBm increment (but the last one).
The attenuator setting was changed from 50dB to 0dB.
=> The configured output power was properly detected by the R channel.
=> RF output is producing the signal properly. R-ch is detecting the produced signal properly.
- Ach/Bch test
Same test as above for Ach and Bch
=> Same result as above
=> A-ch and B-ch are detecting the produced signal properly.
- Transfer function test
Connect a power splitter to the RF out. Detect the split signals by R-ch and A-ch
=> Measurement is at around 0dB +/- 1dB up to 500MHz.
Same measurement for B-ch
=> Same result
=> A/R and B/R indicates proper transfer function measurements.
RF out was split in to two. One was connected to R-ch. The other was connected to A-ch.
The thru response calibration was run.
=> The thru calibration was performed properly.
- Practical tranfer function measurements.
In the above calibration setup, various RF filters were inserted in the Ach path.
The measured data was extracted via GPIB connection.
=> Practical transfer function measurements were performed.
=> GPIB connectivity was confirmed
External reference test
- External 10MHz reference from an SRS frequency counter was connected to Ext Ref In
=> Ext Ref indicator on the screen appeard
=> The internal oscillator seemed to be locked to the external reference in
Spectrum analyzer test
- Measured the signals from DS345 by R/A/B ch
Sinusoidal signal (1V) swept from 10MHz to 30Mhz
=> Corresponding moving peak was detected in each case
- Noise level measurement
R/A/B channels were terminated. The attenuation at each port was set to 0dB.
Frequency span was changed between 500MHz, 10MHz, 100kHz, 1kHz.
=> Noise level of ~10nV/rtHz between 0.1-500MHz was confirmed. All R/A/B channels have the same performance.
I aligned both the X and Y end green to the arms.
c1x01 timing issue was solved. Now all of the models on c1iscex are nicely running.
- c1x01 was synchronized to 1PPS in stead of TDS
- C1:DAQ-DC0_C1X01_STATUS (Upper right indicator) was red. The bits were 0x4000 or 0x2bad.
C1:DAQ-DC0_C1X01_CRC_SUM kept increasing
- c1scx, c1spx, c1asx could not get started.
- login to c1iscex "ssh c1iscex"
- Run "sudo shutdown -h now"
sudo shutdown -h now
- Walk down to the x end rack
- Make sure the supply voltages for the electronics are correct (See Steve's entry)
- Make sure the machine is already shutdown.
- Unplug two AC power supply of the machine.
- Turn off the front panel switch of the IO chassis
- Wait for 10sec
- Turn on the IO chassis
- Plug the AC power supply cables to the machine
- Push the power switch of the realtime machine
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.
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.
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.
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.
Our fluorecent lights became obsolete. We'll have change fixtures over to some more energy efficient one. Do you have any recommendation regarding to less noise performer unit?
We may go this direction of LED fluorecent lamps ?
Sorrensen ps ouput of +15V at rack 1X9 was current limited to 10.3V @ 2A
Increased threshold to 2.1A and the voltage is up to 14.7V
I guess I was thinking that POPDC was a proxy for any type of PRCL lock. Even if we're sideband locked, there is still some signal in POPDC (although it is very small relative to a carrier lock - ~40cts vs. 1,000cts). However, as soon as this question was asked of me, I realized that one of the 2f demodulated signals made more sense.
Since I want the ability to choose between POP110 and POP22, I have put a little 1x3 input matrix before the PRCL lockins in the ASS model. Since POPDC was already there, I included it as an option in the matrix (in case we ever want to do some PRCL ASS after we have some carrier resonating as well).
I started to modify the c1asx model to reduce the RFM model from hitting its max time.
Instead of bringing in ASS, I have modified ASX to do everything and only the clock signals to ITMX pitch and yaw are now going through RFM. RFM is still hitting 62usec and I suppose that is because of the problems with c1iscex.
c1iscex not happy
Cause and symptoms
While restarting the models, c1iscex crashed a couple of times because of some errors and had to be powercycled. The models were modified and they seem to start ok.
But it looks like there is something wrong with c1iscex since the models were started. The GPS time is off and C1:DAQ-DC0_C1X01_CRC_SUM keeps building up even for c1x01 which was left untouched.
1. Since c1x01 ans c1spx were not touched,c1scx and c1asx were killed and we tried to start the other models. This did not help.
2. Koji did a manual daqd restart which did not help either.
We are leaving c1iscex as is for the time being and calling Jamie for help.
P.S. While making the models, I had created IPCx_PCIE blocks in c1iscex which do not exist. I changed them to RFM and SHMEM blocks. This did not allow me to compile the model and was only spitting errors of IPCx mismatch. After some struggle and elog search I figured out from an old elog that eventhough the IPCx blocks are changed in the model, the old junk exists in the ipc file in chans directory. I deleted all junk channels related to the ASX model. The model compiled right away.
I have added the PRCL ASS to the main ASS screen, and created the servo and lockin screens. The filters loaded are the same as those used for the arms (bandpasses and lowpasses for the lockins, and an integrator for the servo).
I'm going to try to lock, and get the ASS to work.
- We are ready to implement ASS for PRM
I have added an IPC sender from the LSC model, to send POPDC to ASS. I have copied over the structure of the arms' ASS, to do the same for PRCL. I have set it up to dither the PRM, and feed back to the PRM. I did not include an LSC set, since I'm assuming that we'll set the input pointing with the arms, and just want to move the PRM to maximize POPDC.
Models have been compiled, installed, and restarted, and the daqd was restarted.
I'm not really sure why the ASS was involved in this. I feel like it might have been simpler to just do everything in the ASX model, to keep things cleaner. Also, the IPC blocks for this stuff (in both ASS and ASX) are not on the top level of the model. I had thought that this was expressly forbidden (although I'm not sure why). I'm emailing Jamie, to see if he remembers what, if anything, is breakable if the IPC blocks are down a level.
I'm not sure if it's forbidden by the RCG, but you should definitely NOT do it. All IO, whether it be between ADC/DACs or IPCs, should always be at the model top level. That's what keeps things portable, and makes it easier to keep track of where are signals are going/coming from.
Getting rid of the LO transmission will certainly help / be good. After adding these channels, the RFM model is regularly hitting 62usec (out of a max acceptable of 60).
In the past, we used to use Stefan's 'ezcademod' or Matt's 'ezlockin' to do auto phase adjustment.
JoeB / Jamie are working on python replacements for these tools, but in the near term possibly I can make a bash script to use ezcaservo and the existing LOCKINs to do this.
Over the last three days, I've had the interferometer to test and optimize the ASX Servo. Based on what I have seen, I think the conclusion is that with the current parameters, the servo does its job provided the input pointing set up at the endtable with the coarse adjustment knobs is reasonably good. Once the cavity is aligned and IR transmission maximized using ASS, I have been able to get the green transmission up to 0.8 which is close to the best we had pre-vent. I have not been elogging regularly over the last few days, so this one is going to be a longish one.
Major changes made:
Details of tests runs:
For the most part, I have been trying to optimize the PZT mirror dither servo. To this end, I did the following:
Attempt to measure transfer function:
One of the things that came up during my presentation was how fast the loop was capable of responding. I was able to get a quantitative idea of this by playing around with the overall servo gain. Initially, it took ~30 seconds for the servo to get the transmission up to its peak value, with a servo gain of 1. When I ramped this up to 5, the response was much faster, with the peak transmission being reached in ~5seconds.
I wanted to get a more quantitative picture, and hence tried to measure the transfer function by first injecting an excitation into the 'SIG' filter-bank in the demodulation stage. However, coherence between the IN1 and IN2 signals was very poor for all the amplitude configurations I tried. At Jenne's suggestion, I tried injecting the excitation at the control-filters stage, but found no improvement. Perhaps the amplitude envelope was wrong or the measurement technique has to be rethought.
New MEDM screen:
PRMI(sb) lock was recovered
- Stared at the time series data of the REFL demod signals, and decided to use REFL165I&Q for the locking.
- Jiggled the demodulation phase of REFL165 and POP110. Changed the servo gains.
- Finally found a short lock. Further optimized the parameters.
- PRM ASC was turned on by giving the identity matrices for the input and output matrices.
Now just hitting the up button is sufficient to engage the ASC servo.
- Under the presence of the ASC, the PRMI is indefinitely locked as before.
- Reacquisition is also instantaneous. (It acquires even if the ASC is left "on".)
- Actually the lock is somewhat robust even when the PRM ASC is not used.
This is VERY GOOD as we can skip one of the steps necessary for the full lock.
Although, the seismic on Friday night is very quiet.
The spot motion at POP seems to be somewhat pitch/yaw mixed, in stead of previous "totally-dominated-by-yaw" situation.
Demod phase adjustment
- Shook PRM at 580Hz / 100cnt
- Swept the demod phase of REFL165 such that the PRM peak is minimized in the Q signal
- Open DTT. Measured transfer functions between REFL165I and the Q signals of each PD.
- Minimized the PRCL signal coupling in the signals.
- The resolution of the adjustment was ~1deg.
Locking test with PRM/BS
Tried the lock acquisition only with PRM and BS. (cf. http://nodus.ligo.caltech.edu:8080/40m/8816)
This just worked nicely.
Today's locking parameters:
MC Trans: 17500
POP110I (in lock): 150
PRCL Source: REFL165(I) 106deg / 45dB / Normalization SQRT(10 POP110I) / Input MTRX 1.0
PRCL Trigger: POP110I x 1.0 50up 25down
PRCL Servo: G=+3.5 Acq: FM4/FM5 Opr: FM2/FM3/FM6/FM7
PRCL Actuator: PRM +1.0
MICH Source: REFL165(Q) 106deg / 45dB / Normalization SQRT(0.1 POP110I) / Input MTRX 1.0
MICH Trigger: POP110I x 1.0 50up 25down
MICH Servo: G=-10 Acq: FM4/FM5 Opr: FM2/FM3/FM6
MICH Actuator: (ITMX -1.0 / ITMY +1.0) or (BS 0.5 / PRM -0.267)
Now the SRM Yaw bias in yaw is functional without any strage behavior.
The problem was found at the connector of the flat ribbon cable from the DAC to the cross connect.
I used the extender board to diagnose the SRM coil driver circuit at 1X4.
The UL coil input did not show any sign of voltage no matter how the bias slider was jiggled.
I opened the side panel of the rack and found the signal was absent at the cross connect which relays two flat ribbon cables
for the SRM coil driver. I checked the DAC output with a multimeter. All the bias outputs were OK at the DAC.
Then I opened the IDC connector at the DAC side of the crossconnect as the signal was already missing there.
I found that the flat ribbon cable was a half line shifted from the supposed location.
This resulted a short circuit of the DAQ +/- pins for the SRM UL coil.
I recrimped the connector and now the SRM Yaw slider is back.
This changed the nominal position of the SRM. The new slider values were saved.
Notes to the fiber team:
I am aligning beam onto the RFPDs (I have finished all 4 REFL diodes, and AS55), in preparation for locking.
In doing so, I have noticed that the fiber lasers for the RFPD testing are always illuminating the photodiodes! This seems bad! Ack!
For now, I blocked the laser light coming from the fiber, did my alignment, then removed my blocks. The exception is REFL55, which I have left an aluminum beam dump, so that we can use REFL55 for PRM-ITMY locking, so I can align the POP diodes.
EDIT: I have also aligned POP QPD, and POP110/22. The fiber launcher for POP110 was not tight in its mount, so when I went to put a beam block in front of it and touched the mount, the whole thing spun a little bit. Now the fiber to POP110 is totally misaligned, and should be realigned.
What was done for the alignment:
1. Aligned the arms (ran ASS).
2. Aligned the beam to all the REFL and AS PDs.
3. Misaligned the ETMs and ITMX.
4. Locked PRM+ITMY using REFL11.
The following were modified to enable locking
(1) PRCL gain changed from +2.0 to -12.
(2) Power normalization matrix for PRCL changed from +10.0 to 0.
(3) FM3 in PRCL servo filter module was turned OFF.
5. POP PDs were aligned.
- IPANG aligned on the QPD. The beam seems to be partially clipped in the chamber.
- Oplev of the IFO mirrors are aligned.
- After the oplev alignment, ITMX Yaw oplev servo started to oscillate. Reduced the gain from -50 to -20.
I used MC_L signal from the Mode Cleaner as the desired signal with GUR2_X as witness signals. I observed good subtraction where coherence is high. But there was noise added in other frequency bands. I am not sure how to avoid that.
Please find attached documents that contains relevant plots.
An exercise of optimally subtracting one seismometer signal by another using weiner filters was done. Results have been summarized document attached.
I was receiving missing path error when I was trying to measure the MC spot positions. Jenne pointed out that Koji had moved all the unused scripts in scripts/ASS to /scripts/ASS/OBSOLETE yesterday and in the process one of the scripts that the MC spot position measurement script calls for (MeasureSpotPositions.py) must have also been moved to the OBSOLETE directory. I moved the script to /scripts/ASS/MC so that we know the script is being used and also changed its path in the main script.
1, Vacuum envelope grounds must be connected all times! After door removal reconnect both cables immediately.
2, The crane folding had a new issue of getting cut as picture shows.
3, Too much oplev light is scattered. This picture was taken just before we put on the heavy door.
4, We were unprepared to hold the smaller side chamber door 29" od of the IOC
5, Silicon bronze 1/2-13 nuts for chamber doors will be replaced. They are not smooth turning.
TP2's fore line - dry pump replaced at performance level 600 mTorr after 10,377 hrs of continuous operation.
I have done some preliminary testing of the X-End Green ASS Servo. I will write a more detailed elog about this soon, but I thought I'd note down the important stuff here.
Yesterday, while we were venting, I aligned the X-arm to the green using the sliders on IFOalign, maximizing the transmission. Then I retook a power spectrum so as to determine the LO frequencies. Jenne pointed out that LO frequencies should not be integers (it usually suffices to append a .098725 or something to the frequency) so I made the necessary changes.
I did a first run of the servo yesterday, and more runs today. Notable points:
More details to follow.