40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
 40m Log, Page 208 of 341 Not logged in
ID Date Author Type Category Subject
881   Mon Aug 25 15:50:18 2008 ranaSummaryPEMRanger SS-1
The manual for the Ranger SS-1 seismometer can be found on line here:
ftp://ftp.kmi.com/pub/software_manuals/300190/300190nc.pdf

and now in our 40m PEM Wiki page:
Ranger_SS-1

To calibrate it, we use the formula from the manual:
                 R_x
G_L = G_0 * ------------   =  149 +/- 3 V/(m/s)
R_x  +  R_c

where
G_0 = 340 V/(m/s)    (generator constant)
R_x = 4300 Ohms      (external damping resistor in Pomona box)
R_c = 5500 Ohms      (internal coil resistance)

Then we have a gain of 200 in the SR560 so that gets us to ~30000 V/(m/s).

And then there's a DAQ conversion factor of the usual 2^16 cts / 4 V.

so the calibration constant is

G = 488 counts / (micron/sec)

in the ~1-50 Hz band
1167   Tue Dec 2 19:18:10 2008 ranaSummaryPEMRanger SS-1
In entry http://dziban.ligo.caltech.edu:40/40m/881 and a follow up from Jenne I put in the Ranger calibration.
Since then, we've reduced the SR560 gain from 200 to 100 so the calibration factor is now:

1e-9 (m/s)/count and then 2 poles at 0 Hz, and a Q~1 zero pair at 1 Hz.
in DTT:
G = 1e-9
p = 0, 0
z = 0.7 0.7
391   Fri Mar 21 23:15:11 2008 ranaConfigurationPEMRanger SS-1: New Setup
The Ranger seismometer has been in a bad state. Its output had been sent into a SR560 without any termination.

The seismometer is, internally, just a mass on a flexure with a magnet and a pickup coil for readout.
The damping of the system depends on the resistor hooked up across the coil. With the SR560 this is
the 1 Meg input impedance of it and so the mass is undamped.

I installed a 4300 Ohm resistor in there which seems to nearly critically damp it. However, this will not
allow us to reach the ultimate quantum noise limited performance. We will have to analyze the thermal, voltage,
and current noise to get that.

I then also increased the gain from 10 to 100 on the SR560. This should now make the front end noise of the
seismometer/SR560 close to equal to the noise of the PEM ADC.
1171   Wed Dec 3 19:21:09 2008 ranaConfigurationPEMRanger move
I looked at the Ranger signals. Somehow it has a relative transfer function of 'f' between it and the Guralp.
      Ranger
i.e.  ------ ~ f
Guralp

which is strange since according to their manuals, they should both be giving us a voltage output which is proportional
to velocity. I checked that the Ranger only has a load resistor and then an SR560 low pass at 300 Hz. Jenne assures
me that the Guralp breakout box shouldn't have any poles either (to be double checked). Its a mystery.

We made sure that the SR560 now is DC coupled, G = 100, & 1-pole low pass at 300 Hz. I moved it over next to the Guralp
(went through the mass recentering procedure after forgetting to lock it before moving). It is behaving as it was
before.

Attached is a 2 page PDF of the comparisons. The 'MC1' channels are Guralp and 'MC2' is Ranger.

The second attachment compares our seismometers (in counts) with the LHO Guralp seismometers. There's no high frequency
rolloff there like what we see here so I bet a dollar that there's a pole in the Guralp box somewhere.
Attachment 1: c.pdf
Attachment 2: wsnb.pdf
2194   Fri Nov 6 16:27:15 2009 JenneUpdatePEMRanger moved

The Ranger seismometer has been moved to ~the middle of the Mode Cleaner tube, and it's orientation has been changed to horizontal (using all of the locking/mass centering procedures).  This is similar in orientation to the way things were back in the day when Rana and Matt had the OAF running nicely.

2351   Fri Dec 4 18:54:03 2009 JenneUpdatePEMRanger moved

The Ranger was left in a place where it could be bumped during next week's activities (near the crawl-space to access the inside of the "L" of the IFO on the Yarm).  It has been moved a meter or so to a safer place.

Also, so that Steve can replace the battery in the SR560 that is used for the Ranger, I swapped it out with one of the ones which already has a new, charged battery.  All of the settings are identical.  For posterity, I took a pic of the front panel before unplugging the old SR560.

