Jim and Dave,
WP4803. We used h1ioppemmx model to check the cdsEzCaRead part was operating correctly with the latest RCG version. I was going to add readbacks for the cdsEzCaRead part used in lieu of a local IRIG-B timing source, but we decided against that at this moment in time as the DAQ would have required a restart.
The tests were successful, there is no problem with EzCaRead. Code was reverted to original at the conclusion of the test.
The x1work computer has been rebuilt, it is running Ubuntu 12.04 workstation. The test stand should be functional at this point. It's highly likely that some packages needed are not installed on x1work, send me an email and I'll get it installed for you. The Remote Host Identification has changed for x1work, so it will complain when you log in.
The Comtrol unit for the Mid-Y weather station appears to have failed during the power recovery. Link lights are dim and flashing rapidly. Power cycling did not help. Troubleshooting is ongoing, but for now, the weather station at Mid-Y is offline.
Dave Barker, myself. The fiber to the timing slave on h1susauxex I/O chassis does not latch into the SFP, and one fiber from the pair was not fully inserted into the SFP. This caused the timing to be off by quite a bit. The diagnostics for the timing fanout showed that nothing was connected to the port. While we were troubleshooting, we found that only one of the fibers latches into the SFP at the timing fanout. The latching tabs on the fiber may be bad, a new fiber should be tried to see if it latches any better. For now, they are just pushed in and held by some nominal amount of friction, but this is not a permanent fix. At some point it would be useful to audit the other timing fibers, but if one is loose, it will cause problems with the models when it becomes detached from the SFP.
On Wednesday before shutting down Hanford for today's power cut, I managed to do another measurment this time with the wire for the LL quadrant going through the ESD LP filter box instead of BIAS as it should have been. To be clear, this is the old configuration and we wanted to see the effects this cable configuration has on the charging measurements.
I have attached here the measurement documentation and the Veff plots for pitch and yaw which also include the measurement one day before for comparison.
The current measurement took place between UTC (2014-08-13 21:48:00) and UTC (2014-08-13 23:00:00), while the previous one took place between UTC (2014-08-12 17:17:00) and UTC (2014-08-12 19:09:00), the ESD LL quadrant wire swap too place at about UTC 2014-08-12 20:00:00. Notice that a couple of hours after the cable swap there was a power glitch which shutted down the ESD power supply so the ESD was not charged until the current measurements took place. This is something to take into acount, between the measurements compared in the plots and in the table below the ESD was off. I have verified that the ion pump, the iluminators and the cold cathode were on during this time (see plot below). Because looking at the Veff values in the table we see that after the cable swap the charge values did not change much, with the only exception of the quadrant that had a charge of opposite sign to the rest. This charge reversed once again to common sign to the other quadrants.
|
UL after23 |
UL after24 |
UR after23 |
UR after24 |
LR after23 |
LR after24 |
Veff PITCH [V] |
228 |
226 |
-169 |
-11 |
153 |
164 |
PITCH slope [10-7 µrad/V] |
-2.606 |
-2.6014 |
2.305 |
2.2564 |
-2.635 |
-2.6454 |
Veff YAW [V] |
320 |
305 |
-11 |
33 |
227 |
201 |
YAW slope [10-7 µrad/V] |
-2.226 |
-2.2153 |
2.489 |
2.4904 |
2.308 |
2.3825 |
The IOC for the MetOne 227b dust monitors was accidentally running. I stopped this one and started the one that Jim B. wrote for the new MetOne dust monitors.
(John W, Daniel S, Keita K)
The viewport on the HAM5/6 septum was rotated by 120 degree clockwise. Torqued to 16 lbs.foot as per the spec. We didn't have to use a new O-ring as the old one was intact.
Corner Station - we are currently vented. OpLev - Doug and Jason doing work at End-X (waiting on CDS to begin ) Also, the mitigation of equipment damage was brought up End-Y - Borja may me taking more measurements using higher resolution. HEPI currently NOT running. IRIG-B not running cleanly after power restored End-X - Krishna will be connecting the tilt-meter to the LIGO DAQ B&K Hammering will be taking place at end stations. Still unclear as to where it will start.
Late entry for Wednesday's restarts
model restarts logged for Wed 13/Aug/2014
2014_08_13 00:39 h1fw1
2014_08_13 01:39 h1fw1
2014_08_13 09:29 h1fw1
2014_08_13 10:48 h1nds1
2014_08_13 10:57 h1nds1
2014_08_13 13:15 h1iopoaf0
2014_08_13 13:15 h1oaf
2014_08_13 13:15 h1odcmaster
2014_08_13 13:15 h1pemcs
2014_08_13 13:15 h1tcscs
2014_08_13 13:24 h1iopoaf0
2014_08_13 13:24 h1oaf
2014_08_13 13:24 h1odcmaster
2014_08_13 13:24 h1pemcs
2014_08_13 13:24 h1tcscs
2014_08_13 18:31 h1ioppsl0
2014_08_13 18:31 h1pslfss
2014_08_13 18:31 h1pslpmc
2014_08_13 18:33 h1psldbb
unexpected restarts of h1fw1. Some DAQ min trend work required nds restarts. Stuck PEM ADC channels required h1oaf0 restarts (residual from Tue power glitch). PSL restart part of power outage shutdown prep.
Power outage day. All CDS computers were restarted. The total number of restarts is 138. Full log in attached text file. No unexpected restarts.
In /ligo/cds/lho/h1/burt/2014/08/13/08:10 I ran: burtwb -f h1ecatx1plc1epics.snap burtwb -f h1ecatx1plc2epics.snap burtwb -f h1ecatx1plc3epics.snap burtwb -f h1ecaty1plc1epics.snap burtwb -f h1ecaty1plc2epics.snap burtwb -f h1ecaty1plc3epics.snap
Jeff K., Krishna V. I analyzed the data from the T240 (labeled as STS atm) on the ground (about ~ 1 m away) and have attached three plots. To make them I used 7k seconds of tiltmeter and T240 data from Tuesday night, roughly between 9:10 PM to 11:10 PM. I resampled both data sets to 1 Hz to get them on the same time base. Then I compared the phase of the T240 signal (converted to acceleration) against the tiltmeter signal in 10-100 mHz range and time shifted them until the phase lined up, as shown in the second figure. I've also shown the residual, obtained by subtracting the time series of the two signals. We are limited by being on different clocks and DAQs, but even so, the coherence is decent. Just as I saw in our lab at UW, there is good coherence when both see tilt and very little coherence when the seismometer is seeing horizontal displacement while the tiltmeter still sees tilt. Edit: I've attached the data in the format: columns [time T240*w^2/g tiltmeter]
During the power outage yesterday, verified CPS units for BSC1, BSC2, and BSC3 had modifications per E1300251. This was to address a high frequency oscillation in the return path. BSC1 SN 12867 BSC1 SN 13525 BSC2 SN 13449 BSC3 SN 12951, 12892, 12959, 12958, 12961, 12895, 12904, 12945, 12948, 13430, 13235, 13444 All units had modifications complete. Filiberto Clara
J. Kissel, T. MacDonald While waiting for the CDS system to be restored after the scheduled power outage, and for B&K to release licenses, Tim and I spent some quality time with a 3 [lb] sledge hammer, a GS13, some concrete, and SR785. We found a large (~45x12 [sq.ft]) area of empty open LVEA floor (don't tell Jodi!), set up a GS13 in the middle, and used a B&K hammer to hit 10 locations along an 40 [ft] line, each separated by 5 [ft]. Sadly, I think the result is null, but still -- null results can be interesting results. If one squints their eyes, one might be able to claim some coherence with a feature between 5-10 [Hz], but we would need more data to determine if anything in this measurement real slab dynamics. Plots attached, details below. Details ------- Timeline - Hooked up S13 and Hammer to SR785 - Tried several binwidths and frequency ranges, looking for interesting features - Didn't get any consistent coherence; looked at spectra of S13; decided its spectra looked too featureless and time series didn't look too promising - Grabbed GS13s 568V and 574V, some power supplies, and freshly made power cable - After some struggles with a wonky power supply, confirmed that both GS13s 568V and 574V are fully functional (looking at time series alone) with different power supplies - Hooked up GS13 to SR785, with hammer - Played with bandwidths and frequency ranges again (went as low as 62 [mHz]), settled on 1 [Hz] binwidth, from 1-400 [Hz], with 10 avgs. We justified the range with "the sledge wouldn't be able to move enough mass to excite anything lower than 1 [Hz], and we're already getting crap coherence, might as well make the measurements quick." Cable construction: - Used D0902011 to determine pinout of signals coming out of GS13 military connector. The GS13 needs +/- 15 [V] on pins D and F, respectively with pin R as GND. The +/- legs of the differential GS13 signal are on K and L, respectively. - Followed signals through Signal / Power pigtail breakout cable that came already attached to the GS13. D to pin 1, F to 3, and R is connected to both 2 and 4. The + GS13 signal is connected to the inner coax of the BSC, and - to the sheild (*tsk*tsk*). See attached pictures for connector pinouts of mil and power connections. - Aaron/Richard fabricated a power-to-banana cable. (+15 [V]) 1 to Red, (GND) 2 to Green, (-15 [V]) 3 to White, (GND) 4 to Black, though the banana ends of both Green and Black are Black. Calibration of TF: - B&K Hammer: - gain = 0.2356 [mV/N] (from calibration datasheet) - assumed frequency independent - GS13: - 2200 [V/(m/s)] (from eLIGO knowledge, confirmed by a few web sources) - assumed frequency independent, since instrument response is flat above 1 [Hz] natural frequency of the instrument - D050358 preamp gain of (1+R2/R1)*(1+R4/R5) = 40.2 [Vout/Vin] - Integrated once (divided by 2*pi*freq) to get displacement units - Divide by 2 for only reading in one leg of differential signal Data and analysis script live in ${SeiSVN}/seismic/Common/Data/2014-08-14_LHOLVEASlabCharacterization/
Peter, Jim, Dave
Peter K found that he could not open the PSL shutter. We did the usual MEDM button presses which used to work to no avail. After restarting the FE and beckhoff ends several times, we reverted the PSL from the new RCG2.8.5 to its old 2.8.3. In this configuration we were able to open the shutter (though not cleanly). Tomorrow we will investigate (using the DTS) if it was the upgrade which caused this problem. For now we will leave h1psl0 at RCG2.8.3 and the laser is operational.
After power was restored, I brought the laser back up. A process not quite as simple as pushing a button but was relatively a painless process. All the servos were locked and running. When all of a sudden I noticed that the pre-modecleaner reflection and transmission were zero. However the laser was up and running. The Beckhoff computer indicated that the external shutter was closed and that the EpicsAlarm was set. Doing a system reset and a computer reboot did not fix the problem. Neither did doing the steps Dave mentioned that were done previously to open the shutter. The laser is up and running with the watchdog set. All servos were left locked.
(Koji, Alexa, Dan)
We examined the beam path in HAM6 to OM1 in order to figure out the angle of the beam. We made measurements at four different points. Using an (x, y, z) coordinate system with z = up, y = East, x = South, we find at (all in mm):
Edge of table: (20.32, 0, 98)
Intermediate point 1: (0, 552.72, 95)
Intermediate point 2: (-25.4, 1219.2, 93)
OM1: (-40.64, 1574.8, 91)
The error of the measurement in height is ±1mm, and the error along the x, y axis is ±2.5mm. The attached layout shows the original (red) beam path and the new (green) beam path. From this layout, one can see the actual vs. measured angle deviation in height and along the hoirzontal plane. Using the points above, we made a linear regression and determined the vertical angle of the beam to be 4.3 mrad. The attached plot shows the data with error bars and the linear fit.
So the situation now is this:
angle of the beam [mrad] | position of the beam at OM1 design center [mm] | |
PIT (positive=up) | -4.3 | -10.6 |
YAW (positive=North) | (-39.7, though the absolute number is not that important here.) | -50.8mm |
Because of this, Koji had to tilt the OM1 up by about 4.3mrad, which is big, and I'd say that there's a high chance we will want to fix the beam angle some time in the future (e.g. larger bounce to alignment coupling). YAW is not that much of a problem because there's enough space to absorb -50.8mm.
We've been discussing how to alleviate this, and the simple hack is to rotate the septum window, which is supposed to have a 0.75deg horizontal wedge which causes 5.9mrad deflection.
According to ICS (via Joe), we should have D1101092 S/N assembly, which should have D1101005 window S/N15, which has dimension measurement that suggests 0.745deg wedge.
However, Koji measured the wedge using laser pointer and got 0.89deg which should cause 7.0mrad deflection. His measurement also suggests that the thickest side is facing south.
Now, when we rotate the septum window by X (positive=clockwise), PIT deflection was zero before but now the beam is deflected vertically by sin(X)*5.9mrad (or 7.3mrad).
Horizontally, the deflection is -5.9mrad (or -7.3) before rotation, and -cos(X)*5.9mrad (or 7.3) after, so the change in the angle would be 5.9mrad*(1-cos(X)).
If we optimize the septum rotation (which only changes by 30deg steps) for 0.75deg septum we need to rotate the septum by 120 deg clockwise.
For 0.89deg septum wedge, it would be 150deg clockwise. See below.
(The beam position change at OM1 is calculated by using 1.93m as the distance from OM1 to the septum.)
Septum rotation (deg) |
Septum wedge (deg), and deflection (mrad) |
PIT deflection change (mrad) | PIT beam pos at OM1 (mm) | PIT beam angle (mrad) | YAW deflection change (mrad) | YAW pos at OM1 (mm) |
120 |
0.75, and 5.9 |
+5.1 |
-10.6+5.1mrad*1930mm |
5.1-4.3=+0.8mrad |
+5.9+2.95 =8.85 |
-50.8+8.85mrad*1930mm |
0.89, and 7.0 |
+6.1 |
-10.6+6.1mrad*1930 |
+6.1-4.3=+1.8mrad |
+7.0+3.5 |
-50.8+20.3mm |
|
150 | 0.75, and 5.9 | +2.95 |
-10.6+2.95mrad*1930 = -4.9mm |
+2.95-4.3=-1.35mrad |
+5.9+5.1 = +11.0 |
-50.8+21.2mm |
0.89, and 7.0 | +3.5 |
-10.6+3.5mrad*1930 = -3.8mm |
+3.5-4.3=-0.8mrad |
+7.0+6.1 = +13.1 |
-50.8+25.3mm |
Anyway, there's not much difference, but since the ICS says 0.745deg wedge, we need to rotate it by 120 deg clockwise if we decide to do it.
Keita and I concerned about the AR reflection from the septum. We thought we should at least check where the AR reflection goes.
This required to make a 3D version of the ray tracing. The result is, in short, the rotation of the wedged window(by 120 or 150deg)
makes the returning beams closer to the arrangement with the nominal beams. They fly about 30-40mm North of the aperture on Faraday.
In this entry, the wedge angle of 0.75 deg is assumed.
The "nominal" beam means: "Use the HAM6 dawing. Assume this incorporates the wedging effect by the septum window."
The "actual" beam means: "Use the measured beam geometry in HAM6."
The "actual+120" and "actual+150" means: "The beams expected by rotating the septum by 120 or 150 deg in CW. The "actual" beam used for the calculation.
1st attachment is an example view of the ray tracing result.
2nd attachment shows the spot positions on OM1 viewed from the back side of OM1.
Rotation of the septum by 120 deg makes the spot close to the "nominal" beam position.
"+120deg" gives us better result than "+150deg".
Note that the result I obtained here are consistent wth Keita's handwriting calculation for the OM1 spots.
3rd attachment
The beam was back-traced to HAM5. We expect that there is a 20mm aperture (iris) at 315mm from the septum window.
It is assumed that the apertue is located at the beam properly. The primary and secondary reflections are located about 35~40mm North of the aperture.
According to D0900623, these beams might be hitting the beam dump for the PBS, but not so clear.
4th attachment
This time, the actual beam was traced-back. Without rotation, the secondary beam definetely hits the apeture structure.
The primary reflction is ~30mm away from the aperture. The rotation moves the secondary reflection further away to North.
Vertical displacement is 5~10mm. So, we can say that the rotation makes the spots close to the original positions.
In all of these cases, it seems like all ghost beams will fall on the Faraday Isolator Refl Baffle which is mounted on the suspension cage.
https://dcc.ligo.org/LIGO-D0900136 (Output Faraday Assy)
https://dcc.ligo.org/D0902845-v5 (Faraday Isolator Refl Baffle)
Volker, Matt H, Corey, Rick S, Guido, Rodica (remote), Rich A (remote)
Quick summary of work on the ISS array this week (I will write a more detailed alog later with details on cabling, mode matching, lens/mirror/ISS array positions, what optics used, photos, etc)
The beamsplitter mount ROM RH4 on HAM2 was swapped out for one that was controllable with pico motors. The in-air cabling was hooked up to a feedthrough port and tested with a temporary setup controlling it on the in-air side. All degrees of freedom work.
Lots of work was spent getting the lenses in the correct spot so that the beam waist and position was in the correct spot, no clipping, etc. The mirror in AROM RH2 was swapped for a flat mirror and the beam is now directed onto the entrance aperture of the ISS array. The lenses were tilted off axis a little bit to make sure no back reflected beam went directly back into the system and black glass beam dumps were installed to try to catch these back reflected beams (positions guessed as we cant see the back reflected beams).
We had to move a couple dumps/baffles into slightly different positions to make things fixed and we had to alter the in-air cable dressing that was done previously as it went right where we wanted to put stuff. All cables have been redressed up to the feedthrough but NO ground loop hunting done on cables yet. SEI personnel might want to check my cable routing from feedthrough to stage zero to stage 1 on the ISI, but I am pretty confident its okay.
Next week.....trying to get the quadrant detector and photodiodes aligned
Great job Matt, Volker, et al. The figures look good (except for the stains on the baffle in pic 21). A suggestion to check the position of the black glass: Is it possible to get a little red laser from the back of the beam splitter through the lenses to have a rough check of the location of the pick-offs. There should be enough back scatter from a red laser. Thanks a lot folks.
For the latest round of ISS array improvements, pico motors were added to the beamsplitter AROM4 (Fig 7 in T13000327), however it seemed to have slipped through the net which feedthrough the additional in-vacuum cables need to be attached to.
Consulting with Eddie, S at CIT he gave this initial recommendation based on what knowledge he had about available feedthroughs on the HAM2 chamber: this leave us with D1-3C2 and D3-F10 as the only viable options. We'll need 156" or a 180" cable to get from CB-6 to either D1 or D3,
With regards to the new Picomotor being installed in HAM2, the cabling is the following:
picomotor--->D1101515 (quad mighty mouse)--->CB6?--->D1101659 (seis resp cable)
However the D1101659's are only 108", and it didnt appear we had a longer cable on hand.
Thus I did a survey of the feedthroughs on HAM2 and I have marked up where there are unused ports in the attached pdf (hopefully you can understand my chicken scratch). I have not labeled which is D1, D2, etc.
There are a number of spare ones that it appears we could use, the most convenient (for a number of reasons) is the feedthrough in what I believe is the SW corner which has 2 unused ones. These are actually allocated for IO for the adaptive optics.
I requested to use the bottom one of these two unused ports (marked with a star). I have checked verbally with Guido and he was happy for us to use it, as is Hugh and Calum.
It was also suggested initially to swap out the CB6 "L" cable bracket from a 2-tier to a 3-tier. I however recommended adding an additional single cable high "L" cable bracket near the edge of the table on the western side near IM1. It is out of the way of any beams (and would be below beams anyway). This will help us use the short (108") cable we have available to go from feedthrough to this cable bracket and also trying to swap out CB6 with a 3 high cable bracket….though possible has the potential for me to bang/hit/damage something. My suggestion seems a simple and safe solution. Calum and I checked with Hugh about rebalancing and he doesn't see it as a big issue. Volker and I don't think it will be in the way of anything.
After the lenses were put into position and the AROM2 mirror placed back in position I completed the in-vacuum cabling from the feedthrough, to stage zero of the ISI, from stage zero to stage 1, to the new "L" cable bracket. Corey had already connected up the picomotor to the D1101515 cable (he told me he used the longest of the 4 cables which would be the 60" long one cable, "cable #4", connector "J5").
With the 3 spare unused cables I dressed them near the edge of the table so that the connectors were floating in free space. The location of the added "L" cable bracket and the routing/dressing of the in-vacuum cables can be seen in the photos
Now that we have the additional pico motor in chamber we now also need to think about how to hook it up/control it from the in-air side. I posed this Q to Rich A and here was his initial suggestion.
1. We can (if we are careful) use 28 AWG wire inside the vacuum system, which will free us up as far as finding the correct length (156 inches)
2. The only way we can use 28 AWG wire inside the vacuum system will be if we use less than ~50 feet of 22 AWG wire outside the vacuum system.
3. Assuming we use the one spare axis available on top of IOT2L (as provided by Picomotor Driver #3), we can stay within the 50 foot limit
4. A special cable will have to be made that goes between the RJ-9 style connector (see connector.jpg) on the one available output of the Picomotor driver and the 25 pin vacuum feedthrough.
5. The Picomotor driver front panel looks like this: (see picomotor.png)
As you can see, there are two 25 pin connectors that are normally used to drive each picomotor. In parallel with these 25 pin connectors are the individual motor connectors shown in a phone jack style connector. This is how we will pick up the one unused axis for HAM2 ISS steering.
6. The interface between the phone jack and a D-sub can be done by making a short transition cable to D-9
7. Now we just make a 9 pin to 25 pin cable. Easy.
What Rich will need is:
1. The length for the in-air cable from Picomotor controller number 3 to the proposed vacuum feedthrough
2. Account number
3. Permission and agreement from Systems and PSL
I have forwarded this request onto SYS and PSL representativies
Apologies in advance. This will contain quite a lot of detail and be quite verbose but want to get everything down whilst still fresh in my mind
We were tasked with installing new picomotors in the setup for the ISS array and also getting the mode matching correct for the ISS array.
Moving ISS Array
We were informed that the ISS array was initially installed in the incorrect location as the cookie cutter was used upside down. Thus the first thing we did was to put the cookie cutter back on (correct way up) and move the ISS array into what should be a more correct position. This moved the ISS array more towards the center of the table.
PicoMotor on mounts Swap
All that had to occur here was to swap out the fixed mount ROM RH4 (see Figure 7 of T13000327) that the beamsplitter optic site in for one that is controllable by picomotors (note AROM RH2..the last mirror before the ISS array) is already controlled by picomotors.
Before anything was swapped out, AROM RH2 was removed and the beam direction off of ROM RH4 was marked with irises (this is so that we could get the same alignment as currently there back. The base was kept in the same position and the current fixed mirror mount swapped out with one that is pico controlled. The same beam splitter optic was used. The mount was adjusted until the beam went back on the same alignment as before the swap. (One thing to note....and should be able to see on one of the pics in this log, is that the beamsplitter isnt located exactly as per its supposed location in D0901083 v12. Its about 1/2" further from ROM RH3 than design. This is no big deal other than when trying to pre plan on where clamps, etc can go). We tested that the beam from the beamsplitter heading past the ISS array has no clipping by the lid on the ISS array, and its not close to clipping.
See above in the comment section about the in-vacuum cabling of the picomotors. With the in-vacuum cable connected to the feedthrough, a temporary in-air setup was used to test that the picomotors worked. They did successfully.
Note: The Kapton "washers" have not been put in as we have only just got the Kapton sheet into clean and bake
ISS array mode matching
T1400176 gave various recommendations on how the mode matching to the ISS array could be performed. The decision made by SYS, et. al. was to use the two telescope lens solution. In particular Case 1 in Table 3, which is for the first lens after the beamsplitter to be a 2" lens of FL 343.6mm and the second lens to be a 1" lens of FL -171.9mm.
The initial position of where these lenses should go is indicated in D0901083 v12 Sheet 2. However with AROM RH2 still out (from above work) and before we put the lenses in, an iris was positioned in the beam path, and a beam scan on a rail (wiped down and wrapped in foil where appropriate) was bolted to the table (see pic beamscan) in an orientation so that the beam was centered on the beamscan as slid the beamscan back and forth along the rail. These will also act as our targets to check that we have the lenses positioned so that the beam goes through the center of the lenses.
The edge of the rail was positioned roughly in the same location as the optic in AROM RH2. This means that the focus should be roughly 16" (40cm) from the edge of this rail. So where do I get the 16" from. Well it is approximately 10" from AROM RH2 to the entrance of the ISS array, and then Ollie informed Volker that the beam travels 6" inside the ISS array (I dont know where he got the 6" from, but thats what we are going with). Also in Table 3 in T1400176 the waist is called out to be 304um, however Rick S informed Volker and I that we should be shooting for something more like 250um if we can.
The lenses were positioned roughly as per the positions indicated in D0901083 v12 Sheet 2 and it was very quickly seen that the focus position was not even close to the location wanted. After discussion with Guido M. Rodica M, it was decided that we could just slide the lens positions down stream a bit and shouldnt have to much affect. So we moved them both approximately 4" downstream (as indicated by the blue "A"s (seen in New Location for L1L2 pdf). We did notice that the beam onto the beam scan was hitting lower on the beamscan than without the lenses in but we made no attempt to fix that at the moment (more on that later).
Moving the lenses moved the waist position like we expected and so we had an initial go at taking some measurements with the beam scan. Below is the raw data:
Distance from Rail edge (cm) | Beam Diameter (13.5%) in X (um) | Beam Diameter (13.5%) in y (um) |
---|---|---|
23 | 420 | 430 |
21 | 413 | 420 |
19 | 413 | 430 |
17 | 419 | 448 |
15 | 439 | 470 |
13 | 470 | 500 |
11 | 508 | 430 |
9 | 555 | 570 |
7 | 605 | 620 |
5 | 660 | 670 |
Couple other notes:
As Volker and I were dressed up and in chamber, Rick S kindly volunteered to plot the data. The results can be seen in 1st scan horizontal.pdf and 1st scan vertical.pdf
As can be seen in these results, the waist is to small and still not in the correct location. However now that we have some results, using the jamMT program Rick had on the computer, we could use the results we have above and the lens positions to work backwards on what the incoming beam profile is actually like so that we could then alter the lens positions to get the beam size and focal position where we want. The results can be seen in jammt final solution.pdf (note the origin in the horizontal axis is where the edge of the rail is (ie the position roughly of the AROM RH2 mirror)).
The lenses were positioned in the positions as indicated by the jamMT solution and we did another beam scan measurement. Below is the results:
Distance from Rail edge (cm) | Beam Diameter (13.5%) in X (um) | Beam Diameter (13.5%) in y (um) |
---|---|---|
23 | 637 | 685 |
21 | 690 | 725 |
19 | 735 | 750 |
17 | 780 | 800 |
15 | 840 ?? | 842 |
13 | 855 | 890 |
11 | 910 | 945 |
9 | 960 | 1000 |
7 | 1010 | 1055 |
5 | 1030 | 1107 |
Couple other notes:
Again because Volker and I were in chamber, Rick S again plotted the results for us. These can be seen in 2nd scan horizontal.pdf and 2nd scan vertical.pdf
The results are pretty much bang on what we wanted. Great.
Now that the lenses positions are known we wanted to look at the beam being directed down vertically some (1-2mm) with the lenses in compared to not being in. This means that the beam is not going through the center of the lenses. However with the spacers we had available, we could not find a nice solution, short of kludging together something with washers. However Rick S suggested (and also wanted us to look at anyway) just how sensitive the telescope was if alter the picos on the beamsplitter ie do we need to tilt the mount a lot to get any change). Turns out we dont and its very sensitive so only a small amount of movement of the mirror mounts vertical position moved the beam back to the position we needed (sure this still means that the beam isnt going through the center of the lenses, but we now have the beam height as we want it). Again not a perfect solution but works with what have on hand.
We aso put in the back glass beam dumps. We had to position these by eye/guesstimation as we couldnt see the back reflected light. But we did our best to make sure they clip no beams on the table
Directing beam onto ISS array
Now that the mode matching is right, we can now direct it onto the ISS array. First off we need to swap out the curved optic that was initially in AROM RH2 for a flat mirror. The details of the mirror swapped in can be seen in optic used in AROM2 pic.
This optic had first contact painted on both sides of the mirror, but it also unfortunately in marker had the details of the optic written on the barrel (see pic writing on optic). Decided to try cleaning it off with fresh acetone and the swabs (see pic cleaning optic). The marker came off after a few swabs, and then we used 3-4 swabs on the barrel after we were confident it was clean just to be sure.
Before putting the optic into the mount the back first contact was removed (not using top gun (decision made in consultation with Calum)) and then the optic placed in the mount (see pic optic with first contact). Once mirror installed in position indicated in D0901083 v12 sheet 2 we removed the other layer of first contact.
Rick S gave us circular inserts that go into the aperture of the ISS array (I dont have a pic or a DCC number sorry) and by putting the mid size one into the aperture we were able to direct the beam (using AROM2 to adjust the beam direction and a handheld IR viewer to see whats going on) until it was centered on the hole in the insert. This should have the beam initially aligned to the ISS array as was our task :-)
We then put the SiCarbide baffle which goes in front of the ISS array (with the two holes) back into position. To enable the beam to go through the two holes we had to move the Brewster angled beam dump that is near the side of the ISS array and dumps a beam from HAM1 (I dont know its designation), closer to the edge of the table to allow the baffle we are trying to put in, in.
Everything was then dog clamped down and in-vacuum cables dressed
Pics:
Pic 7-13...are pics of the various components altered/installed so as the as built drawings can be updated
Pic 14 shows the one tiny bit of free space that is still on the table
Pic 15 shows roughly the "beams" view as going from IM1 to IM2 showing should be no clipping of this beam by black glass installed
For bookkeeping's sake, will go with the following labeling/naming of new/changed optics: