40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 110 of 339  Not logged in ELOG logo
ID Date Authorup Type Category Subject
  11795   Sat Nov 21 00:46:33 2015 KojiUpdateIOOIMC OLTF

Here is the comparison before and after the fix.

Before the work, the UGF was ~40kHz. The phase margin was ~5deg. This caused huge bump of the frequency noise.

After the LO power increase, I had to reduce the MC loop gain (VCO Gain) from 18dB to 6dB. This resulted 4dB (x2.5) increase of the OLTF. This means that my fix increased the optical gain by 16dB (x6.3). The resulting UGF and phase mergin were measured to be 117kHz and 31deg, respectively.

 

Now I was curious to see if the PMC err shows reasonable improvement when the IMC is locked. Attachment 2 shows the latest comparison of the PMC err with and without the IMC locked. The PMC error has been taken up to 500kHz. The errors were divided by 17.5kHz LPF and 150kHz LPF to compensate the sensing response. The PMC cavity pole was ignored in this calculation. T990025 saids the PMC finesse is 4400 and the cavity pole is 174kHz. If this is true, this also needs to be applied.

Observations:

1. Now we can see improvement of the PMC error in the region between 10kHz to 70kHz.

2. The sharp peak at 8kHz is due to the marginally stable PMC servo. We should implement another notch there. T990025 suggests that the body resonance of the PMC spacer is somewhere around there. We might be able to damp it by placing a lossy material on it.

3. Similarly, the features at 12kHz and 28kHz is coming from the PMC. They are seen in the OLTF of the PMC loop.

4. The large peak at 36kHz does not change with the IMC state. This does mean that it is coming from the laser itself, or anything high-Q of the PMC. This signal is seen in the IMC error too.

5. 72kHz, 108kHz, 144kHz: Harmonics of 36kHz?

6. Broad feature from 40kHz to 200kHz. The IMC loop is adding the noise. This is the frequency range of the PC drive. Is something in the PC drive noisy???
 

7. The feature at 130kHz. Unknown. Seems not related to IMC. The laser noise or the PMC noise.


Remaining IMC issues:

Done (Nov 23, 2015) - 29.5MHz oscillator output degraded. Possibly unstable and noisy. Do we have any replacement? Can we take a Marconi back from one of the labs?

Done (Nov 23, 2015) - Too high LO?

- Large 36kHz peak in the IMC

- IMC loop shape optimization

- IMC locking issue. The lock streatch is not long.

- IMC PC drive issue. Could be related to the above issue.

Maybe not relevant - PC drive noise?

Attachment 1: IMC_OLTF.pdf
IMC_OLTF.pdf
Attachment 2: PMC_noise_comparison.pdf
PMC_noise_comparison.pdf
  11797   Sun Nov 22 12:07:09 2015 KojiUpdateIOOIMC fix

TO DO

Done (Nov 23, 2015) - Check if the attenuator is still there in the input chain

Done (Nov 23, 2015) - Check if the actual LO levels at the 17dBm mixers are reasonable.

- Check if the actual LO levels for the LSC demods are OK too

  11798   Sun Nov 22 12:12:17 2015 KojiUpdateIOOIMC OLTF

Well. I thought a bit more and now I think it is likely that this is just the servo bump as you can see in the closed-loop TF.

Quote:

6. Broad feature from 40kHz to 200kHz. The IMC loop is adding the noise. This is the frequency range of the PC drive. Is something in the PC drive noisy???

  11800   Mon Nov 23 20:32:43 2015 KojiUpdateLSCFrequency source fixed, IMC LO level adjusted

The frequency source was fixed. The IMC LO level was adjusted.

IMC is locked => OLTF measured UGF 144kHz PM 30deg.

  11801   Mon Nov 23 21:48:49 2015 KojiUpdateLSCFrequency source fixed, IMC LO level adjusted

The trouble we had: the 29.5 MHz source had an output of 6 dBm instead of 13 dBm.

The cause of the issue: A short cable inside had its shield cut and had no connection of the return.


- The frequency source box was dismantled.
- The power supply voltages of +28 and +18 were provided from bench supplies.
- The 29.5 MHz output of 5~6 dBm was confirmed on the work bench.
- The 11 MHz OCXO out (unused) had an output of 13 dBm.

- Once the lid was opened, it was immediately found that the output cable for the 29.5 MHz source had a sharp cut of the shield (Attachment1).
- OK. This cable was replaced. The output of 13 dBm was recovered.

- But wait. Why is the decoupling capacitor on the 29.5 MHz OCXO bulging? The polarity of the electrolytic capacitor was wrong!
- OK. This capacitor was replaced. It was 100 uF 35 V but now it is 100 uF 50 V.

- I further found some cables which had flaky shields. Some of them were twisted. When the panel cable s connected, the feedthroughs were rotated. This twists internally connected cables. Solder balls were added to the connector to reinforce the cable end.

- When the box was dismantled, it was already noticed that some of the plastic screws to mount the internal copper heat sinks for ZHL-2's were broken.
They seemed to be degraded because of the silicone grease. I didn't try to replace all as it was expected to take too much time, so only the broken screws
were replaced with steel screws with shoulder washers
at the both side of the box.

- After confirming the circuit diagram, the box was returned to the rack. The 29.5 MHz output of 13 dBm there was confirmed.

