40m QIL Cryo_Lab CTN SUS_Lab CAML OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 51 of 357  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  10835   Tue Dec 23 14:27:16 2014 ericqUpdateCDSChiara moved to UPS

 Steve and I switched chiara over to the UPS we bought for it, after ensuring the vacuum system was in a safe state. Everything went without a hitch. 

Also, Diego and I have been working on getting some of the new computers up and running. Zita (the striptool projecting machine) has been replaced. One think pad laptop is missing an HD and battery, but the other one is fine. Diego has been working on a dell laptop, too. I was having problems editing the MAC address rules on the martian wifi router, but the working thinkpad's MAC was already listed. 

  10836   Tue Dec 23 14:30:11 2014 ericqUpdateCDSChiara moved to UPS

Quote:

 Steve and I switched chiara over to the UPS we bought for it, after ensuring the vacuum system was in a safe state. Everything went without a hitch. 

Also, Diego and I have been working on getting some of the new computers up and running. Zita (the striptool projecting machine) has been replaced. One think pad laptop is missing an HD and battery, but the other one is fine. Diego has been working on a dell laptop, too. I was having problems editing the MAC address rules on the martian wifi router, but the working thinkpad's MAC was already listed. 

 Turns out that, as the martian wifi router is quite old, it doesn't like Chrome; using Firefox worked like a charm and now also giada (the Dell laptop) is on 40MARS.

  13977   Sun Jun 17 14:20:35 2018 KojiUpdateGeneralChiara new USB 4TB DIsk

I have connected a 4TB disk to chiara via a USB-SATA adapter. This disk has been recognized as /dev/sde. A GUID Partition Table (GPT), not MBR was made with gdisk to make a partition with the size beyond 2TB.
I tried to use "dd" to copy /home/cds (/dev/sdb1) to /dev/sde1, but failed. The copy was done (taking ~12h) and the partition was not recognized as a complete filesystem.

So I decided to use rsync instead.

sudo mkfs -t ext4 /dev/sde1
sudo mkdir /media/usb4g
sudo mount -t ext4 -o rw /dev/sde1 /media/usb4g
sudo rsync -a --progress /home/cds/ /media/usb4g

Progress
14:33 Copied     33G/1831G
14:38 Copied     36G/1831G
17:02 Copied   365G/1831G (~2.2GB/min)
01:18 Copied 1449G/1831G (~2.2GB/min)
04:36 Completed
> sent 1907955222607 bytes  received 126124609 bytes  37010956.31 bytes/sec
> total size is 1907271994803  speedup is 1.00

  13980   Mon Jun 18 12:07:03 2018 KojiUpdateGeneralChiara new USB 4TB DIsk

The initial local backup with rsync was done. Now the new 4TB disk is (supposed to be) automatically mounted at boot as /media/40mBackup so that we can run the daily backup on this disk. (<- This was confirmed by "sudomount -a")

controls@chiara|~> sudo blkid
...
/dev/sde1: UUID="92dc7073-bf4d-4c58-8052-63129ff5755b" TYPE="ext4"

controls@chiara|~> cat /etc/fstab

...

UUID=92dc7073-bf4d-4c58-8052-63129ff5755b   /media/40mBackup    ext4    defaults    0   0

Here I've used UUID rather than the device name "/dev/sde1" because the device name can get altered depending on the order of the usb connection.

This new disk is just a bare HDD drive sitting on the top of the chassis. We eventually want to accommodate this disk in the chassis so that we can recover the function only with the modification of /etc/fstab.  We need to wait for a next chance to have chiara down. In fact, when we can isolate chiara, we want to use this disk as the main disk and install another 4TB disk as a backup.

  14360   Fri Dec 14 22:19:22 2018 KojiUpdateGeneralChiara new USB 4TB DIsk

Edit: It was not 4TB disk but 6TB disk in fact. (We actually ordered 4TB disk...)

I think the problem of the backup disk was the flaky power supply for the external drive.
I swapped the drive to a new HGST 4TB one, but it was neither recognized nor spun up with the external power supply we had. So I decided to put both the new and old drives in the PC chassis to power them up with the internal power supply. I tested the old disk via a USB-SATA cable. However, this disk was not recognized. I noticed that the disk was not HGST 4TB but Seagate 3TB. Is it possible? I thought it was 4TB... Did I miss something?

Once the new 4TB was connected to the USB-SATA, it was very smooth to get it mounted. Now the disk is mounted as /media/40mBackup as before. /etc/fstab was also modified with the new UUID. All the command logs are found here below.

Let's see how the morning backup goes. It would take a while to copy everything on the new disk. So it was actually very nice to set this disk up by Friday midnight.


controls@chiara|~> lsblk

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 465.8G  0 disk 
---- sda1   8:1    0 446.9G  0 part /
---- sda2   8:2    0     1K  0 part 
---- sda5   8:5    0  18.9G  0 part [SWAP]
sdb      8:16   0   1.8T  0 disk 
---- sdb1   8:17   0   1.8T  0 part 
sdc      8:32   0   3.7T  0 disk 
---- sdc1   8:33   0   3.7T  0 part /home/cds
sr0     11:0    1  1024M  0 rom  
sdd      8:64   0   5.5T  0 disk 

controls@chiara|~> sudo mkfs -t ext4 /dev/sdd1

