Displaying reports 65021-65040 of 77211.Go to page Start 3248 3249 3250 3251 3252 3253 3254 3255 3256 End
Reports until 18:25, Monday 30 June 2014
H1 SUS
arnaud.pele@LIGO.ORG - posted 18:25, Monday 30 June 2014 (12553)
Tip tilts medm populated

This is a late alog from last week :

OM1 OM2 and OM3 needed some medm work :

1.Base change matrices for damping: they have been populated using the usual matlab script "make_sushtts_projection.m" in /HTTS/Common/MatlabTools.
2.Calibration filters : copied from the RMs
3.Coil output signs : set to - + + - in the order UL LL UR LR. From an email from Suresh, magnet polarity is opposite of HAUX (E1200215), therefore the sign convention is also opposite.
3.Damping filters : copied from RMs, they seem to work with gain of -20 for L, -0.04 for Pitch and Yaw
4.Safe.snap were updated and commited into the svn

It would be good to take some TFs/spectra at some point

H1 CDS
david.barker@LIGO.ORG - posted 18:12, Monday 30 June 2014 (12552)
new IOP SWWD installed on all HAMs

I restarted the following IOP models: sush2a, sush34, sush56, seih16, seih23, seih45. All user models on these front ends were stopped and restarted as part of this work. Guardian was used to put the associated SUS and SEI sytems into a safe state.

The only systems left to be upgraded are the SUS and SEI for BSC1,2,3. This is scheduled for tomorrow. 

No DAQ restart was required for this work as it had already been restarted last week.

H1 SUS
jeffrey.kissel@LIGO.ORG - posted 17:28, Monday 30 June 2014 - last comment - 17:10, Monday 07 July 2014(12544)
H1 SUS ITMX Discrepant Drive Strength Fixed.
J. Kissel, A. Pele, T. Sadecki, B. Weaver,

After another day's worth of fumbling and hand-waving, we've finally traced the discrepant transfer function magnitude to a loose cable connection at the air-side of the feedthrough. In the course of attempted fixes, we measured a few more things, moved a few more things, replaced the R0 F2 and F3 OSEMs, but the only thing that fixed it was the cable connection. This flaw with the electronics chain should have been found earlier with our cable swap on Friday, with remeasuring the open light current, and with Arnaud's DC actuation test below, but frustratingly, it did not. But we found it. 

I'm in the process of getting formal transfer function measurements now, but I'm confident from what I'm seeing thus far that this SUS is read for close-out. Will post comparison TFs once they're finished.
We have exORSIIIIIIIZED the demons. This SUS is clee-uh.

Details (In rough chronological order)
-------
- Arnaud compared the ETMY and ITMX R0 F2 to F2 and F3 to F3 drive at DC using the alignment offsets (the only QUADs available, so take ERM and TCP chain comparison with a grain of salt), and concluded that the chains are driving with comparable and within a chain F2 and F3 are of comparable strength with such a quick study. 
- Betsy retook an L2L transfer function (just for sanity's), saw the same discrepant factor of two -- and some more Yaw resonant cross-coupling. Still F2 shows the majority of the badness.
- Decided just to swap the OSEMs, and hopefully move on. Below are the new serial numbers, open light current, and compensation gains and offsets. These *have* been installed. We'll take a new safe.snap this evening after all the commotion has died down.
- Betsy & Travis poked at this, looked at that, iterated with measurements several times on the floor.
- At last, Betsy went a long the signal chain, and made sure all connections were secure, and finally found this bad connection at the in-air connection at the feedthrough.
- Simultaneously, Travis loosened up the the cable loop from the optical table to the top mass. This may have alleviated the extra Yaw peaks that had shown up today. 

Open light current values and serial numbers for the new OSEMs.
      Raw    New     New        S/N
      ADC    Gain    Offset      
R0F2 25646   1.170   -12823     077
R0F3 26554   1.130   -13277     147

We'll also update the OSEM chart and grab a new safe.snap once transfer functions are finished.
 
Comments related to this report
jeffrey.kissel@LIGO.ORG - 21:57, Monday 30 June 2014 (12555)
TFs look great. For some reason the comparison script is failing on my laptop; will post comparisons tomorrow. But, for all intents and purposes, H1 SUS ITMX is ready for close-out. A victory for team SUS!
Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 09:00, Tuesday 01 July 2014 (12560)
Comparison plots. All looks well, as expected. To demonstrate the problem, I also include the prior *bad* measurements of the reaction chain (2014-06-27_2117).
Non-image files attached to this comment
arnaud.pele@LIGO.ORG - 17:10, Monday 07 July 2014 (12634)

More transfer function measurements were taken on the lower stages of ITMX last tuesday.

Interesting things to notice :

1. The measurements with no top mass damping (1st and 3rd attachments) appear to show resonnances which are not predicted by the model. Those are most certainly resonnances of the reaction chain moving because of the reaction force (e.g. 3rd page of 1st attachment : resonnance at 0.66Hz is not predicted by the model, but matches with the frequency of the first yaw mode measured on the top mass reaction chain, cf this measurement from alog 12555).

2. There is a factor of 2ish discrepancy between the model and the measurement for both UIM and PUM

Non-image files attached to this comment
H1 SUS
arnaud.pele@LIGO.ORG - posted 17:00, Monday 30 June 2014 (12550)
medm overview screens locally modified

Today the sus overview medm screens were udpated (again) to account for the new-new iop dackill state channel name. They haven't been commited into the svn, and won't be until LLO has the change.

The linearization modification Jeff made for the etmy has been moved to SUS_CUST_QUAD_OVERVIEW_with_linearization_2014-06-30.adl

Locally modified files are :

M       bsfm/SUS_CUST_BSFM_OVERVIEW.adl
M       quad/SUS_CUST_QUAD_OVERVIEW.adl
M       quad/SUS_CUST_QUAD_R0.adl
M       omcs/SUS_CUST_OMCS_OVERVIEW.adl
M       hxts/SUS_CUST_HLTS_OVERVIEW.adl
M       hxts/SUS_CUST_HSTS_OVERVIEW.adl
M       tmts/SUS_CUST_TMTS_OVERVIEW.adl

M       SUS_CUST_IOP_DACKILL.adl

H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:06, Monday 30 June 2014 (12549)
Ops Summary
Day Shift Summary
LVEA Laser Hazard

08:45 Justin – Transition LVEA to laser safe 
09:00 Thomas – BSC3 working on ACB alignment
09:48 Jason & Betsy – Alignment work on ITMX/ACB
10:50 Filiberto – Replacing DC power strip in SUS-R1 next to HAM2 
11:00 Dave – Restarted HAM models for new watchdogs
11:52 Battery alarm on UPS for control room Vacuum workstation. Cyrus is looking into  
12:31 Monthly Hanford emergency alert test
12:52 Justin – General LSO check in LVEA
13:16 Filiberto – Pulling cables at End-X
13:45 Peter – Brought up the PSL laser
14:05 – 14:20 Dale – Tour in control room
14:20 Justin – Transition LVEA South and East bays to laser hazard
14:22 Dick – Collecting alignment gear from the LVEA
14:52 Filiberto – Pulling cables at End-Y
16:03 Rick, Peter, & Matt – Working in HAM2
H1 CDS
cyrus.reed@LIGO.ORG - posted 15:18, Monday 30 June 2014 (12547)
Vacuum Workstation UPS
I have removed the UPS from the dedicated vacuum workstation in the control room.  It has had a warning indicator lit for the battery since last week, and decided to get more vocal today (beeping).  This means this workstation will not remain up through power outages, but it was not going to with the UPS in the state it was in anyway.  We will need to source a replacement battery, or see if we have a connection to the main UPS available.
H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 13:57, Monday 30 June 2014 (12543)
PSL Status
PSL laser went down at 12:10 on Friday the 27th due to an apparent chiller problem. Peter King restarted the PSL laser at 13:45 on Monday the 30th. 
H1 AOS
jason.oberling@LIGO.ORG - posted 13:52, Monday 30 June 2014 (12542)
ITMx ACB Alignment

J, Oberling, B. Weaver, T. Sadecki, T. Vo

Last Friday we took a look at the ITMx ACB alignment and found it to be off laterally by +7.8 mm, which was a shift of +8.3 mm compared to the ACB lateral position error from the original alignment (-0.5 mm).  Looking at the HEPI moves made last week (+1.3 mm lateral, 1.25 mrad CCW => ~2.5 mm lateral at the ACB) explained 3.8 mm of the +7.8 mm error, but we still couldn't explain the last 4.5 mm.  Betsy, Travis, and Thomas looked at the ACB and compared it by eye to other "more square" things in the chamber and found that the ACB visually looked like it needed to yaw CW and pitch down (there are no marks or monuments on the ACB to assess pitch and yaw).  Possible after all the swinging back of the ACB for the recent lower structure replacement work it didn't return to its original pitch/yaw; as previously mentioned there are no visual indicators on the ACB for aligning pitch/yaw.  We therefore pitched and yawed the ACB until it was aligned to the ITMx within the ±2.0 mm tolerance.  Another visual assessment of the ACB showed it to look much more square with everything else in the chamber.  The current alignment errors of the ACB, w.r.t the ITMx, are:

H1 SUS
betsy.weaver@LIGO.ORG - posted 13:34, Monday 30 June 2014 - last comment - 15:15, Monday 30 June 2014(12541)
Particle counts in BSC3 this morning

Here are the particle counts from in side of BSC3 (in the same usual spot near the floor where we have been measuring for the last ~week).

 

After ~20mins of 1 guy in chamber:

0.3um  100

0.5um  40

1.0um  10

 

2 people in chamber, but counts taken just after 1 had walked around down in bottom floor of chamber and crawled up under the ACB:

0.3um  1160

0.5um  780

1.0um  340

 

~45 mins later while doing more baffle work, less walking on chamber floor:

0.3um  398

0.5um  284

1.0um  99

Comments related to this report
calum.torrie@LIGO.ORG - 15:15, Monday 30 June 2014 (12545)

As per note in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=12488 at next opportunity i.e. when optic can be protected by lens cap the floor (of the chamber) and the flooring should be wiped and vacuumed. Jeff Bartlett has this on his to do list.

H1 SEI (SEI)
hugo.paris@LIGO.ORG - posted 13:12, Monday 30 June 2014 (12540)
HAM-ISI command Scrips updated

Command scripts were not setting the right value for the correct state epics variable, when turning the HAM-ISI isolation loops ON.  This "correct state" is compared to the "current" state for each main filter module (ISO, Damp, FF,...) to determine whether the ISI is in the expected state, and turn the red indicators of the overview screen green accordingly.

This minor bug was corrected. The new HAMISItool script was committed to the Seismic svn, and "svn up" here at Hanford.

Work was covered by WP# 4702 which can now be closed.

Images attached to this report
H1 SEI (SEI)
hugo.paris@LIGO.ORG - posted 13:04, Monday 30 June 2014 (12539)
SEI MEDM Screens Updated

The ISI Blend_Switch screens did not mention which unit they belonged to. This was corrected for both type of ISI. The new displays are committed to the seismic SVN, and were "svn up" here at Hanford.

Work was performed under WP #4703, which can now be closed.

Images attached to this report
H1 INS
calum.torrie@LIGO.ORG - posted 12:44, Monday 30 June 2014 (12538)
Power Limit into Mode Cleaner

Questions - We systems were recently asked about what the current Power Limit into the Mode Cleaner was and if there was a document what was the link? LHO specifically wanted to flash the mode-cleaner in air with 200 Milli-Watts. 

Links - The document is M1300464, link is https://dcc.ligo.org/LIGO-M1300464, the relevant sections and limits are 4.1 (in air) and 4.2 (under vacuum).

Answer - As per section 4.1 of M1300464 200 Milli-Watts in air is acceptable.

Reference - I note that LLO currently have the "clean" Mode Cleaner at 2.3 W (under vacuum) as per LLO alog entry: - https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=13209 and as per section 4.2 of M1300464 that this is also acceptable. 

Action - LLO have been asked (in e-mail by Calum) to re-measure the absorption as per section 4.2 of M1300464. (They LLO have already been doing this recently, refer to https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=13109.)
H1 SUS
jeffrey.kissel@LIGO.ORG - posted 11:59, Monday 30 June 2014 - last comment - 09:47, Tuesday 01 July 2014(12534)
Open light current values gathered for H1 SUS ITMX R0 F2 and F3
B. Weaver, T. Sadecki, A. Pele, J. Kissel

In hopes of find a smoking gun in a dead OSEM LED or photo-diode, we backed off the H1 SUS ITMX's R0 F2 and F3 OSEMs and gathered a new measurement of their open light current. Sadly, the difference is at most 5-10%, and does not explain the factor of two seen last Friday (LHO aLOG 12522). Thus far we haven't changed the OSEMINF compensation values to match the new reading, because we're not sure if we're gunna swap out the OSEMs yet. Or next step is to drive alignment offsets and compare against other suspensions to see if the coil / actuation side of the OSEM is the culprit. We'll also measure coil resistance. (Remember, the electronics chain has been exonerated with the cable swap test we did on Friday).

For reference:
      Raw   New    New      Former   Former
      ADC   Gain   Offset   Gain     Offset
R0F2 28600  1.049  -14300   1.003    -14958
R0F3 26320  1.140  -13160   1.063    -14114

Obtained using the following matlab script:
/ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/
[resultstring gains offsets] = prettyOSEMgains('H1','ITMX');
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:47, Tuesday 01 July 2014 (12561)
Note that these numbers were never installed, and now obsolete since we replaced these two OSEMs. See LHO aLOG 12544 for new OSEMs and open light current values.
H1 PSL (IOO, PSL)
matthew.heintze@LIGO.ORG - posted 14:55, Friday 27 June 2014 - last comment - 15:52, Friday 15 August 2014(12517)
ISS work in HAM2 this week

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

 

 

Comments related to this report
guido.mueller@LIGO.ORG - 18:40, Friday 27 June 2014 (12521)
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.
matthew.heintze@LIGO.ORG - 11:17, Monday 30 June 2014 (12531)

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

Images attached to this comment
Non-image files attached to this comment
matthew.heintze@LIGO.ORG - 11:26, Monday 30 June 2014 (12533)

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

Images attached to this comment
matthew.heintze@LIGO.ORG - 14:17, Monday 30 June 2014 (12537)

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:

  • Distance from rail edge to 2nd lens ~33cm +/- 0.5 cm
  • Distance b/w 2 lenses 24cm
  • Edge of rail @row B32-1cm (or B31 + 3.5cm)
  • Error of Beam Diameter ~+/-10 um

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:

  • We are tilting the optics a bit to make sure the back reflected beam does not go back through the system. The ellipticity is very sensitive to how much tilt lens has.
  • Distance b/w lenses ~23.5cm
  • Distance from 2nd lens to edge of rail 25cm
  • error in beam diameters +/- 10um

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

Images attached to this comment
Non-image files attached to this comment
corey.gray@LIGO.ORG - 15:52, Friday 15 August 2014 (13436)

For bookkeeping's sake, will go with the following labeling/naming of new/changed optics:

  1. AROM RH5:  This was previously ROM RH4.  Didn't want to call it AROM RH4 since we already have an optic named this. 
  2. L1:  This is the first lens after the beamsplitter (i.e. the new AROM RH5).  This is a 2" Lens with FL = 343.6mm
  3. L2:  This is the second lens after beamsplitter.  This is a 1" lens with FL = -171.9mm

 

LHO General
justin.bergman@LIGO.ORG - posted 09:59, Friday 27 June 2014 - last comment - 15:30, Monday 30 June 2014(12509)
Morning Mtg

No change anticipated to corner station laser hazard configuration today.

Matt H/Corey - Continuing ISS prep work

HAM3 - ongoing work with 532 nm fiber-coupled laser (Kiwamu/Sheila)

ITMX - alignment looks ok...need to check Arnaud's TFs from last night

Jason may need to review ITMX alignment

EX - TCS will transition to laser hazard, finish populating the HWS section of ISCTEX and do some alignment work with the ALS laser

Richard M investigating heat concerns with racks at end stations

Calum presentation on contamination control

       -MEMO regarding particle counters T1400024

       -Tree showing where to start with contamination control knowledge E1400029

Comments related to this report
calum.torrie@LIGO.ORG - 15:30, Monday 30 June 2014 (12548)

Follow up on note with some additional information than that posted by Justin Bergman re: talk by Calum on Contamination Control on Friday 27th June at LHO.

1) LIGO-T1400024: Airborne Particle Counters (Handheld) - General Instructions and LIGO use