Attachment 1: IMG_2136.JPG
IMG_2136.JPG
Attachment 2: IMG_2129.JPG
IMG_2129.JPG
Attachment 3: IMG_2133.JPG
IMG_2133.JPG
  11802   Mon Nov 23 22:12:10 2015 KojiUpdateIOOLO level check for the IMC demod board

In order to check the proper LO level, the IMC demod board was checked. As a short summary, -8dBm is the proper input for the IMC demod board. This was realized when the variable attenuator of the RF AM Stabilizer was set up be -7dB.


Initially, I tried to do the measurement using the extender board. But every board had the issue of +15V not working. After several extender boards were tried, I noticed that the current draw of the demod board burned the 15V line of the extender board.

Then I moved to the work bench. The signals were checked with the 10:1 probe. It's not properly the 50Ohm system, exactly to say.

I found that the LO signals at the mixers have huge distortion as it reaches the nominal 17dBm, and I wondered if ERA-5s were gone. Just in case I replaced the ERA-5s but didn't see any significant change. Then I thought it is due to the mixer itself. The mixer was removed and replaced with a 50Ohm SMD resister. Then the output of the last ERA-5 became sinusoidal, and the level was adjusted to be ~17dBm (4.52 Vpp) when the input power was measured to be -7.7dBm with the RF power meter. Once the mixer was reinstalled, it was confirmed that the waveform becase rectangular like, with the similar amplitude (4.42Vpp).

Now the module was returned to the rack. The RF level at the LO input was adjusted to be -8dBm by setting the attenuator level to be 7dBm.

Once the IMC is locked with this setting, the open loop transfer function was measured. The optical gain seemed almost unchanged compared with the recent nominal. The UGF and PM were measured to be 144kHz and 30deg.

Attachment 1: IMG_2137.JPG
IMG_2137.JPG
Attachment 2: IMG_2138.JPG
IMG_2138.JPG
  11804   Tue Nov 24 01:14:23 2015 KojiUpdateLSCALSY recovered

Sorry, I completely forgot to turn the Marconi on...

  11808   Wed Nov 25 10:07:10 2015 KojiUpdateIOOLO level check for the IMC demod board

I didn't finish making the DCC entry for this module yet.

But the attenuators are
- AT1: 10dB. There is a sign that it was 3dB before ---  a 3dB chip was also attached on the boardnext to 10dB.
- AT2/3: Removed. They were replaced with 0Ohm resistors.

Currently the input is -8dBm. The input and output of the first ERA-5 are -17dBm and +7dBm, respectively.
Then the input and output of the second ERA-5 are -2dBm and 17dB, respectively.

In order to remove the second amplification stage, the first stage has to produce 26dBm. This is too much for either ERA-5 or any chips that fits on the foot print. If we use low gain but high output amp like GVA-81 (G=10dB, DF782 package), it is doable

Input 0dBm - [ATTN 3] - -3dBm - [ERA-5 G=20dB] - +16~+17dBm - [Circuits -9dB] - +7dBm - [Attn 0dB] - +7dBm - [GVA-81 G=10dB] - +17dBm

I think we should check the conditions of all the LSC demods.

  11811   Wed Nov 25 16:46:10 2015 KojiUpdateIOOLO level check for the IMC demod board

Awwww. I found that the demod board has the power splitter (PSCJ-2-1) with one output unterminated.
This power splitter should be removed.

https://dcc.ligo.org/D1500443

Attachment 1: D990511-40m_151123.pdf
D990511-40m_151123.pdf
  11817   Thu Nov 26 19:39:27 2015 KojiUpdateLSCCurrent state of the frequency source, and possible improvement

Uploaded on T1000461 too.

Attachment 1: RF_Frequency_Source.pdf
RF_Frequency_Source.pdf RF_Frequency_Source.pdf
  11822   Sun Nov 29 12:32:26 2015 KojiUpdateLSCCurrent state of the frequency source, and possible improvement

I'm not claiming we need to modify the frequency source immediately as we are not limited by the oscillator amplitude or phase noise.
I just wanted to note something in mind before it goes away quickly.

Alberto's T1000461 tells us that the oscillator and phase noise are degraded by factor of ~3 and ~5 due to the RF chanin.
My diagram is possible removal of up-down situation of the chain.

Maybe more direct improvement would be:

- Removal of two amplifiers out of four. The heat condition of the box is touch thought it is not critical.

- The modification will allow us to have a spare 11MHz channel at 1X2 rack that would be useful for 3f modulation.

  11826   Mon Nov 30 15:17:57 2015 KojiUpdateLSCLO level check for the LSC RF distribution box

T1000461 tells us that the nominal LO input is 2dBm although we don't know what's the LO level is at the mixers in the demod boards.

  11829   Mon Nov 30 18:27:30 2015 KojiUpdateLSCstrange behavior of ASDC

It wasn't fully mentioned in ELOG 11814.
We checked the PD first and this behavior didn't change after the realignment of the AS55PD.
Yutaro confirmed that this effect is happening in the vacuum chamber.

  11834   Tue Dec 1 17:26:14 2015 KojiUpdateGeneralMegatron maitenence

SLOWDC servo was dead. I followed EricQ's instruction.

  11835   Tue Dec 1 20:20:16 2015 KojiUpdateGeneralMegatron maitenence

MC Autolocker got stack somewhere. I had to go to megatron and kill MC Autolocker.

init relaunched the autolocker automatically, and now it started properly.

  11852   Sat Dec 5 21:28:33 2015 KojiHowToCamerasWhen image capture does not work...

Do we need "make" everytime? Do you mean just running "modprobe" didn't work?

  11867   Wed Dec 9 18:45:58 2015 KojiSummaryGeneralNetwork Topology Check

[Eric Q, Gautam, Koji]

We went through the network connections to produce the mapping of the instruments.
Gautam summarized the notes into a spread sheet. See attachments.

We didn't find any irregular connections except for the connection of NETMGR port of c1ioo to Martian Network.
This cable was removed.

Attachment 1: Network_topology_9Dec2015.xlsx
Attachment 2: Network_topology_9Dec2015.pdf
Network_topology_9Dec2015.pdf Network_topology_9Dec2015.pdf Network_topology_9Dec2015.pdf
  11873   Fri Dec 11 13:28:36 2015 KojiUpdateLSCPower recycling gain estimation from arm loss measurement

Can I ask you to make a plot of the power recycling gain as a function of the average arm loss, indicating the current loss value?

  11876   Fri Dec 11 23:12:09 2015 KojiSummaryCOCLoss map measurement document

Yutaro left detailed slides for his loss map measurement

https://dcc.ligo.org/LIGO-G1501547

  11920   Thu Jan 7 19:04:25 2016 KojiUpdateLSCAUX X Freq Noise measured

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

  11923   Fri Jan 8 22:37:17 2016 KojiUpdateGeneralNew WiFi router

I configured a new wifi bridge for a GPIB Instruments.

The some facts are described on https://wiki-40m.ligo.caltech.edu/Network

The setting up wasn't so straight forward. I added more details there as a linked page.
One thing I had to do with the martian wifi router was that I had to separate the name of SSIDs for 2GHz and 5GHz networks.


Now the data download from Agilent is super fast!
The first establishing the connection takes the most of the time, and the data transfer takes literary nothing.

controls@pianosa|netgpibdata > time ./netgpibdata -i 192.168.113.167 -d AG4395A -a 10 -f meas01
Connecting to host 192.168.113.167, GPIB 10...
done.
Data will be written into meas01.dat.
Parameters will be written into meas01.par.
Writing measurement data to file...
Writing to the parameter file.

real    0m4.056s
user    0m0.068s
sys    0m0.020s

 

  11941   Thu Jan 21 00:02:11 2016 KojiUpdateLSCHopeful signs

That's a good news. Only quantitative analysis will tell us if it is true or not.

Also we still want to analyze the traffic with the new switch.

Quote:

On a brighter note, I've only noticed one brief EPICS freeze all night. In addition, the wall StripTools seem totally contiuous since ~4pm, whereas I'm used to seeing some blocky shapes particularly in the seismic rainbow. Could this possibly mean that the old WiFi router was somehow involved in all this? 

 

  11964   Sat Jan 30 09:56:24 2016 KojiUpdateGreen LockingInnolight laser is 10 years old

It is strange that there is no difference between with and without NE, isn't it?

  11968   Mon Feb 1 15:43:18 2016 KojiUpdateGreen LockingInnolight laser is 10 years old

This is the same one as what you got from Steve. But you can find full pages.

https://wiki-40m.ligo.caltech.edu/PSL/NPRO

  11971   Tue Feb 2 18:54:02 2016 KojiUpdateGreen LockingLightwave NPRO moved from PSL table to SP table

jiIn fact, it is one of the most difficult type mode profiling to measure a beam directly out from a laser source.

If you reduce the power by ADJ, this significantly changes the output mode as the pumping power varies temperature gradient of the laser crystal and thus thermal lensing in it. I'd recommend you to keep the nominal power.

If you use a PBS for power reduction, you should increase the transmission ~x10 from the minimum so that you are not dominated by possible junk polarization.

Any transmissive BK7 components where the beam is small can cause thermal lensing. In order to avoid this issue, I usually use two noncoated (or one AR coated) optical windows made of UV fused silica to pick off the beam. Once the beam power is reduced I suppose it is OK to use an additional ND filter in front of the CCD.

Another more reliable method is an old-good knife edge measurement.

  11974   Thu Feb 4 09:16:46 2016 KojiUpdateGreen LockingLightwave NPRO moved from PSL table to SP table

I don't think the discrepancy is a serious issue as long as the mode is clean. The mode is determined by the NPRO crystal and is hard to change by anything except for the thermal lensing in the crystal.

And I never succeeded to reproduce the mode listed in the manual.

One thing you'd better to take care is that clipping of the beam produces diffraction. The diffracted beam spreads faster than the nominal TEM00 mode. Therefore the power meter should to be placed right after the razor blade. i.e. As you move the longitudinal position of the razor blade, you need to move the power meter.

  11989   Fri Feb 12 19:07:52 2016 KojiUpdateGreen LockingLaser swap - green light recovered but no flashes in the arm

800e-6 / 0.225^2 = 0.016

=> 1.6%/W

I thought Kiwamu had roughtly 2%/W.

 

  11991   Mon Feb 15 13:09:33 2016 KojiUpdateGeneralSomething has gone wrong - was there a power outage?

Looks like that's the case. LIGO GC also sent an e-mail that there was a popwer glitch.

  12000   Fri Feb 19 15:12:38 2016 KojiSummaryPEMGuralp Health Check

I measured the guralp raw outputs and the TFs using the handheld unit and an FFT analyzer.