mke2fs 1.42 (29-Nov-2011)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
183144448 inodes, 1465130385 blocks
73256519 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
44713 block groups
32768 blocks per group, 32768 fragments per group
4096 inodes per group
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
    102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done      

controls@chiara|~> blkid

/dev/sda1: UUID="972db769-4020-4b74-b943-9b868c26043a" TYPE="ext4" 
/dev/sda5: UUID="a3f5d977-72d7-47c9-a059-38633d16413e" TYPE="swap" 
/dev/sdc1: UUID="92dc7073-bf4d-4c58-8052-63129ff5755b" TYPE="ext4" 
/dev/sdd1: UUID="1843f813-872b-44ff-9a4e-38b77976e8dc" TYPE="ext4" 

controls@chiara|~> sudo emacs -nw /etc/fstab
controls@chiara|~> cat /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda1 during installation
UUID=972db769-4020-4b74-b943-9b868c26043a /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=a3f5d977-72d7-47c9-a059-38633d16413e none            swap    sw              0       0
#UUID="90a5c98a-22fb-4685-9c17-77ed07a5e000"    /media/40mBackup       ext4      defaults,relatime,commit=60       0         0
UUID="1843f813-872b-44ff-9a4e-38b77976e8dc"    /media/40mBackup       ext4      defaults,relatime,commit=60       0         0

#fb:/frames      /frames nfs     ro,bg


UUID=92dc7073-bf4d-4c58-8052-63129ff5755b   /home/cds    ext4    defaults,relatime,commit=60    0   0

controls@chiara|~> sudo mount -a
controls@chiara|~> df

Filesystem      1K-blocks       Used  Available Use% Mounted on
/dev/sda1       461229088   10694700  427105320   3% /
udev             15915020         12   15915008   1% /dev
tmpfs             3185412        868    3184544   1% /run
none                 5120          0       5120   0% /run/lock
none             15927044        484   15926560   1% /run/shm
/dev/sdc1      3845709644 1809568856 1840789912  50% /home/cds
/dev/sdd1      5814346836     190408 5521130352   1% /media/40mBackup
  14361   Sat Dec 15 18:29:53 2018 KojiUpdateGeneralChiara new USB 4TB DIsk

The local backup was done at 18:18 after 11h18m of running.

2018-12-15 07:00:01,699 INFO       Updating backup image of /cvs/cds
2018-12-15 18:17:56,378 INFO       Backup rsync job ran successfully, transferred 5717707 files.

 

  10575   Tue Oct 7 10:09:07 2014 manasaUpdateGeneralChiara not responding

Chiara doesn't seem to be responding and I guess something happened 7 hrs ago.

I tried to hook up chiara to a monitor to reboot or atleast look for error messages; but it is not even detecting the external monitor (Tried changing monitors and vga cables; still see nothing).

I tried to ssh into it and only received errors :
NFS lookup failed for server XXX.XXX.XXX.XXX : error 5 (RPC: Timed out)
ssh: chiara: host/servname not known

Steve had the vacuum checked and everything seems fine with the status of the vacuum system atleast.

  10577   Tue Oct 7 16:19:50 2014 ericqUpdateGeneralChiara not responding

We're back! It was entirely my fault.

Some months ago I wrote a script that chiara calls every night, that rsyncs its hard drive to an external drive. With the power outage yesterday, the external drive didn't automatically mount, and thus chiara tried to rsync its disk to the mount point, which was at the time just a local folder, which made it go splat. 

I'm fixing the backup script to only run if the destination of the rsync job is not a local volume. 

  10578   Tue Oct 7 16:41:12 2014 JenneUpdateGeneralChiara not responding

I put a little script into ...../scripts/Admin that will check the fullness of Chiara's disk.  We only have the mailx program installed on Nodus, so for now it runs on Nodus and sends and email when the chiara disk that nodus mounts is more than 97% full.

  3438   Wed Aug 18 20:54:23 2010 rana, yoichiConfigurationEnvironmentChiller's chiller turned off

WE programmed the MOPA chiller's AC unit to turn off at 6PM each day and automatically turn on at 7 AM each morning. Its now very quiet in the control room at night.

Next, we'll leave it off during the day and see if it makes Steve go crazy or not.

  2096   Thu Oct 15 02:41:04 2009 ranaUpdateCOCChoice of folding mirrors in the RC cavities

In addition to the main mirrors (PRM, SRM) we will also have fold mirrors (called PR1, PR2, SR1, SR2). I am curious to see if we can get away with just using commercial optics; I think that the CVI Y1S coatings may do the trick.

Picture_9.png

The above plots show the reflectivities v. wavelength. I've asked the sales rep to give us specs on the reflectivity v. angle. I bet that we can guess what the answer will be from these plots.

  8966   Mon Aug 5 18:18:32 2013 gautamUpdateCDSChoosing LO Amplitudes and Frequencies

In order to decide what frequencies to dither the 4 degrees of freedom (M1-pitch&yaw, M2-pitch&yaw) at, I took the power spectrum of the X and Y-arm green transmission (C1:ALS-TRX_OUT, C1:ALS-TRY_OUT). Plots showing the power spectra are attached. Looking at the power spectra, I would think that for the X-arm, it would be okay to dither at 40, 50, 60 and 70 Hz. In order to check if the piezos could respond to these frequencies, I used my QPD setup and shook the PZTs with a 100Hz, 1Vpp sinusoid, and saw that the spot moved smoothly on the QPD.


 As for choosing the modulation amplitude, I did a simplistic approximation assuming that the misalignment only rotates the beam axis relative to the cavity axis, and determined what angle coupled 10% of the power into the next eigenmode. Assuming that this is small enough such that if we are already locked to TEM00, the dither won't kick it up to some higher-order mode, the LO amplitude should be in the range of 30-60 digital counts (determined using the PZT calibration constants determined here. This corresponds to a sine-wave of ~50mV amplitude reaching the PZTs (after HV amplification). I am not sure if this is too small, but according to the PZT datasheet, these platforms are supposed to have a resolution of 0.02 urad, which would correspond to the input signal changing by ~0.1 mV, so this signal should be capable of dithering the tip-tilt. 


 I have already added band-pass filters centered at these frequencies to the model (with a passband of 5Hz, 2Hz on either side), and low-pass filters to pull out the DC component of the output of the lock-in amplifiers. It remains to tune the gains of the filter stages. These parameters (frequency, amplitude of the LOs) may also have to be changed after tests). Hopefully the PZTs can be plugged in tomorrow, and I can try and make a measurement of the output matrix. 

Koji also suggested that it may be good to have a path in the model that feeds back to the PZTs by dithering the cavity mirrors as opposed to the PZT mounted mirrors. I will work on incorporating this into the SIMULINK model (c1asx.mdl) and also into the master medm screen.


 

Notes:

  1. The spot size of the X-arm green transmission on the PD was larger than the active surface. I moved the GTRX PD a little back and put in a lens (KPX085, 62.9mm FL, AR.14) in front of the PD, such that the spot is now occupying about 1/4th of the active surface area. The lens was mounted in a Thorlabs LMR1mount, and has been labelled.
  2. I made a slight change to the SIMULINK model, so as to calibrate the PZT sliders to (approximately) volts (I added a multiplier block that multiplies the slider value by constant value 3267.8). The idea is that we can approximately relate the slider value to tilt, knowing the calibration constant in mrad/V for the PZTs.

 

Power Spectra of Arm Green Transmission:

GTR_Power_Spectrum.pdf

  8968   Mon Aug 5 19:10:01 2013 KojiUpdateCDSChoosing LO Amplitudes and Frequencies

- I suppose the green transmission paths were thoroughly inspected and aligned in prior to the measurement

- Of course it is a BAD idea to use 60Hz as the LO frequency.

- Power spectra should be plotted as "RIN (relative intensity noise)" as the DC of 1 and 100 gives you 100 times different power spectra for the same beam.
  Don't forget to subtract the offset from your DC values.

  8972   Tue Aug 6 16:36:51 2013 gautamUpdateCDSChoosing LO Amplitudes and Frequencies-revised

I redid the power spectrum measurement for the X-arm green transmission after aligning the arm to green using the ITMX/ETMX Pitch and Yaw sliders on IFOalign.

The Y-axis now reflects the relative intensity noise (RIN), which I obtained by taking the average value of the X-arm green transmission using tdsavg. Based on this measurement, I have now picked four new frequencies at which to try and modulate the PZT mirrors: 10, 19, 34 and 39 Hz. Bandpass filters in the LIA stage have been appropriately modified. 

Power Spectrum:

powerSpec0806.pdf

  9229   Thu Oct 10 08:25:07 2013 SteveUpdatesafetyChris received safety training

Chris Couste, our new undergrad help received 40m specific, basic safety training yesterday.

  10329   Mon Aug 4 17:30:00 2014 ericqUpdateGeneralChronic Suspension Problems

TRX and TRY communication were recovered by doing a simultaneous reboot of all of the frontends.

Working with the interferometer has been extremely frustrating today. Having transmission values let us lock and ASS, but that has been less helpful than you would hope.

Saving the ASS offsets has repeatedly resulted in an overall bad change in alignment, moving the TTs and other things off randomly.

ITMX continues to be kicked. ITMY intermittently wanders away. It has not been possible to maintain IFO alignment for a reasonable length of time.

Also, the wall IOO striptool shows the MC2 Trans QPD Yaw having large step-function features. The MC is having an ok duty cycle, but this just may mean that the WFS are able to absorb what is happening to the MC suspensions.

The suspensions are really misbehaving. We need to get to the bottom of this, or else we are going to keep losing time to alignment.

  10330   Mon Aug 4 18:25:46 2014 JenneUpdateGeneralChronic Suspension Problems

Q is working on fixing the "save offsets" script for the ASS, because that has lost me my alignment two more times in the last few hours.  But, right now I have both arms locked with transmitted powers of about 0.9!  To get this, I ran the ASS scripts, and hand-tweaked the bias sliders of some of the optics to relieve the ASS outputs.  Then I turned the ASS gain to zero, and by-hand turned off the oscillators.  So, the ASS outputs are just frozen. 

I haven't seen IMTX suspension kicks, I think since Q did the front end reboot earlier. There has been ITMY activity, however. I think I'm going to be bold, and try locking ALS.

  17389   Tue Jan 10 15:07:33 2023 JCUpdateGeneralClean Large Optical Table

I have been working on cleaning the large optical table next to the PSL table. I have placed the known optics along in the optical cabinets Section Y5. Post and pillars have been placed in a cabinet along X-Arm. (I will work on gathering optics and optical hardware into a single area in the future, having them separated is only temporary.) I found some optics that were chipped and/or unlabeled. These have been placed in a box. 

There were cables coming into this table from the wire rack above, I plan on removing this. If there are any issues with me doing this, please message me. 