Attachment 1: RangerSeismometer_SR560settings_4Dec2009.JPG
1106   Sun Nov 2 21:37:22 2008 ranaUpdatePEMRanger recovery
The ranger signal has been bad since around 11 AM on Oct 25 (last Saturday). There are no elog
entries from that day, but I am quite sure that someone must have been working around the PSL
rack area.

It looks like what happened is that someone moved the chair with the monitor on it and/or the wooden
stool next to it. That put tension on the cable connecting the SR560 and the seismometer. The SR560
connector now seems loose and I think probably the cable ground wasn't connected. I swapped the
cable over to the "B" side of the SR560 and the ranger signal is now reasonable (very small offset
and normal seismic signal).

Please be careful when working around there. Everyone always says "I didn't do anything" or "it doesn't
effect anything".

We need to clean up the cabling around there in addition to running a new power cable for the RF amplifier
on the POY table.

I have also reduced its sample rate from 2048 to 512 Hz. The data are OK after 909640694.

I also increased the sample rate of AS_MIC from 2048 to 16384 Hz but that one seems to be broken
---->> the microphone seems to be either disconnected or broken.
10067   Wed Jun 18 22:47:48 2014 ericqUpdateCDSRaspberry pi added to martian network

I set up a raspberry pi on the martian network, to be hooked up to a frequency counter for tracking ALS beatnotes.

The instructions at https://wiki-40m.ligo.caltech.edu/Martian_Host_Table are outdated, the name server configuration is now at /etc/bind/zones/martian.db, I need to remember to update the wiki soon.

In any case, the raspberry pi is called "domenica," is found at 192.168.113.107, and has the standard controls user, with /cvs/cds mounted in the same way as the control room machines.

Once I'm comfortable with the configuration of the pi, I'm going to take an image of the SD card that serves as its hard drive, so that we can just image new cards for future raspberry pis on the martian network if we ever want them.

11965   Mon Feb 1 09:16:32 2016 SteveUpdatePEMRat got cut

We got it! Traps are removed.

Attachment 1: bingo.jpg
Attachment 2: bingo3.png
14186   Tue Aug 28 15:29:19 2018 SteveFrogsPEMRat is cut

The rat is cut by mechanical trap and it was removed from ITMX south west location.

A nagy kover patkanyt a fogo elkapta es megolte.

Attachment 1: rat#2.png.png
11911   Tue Jan 5 15:48:16 2016 SteveUpdatesafetyRat trap locations

Please look around when working close to these five locations. Use flashlights or leave lights on.

These mechanial traps are HAZARDOUS !

No visitors or tours till Monday, Jan 11  2016

Attachment 1: Control_Room.jpg
Attachment 2: EarmCESdoor.jpg
Attachment 3: 1Y1.jpg
Attachment 4: MC2.jpg
Attachment 5: XarmMaglev.jpg
11913   Tue Jan 5 17:19:57 2016 ranaUpdatesafetyRat trap locations

In the modern times, people use glue traps to catch rats instead of springs. They are less hazardous to people and don't spread rat fluid on the floor.

11909   Tue Jan 5 09:48:52 2016 SteveUpdatePEMRat trap moved

Our janitor confirmed that Q was not hallucinating about this animal. The dropping size indicating a good size one in the IFO room.

One of the mechanical traps moved from the control room to the east arm, close to the " machine shop " door.

I'm going to get more traps.

Quote:

Two mechanical and two sticdky traps were set to catch univited visitor.

Absolutely no food or food remains into inside garbage cans!!!!!!!!!!!!!!!!!!!!!!!!!

 Quote: A small rat / large mouse just ran through the control room. Ugh.

11895   Mon Dec 21 14:31:41 2015 SteveUpdatePEMRat traps set

Two mechanical and two sticdky traps were set to catch univited visitor.

Absolutely no food or food remains into inside garbage cans!!!!!!!!!!!!!!!!!!!!!!!!!

 Quote: A small rat / large mouse just ran through the control room. Ugh.

Attachment 1: ratsNC.jpg
11893   Sun Dec 20 23:23:54 2015 ericqUpdateALARMRats.

A small rat / large mouse just ran through the control room. Ugh.

10657   Fri Oct 31 11:46:15 2014 manasaUpdate Rattling HEPA : Eventually stops

The PSL HEPA stopped working while it was running at 80%. I have closed the PSL enclosure.

Steve is working to fix this.