[Setup]

The handheld unit was connected to each guralp with the same cable which is confirmed t be functional with the Yend Guralp.

The signal for Z, N, and E directions are obtained from the banana connectors on the handheld unit. Each direction has mass, low gain velocity, and high gain velocity output. The PSDs of the signals were measured with an FFT analyzer. The transfer function from the mass signal to the low/high gain signals were also measured for each direction.

The adjustment screw for the E output of the Xend does not work. I had to tilt the Xend Guralp using the leg screws to bring the E signal to zero.

[Result]

Attachment 1: Raw voltage PSD for all outputs
Attachment 2: Comparison of the low gain vel outputs

- All of the mass output show similar PSDs.
- Low gain velocity outputs shows somewhat similar levels. I still need to check if the output is really the ground velocity or not.
- High gain velocity outputs are either not high gain, broken, or not implemented.

- We need to calibrate the low gain output using signal injection, huddle test, or something else.

Attachment 3: TFs between each mass output and the low or high gain outputs

- TFs between the mass signal and the low vel signals show the similar transfer functions between the channels.
- The high gain outputs show low or no transfer function with regard to the mass signals.
 

Attachment 1: Guralp_Raw_PSD.pdf
Guralp_Raw_PSD.pdf
Attachment 2: low_vel_comparison.pdf
low_vel_comparison.pdf
Attachment 3: Guralp_TF.pdf
Guralp_TF.pdf
  12037   Wed Mar 16 16:02:40 2016 KojiUpdateSUSwire standoff test cut

It looks almost OK, but we need a bit sharper picture for both the groove and thw wire.

Attachment 1: ruby.png
ruby.png
  12042   Tue Mar 22 21:30:15 2016 KojiUpdateIOOPMCIMC aligned, WFS offset adjusted

The alignment of the PMC adjusted on the PSL table: Trans 0.737->0.749

The alignment of the IMC adjusrted on the sliders: Trans 14300->15300

WFS offset has been reset by /opt/rtcds/caltech/c1/scripts/MC/WFS/WFSoffsets

Attachment 1: 08.png
08.png
  12049   Sat Mar 26 18:28:24 2016 KojiUpdateelogelogd flakiness

Elogd have been restarted several times today because it died everytime I submit something.
Here is the copy of the log.


GET /OMC_Lab/255?cmd=loc&value=Submit HTTP/1.1
Returned 6 bytes
GET /40m/elog.rdf HTTP/1.1
Returned 17109 bytes
TCP connection #1 on socket 5 closed
POST /OMC_Lab/ HTTP/1.1
Returned 20 bytes
GET /OMC_Lab/255 HTTP/1.1
Returned 53721 bytes
GET /ckeditor/skins/moono/images/arrow.png HTTP/1.1
Returned 489 bytes
POST /OMC_Lab/ HTTP/1.1
*** buffer overflow detected ***: /export/home/elog/elog/elogd terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f1435639e57]
/lib/x86_64-linux-gnu/libc.so.6(+0x108d50)[0x7f1435638d50]
/lib/x86_64-linux-gnu/libc.so.6(+0x1081b9)[0x7f14356381b9]
/lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0xdd)[0x7f14355ab0cd]
/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x25a8)[0x7f143557ac18]
/lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x94)[0x7f1435638254]
/lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x7f143563819d]
/export/home/elog/elog/elogd[0x426405]
/export/home/elog/elog/elogd[0x473b7f]
/export/home/elog/elog/elogd[0x4abfb2]
/export/home/elog/elog/elogd[0x4ad7fb]
/export/home/elog/elog/elogd[0x4b0af5]
/export/home/elog/elog/elogd[0x4b1eb9]
/export/home/elog/elog/elogd[0x403568]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f143555176d]
/export/home/elog/elog/elogd[0x404299]
======= Memory map: ========
00400000-004e6000 r-xp 00000000 fc:00 10361276                           /export/home/elog/elog-3.0.d/elogd
006e5000-006e6000 r--p 000e5000 fc:00 10361276                           /export/home/elog/elog-3.0.d/elogd
006e6000-007c6000 rw-p 000e6000 fc:00 10361276                           /export/home/elog/elog-3.0.d/elogd
007c6000-0173d000 rw-p 00000000 00:00 0
0214d000-02656000 rw-p 00000000 00:00 0                                  [heap]
7f14342f8000-7f143430d000 r-xp 00000000 fc:00 2883628                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f143430d000-7f143450c000 ---p 00015000 fc:00 2883628                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f143450c000-7f143450d000 r--p 00014000 fc:00 2883628                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f143450d000-7f143450e000 rw-p 00015000 fc:00 2883628                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f143450e000-7f14348cd000 rw-p 00000000 00:00 0
7f1434a34000-7f1434d39000 r--p 00000000 fc:00 530477                     /usr/lib/locale/locale-archive
7f1434d39000-7f1434d4f000 r-xp 00000000 fc:00 655527                     /usr/local/lib/libz.so.1.2.8
7f1434d4f000-7f1434f4e000 ---p 00016000 fc:00 655527                     /usr/local/lib/libz.so.1.2.8
7f1434f4e000-7f1434f4f000 r--p 00015000 fc:00 655527                     /usr/local/lib/libz.so.1.2.8
7f1434f4f000-7f1434f50000 rw-p 00016000 fc:00 655527                     /usr/local/lib/libz.so.1.2.8
7f1434f50000-7f1434f52000 r-xp 00000000 fc:00 2883655                    /lib/x86_64-linux-gnu/libdl-2.15.so
7f1434f52000-7f1435152000 ---p 00002000 fc:00 2883655                    /lib/x86_64-linux-gnu/libdl-2.15.so
7f1435152000-7f1435153000 r--p 00002000 fc:00 2883655                    /lib/x86_64-linux-gnu/libdl-2.15.so
7f1435153000-7f1435154000 rw-p 00003000 fc:00 2883655                    /lib/x86_64-linux-gnu/libdl-2.15.so
7f1435154000-7f1435307000 r-xp 00000000 fc:00 2883609                    /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7f1435307000-7f1435506000 ---p 001b3000 fc:00 2883609                    /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7f1435506000-7f1435521000 r--p 001b2000 fc:00 2883609                    /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7f1435521000-7f143552c000 rw-p 001cd000 fc:00 2883609                    /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7f143552c000-7f1435530000 rw-p 00000000 00:00 0
7f1435530000-7f14356e4000 r-xp 00000000 fc:00 2884139                    /lib/x86_64-linux-gnu/libc-2.15.so
7f14356e4000-7f14358e3000 ---p 001b4000 fc:00 2884139                    /lib/x86_64-linux-gnu/libc-2.15.so
7f14358e3000-7f14358e7000 r--p 001b3000 fc:00 2884139                    /lib/x86_64-linux-gnu/libc-2.15.so
7f14358e7000-7f14358e9000 rw-p 001b7000 fc:00 2884139                    /lib/x86_64-linux-gnu/libc-2.15.so
7f14358e9000-7f14358ee000 rw-p 00000000 00:00 0
7f14358ee000-7f1435943000 r-xp 00000000 fc:00 2884155                    /lib/x86_64-linux-gnu/libssl.so.1.0.0
7f1435943000-7f1435b42000 ---p 00055000 fc:00 2884155                    /lib/x86_64-linux-gnu/libssl.so.1.0.0
7f1435b42000-7f1435b45000 r--p 00054000 fc:00 2884155                    /lib/x86_64-linux-gnu/libssl.so.1.0.0
7f1435b45000-7f1435b4c000 rw-p 00057000 fc:00 2884155                    /lib/x86_64-linux-gnu/libssl.so.1.0.0
7f1435b4c000-7f1435b6e000 r-xp 00000000 fc:00 2884145                    /lib/x86_64-linux-gnu/ld-2.15.so
7f1435d57000-7f1435d5c000 rw-p 00000000 00:00 0
7f1435d6a000-7f1435d6e000 rw-p 00000000 00:00 0
7f1435d6e000-7f1435d6f000 r--p 00022000 fc:00 2884145                    /lib/x86_64-linux-gnu/ld-2.15.so
7f1435d6f000-7f1435d71000 rw-p 00023000 fc:00 2884145                    /lib/x86_64-linux-gnu/ld-2.15.so
7ffd85795000-7ffd85997000 rw-p 00000000 00:00 0                          [stack]
7ffd859b2000-7ffd859b4000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
er_id"
Received unknown cookie "ajs_group_id"
Received unknown cookie "ajs_anonymous_id"
Received unknown cookie "__utma"
Received unknown cookie "_ga"
Received unknown cookie "__unam"
Received unknown cookie "__utma"
Received unknown cookie "tk_ni"
Received unknown cookie "ajs_user_id"
Received unknown cookie "ajs_group_id"
Received unknown cookie "ajs_anonymous_id"
Received unknown cookie "cache_disable"
Received unknown cookie "NO_CACHE"
Received unknown cookie "__utma"
Received unknown cookie "_ga"
Received unknown cookie "__unam"
Received unknown cookie "__utma"
Received unknown cookie "tk_ni"
Received unknown cookie "ajs_user_id"
Received unknown cookie "ajs_group_id"
Received unknown cookie "ajs_anonymous_id"
Received unknown cookie "__utma"
Received unknown cookie "_ga"
Received unknown cookie "__unam"
Received unknown cookie "__utma"
Received unknown cookie "tk_ni"
Received unknown cookie "ajs_user_id"
Received unknown cookie "ajs_group_id"
Received unknown cookie "ajs_anonymous_id"
Received unknown cookie "__utma"
Received unknown cookie "_ga"
Received unknown cookie "__unam"
Received unknown cookie "__utma"
Received unknown cookie "tk_ni"
Received unknown cookie "ajs_user_id"
Received unknown cookie "ajs_group_id"
Received unknown cookie "ajs_anonymous_id"
Received unknown cookie "__utma"
Received unknown cookie "_ga"
Received unknown cookie "__unam"
Received unknown cookie "__utma"
Received unknown cookie "tk_ni"
Received unknown cookie "ajs_user_id"
Received unknown cookie "ajs_group_id"
Received unknown cookie "ajs_anonymous_id"
  12052   Mon Mar 28 22:16:44 2016 KojiUpdateGeneralNew WiFi router

I configured three more mini wifi extender. They are ready to use.

We should add these to the host table (I forgot where it is)

192.168.113.233 NETGEAR_EX3700_1
192.168.113.234 NETGEAR_EX3700_2
192.168.113.235 NETGEAR_EX3700_3
192.168.113.236 NETGEAR_EX3700_4

  12072   Tue Apr 12 22:41:00 2016 KojiUpdateIOOPMC/IMC aligned, WFS offset adjusted