Jeff has now got 3 to 4 hand-held particle counters avaailble for sign out at the contamination area (on our right as you walk down Dycem flooring towards LVEA from cleaning area). An additional 4 unit are on order (2x for hand-held use and 2x to replace broken plumbed in units.) Convert and report all numbers collected in particles per cubic foot (#/ft3), or particles per cubic meter (#/m3) of air sampled. Jeff has the hand-held particles counters set to display particles per cubic foot (#/ft3) i.e. the paticle counter is taking care of the conversion etc ... Just to be sure please include a picture (when you can) of the particle counter screen.

 

2) LIGO-E1400029: LIGO, Contamination Control Training Material

Level 1 and level 2 are required reading. Most if not all of you have read these at some point. While this will be compulsory for all new staff and a refresher course will be offered soon if you feel you are in need of some additional guidance now please read and review the following: -

LEVEL I General Entry Cert to access any clean room space- All workers
LIGO-E0900047: LIGO Contamination Control Plan (PAGES 1 THROUGH 27 ONLY.)

LEVEL II Chamber Entry - in chamber workers
All documents in section I above plus
LIGO-E1201035: aLIGO Chamber Entry & Exit Procedures &
LIGO-T1400024: Particle Counters - Technical Note on How to use in the field

If you wanted to check agasint what you have just read you could also have a go at our quiz, see: -

LIGO-T1400177: aLIGO Contamination Control Quiz

H1 INS
calum.torrie@LIGO.ORG - posted 08:28, Thursday 26 June 2014 - last comment - 12:28, Monday 30 June 2014(12488)
Particle Counts BSC3
Particle Counts were taken in BSC3 before and during work activity on the ITM quad.

Counts were very high, see below. Work continued because the ITM will be cleaned again before close and because of pressing needs from other groups.
Refer to LIGO-T1400024-v4 (https://dcc.ligo.org/LIGO-T1400024) for guidance on particle counts. Would like to see push and draw cross-flow system setup at BSC3.

start of work (2 bodies in chamber, no work)
0.3 um 1020
1.0 um 160 

5 minutes after above (same 2 bodies, no work) 
0.3 um 964
1.0 um 174 

5  minutes after above (same 2 bodies, no work) 
0.3 um 560
1.0 um 80 

5-10 minutes after above (same 2 bodies, no work) 
0.3 um 380
1.0 um 50 

5 minutes later (same 2 bodies, with some "walking" in chamber)
0.3 um 540
1.0 um 120 

5 minutes later (prep for sleeve removal, now 3 bodies)
0.3 um 780
1.0 um 190

5 minutes later (after sleeve removed, now 3 bodies)
0.3 um 1270
1.0 um 210
Comments related to this report
calum.torrie@LIGO.ORG - 12:28, Monday 30 June 2014 (12535)

On Thursday 26th June (following these counts being raised at the morning LHO meeting Bubba et al set up the draw fan on the BSC3 door (opening) as per the attached picture, DSCN0367.jpg. Following the installation of the draw fan I went back to take readings in and around WBSC3. The readings were as follows: - 1) In clean-room outside WBSC3/1 (in middle of room). 0.3 um 50 1.0 um 20 2) In clean-room outside WBSC3/1 (adjacent to draw fan). 0.3 um 10 1.0 um 0 3) In clean-room (in front of draw fan). 0.3 um 150 1.0 um 30 4) In WBSC3 (at opening). 0.3 um 80 1.0 um 10 5) In WBSC3 (just inside chamber). 0.3 um 170 1.0 um 40 6) In WBSC3 (above open flooring, below ITM). 0.3 um 260 1.0 um 70 Clearly the installation of the draw fan has made a marked improvement. However, more measurements are required to confirm this in the longer term. Refer to alog entry https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=12529 for follow up reading taken on the 30th June 2014. ACTION - At next opportunity i.e. when optic can be protected by lens cap the floor (of the chamber) and the flooring should be wiped and vacuumed. Jeff Bartlett has this on his to do list.