My main purpose for cleaning this is to potentially have an open area to place OMC for the next vent. We can also move the PD Testing table here. 

Attachment 1: IMG_6465.JPG
IMG_6465.JPG
  14824   Fri Aug 2 16:46:09 2019 KruthiUpdateCamerasClean up

I've put the analog camera back and disconnected the 151 unit GigE. But I ran out of time and wasn't able to replace the beamsplitter. I've put all the equipments back to the place where I took them from. The chopper and beam dump mount, that Koji had got me for the scatterometer, are kept outside, on the table I was working on earlier, in the control room. The camera lenses, additional GigEs, wedge beamsplitter, 1050nm LED and all related equipments are kept in the GigE box. This box was put back into CCD cameras' cabinet near the X arm.

Note: To clean stuff up, I had entered the lab around 9.30pm on Monday. This might have affected Yehonathan's loss measurement readings (until then around 57 readings had been recorded).

Sorry for the late update.

  5451   Sun Sep 18 16:42:00 2011 KojiBureaucracyEnvironmentClean up your mess

Mess in the lab is increasing. Kiwamu and I had to clean up some stuffs to continue our work.
(i.e. some components were disturbing to open the lid of the tables.)

Basically the tools/equipments/component/cables/digital cameras/lens caps/IR viewers
you have used for the day should be cleaned up at the end of the day.

If one likes to leave a temporary stuff, leave a note to indicate by whom, for what, how long
it will be kept like that, and when one is going to back there with contact info like the cell phone #.

  3953   Fri Nov 19 04:23:12 2010 SureshUpdateSUSCleaned and stuck magnets to dumbbells

To clean the glue off the magnets and dumbbells I soaked them in Acetone for about an hour and then scrubbed the ends clean with a lint free tissue soaked in Acetone. 

I then examined the ends under a microscope and found that while the flat faces were clean some of the grooves were still filled with glue.

 

Top Bottom

dumbells_before_ultrasonic_bath_2.jpg

dumbells_before_Ultrasonic_wash_1.jpg
 magnets_after_scrub.jpg magnets_after_scrub.jpg


While examining the magnets I found some small magnetic fibers stuck to the magnets.  Rana had mentioned these before as potential trouble makers which could degrade the high frequency performance of the OSEMs.

 Magnetic_Hair.jpg

 

To try and get the glue out of the grooves I put the dumbells through an ultrasonic bath for ten mins.  Most of the glue has been removed from the grooves.  Pics below

 

dumbells_after_ultrasonic_wash_1.jpg

dumbells_after_ultrasonic_wash_2.jpg

 

I proceeded try and recover the lost time by sticking the magnets back to the dumbbells.  Increased the quantity of the glue to a slightly larger amount than usual.  It should definitely squish out a bit now.  We will know tomorrow when we open the gluing fixture.

 

 

 

  9833   Sun Apr 20 18:15:37 2014 ericqUpdateIOOCleaner Cleanup

Came in, and the PMC and MC needed aligning. 

PMC Trans .74->.83

I wasn't able to move the MC1&3 the right way in pitch without having a terrible MC2 position... using the move MC2 scripts to bring it back threw off the other spots.

  12089   Tue Apr 26 15:22:35 2016 SteveUpdateendtable upgradeCleaning ETMX vacuum dirty window

Gautom is progressing with the layout nicely. The X-arm transmission window have not seen cleaning for decades. This should be the time to do it. Here is picture of dirtiness.

It is not that simple... How much effort should we put in it? The hole table with 1W inno laser plus... set up now about ~500 lbs  We can pull it off carefully, but it is not risk free.

We should look at our other signal port windows! Gautom's long reach able him to do the first contact cleaning without moving anything. It is great!
 

Attachment 1: ETMX-Tvp.jpg
ETMX-Tvp.jpg
Attachment 2: ETMX-TvpDetail.jpg
ETMX-TvpDetail.jpg
  12094   Wed Apr 27 15:04:47 2016 SteveUpdateendtable upgradeCleaning ETMX vacuum dirty window

It looks very promising.

 

Attachment 1: 1cETMX-Tcmp.jpg
1cETMX-Tcmp.jpg
  12100   Fri Apr 29 16:05:23 2016 gautamUpdateendtable upgradeCleaning ETMX vacuum dirty window

After a second round of F.C. application, I think the window is clean enough and there are no residual F.C. pieces anywhere near the central parts of the window (indeed I think we got most of it off). So I am going to go ahead and install the Oplev. 

Quote:

It looks very promising.

 

 

Attachment 1: IMG_0755.JPG
IMG_0755.JPG
  3975   Tue Nov 23 11:20:30 2010 josephbUpdateCDSCleaning up old target directory

Winter Cleaning:

I cleaned up the /cvs/cds/caltech/target/ directory of all the random models we had built over the last year, in preparation for the move of the old /cvs/cds/caltech/target slow control machine code into the new /opt/rtcds/caltech/c1/target directories.

I basically deleted all the directories generated by the RCG code that were put there, including things like c1tst, c1tstepics, c1x00, c1x00epics, and so forth.  Pre-RCG era code was left untouched.

  8223   Mon Mar 4 18:11:10 2013 JamieUpdateSUSCleaning up suspension POS inputs

I did a little bit of cleanup of the suspension POS inputs today, both in model and MEDM land.

model