Did it again.

PMC Trans ~0.739
IMC Trans ~15000

  12146   Thu Jun 2 16:35:44 2016 KojiUpdateSUS wire standoffs update

Gap of the prism from the mirror

Sag: s = R(1-Cos[ArcSin[d/2/R]])

- Mirror curvature sag for 2mm prism (R=37.75mm): s=13um

- Minimum gap: 20um => s=33um => R=15mm

- Nominal gap: 35um => s=48um => R=10mm

- Maximum gap: 50um => s=63um => R=8mm


The second figure shows somewhat realistic arrangement of the pieces

Attachment 1: sapphire_stand_off_v3.pdf
sapphire_stand_off_v3.pdf
Attachment 2: arrangement-v3.pdf
arrangement-v3.pdf
  12223   Tue Jun 28 20:43:23 2016 KojiSummaryCOCFirst Contact cleaning practice

Made a dry run of the in-situ cleaning for a 3inch optic.

Attachment 1: The Al dummy mass is clamped in the suspension cage.
Attachment 2: The front surface was painted. The nominal brush with the FC bottle was used.
Attachment 3: Zoom in of the front surface.
Attachment 4: The back surface was painted.
Attachment 5: The back surface was peeled.
Attachment 6: The front surface was peeled too.
Attachment 7: The peeled layers.

Findings:

1. To paint a thick layer (particlarly on the rim) is the key to peel it nicely.

2. It was helpful for easier peeling to have mutiple peek tabs. Two tabs were sufficient for ~1" circle.

3. The nominal brush with the bottle was OK although one has to apply the liquid many times to cover such a large area. A larger brush may cause dripping.

4. The nominal brush was sufficiently long once the OSEMs are removed. In any case it is better to remove the OSEMs.

Attachment 1: IMG_20160628_170335196.jpg
IMG_20160628_170335196.jpg
Attachment 2: IMG_20160628_171547769.jpg
IMG_20160628_171547769.jpg
Attachment 3: IMG_20160628_171607802.jpg
IMG_20160628_171607802.jpg
Attachment 4: IMG_20160628_172328190.jpg
IMG_20160628_172328190.jpg
Attachment 5: IMG_20160628_174541960.jpg
IMG_20160628_174541960.jpg
Attachment 6: IMG_20160628_174556004.jpg
IMG_20160628_174556004.jpg
Attachment 7: IMG_20160628_174617198.jpg
IMG_20160628_174617198.jpg
  12255   Wed Jul 6 19:36:45 2016 KojiUpdateGeneralSUS Vmon

I wanted to know what this Vmon exactly is. D010001 is telling us that the Vmon channels are HPFed with fc=30Hz (Attachment 1). Is this true?


I checked the quiscent noise spectrum of the ITMX UL coil output (C1:SUS-ITMX_ULCOIL_OUT) and the corresponding VMON (C1:SUS-ITMX_ULVmon). (Attachment 2 Ref curves). I did not find any good coherence. So the nominal quiscent Vmon output is carrying no useful information. 

Question: How much do we need to excite the coil output in order to see any meaningful signal?

As I excite the ITMX UL coil (C1:SUS-ITMX_ULCOIL_EXC) with uniform noise of 100-300 counts below 0.3Hz, I eventually could see the increase of the power spectrum and the coherence (Attachment 2). Below 0.1 Hz the coherence was ~1 and the transfer function was measured to be -75dB and flat. But wait, why is the transfer function flat?

In fact, if I inject broadband noise to the coil, I could increase the coil output and Vmon at the same time without gaining the coherence. (Attachment 3). After some more investigation, I suspect that this HPF is diabled (= bypassed) and aliasing of the high freq signal is causing the noise in Vmon.

In order to check this hypothesis, we need to visit the board.

Attachment 1: HPF.png
HPF.png
Attachment 2: 160706_ITMX_VMON2.pdf
160706_ITMX_VMON2.pdf
Attachment 3: 160706_ITMX_VMON1.pdf
160706_ITMX_VMON1.pdf
  12256   Wed Jul 6 20:51:00 2016 KojiUpdateGeneralSeismometer Enclosure Development | SURF 2016

Circuit1: It is nice to receive the voltage across the transimpedance resistor with a high impedance buffer (or amplifier), as close to the resister as possible. This amplifier needs to have low numbers for input bias current, input offset current, and input current noise. These current noise becomes the noise of the temperature reading. On the top of that, the input voltage noise of the buffer will be added to the output. The typical noise model can be found in http://www.analog.com/media/en/technical-documentation/application-notes/AN-940.pdf

The good candidates for the buffer is LT1128, ADA4004, OPA140, and LT1012. If the application is not too sensitive to the total noise, OPA604 is a good choise with easier handling.

Circuit2: With the same reason, AD741 is an old generic amp that is not a great choise for this purpose. The current noise is more significant because of the higher transimpedance here. The same noise model as above can be used to analyze the performance.

  12257   Wed Jul 6 21:05:36 2016 KojiUpdateComputer Scripts / ProgramsNew Tabs and Working Summary Pages

I started to receive emails from cron every 15min. Is the email related to this? And is it normal? I never received these cron emails before when the sum-page was running.