Images attached to this comment
calum.torrie@LIGO.ORG - 12:26, Monday 30 June 2014 (12536)
On 26th June I also went into WBSC1 to measure the particle counts. No work was going on in WBSC1. The soft door covers were on and the HEPI and outside of chamber were entirely covered with Ameristat sheeting.

1) Outside WBSC1 adjacent to soft door cover, see attached picture DSCN0373.JPG.
0.3 um 50
1.0 um 20

2) Inside WBSC1 adjacent to soft door cover.
0.3 um 0
1.0 um 0
Images attached to this comment
H1 SUS
arnaud.pele@LIGO.ORG - posted 10:57, Monday 23 June 2014 - last comment - 17:30, Monday 30 June 2014(12447)
sustools.py updated

[Mark Arnaud]

as reported on thursday, sustools.py has been updated in order to account for the new IOP wd state channel names.

By typing in the command line :

/opt/rtcds/userapps/release/sus/common/scripts/./sustools.py -o ETMX wdNames

The output returns all wd state channel names associated with this suspension, including the new IOP channel name:

['H1:SUS-ETMX_R0_WDMON', 'H1:SUS-ETMX_M0_WDMON', 'H1:SUS-ETMX_L1_WDMON', 'H1:SUS-ETMX_L2_WDMON', 'H1:IOP-SUS_EX_ETMX_DACKILL', 'H1:SUS-ETMX_DACKILL']

All sus guardians will be restarted and tested tomorrow

Comments related to this report
arnaud.pele@LIGO.ORG - 17:30, Monday 30 June 2014 (12551)

By doing this change (adding "ifo-rooted" iop channels), guardian machine ran into a memory issue, similarly as few months ago with ISI guardians.

Without going into details, we basically reverted the upgrade, meaning that guardian won't look at iop wd until further notice.

All sus guardians were restarted.

 

Displaying reports 65021-65040 of 77211.Go to page Start 3248 3249 3250 3251 3252 3253 3254 3255 3256 End