sus_single_control.mdl was simplified such that now there are just two position inputs:

  • POS: with LSC filter
  • ALTPOS: unfiltered

The regular LSC inputs go into POS, and any optic-specific extra pos inputs go into ALTPOS after being properly filtered and summed.

So for instance, MC2_MCL and MC2_ALS are filtered and summed then go into MC2 ALTPOS.  The ETM ALS inputs go into ALTPOS.

I modified the GLOBAL DAMPING outputs so that they are filtered in the GLOBAL block before being sent to be summed before going into ALTPOS for {I,E}TM{X,Y}.

All suspension models were rebuilt/installed/restarted.

MEDM

The SUS_SINGLE.adl template screen was modified such that the POS button now points to optic-specific POS filter screens at:

/opt/rtcds/caltech/c1/medm/master/sus/SUS_$(OPTIC)_POS.adl

For MC1, MC3, PRM, BS, SRM these are links to SUS_SINGLE_POS.adl.  The rest of the suspensions (MC2, {I,E}TM{X,Y}) now have custom screens that are variations of SUS_SINGLE_POS but with their extra filter screens added in.  For instance, here is the new SUS_ETMX_POS.adl:

SUS_ETMX_POS.png

This gets rid of all the white screen crap that was in here before.

All of this has been committed to the SVN.  NOTE: symlinks were heavily used when sorting this stuff out, so check for symlinks when modifying in the future.

  17689   Mon Jul 17 15:56:22 2023 JCUpdateGeneralCleanroom Assembly

I've made a cleanroom assembly in solidworks to create a list of all the components we will need when making this. Sadly, the 80/20 that we have in the cage area was taken already. I can't point fingers because the lock was removed due to it being an optional emergency exit way pointed out by Caltech Safety. Here is the 3D model of what the assembly looks like. Please let me know if you have any questions. 

 

I have not calculated the cost yet, but I will tomorrow. 

 

Attachment 1: Cleanroom_Assembly_Face_View.PNG
Cleanroom_Assembly_Face_View.PNG
Attachment 2: Cleanroom_Assembly_Top_View.PNG
Cleanroom_Assembly_Top_View.PNG
Attachment 3: Cleanroom_Assembly_ISO_View.PNG
Cleanroom_Assembly_ISO_View.PNG
  4443   Fri Mar 25 08:58:38 2011 AidanUpdateTreasureCleared stuff off SP table

I tidied up some of the stuff that was on the SP table. The ISS box that has been sitting on there for months is now underneath the X-arm on top of the spare Marconi which is stored there.

 

 

Attachment 1: ISS_box.JPG
ISS_box.JPG
  6968   Thu Jul 12 15:25:24 2012 JenneUpdateSUSClearing test points

Somehow we got an excitation going on BS OpLevs, and even though Yuta thought he might have accidentally started it, he couldn't find where, so we couldn't stop it.

Since we don't have anything written on the wiki, I ended up calling Joe to remind me how to clear test points:

controls@allegra:~ 0$ diag -l -z
diag> tp clear * *
test point cleared
diag> awg clear 21.*
reset succeeded