Attachment 1: cron_mail.txt.zip
  12260   Wed Jul 6 21:50:21 2016 KojiUpdateComputer Scripts / ProgramsNew Tabs and Working Summary Pages

It seemed something has been done. And I got cron emails.
Then, it seemed something has been done. And the emails stopped.

  12267   Thu Jul 7 14:45:26 2016 KojiUpdateGeneralpianosa monitor dead

Johannes, Koji

We obtained two monitors of the same type from Larry.

  12269   Thu Jul 7 16:05:55 2016 KojiUpdateGeneralSUS Vmon

Ah, thanks. That makes sense. In that case, we should remove the texts "30Hz HPF" from the suspension screens.

Now we just need AA LPFs for these channels, or hook them up to the RT system.

  12272   Fri Jul 8 11:48:09 2016 KojiUpdateGeneralVent progress - ETMX SUS Coil driver electronics investigation

YES

Move the suspension on the south clean bench and make more close inspection. We need to remove the OSEMs.

Then unmount the mirror. Bring it to the clean room and work on the bond removal.
Meanwhile, set up all suspension components inclusing the alignment test setup.

  12278   Fri Jul 8 20:44:09 2016 KojiUpdateGeneralETMX removed from suspension

In the evening, I went into the clean room to check how it goes.

- The air around the table is quite warm like a hell. Is this normal?

- I checked how the scattered epoxy spots look like. They were not touching the bath anymore due to evaporation.
- I scraped the spots with the tweezers there. They were easily removed. The particlates on the side barrel were wiped by a wipe with aceton. (Result: Attachment 3)

- Then looked at the other side. I poked the standoff with the tweezer. It was easily removed. I don't think the bond was too weak. Just the area of the bond was so tiny.
- Also residue was scraped by a tweezer and wiped with a cloth. (Attachment 2)

- The removed stand off is in the stainless bowl together with the parts that Eric removed.

- I didn't want to leave the optic in the aceton fume. It was placed on a metal donuts for a 3" optic. (Attachment 4)

- I couldn't find a vacant clean glass jar for the lid. So, a foil hut was built. We should be very careful not to scratch the optic when we remove the hut. (Attachment 5)

- The aceton bath was covered with the foil as it was. (Attachment 6)

Attachment 1: photo1.jpg
photo1.jpg
Attachment 2: photo2.jpg
photo2.jpg
Attachment 3: photo3.jpg
photo3.jpg
Attachment 4: photo4.jpg
photo4.jpg
Attachment 5: photo5.jpg
photo5.jpg
Attachment 6: photo6.jpg
photo6.jpg
  12279   Fri Jul 8 21:02:09 2016 KojiUpdateComputer Scripts / ProgramsMEDM Tab on Summary Pages

Very nice!

Some of the screens are up-to-date, and some are not. Are the errors associated with the screens that failed to get updated?

  12293   Tue Jul 12 18:13:19 2016 KojiUpdateVACN2 bottle replaced

Gautam, Koji

We replaced the right N2 bottle as it was empty.

  12298   Wed Jul 13 03:16:47 2016 KojiUpdateGeneralITMX dust

Multicolor flash light:

- It seems that the usb port charging doesn't work.

- There is a battery charger on Steve's desk. I set the batteries on it.

 

White LED flash light:

- I temporarily brought a compatible charger from WB. It's charging two batteries behind the LCD display on my desk.

 

  12300   Wed Jul 13 21:13:51 2016 KojiUpdateGeneralETMX guide rod gluing / ETMY Magnet gluing

[Eric, Koji]

  • ETMX: The Al guide rod has been glued on the mirror.
  • ETMY: The UR, LR, and SD magnets have been glued on the mirror.
  • For both, we are waiting for the glue getting cured.

Handing over message to the next step

  • ETMX: The arm of the fixture has probably been glued together with the guide rod. It has to be taken care when the fixture is removed.
    (See
    ETMX gluing section and Attachment 13)

ETMX: guide rod gluing (done) -> fixture unmounting side -> fixture setting -> magnet gluing -> suspend -> pitch balance -> ruby gluing -> air bake
ETMY: magnet (done) -> fixture unmounting -> air bake


ETMY gluing

Mirror transport:
- A transport setup was made with a donut holder for a 3" optic, glass jar, stain less tray, and a CS Stat zipbag. (Attachment 1)

Shimming:
- The magnets have been glued witht the gluing fixture. (Attachment 2)
- We checked the dimensions of the glued magnet and found that the thicker side has to be raised by 1mm. (We used the fact that the relative distance between the wire groove and the magnet is always the same.)
- The ETMs have 2.5deg wedge and this corresponds to 3.2mm height difference between the left and right edges. This meant that the thinner side had to be raised by 4.2mm.
- We used a 0.9mm Teflon sheet for the thicker side (Attachment 3) and two 2.2mm Teflon pieces for the thinner side (Attachment 4). For stabilization of the fixture, two Teflon tubes with a diameter of ~3mm are inserted to the top and bottom side of the mirror (Attachment 5).

Magnet orientation:
- Mirror orientation in the fixture (Attachment 6).
- It was confirmed that existing UR, LR, and Right SD magnets have the polarity of N facing out, S facing out, and N facing out. And we confirmed that this is consistent with ETMX and the procedure document (E970037)
- Along with the procedure document, we arranged the magnet-dumbbells UL, LL, and Left SD magnets to have S-out, N-out, and N-out. (Attachments 7, 8, and 9)