6792   Mon Jun 11 16:08:58 2012 JenneUpdateEnvironmentRattling in the HEPA

There is an intermittent rattling sound coming from the HEPA in the NE corner of the PSL table (right above the PMC, all of our input optics).

Steve says it might be a bad bearing, but he'll check it out in the morning and get it fixed.

6793   Mon Jun 11 21:35:55 2012 JenneUpdateEnvironmentRattling in the HEPA

 Quote: There is an intermittent rattling sound coming from the HEPA in the NE corner of the PSL table (right above the PMC, all of our input optics). Steve says it might be a bad bearing, but he'll check it out in the morning and get it fixed.

MC was having a hard time staying locked, with no discernable reason from the control room (i.e. no big seismic, no PMC PZT railing).    The HEPA was on 100%, so I turned it down to 50% to hopefully reduce the rattling, if that was what was wrong.

10103   Wed Jun 25 17:49:36 2014 HarryUpdateGeneralRazorblade Analysis Pt. 2

Reconfigured razorblade analysis setup on the PD table as per instructions. Used it to collect data to calculate beam waist with, analyses to follow.

See attached schematic for optical setup.

Attachment 1: RazorbladeSetup.pdf
10083   Fri Jun 20 18:33:53 2014 HarryUpdateGeneralRazorblade Beam Analysis Setup

Eric Q and I set up the optical configuration for razorblade beam analysis on SP table for future use.

It has been aligned, and will be in use on Monday.

The beam will be characterized for future characterization of optical fibers.

10092   Tue Jun 24 13:04:49 2014 Harry, ManasaUpdateGeneralRazorblade Beam Analysis Setup

Harry will update this elog with details about his beam waist measurements for the old NPRO on the SP table.

10099   Wed Jun 25 09:17:33 2014 Harry, ManasaUpdateGeneralRazorblade Beam Analysis Setup

 Quote: Harry will update this elog with details about his beam waist measurements for the old NPRO on the SP table.

see http://nodus.ligo.caltech.edu:8080/40m/10098 for the update

10098   Wed Jun 25 09:16:52 2014 HarryUpdateGeneralRazorblade Measurements

Purpose

To use a razorblade to measure beam waist at multiple points along the optical axis, so as to later extrapolate the modal profile of the entire beam. This information will then be used to effectively couple AUX laser light to fibers for use in the frequency offset locking apparatus.

Data Acquisition

1) Step the micrometer-controlled razorblade across the beam at a given value of Z, along optical axis, in the plane orthogonal to it (arbitrarily called X).

2) At each value of X, record the corresponding output of a photodiode, (Thorlabs PD A55) here given in mV.

3) Repeat process at multiple points along Z

Analysis

Data from each iteration in the X were fitted to the error function shown below.

V(x) = A*(erf((x-m)/s)+c)

In the Y, they were fitted to:

V(x) = -A*(erf((x-m)/s)+c)

'A' corresponds to an amplitude, 'm' to a mean, 's' to a σ, and 'c' to an offset.