The tp clear clears all test points everywhere.  The awg clear wouldn't let me do a universal clear, so I just did #21, which is the SUS model.  So if you want to kill excitations on a specific model, you must find it's DCU ID (it's in the top right corner of the GDS status screens for each model). 

  12555   Wed Oct 12 22:51:26 2016 KojiUpdateGeneralClipping could not be improved by the PZTs - NEED ANOTHER VENT

[Gautam Koji]

We engaged the HV driver to the output port PZTs, hoping to mitigate the AS port clipping. Basically, the range of the PZT is not enough to make the beam look clean. Also, our observation suggested there are possible multiple clipping in the chamber. We need another vent to make the things clearly right. Eric came in the lab and preparing the IFO for it.


1. Before the test, the test masses have been aligned with the dither servo.

2. We looked at the beam shape on the AS camera with a single bounce beam. We confirmed that the beam is hard-clipped at the upper and left sides of the beam on the video display. This clipping is not happening outside of the chamber.

3. We brought an HV power supply to the short OMC rack. There is a power supply cable with two spades. The red and black wires are +150V and GND respectively.

4. The voltage of +/-10V was applied on each of the four PZT drive inputs. We found that the motion of the beam on the camera is tiny and in any case, we could not improve the beam shape.

5. We wondered that if we are observing ANY improvement of the clipping. For this purpose, we aligned AS110 sensor every time we gave the misalignment with the PZTs. Basically, we are at the alignment to have the best power we can get. We thought this was weird.

6. Then we moved the AS port spot with the ITMX. We could clearly make the spot more round. However, this reduced the power at the AS port reduced by ~15%. When the beam was further clipped, the power went down again. Basically, the initial alignment gave us the max power we could get. As the max power was given with the clipped beam, we get confused and feel safer to check the situation with the chambers open.

During this investigation, we moved the AS port opitcs and the AS camera. So they are not too precise reference of the alignment. The PZT HV setup has been removed.

  6690   Sat May 26 01:28:58 2012 KojiUpdateGeneralClipping improvement

The beam at the dark port was largely clipped.
The arm transmissions (TRX/TRY) were ~0.6 no matter how you try to align.

The PZT1/2 X was scanned and TRX/TRY are now both ~0.9.
This means that the beam was mostly clipped in or after the mode mathing optics.

FPMI contrast is (2.45-0.02)/(2.45+0.02) = 98%
Not so bad although it does not tell anything about clipping before the IFO.

In the next opportunity, we should try to "pin" the beam axis on the arm mirrors using A2L.

1. I am not sure exactly where the clipping was. It means that a small clipping might still be there.

2. I am afraid that the beam is still clipped in the faraday. The beam can be scanned using the steering on the PSL table.

 

Attachment 1: Untitled.png
Untitled.png
  4788   Mon Jun 6 17:22:09 2011 valeraConfigurationLSCClipping in the X arm 1064 um trans path

I changed optics in the ETMX transmon path to remove clipping (which made a false QPD signal).

During the weekend I found that there was an offset in X arm c1ass pitch servo, which derives the signal by demodulating the arm cavity power, coming from the beam clipping in the transmon path.

The clipping was on the pair of the 1" mirrors that steer the beam after the 2" lens (see attached picture). The beam is about 5-6 mm in diameter at this distance from the lens and was not well centered.

I moved the steering mirrors downstream by about 8" where the beam is about 2-3 mm (the attached picture shows the mirrors in the new location). The Y arm layout is different from X arm and I didn't find any obvious clipping in transmon path.

The max X arm buildup went up from 1.3 to 1.5. I changed the TRX gain from -0.003 to -0.002 to obtain the normalized X arm power of 1 in this state. The MC refl DC is 1.6 out of 4.9 V and the Y arm buildup is ~0.9 so the TRX(Y) gains will have to be adjusted once the MC visibility is maximized.

Attachment 1: XarmTransMon.pdf
XarmTransMon.pdf
  8965   Mon Aug 5 18:02:34 2013 manasaUpdateGeneralClose up list checked
  •  
  • Center beam on all AS optics
  • GET CAMERA IMAGES OF EVERYTHING

    • We must get images right before closing, right after closing, etc.
  • Make sure REFL is clear
    • dither PRM, see motion on AP tables
  • Make sure AS is clear
    • dither BS/ITM, see motion on AP tables
  • Using IPANG/POS pick-off mirrors, center beams on:
    • IPPOS
    • IPANG (aligned low in pitch)
  • Check green alignment in the arms and make sure the transmitted green reaches the PSL table.
  • Check all OpLevs centered, in and out of vacuum

    [Jenne, Manasa]

    IPANG needed to be re-aligned today. Heavy doors are in place and bolts tight (torque 25 & 45).

    Steve! We are ready for pump down!

    I will check the IFO alignment once again early tomorrow morning before Steve starts pumping down.

     

     

     

     

     

  10512   Wed Sep 17 01:40:55 2014 JenneUpdateLSCCloser to REFL DC? Maybe?

I tried a bunch of times to reduce my CARM offset so I could jump to REFLDC digitally, but I think I'm maybe being a little ambitious with the arm power I'm trying to get to.

I have modified the carm_cm_up script so that it does my new procedure.  Everything is the same through locking the PRCL and MICH on 3f.  Then it reduces the CARM offset to 1.5 nm.  This is where we *used* to transition to sqrtInvTrans.  Now I have it going a bit farther to 0.5 nm, and arm powers of about 1 before doing that transition.  Also, before it transitions it lowers the CARM gain and engages the 1kHz lowpass in FM9.  A gain of about 4 is fine to keep the gain peaking in the CARM loop to only about 10dB, and sets a UGF of 100Hz which is the peak of the phase bubble with the lowpass engaged. 

Once I got to this point (several times tonight), I turned on CARM and DARM oscillations and looked at the transfer functions between (CARM and REFLDC) and (DARM and AS55Q). I have 2 DTT templates setup for this, in /users/Templates/PRFPMI.  These templates assume that you have your new DARM signal (AS55) going to SRCL_IN1 and your new CARM signal (REFLDC, which is actually REFL11I coming through the CM board) going to MC_IN1. 

I'm not sure why I'm losing lock. I don't see anything terribly telling on the time series plots, in particular none of the loops look like they are oscillating.  Here is one of the better examples from this evening:

Zoom_TRXTRYupto25_1094967592.png

Other notes:

* I realigned the Xgreen on the PSL table (again) to maximize the beatnote amplitude.  Y was fine, but X was very poorly overlapped on the camera.

* I put the SR785 back by the LSC rack and plugged it into the CM board for transfer functions.  Didn't take any tonight.

* We have a small wishlist for scripting things:  (1) DRMI restore script should reset REFL11 to "normal" REFL11.  (2) CARM/DARM acquisition restore script should reset REFL11 to REFLDC.  (3) CARM/DARM acquisition restore should also set PRMI parameters (as Q noted last week).

  12749   Tue Jan 24 07:36:56 2017 Max IsiUpdateSummary PagesCluster maintenance
System-wide CIT LDAS cluster maintenance may cause disruptions to summary pages today. 
  12752   Wed Jan 25 09:00:39 2017 Max IsiUpdateSummary PagesCluster maintenance
LDAS has not recovered from maintenance causing the pages to remain unavailable until further notice.

> System-wide CIT LDAS cluster maintenance may cause disruptions to summary pages today. 
  12787   Thu Feb 2 11:25:45 2017 Max IsiUpdateSummary PagesCluster maintenance
FYI this issue has still not been solved, but the pages are working because I got the software running on an
alternative headnode (pcdev2). This may cause unexpected behavior (or not).

> LDAS has not recovered from maintenance causing the pages to remain unavailable until further notice.
> 
> > System-wide CIT LDAS cluster maintenance may cause disruptions to summary pages today. 
  15823   Fri Feb 19 15:17:51 2021 JordanUpdateSUSCoM Range on 3"->2" Adapter Ring for SOS

Adjusting the thickness of the cylindrical hole for the mirror on the 2" optic sleeve, from .6875" to .61" thick, moves the CoM to 0.0003" out of plane from the suspension wire. This is with the dumbell at its neutral point.

How close to zero do we need this to be? More fine tuning of that thickness can get it to zero, but this would require much tighter machining tolerance on that hole depth.

Moving the dumbell towards the back of the SOS assembly (noted as negative direction, with origin at the plane formed by the wires), moves the CoM to -0.002" from the plane.

Moving the dumbell towards the front of the SoS assmebly (positive direction wrt the plane formed by the suspension wire), moves the CoM to +0.0022" from the plane.

So the total adjustment range with the dumbell is -0.002"to 0.0022", with the plane formed by the wires as the origin.

See Attachments

Attachment 1: Neutral_Point.png
Neutral_Point.png
Attachment 2: Dumbell_Max_Negative_Travel.png
Dumbell_Max_Negative_Travel.png
Attachment 3: Dumbell_Max_Positive_Travel.png
Dumbell_Max_Positive_Travel.png
  15824   Fri Feb 19 16:06:01 2021 KojiUpdateSUSCoM Range on 3"->2" Adapter Ring for SOS

We want to move the CoM with the adjustment range so that the residual deviation is adjusted by the bottom dumbbell. 0.0003" is well within the range and good enough.

 

  15825   Fri Feb 19 16:14:16 2021 gautamUpdateSUSCoM Range on 3"->2" Adapter Ring for SOS

I briefly talked with Jordan about this. This suspension will have OSEMs right? With 400ohm series resistance for the coil drivers, we will have ~+/-20mrad actuation range. Of course we'd like to use as much of this for interferometry and not static pitch alignment correction (possibly even increase the series resistance to relax the dewhitening requirements). But what is the target adjustability range in mrad with the dumbell/screw config? My target in the linked elog is 500urad (not any systematic optimum, but will allow us to use most of the DAC range for interferometry). Are these numbers in inches commensurate with this 500urad?

On a related note - are there grooves for the wires to sit in on the side of the sleeve? We looked at the solidworks drawing, and noticed that the groove doesn't extend all the way to the top of the clamp. Also, the material of both the clamping piece and the piece onto which the wire is pressed onto is SS. Don't we want them to be Aluminium (or something softer than the wire) so that the wire makes a groove when the clamp is tightened?

Quote:

We want to move the CoM with the adjustment range so that the residual deviation is adjusted by the bottom dumbbell. 0.0003" is well within the range and good enough.

  15826   Fri Feb 19 16:55:26 2021 KojiUpdateSUSCoM Range on 3"->2" Adapter Ring for SOS

Jordan's screenshot actually shows that the vertical distance (Y) is 0.0000". We want to have the vertical distance of CoM from the wire clamping point to be 0.9mm in the nominal SOS design (this might need to be adjusted to have a similar pitch resonant freq for the different inertia of moment). Let's say it is ~mm ish.

The full range of the bottom dumbbell adjustment gives us the CoM adjustment range of +/-0.002” = +/-50um. This corresponds to an alignment range of +/-50mrad. And we want to set it within +/-500urad.
So we need to adjust the dumbbell position with the precision of 1/100 of the full range (precision of 0.5um).

The groove does not extend to the top of the clamp. The groove shallower than the wire diameter cause the hysteresis of the alignment. Also, the material of the pieces should be stainless steel. Al clamp is softer than the wire and will cause the groove to be dug on the material, causing increased bending friction and hysteresis again.

Saying, all of our suspended masses with Al stand-offs are suffering this issue to some extent. That was the reason to buy the ruby standoffs.

  15806   Fri Feb 12 15:03:48 2021 JordanUpdateSUSCoM on 3"->2" Adapter Ring for SOS

As it currently stands the Center of Mass of the Adapter Ring/Optic assembly is 0.0175" out of the plane formed by the suspension wire. See Attachments. The side plate, along with the EQ stops are hidden to show the CoM and the plane.

Note: The changes discussed in the meeting with Calum have not been added and are a work in progress. These changes include:

- Adding a 45 deg chamfer to the both parallel faces of the adapter ring. This along with a modified bracket for the EQ stops will allow for easier adjustment of the screws. 

- Potentially changing material of adapter ring to stainless stell to more accurately emulate the mass of a 3" optic.

- Different adjustment mechanism of the "dumbell" at bottom of adapter ring to something similar to the VOPO suspension (will need to consult Calum further)

Attachment 1: Screenshot_(1).png
Screenshot_(1).png
Attachment 2: Screenshot_(3).png
Screenshot_(3).png
Attachment 3: CoM.PNG
CoM.PNG
  15813   Wed Feb 17 13:59:43 2021 KojiUpdateSUSCoM on 3"->2" Adapter Ring for SOS

Note from today's meeting:

1. Can we adjust the thickness of the cylindrical hole for the mirror to move the COM in the plane of the wires. (We should be able to do that)

and

2. Please check how much we can displace the COM by the bottom dumbbell.

  16004   Wed Apr 7 13:07:03 2021 JordanUpdateSUSCoM on 3"->2" Adapter Ring for SOS

Adding the chamfer around the edge of the optic ring did not change the center of mass relative to the plane from the suspension wires.

The CoM was .0003" away from the plane. Adding the chamfer moved it closer by .0001". See the attached photo.

I've also attached the list of the Moments of Inertia of the SOS Assembly.

Attachment 1: CoM_with_Chamfer.png
CoM_with_Chamfer.png
Attachment 2: Moments_of_Inertia.PNG
Moments_of_Inertia.PNG
  16165   Thu May 27 14:11:15 2021 JordanUpdateSUSCoM to Clamping Point Measurement for 3" Adapter Ring

The current vertical distance between the CoM and the wire clamping point on the 3" Ring assembly is 0.33mm. That is the CoM is .33 mm below the clamping point of the wire. I took the clamping point to be the top edge of the wire clamp piece. see the below attachments.

I am now modifying the dumbell mechanism at the bottom of the ring to move the CoM to the target distance of 1.1mm.

Attachment 1: CoM_to_Clamp.PNG
CoM_to_Clamp.PNG
Attachment 2: CoM_to_Clamp_2.PNG
CoM_to_Clamp_2.PNG
  16169   Tue Jun 1 14:26:23 2021 JordanUpdateSUSCoM to Clamping Point Measurement for 3" Adapter Ring

After changing the material of the Balance Mass from 6061 Al to 304 Steel, and changing the thickness to 0.21" from 0.25". The CoM is now 1.11mm below the clamping point.

Koji expected a mass change of ~ 4g to move the mass to 1.1mm. The 6061 mass weighed ~1.31g and the 304 mass weighs 4.1g.

A potential issue with this is the screw used the adjust the position of these balance masses, threads through both the aluminum ring and this now 304 steel mass. A non silver plated screw could cold weld at the mass, but a silver plated screw will gall in the aluminum threads.

Quote:

The current vertical distance between the CoM and the wire clamping point on the 3" Ring assembly is 0.33mm. That is the CoM is .33 mm below the clamping point of the wire. I took the clamping point to be the top edge of the wire clamp piece. see the below attachments.

I am now modifying the dumbell mechanism at the bottom of the ring to move the CoM to the target distance of 1.1mm.

 

Attachment 1: CoM_to_Clamp_Updated.PNG
CoM_to_Clamp_Updated.PNG
  16173   Wed Jun 2 01:08:57 2021 KojiUpdateSUSCoM to Clamping Point Measurement for 3" Adapter Ring

How about to use the non-Ag coated threaded shaft + the end SS masses with helicoils inserted? Does this save the masses to get stuck?

 

  8877   Thu Jul 18 23:34:40 2013 gautamConfigurationendtable upgradeCoarse adjustment of PZT axes orientation in mount

 I have managed to orient the PZT in the mount such that its axes are approximately aligned with the vertical and the horizontal. 

In the process, I discovered that the 4 screws on the back face of the PZT correspond to the location of the piezoelectric stacks beneath the tip-tilt platform. The PZT can therefore be oriented during the mounting process itself, before the mirror is glued onto the tip-tilt platform.

In order to verify that the pitch and yaw motion of the mirror have indeed been roughly decoupled, I centred the spot on the QPD, fed to the 'pitch' input of the PZT driver board (connected to channel 1 of the PZT) a 10 Vpp, 1 Hz sine wave from the SR function generator (having turned all the other relevant electronics, HV power supply etc ON. The oscilloscope trace of the output observed on the QPD is shown. The residual fluctuation in the Y-coordinate (blue trace) is I believe due to the tilt in the QPD, and also due to the fact that the PZT isnt perfectly oriented in the mount.

It looks like moving the tip-tilt through its full range of motion takes us outside the linear regime of the QPD calibration. I may have to rethink the calibration setup to keep the spot on the QPD in the linear range if the full range is to be calibrated, possibly decrease the distance between the mirror and the QPD. Also, in the current orientation, CH1 on the PZT controls YAW motion, while CH2 controls pitch.

Oscilloscope Trace:

Yellow: X-coordinate

Blue: Y-coordinate

PZT_out_waveform.jpg

  14444   Fri Feb 8 20:35:57 2019 gautamSummaryTip-TIltCoating spec

[Attachment #1]: Computed spectral power transmissivity (according to my model) for the coating design at a few angles of incidence. Behavior lines up well with what FNO measured, although I get a transmission that is slightly lower than measured at 45 degrees. I suspect this is because of slight changes in the dispersion relation assumed and what was used for the coating in reality.

[Attachment #2]: Similar information as Attachment #1, but with the angle of incidence as the independent parameter in a continuous sweep. 

Conclusion: The coating behaves in a way that is in reasonable agreement with our model. At 41.1 degrees, which is what the PR3 angle of incidence will be, T<50 ppm, which was what we specified. The larger range of angles was included because originally, we thought of using this optic as a substitute for SR3 as well. But I claim that for the shorter SRC (signal recycling as opposed to RSE), we will not end up using the new optic, but rather go for the G&H mirror. In any case, as Koji pointed out, ~50 ppm extra loss in the RC will not severely limit the recycling gain. Such large variation was not seen in the MC analysis because we only varied the angle of incidence by +/- 0.5 degrees about the nominal design value of 41.1 degrees.

Attachment 1: specRefl.pdf
specRefl.pdf
Attachment 2: AoIscan.pdf
AoIscan.pdf
ELOG V3.1.3-