Gluing:
- In prior to gluing, all three dumbbells surfaces were cleaned by acetone and razor blade scrubbing.
- After the epoxy curing test (see below), the three magnet-dumbbell pairs have been glued on the mirror. A single dub of EP30-2 was applied to each dumbbell surface.

- Attachments 10, 11, and 12 shows how glue is spread at each joint.

ETMX gluing

Guide rod positioning:
- The longitudinal position of the guide rod was adjusted using the micrometer microscope such that it located at the center of the mirror thickness.
- The guide rod is not long enough to have the edges sticking out from the form of the fixture arm. Therefore only arm finger of the arm held the guide rod. 
- The height was adjusted to be 1.73mm (68mil) lower than the mirror scribe line. The mirror is fixed on the fixture upside down. So this bonds the guide rod above the scribe line.

Gluing:
- Then the epoxy was applied to the guide rod. The glue was applied to two edges of the rod, but capillary action spread the glue around the rod. It seemed that the fixture and the rod were connected with the glue. Care should be taken when the fixture is going to be removed. (Attachment 13)
- The top side (in the picture) where the stand-off will come is still relatively kept clean. So it must be OK for the stand off. If there is an issue, we can shave the epoxy with a razor blade.

Glue testing

- EP30-2 tends to fail to get cured. In order to check the mixture is properly made or not, we put a test piece into air bake oven.
- The procedure says, 200F 15min bake show if the glue is in a good shape or not.

- We have the temperature sensor setup on a air bake oven, but it seemed that the indicated temperature there is overestimate.
  The heating setting of 2 was enough to show the temp of 100degC although EP30-2 didn't get cured with this setting.

- Our experience says that heater setting of "5" makes the temperature ~90degC. On July 12nd, this setting showed the temp of 90degC. Today (July 13rd) it didn't. In the both cases, the epoxy got cured nicely. So we should use this setting.

Attachment 1: P7138742.jpg
P7138742.jpg
Attachment 2: gluing_fixture.jpg
gluing_fixture.jpg
Attachment 3: shimming3.jpg
shimming3.jpg
Attachment 4: shimming1.jpg
shimming1.jpg
Attachment 5: shimming2.jpg
shimming2.jpg
Attachment 6: gluing_fixture3.jpg
gluing_fixture3.jpg
Attachment 7: P7138747.jpg
P7138747.jpg
Attachment 8: P7138748.jpg
P7138748.jpg
Attachment 9: P7138750.jpg
P7138750.jpg
Attachment 10: P7138773.jpg
P7138773.jpg
Attachment 11: P7138774.jpg
P7138774.jpg
Attachment 12: P7138775.jpg
P7138775.jpg
Attachment 13: P7138772.jpg
P7138772.jpg
  12301   Thu Jul 14 01:00:33 2016 KojiUpdateGeneralETMX ruby guided gluing

Today I took the picture of the glued ruby stand-off. The groove has not been invaded by the epoxy!

Attachment 1: ruby.jpg
ruby.jpg
  12325   Fri Jul 22 03:02:37 2016 KojiUpdateCOCFC painting

[Koji Gautam]

We have worked on the FC painting on ITMX and ITMY. We also replaced the OSEM fixing screws with the ones with a hex knob.
This was done except for the SD OSEM as the new screw was not long enough. We left an allen-key version of the screw for the SD OSEM.

All the full-resolution photos can be found on g-photo.


ITMY

Attachment1: The barrel was pretty dusty. Some dusts were observed on the HR face but it was not so terrible. The barrel and the HR face were blown with the ionized N2 and then wiped with IPA. The face wiping was done n a similar way as the drag wiping.

Attachment2: FC was applied to the HR surface.

Attachment3: The AR surface was also painted with FC. The brush touched the coil holder.

Attachment4: The brush touched the coil holder. Another PEEK tab was applied to remove this FC stain on the metal holder.

Attachment5: This is the result of successful removal of the FC stain.

ITMX

Attachment6: The OSEM arrangement before removal. We confirmed that the OSEM arrangement was as described on Wiki.

Attachment7/8: The ITMX was obviously a lot dirtier than ITMY. The barrel accumulated dusts.

Attachment9: This is the HR face picture with large dusts on it.

Attachment10: The HR surface was painted with FC.

Attachment11: This is the AR surface with FC painted.

Attachment 1: ITMY_barrel_dust.jpg
ITMY_barrel_dust.jpg
Attachment 2: ITMY_HR_FC.jpg
ITMY_HR_FC.jpg
Attachment 3: ITMY_AR_FC.jpg
ITMY_AR_FC.jpg
Attachment 4: ITMY_drip_removal.jpg
ITMY_drip_removal.jpg
Attachment 5: ITMY_drip_removed.jpg
ITMY_drip_removed.jpg
Attachment 6: ITMX_OSEMS.jpg
ITMX_OSEMS.jpg
Attachment 7: ITMX_barrel_dust1.jpg
ITMX_barrel_dust1.jpg
Attachment 8: ITMX_barrel_dust2.jpg
ITMX_barrel_dust2.jpg
Attachment 9: ITMX_HR_dusty.jpg
ITMX_HR_dusty.jpg
Attachment 10: ITMX_HR_FC.jpg
ITMX_HR_FC.jpg
Attachment 11: ITMX_AR_FC.jpg
ITMX_AR_FC.jpg
ELOG V3.1.3-