(Only because in Y measurements, the blade progressed toward eclipsing the beam, as opposed to in the X where it progressively revealed the beam.

These fits can be solved for x = (erf-1((V/A)-c)*s)+m1  which can be calculated at the points (Vmax/e2) and (Vmax*(1-1/e2)). The difference between these points will yield beam waist, w(z).

Conclusion

Calculations yielded waists of: X1=66.43um, X2=67.73um, X3=49.45um, Y1=61.20um, Y2=58.70, Y3=58.89

These data seem suspect, and shall be subjected to further analysis.

Attachment 1: 40m.zip
3409   Thu Aug 12 16:18:00 2010 JennaUpdateElectronicsRb clocks overnight

I took a look at the data from the middle of the night to see if it was significantly quieter than the data from the day, but it doesn't seem to be. The plot shows data from yesterday around 12:30pm and from this morning around 2am. It's a bit quieter at low frequencies, but not by much.

Attachment 1: rbcomp.pdf
4573   Wed Apr 27 17:38:01 2011 kiwamuUpdateElectronicsRe : AS55 demod board with new 90 deg splitter : healthy

Figure.1  I-Q relative phase measurement as a function of LO power.

Blue curve : relative phase of AS55 that I have modified today (#4572).

Red curve : relative phase of AS11 that I had modified a week ago (#4554). Just for comparison.

The relative phase of AS55 agrees approximately what we expected according to the datasheet of PSCQ-2-51W. We expected 85 degree.

Figure.1  I-Q amplitude imbalance as a function of LO power.

From - 5 dBm to 5 dBm in LO power the imbalance is within 3 %.

But the precision of the measurement is also about 2 % (because I used an oscilloscope). Even so the imbalance is still good.

 Quote from #4572 Some plots will be posted later.

4943   Wed Jul 6 02:12:36 2011 kiwamuUpdateSUSRe : More normalization of all sus controllers

[Jenne / Rana/ Kiwamu]

We found the 30 Hz high pass filters had lower gain than what they used to be at low frequcnies.

So we increased the gain of the high pass filters called '30:0.0'  by a factor of 10 to have the same gain as before.

Now all the suspension shows some kind of damping. Needs more optimizations, for example Q-adjustments for all the suspensions...

 Quote from #4942 This is getting closer, but with the whitening left OFF and the cts2um filter also OFF, none of the suspensions are working correctly.

4944   Wed Jul 6 10:35:35 2011 JamieUpdateSUSRe : More normalization of all sus controllers

 Quote: We found the 30 Hz high pass filters had lower gain than what they used to be at low frequcnies. So we increased the gain of the high pass filters called '30:0.0'  by a factor of 10 to have the same gain as before.

I'm not convinced that this is what you want to do, or at least I wouldn't do it this way.  The "k" in the zpk filter was set such that the filter had unity gain above the high-pass cut-off frequency.  For a 30 Hz high-pass the k needs to be a factor of 10 smaller than it would be for a 3 Hz high-pass to achieve this high frequency unity gain.

As it is now these HP filters have 20 dB of gain above 30 Hz.  If the open loop transfer function needs to more gain I would have done that by adjusting the overall DC gain of the filter bank, not by increasing the gain in this one filter.  Maybe you guys have been doing it differently, though.  Or maybe I'm just completely off base.

4946   Wed Jul 6 15:32:32 2011 JamieUpdateSUSRe : More normalization of all sus controllers

So after talking to Kiwamu about it, I understand now that since the damping loops need all of this extra gain when the high-pass corner is moved up, it's more convenient to put that gain in the control filter itself, rather than having to crank the overall DC gain up to some inconveniently high value.

4799   Thu Jun 9 12:21:07 2011 kiwamuUpdatePSLRe : PMC needs help

Nulling the slow actuation offset fixed the issue. Now PMC is back to normal.

The reflected beam on the CCD was quite symmetric (it looked very TEM00 mode !) for some reasons, I somehow suspected the mode matching to PMC.

One possibility I thought of was the laser temperature because it could change the laser spatial mode.

So I looked at the slow actuation offset on the FSS screen and found it was at -4.0 which sounds somewhat big.

Then I zeroed the offset by the slider and relocked PMC.

Then the spatial pattern of the reflected beam became usual (i.e. junk light looking) and the transmitted light wet up to 0.83 which is normal.

 Quote from #4798 The PMC is losing power.

5075   Sun Jul 31 00:37:57 2011 kiwamuUpdatePSLRe : PSL table work

I think you made a simple mistake in your diagram -- the mixer must be replaced by a summer circuit. Otherwise you cannot do the PDH lock.

 Quote from #5069

5316   Mon Aug 29 00:49:00 2011 kiwamuUpdateCDSRe : fb down

Fb is in a bad situation. It needs a MANUAL fsck to fix the file system.

HELP US, Jamieeeeeeeeeeee !!!

When Suresh and I connected a display and tried to see what was going on, the fb computer was in a file system check.

This was because Suresh did a hardware reboot by pressing a power button on the front panel.

Since the file checking took so long time and didn't proceed fast, we pressed the reset button and again the power button.

Actually the reset button didn't work (maybe ?) it just made some light indicators flashing.

After the second reboot the reboot message said that it needs a manual fsck to fix the file system. This maybe because we interrupted the file checking.

We are leaving it to Jamie because the fsck command would do something bad if unfamiliar persons, like us, do it.

In addition to it, the boot message was also saying that line 37 in /etc/fstab was bad.

We logged into the machine with a safe mode, then found there was an empty line in 37th line of fstab.

We tried erasing this empty line, but failed for some reasons. We were able to edit it by using vi, but wasn't able to save it.

5317   Mon Aug 29 12:05:32 2011 jamieUpdateCDSRe : fb down

fb was requiring manual fsck on it's disks because it was sensing filesystem errors.  The errors had to do with the filesystem timestamps being in the future.  It turned out that fb's system date was set to something in 2005.  I'm not sure what caused the date to be so off (motherboard battery problem?)  But I did determine after I got the system booting that the NTP client on fb was misconfigured and was therefore incapable of setting the system date.  It seems that it was configured to query a non-existent ntp server.  Why the hell it would have been set like this I have no idea.

In any event, I did a manual check on /dev/sdb1, which is the root disk, and postponed a check on /dev/sda1 (the RAID mounted at /frames) until I had the system booting.  /dev/sda1 is being checked now, since there are filesystems errors that need to be corrected, but it will probably take a couple of hours to complete.  Once the filesystems are clean I'll reboot fb and try to get everything up and running again.

5319   Mon Aug 29 18:16:10 2011 jamieUpdateCDSRe : fb down

fb is now up and running, although the /frames raid is still undergoing an fsck which is likely take another day.  Consequently there is no daqd and no frames are being written to disk.  It's running and providing the diskless root to the rest of the front end systems, so, so the rest of the IFO should be operational.

I burt restored the following (which I believe is everything that was rebooted), from Saturday night:

/opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1lscepics.snap /opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1susepics.snap /opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1iooepics.snap /opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1assepics.snap /opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1mcsepics.snap /opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1gcvepics.snap /opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1gfdepics.snap /opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1rfmepics.snap /opt/rtcds/caltech/c1/burt/autoburt/snapshots/2011/Aug/27/23:07/c1pemepics.snap 

16715   Tue Mar 8 19:29:36 2022 PacoUpdateBHDRe-balance of AS1

[Paco]

Installed AS1 in vacuum, near the center of the table, and installed the OSEMs. All OSEMS are "balanced" nominally, i.e. their shadow is at the halfway point optimum, but fine tuning is required, which I will attempt tomorrow after restoring the AS1 suspension screen settings. Today, I tried damping the SIDE DOF, but didn't succeed, although there was definitely some oscillating behaviour with high (> 5) gains on the damping, so I believe this is a matter of patience. For now, all OSEMs are looking ok, the SOS is in place, and hopefully it will soon be damped.

16716   Wed Mar 9 09:35:26 2022 PacoUpdateBHDRe-balance of AS1

[Paco]

AS1 is installed, OSEMs balanced, and the optic damped successfully. We should run the free swinging test overnight to validate this re-installation.

3798   Wed Oct 27 16:15:35 2010 SureshUpdateSUSRe-glued magnet to the PRM

Thanh and I re-glued the magnet to the PRM following the procedure outlined by Jenne

The PRM in the gluing fixture has been placed in the little foil house and left to cure for a day.

If all goes well the balancing the PRM will be done tomorrow.

11501   Wed Aug 12 22:33:36 2015 IgnacioUpdateIOORe-measured MC2 -> MCL TF

Since I will need to do transfer function measurements in order to implement FF for the arms and the MC2's yaw and pitch channels, I decided to practice this by replicating the transfer function measurement Eric did for MC2 to MCL. I followed his procedure and the data that I aquired for the TF looked as shown below,

About five minutes of data were taken (0.05 Hz resolution, 25 averages) by injecting noise from 1 to 100 Hz. The TF coherence looked as below,

Attachment 1: bode_TF.png
Attachment 2: Coherence.png
16678   Thu Feb 24 18:05:58 2022 YehonathanUpdateBHDRe-susspension of AS1

{Yehonathan, Anchal, Paco}

Yesterday, Anchal and Paco removed AS1 from the vacuum chamber and moved it into the cleanroom. The suspension wires were cut and the AS1 optic was put on the table.

Two things were noticed:

1. One of the wires was not sitting inside the side block groove (attachment 1)

2. One of the face magnets was grossly tilted (attachment 2). Probably due to uneven polishing of the dumbbell.

We put new wires into the side blocks making sure they sit in their grooves and we removed the tilted magnet. A different, more straight magnet was picked from the remaining spare magnets. The dumbbell and adapter were cleaned from glue residues and a batch of glue was prepared.

In the process of gluing a different magnet was knocked off. We cleaned that magnet too. The 2 magnets were glued on the adapter.

Today I came and saw that the gluing failed completely. One of the magnets was completely away from its socket and the other one wasn't glued at all.

I prepared a new batch of glue and glued the two magnets.

Attachment 1: signal-2022-02-24-173933_003.jpeg
Attachment 2: signal-2022-02-24-173933_002.jpeg
16694   Wed Mar 2 14:02:43 2022 YehonathanUpdateBHDRe-susspension of AS1

Yesterday, I rebuilt the OpLev setup in the cleanroom in order to suspend AS1. It took me a while to find all the necessary parts but I found them in the end.

The HeNe laser was placed on the optical table and turned on. The beam was aimed to bounce off a folding mirror to the SOS tower.

The beam's height was controlled by the HeNe laser stage and made to be 5+14/32". The beam from the folding mirror was made parallel to the table, first with an iris and then with the QPD connected to a scope.

Preparing the SOS tower for the suspension I noticed that the wire clamp is scratched on both sides from previous suspensions. I discarded that wire clamp but couldn't find the spares. Time ran out and I had to stop.

16698   Thu Mar 3 17:09:46 2022 PacoUpdateBHDRe-susspension of AS1

[Anchal, Paco]

Wire clamp spare was installed, furthermore AS1 was reinstalled on adapter, attached wire clamps, and cleaned using ionized air gun. Finally, we suspended it on the SOS tower and left it resting on the bottom earthquake stops; ready for balancing.

 Quote: Yesterday, I rebuilt the OpLev setup in the cleanroom in order to suspend AS1. It took me a while to find all the necessary parts but I found them in the end. The HeNe laser was placed on the optical table and turned on. The beam was aimed to bounce off a folding mirror to the SOS tower. The beam's height was controlled by the HeNe laser stage and made to be 5+14/32". The beam from the folding mirror was made parallel to the table, first with an iris and then with the QPD connected to a scope. Preparing the SOS tower for the suspension I noticed that the wire clamp is scratched on both sides from previous suspensions. I discarded that wire clamp but couldn't find the spares. Time ran out and I had to stop.

16710   Mon Mar 7 16:56:08 2022 YehonathanUpdateBHDRe-susspension of AS1

{Paco, Yehonathan}

We tried to roughly balance the adapter with two counterweights at the front, like with the other thin optics using an iris. As before, we couldn't get the beam above the iris hole no matter how much we inserted the counterweights into the adapter. We noticed that one of the side blocks is actually the one where the clearance for the wire was made on the wrong side. So there was clearance on both the up and bottom sides of the side block (see attachment 1).

Could this be the cause of the balancing issue? Running out of ideas on how to fix it we gave it a try and replaced it with a spare side block. We also found that the wire on the other side block was kinked so we replaced the wire on this one as well.

After inserting new wires into the side blocks, we hung the adapter on the winches and the beam was above the iris aperture! How could this tiny amount of missing mass make this much difference?

We were able to roughly balance the adapter.

We then tried to balance the roll of the adapter but accidentally knocked off the side magnet 😫.

We usually glue several side magnets together and they all together support the metallic plate on which the magnets are magnetically attached to. This time we had only one side magnet to glue so instead of trying to glue the magnet vertically we are trying to glue it horizontally using a flat surface and a stage to clamp it (attachments 2,3).

BTW, the HeNe was not working when we came into the cleanroom. We realized it was the old HeNe that we already determined to be broken but there was no sign on it. I attached a "BAD" sign on it and replaced it with the new HeNe. The OpLeve beam was realigned. All of this happened before all the things described above

Attachment 1: signal-2022-03-07-171520_001.png
Attachment 2: signal-2022-03-07-172659_001.jpeg
Attachment 3: signal-2022-03-07-172659_003.jpeg
16711   Mon Mar 7 18:53:16 2022 KojiUpdateBHDRe-susspension of AS1

Not sure if that small difference can cause the alignment inability. Particularly, the removed metal was just below the wire. This means that there is no misalignment effect at the first order.

Here is my idea:
You may be able to assist the alignment by adding washers on one side of the four holes to this "H" shaped parts. The holes are away from the center line, adding some weight definitely do some misalignment.

16714   Tue Mar 8 12:24:13 2022 YehonathanUpdateBHDRe-susspension of AS1

The gluing seemed to be successful. I assembled the side block with the magnet on the adapter. Paco helped me hang the adapter on the SOS tower.

The height and roll of the adapters were balanced (attachment 1,2).

The QPD was placed at the beam reflection. The beam was centered horizontally on the QPD and then measured vertically. The pitch DOF was balanced using the counterweights. The counterweight was locked. Balance was retained.

I tried to assemble the upper mirror clamp on the tower but for some reason, one of its tap holes was not able to accept screws. I gave it to Jordan for retapping. I measured the motion spectrum using the QPD connected to a scope (attachment 3).

Major peaks are at 668mHz, 942mHz, and 1029mHz.

Attachment 1: AS1_Roll_Balance.png
Attachment 2: AS1_Height_Balance.png
Attachment 3: FreeSwingingSpectra_new.pdf
3823   Fri Oct 29 14:06:12 2010 kiwamuUpdateGreen LockingRe: 80MHz VCO for green PLL : VCO calibration

P.S. There is a document about the 80MHz VCO box. This may be helpful.

link to LIGO DCC

14014   Mon Jun 25 19:14:02 2018 UditSummaryGeneralRe: A summary of the Tip-TIlt Mirror Holder design changes

2. Weighted screw rod at the bottom for tilting the mirror-holder:

The screw length selected here (2") is not interfering with any part of the assembly.

The 'weights' I have here are just thumb nuts from Mcmaster, so their weight is fixed (1.65g each, btw).

Problem I'd like to solve: Find an assortment of weighted, symmetric nuts with caps on one end to fix position on shaft.

3. Set-screws on both side of wire clamp to adjust its horizontal position:

Thanks for pointing out the mismatch in travel distance of protrusion and clamp screws. To match them, the clamp screw slot now sticks out of the profile (by 1.5mm). The range of the clamp motion is +/- 3 mm.

Also, here's a screenshot of the slot in the mirror holder:

--

- Excluding the weighted screw rod assembly, the height gap between assembly COM and wire release point is 3.1 mm.

 Quote: > 2. Weighted screw rod at the bottom for tilting the mirror-holder: Too long. The design of the holder should be check with the entire assembly. We should be able to make it compact if we heavier weights. How are these weights fixed on the shaft? Also can we have options for smaller weights for the case we don't need such a range? Note the mass of the weights. > 3. Set-screws on both side of wire clamp to adjust its horizontal position: How much is the range of the clamp motion limited by the slot for the side screws and the slot for the protrusion? Are they matched? Can you show us the design of the slot made on the mirror holder? >> Where is the center of mass (CoM) for the entire mirror holder assy and how much is the height gap between the CoM and the wire release points. Can you do this with 3/8" and 1/2" fused silica mirrors?

14015   Mon Jun 25 21:14:08 2018 KojiSummaryGeneralRe: A summary of the Tip-TIlt Mirror Holder design changes

3.
- Do we need this much of extended range of the clamp location? How much range will we need if we use either 3/8 or 1/4 inch mirrors?
- This slot on the mirror holder ring is not machinable.

About the CoM height
- Include the angle adjustment screw and adjust the wire releasing point to have comparable pitch resonant freq to the SOS suspension.

5251   Wed Aug 17 02:48:56 2011 kiwamuUpdateRF SystemRe: AM in the PM

[Keiko / Suresh / Anamaria / Kiwamu]

The AM components do exist also on the beam after the EOM.

The peaks were found at 11, 29 and 55 MHz, where the PM are supposed to be imposed.

Suresh and Keiko minimized them by rotating the HWP, which is in front of the EOM.

Also Anamaria and I tried minimizing them by adjusting the EOM crystal alignment.

However everytime after we minimized the AM peaks, they grew back in a time scale of ~ 1 min.

Potentially it could be a problem of the HWP and/or EOM alignment.

Since we wanted to proceed the in-vac work anyways, we stopped investigating it and decided to postpone it for tomorrow.

We again adjusted the incident power to 20 mW.

-- P.S.

The incident power going to MC went down to 7 mW for some reasons. This was found after ~ 6 hours from our works on the PSL table.

We haven't touched anything on the PSL table since the daytime work.

Possibly the angle of the HWP is drifting (why?) and changed the amount of the P-polarizing beam power.

Suresh locked the angles of two HWPs, which are the one just after the EOM and the one after the attenuation PBS.

 Quote from #5249 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.

5285   Tue Aug 23 09:40:37 2011 kiwamuUpdateGeneralRe: AS clipping fixed

Indeed it was suspenseful.

We tried finding where the clipping happened, but we couldn't find any obvious clippings.

So we checked centering of the beams on all the optics associated with the AS path, starting from BS, SR3,... to the AS optical bench.

And during the work some of them were recentered.

At the end we found no clipping. To make sure we tested the available range (no clipping range) by exciting the angular motion of BS with AWG (f ~ 1Hz, a ~ 1000).

The beam looked successfully coming out at the most of the angular oscillation point.

 Quote from #5284 Where was the AS clipping?! Ah, the suspense...

619   Tue Jul 1 21:54:05 2008 KojiUpdateGeneralRe: Abs. Length Meas. setup
I tried to look for the beating in the signal from the PD but I couldn't find. I had the temperature of the laser initially set to 40deg and then slowly increased by one degree. The manual of the laser says the frequency should change by several GHz. The problem is then that our PD is limited to no more than 30Mhz.

Although the two beams seem to overlap quite well, we might still need a better matching of the injected beam.

Alberto

Quote:
o The position of the iris was adjusted so as not to disturub the beam for OMCR CCD.

o The RF spectrum analyzer was returned to the place of the network analyzer.

 Quote: In the process of making this report, I noticed that one of the iris apertures is about disturbing the beam for OMCR CCD. I will check this before I go to Hanford. Also an RF spectrum analyzer is at the AP table. I try to return this near the PSL on Monday morning.
5652   Tue Oct 11 19:11:25 2011 kiwamuUpdateLSCRe: BS actuator reponse at low frequency : measured

I think the precision due to the loop gain uncertainty is something like 0.1% at 0.1 Hz. It's not the issue.

The real issue was the loud motion of MICH, which degrades the coherence of the measurement.

Also last night I tried the fringe hopping technique and gave it up for several reasons.

(uncertainty due to the loop gain)

When MICH is locked, the signal at C1:LSC-MICH_OUT can be expressed in frequency domain by

MICH_OUT = G / (1+G) * (1 / A) * X + G / (1+G) * (1 / H) * (1 / A) * S,                 [1]

where G is the open loop gain, A is the actuator response, H is the sensor transfer function (constant factor),
X is the natural (unsuppressed) motion of MICH and S is an excitation injected at C1:LSC-MICH_EXC.
When the natural motion of MICH X is smaller than the excited displacement S/H, dividing MICH_OUT by S gives

[Transfer function] = S / MICH_OUT
= (1+G) /G * H * A

At low frequency the open loop gain is always big, so that the transfer function can be approximated to

[Transfer function] ~ H *A

This approximation is valid with a precision of 1/G.
In my case yesterday, the open loop gain at 0.1Hz was about 103 or more than that, so the uncertainty due to the loop gain was 0.1% or even less.

(Effect from the MICH motion)

In the equation [1], it is shown that the MICH motion X shows up together with the excitation signal.
Actually this MICH motion term was not completely negligible and eventually this term disturbs the measurement resulting in a low coherence.
In order to get a high coherence in the measurement, X should be smaller than the excited displacement S/H,

X << S / H

This the reason why I had to inject a big excitation signal. Although the coherence around 1Hz turned out to be still low due to the loud natural motion in MICH.
The excitation was already close to 0.1 um level in terms of peak-to-peak displacement, and I wasn't able to increase it any more because the MICH signal would run into a nonlinear regime.
In the worst case I lost the lock due to a too much excitation.

(Fringe hopping technique)

Actually I tried and gave up this technique. That's why I did the in-loop measurement.
My feeling is that this technique is not suitable for the 40m.
What I tried was to flip the sign of the MICH control such that the fringe hops from the dark fringe to the neighbor bright fringe or vice versa.
Difference in the control signal (C1:LSC-MICH_OUT) was supposed to give us the amount of signal which drives the actuator by exactly quarter of the laser wave length.
However this technique turned out to be not good because
(1) BS actuator is too strong
=> expected difference in the control signal is quite small.
=> \lambda / 4 / A ~ 12 counts, where A is the actuator DC response of about 2.2e-8 [m/counts].
(2) MICH motion was too loud
=> I saw such a tiny 12 counts difference in the control signal, but once the hopping is done the control signal immediately fluctuated and it was really hard to precisely measure it.
=> It's simply because MICH was loud, and the actuator tried to suppress the motion and it resulted such an immediate signal fluctuation in the control signal

 Quote from #5649 This seems like an error prone method for DC responses due to the loop gain uncertainty. Better may be to use the fringe hopping method (c.f. Luca Matone) or the fringe counting method

ELOG V3.1.3-