Displaying reports 64581-64600 of 77212.Go to page Start 3226 3227 3228 3229 3230 3231 3232 3233 3234 End
Reports until 15:24, Friday 25 July 2014
H1 PEM (PEM)
margarita.vidrio@LIGO.ORG - posted 15:24, Friday 25 July 2014 - last comment - 14:27, Friday 01 August 2014(12996)
Statistics for 8 years of wind at LHO

Summary: Eight years of wind data at 3 LHO stations were analyzed. Fifteen percent of hours had wind speeds exceeding 10 m/s, the speed at which displacement and tilt from wind start to significantly increase the seismometer signals. Nearly 25% of hours in April, the month with the highest average wind speed, have winds exceeding 10 m/s. Data are also shown for individual stations; readings for EY are the highest.

Introduction: The analysis of wind data is important because wind speeds over 10 m/s increase ground motion and thus affect interferometer performance. This increase in ground motion is caused by wind interacting with the topology of the site and, most importantly, the surfaces of buildings. In addition to producing displacements, wind blowing on the buildings can tilt them, which can produce spurious acceleration signals from seismometers.

Methods: Eight years of data between 2004 and 2012 were analyzed for patterns across the years. The data was extracted from DataViewer for the Corner Station (CS), End Station X (EX), and End Station Y (EY). The "Maximum Channel" was selected of the "Hourly Trend" setting within DataViewer. This time period was selected because it was not missing more than 58 days of data at a single time in the series and only a total of 218.7 days were missing from the entire data source. This amounted to about 8% of the data missing from the entire data set. The data was considered missing if DataViewer did not provide it.

Results: The first figure shows that 15% of the hours in the 8 years analyzed exceeded 10 m/s, which significantly increases ground motion. The second figure shows that, during each of the spring months, the wind was greater than 10 m/s in more than 15% of the hours, peaking at 24% in April. The third figure shows that the average hourly maximum wind speed varied the most from year-to-year in the month of February. The fourth figure includes statistics for the individual stations. Averages for EY are higher than for other stations. For example, 27% of April hours exceed 10 m/s at EY while the average for all stations was 24%.

Margarita Vidrio, Robert Schofield

Non-image files attached to this report
Comments related to this report
margarita.vidrio@LIGO.ORG - 14:27, Friday 01 August 2014 (13154)

In Fig 5, the wind speeds exceed 10 m/s thirty eight percent of the time in June at 2 AM and April at 11 PM. Also, the month of December shows a consistent percentage (between 8%-10%) of wind speeds over 10 m/s across all times of the day.

Non-image files attached to this comment
H1 INS (SEI, SUS)
matthew.heintze@LIGO.ORG - posted 15:14, Friday 25 July 2014 - last comment - 18:15, Friday 25 July 2014(12995)
HAM2 closed up :-) :-) :-)

Jeremy B, Stuart A, Jeff K, Arnaud, Jeff B, Matt H, Apollo, Richard M

 

Success....HAM2 closed up :-)

 

Quick rundown of events. 

Entering HAM2 straight after doing door work on HAM3 and the particle counts were zero. We had some troubles with PRM showing signs of rubbing overnight so we looked at this first. I didnt find anything glaring but saw a couple stops kinda close. We backed these off ran another set of TFs and got a clean bill of health. Then to save time later we centered all ther OSEMs on all four suspensions on all stages. After this I locked all four HXTs's to get ready for FC pull

Jeff B went in and did a quick last wipe down, put in wafer and monitor optic, removed optics/wafers that were still in chamber, etc. We were all straged to pull FC but couldnt get low particle counts. People were working in BSC's so asked the to stand down to let the particle counts drop. 

After a quick lunch to let the particle counts settle, it was all systems go. On the way out we bumped into Mike Landry et. al. who had been doing tests with the large optics/top gun. I am sure he will write a report on his work but he indicated it took ~9mins for the fields to drop. Thus we decided we should blow the smaller optics for 5mins continuously with the top gun after FC pulled. As I was worried about the pony sized bottles running out we dragged a large cylinder out there for the top gun. 

Particle counts showed us good to go and so we pulled PR3, then MC1 then PRM FC. I went for MC1 now due to the awkwardness of having to unlock that suspension and how have to get on the table to do so. And I didnt want to do this with a half unlocked ISI. I inspected each optic for particulate and Arnaud/Stuart have a log of what I saw (which they will post). We also pulled the FC on the moitor optic. After I reminded myself about 50 times about it :-). We actually had to pull FC twice on it as after I pulled the outer layer, we saw there was still FC on the backside, so had to remove optic to pull backside FC and put optic back. Afte unlocking those three suspensions, TFs were taken on all three by Jeff K/Arnaus and given the all clear. Once the all clear given, the ISI was unlocked on east side and door went on. 

Whilst door being put on on east side I pulled the FC on the MC1 suspension (particle counts were low), and unlocked the suspension. We found we had to change some of the OSEM positions on the three stages.  TF's were taken on this suspension and given the all clear. Whilst TFs were being taken, Richard M transitioned us to laser hazard, and I visually inspected the ISS array cables one last time and they all looked plugged in. 

Once TF's were given the okay, the offset settings for the MC mirrors for when we flashed the mode cleaner successfully in the past were applied and the mode cleaner flashed right away. YES.

ISI on west side unlocked and door went on :-) :-)

Stuart/Arnaud have a detailed log of particle counts/timeline/particles per square inch on the optic which will post to this log

Pic: The HAM closeup crew. Thankyou to all who have helped get LHO to this point. Its amazing to be to this point and when we had schedulded it

Images attached to this report
Comments related to this report
stuart.aston@LIGO.ORG - 18:15, Friday 25 July 2014 (13009)
Attached below is a log and particle counts taken during the HAM2 work covering the period 1056 (local) to 1431 (local). Thanks to Arnaud for logging the afternoon session.
Non-image files attached to this comment
H1 SUS (INS, IOO)
jeffrey.kissel@LIGO.ORG - posted 15:06, Friday 25 July 2014 (12993)
IM TFs Clean Before HAM2 Doors + Fix of OSEM Calibration
J. Kissel, S. Aston

I've gathered TFs of the IMs before the HAM2 doors are installed. They're free, see first attachment.

More importantly -- confused by a large discrepancy between model and measurement, I noticed in
/ligo/svncommon/SusSVN/sus/trunk/HAUX/Common/MatlabTools/plotHAUX_dtttfs.m
that the coil driver transconductance had not been updated (reduced to 0.998 [mA/V]) since we reduced the coil driver strength (see LHO aLOG 8758). Correcting this, the calibration *still* was off by a factor of 2ish. Exploring further, I found the OSEMINF filter's "to_um" filter was a gain of 0.0391251 [um/ct], instead of the expected 0.0233333 [um/ct] (see LLO aLOG 4291) that installed in every other suspension. As such, I multiplied the measurement by a correction factor of (0.039 / 0.023) ~= 1.6, and achieved the expected match of model and measurement.

I've now corrected the OSEMINF "to_um" filter, and corresponding "norm_um" filters in the DAMP bank, changed at 10:20:21 PDT (17:20:21 UTC). I've also cleared out all unused extra filters in the DAMP bank to avoid future confusion.

Comparing against previous measurements we see resonances in the same place, but off by the expected calibration factors (see last 4 attachments).

I would have compared against LLO's results, but data from each of their SUS show a wildly different overall scale factor, making comparisons difficult at best. I'll see if Stuart can chase down the difference once he get's back to LLO.
Non-image files attached to this report
H1 INS
matthew.heintze@LIGO.ORG - posted 14:53, Friday 25 July 2014 - last comment - 17:01, Friday 25 July 2014(12994)
HAM3 work today

Jeremy B, Matt H, Jeff B, Apollo

As you may remember from one of my alogs last night, i forgot to pull the FC on the witness optic in HAM3. It was decided to play it safe and pull the door to get at it. So before anyone else started in chamber work we quickly pulled the door. Particle counts in cleanroom were 10 counts and straight after the door came off was also 10 counts in chamber. Door came off at 9.09 am, Half the ISI was locked....and whilst ISI was being locked I looked at MC2 optic. Looked same as yesterday which is awesome. I tried pulling the FC on the small optic and in doing so it ripped so I only had a little bit come off with first go (I think the layer was to thin). So had to try to get at it with a gloved hand to get the rest. We did so, but it definitely meant that the cautious approach was the right one. We did a quick check to make sure we got all the FC, unlocked the ISI and the door went back on at 9.22am (off for around 13mins). Jeff checked particle counts as the door was jamming shut with the chamber and saw no puff of particulate. 

Stuart has a detailed log of timeline and particle counts that hoping he will add to this

Comments related to this report
stuart.aston@LIGO.ORG - 17:01, Friday 25 July 2014 (13004)
Attached below is a log and particle counts taken during the HAM3 work covering the period 0900 (local) to 0922 (local).
Non-image files attached to this comment
H1 PSL
richard.mccarthy@LIGO.ORG - posted 12:08, Friday 25 July 2014 - last comment - 17:23, Friday 25 July 2014(12991)
ISS Photo Diode Array Test
Matt H.  requested that we verify the ISS PDs were still connected in vacuum.  I was able to get to the all 16 cables and tested each pair. They all tested fine with a reading of approximately .384VDC Anode to Cathode and OPEN Cathode to Anode on my Fluke 87V set to diode test. The last set I tested seemed to be reversed so I left them disconnected until I can have better access to the chassis under the chamber behind the HEPI support Structure.
Comments related to this report
matthew.heintze@LIGO.ORG - 17:23, Friday 25 July 2014 (13006)

Below is the instructions I received from Peter K and passed on. Thanks Richard for doing this

 

The only way to test all the diodes without laser light is to use the diode
tester function of a multimeter.  To do that you'll have to disconnect the
cables from the electronics that's where they were when we put the array
in.  With the multimeter on diode test, the negative (black) lead goes to the
cables/connector labelled cathode.  The positive (red) lead goes to the ones
labelled anode.  Touch the centre pins of the cable SMA connectors.  If
everything is okay you'll get a buzz and a voltage reading just over 0.3 V
(either 0.38 or 0.34, don't remember exactly which).

H1 CDS (VE)
david.barker@LIGO.ORG - posted 11:56, Friday 25 July 2014 (12989)
EPICS alarms to Cell phones reconfigured for missing cold cathode gauge

I have reconfigued the Vacuum Alarms To Cell Phones to not alarm on the missing MX Y1 beam tube cold cathode (343B) and replace it with the cold cathode on the other side of the gatevalve (344B). This is a temporary change until 343B gauge is repaired.

H1 CDS (SYS)
david.barker@LIGO.ORG - posted 11:18, Friday 25 July 2014 (12988)
First PCAL model running on h1odcx

WP4750. Shivaraj and Dave.

With Stefan's kind permission, we added the first version of the PCAL front end model to h1odcx as a CAL top-names part. We have not restarted the DAQ, so the data from this model will be corrupted until we do so.

Channels in this new system have names which start with H1:CAL-PCALX_

H1 SEI
hugh.radkins@LIGO.ORG - posted 11:06, Friday 25 July 2014 (12987)
TFs Ranover night on WHAM2

JeffK HughR

Look pretty good, Jeff looked pretty close.  Maybe I'll get a chance to plot a Dof by Dof for better compare which we did on screen.

Meanwhile see the attached for a Global Basis comparison with data from back in November.  Current data is bottom set (see title); two bands zoomed in 1) main resonances 2) upper frequencies where the ISI cable bracket might show itself.

Images attached to this report
H1 SUS
travis.sadecki@LIGO.ORG - posted 10:51, Friday 25 July 2014 (12986)
ITMx unlocked and ITMy locked

ITMx has been unlocked for SEI TFs.  ITMy has been locked for ACB install.

H1 INS
jim.warner@LIGO.ORG - posted 10:22, Friday 25 July 2014 (12985)
ITMY ISI locked, ITMX unlocked, BS still a mystery
Travis and I went into the 3 vertex BSC's this morning, and locked ITMY (for ACB install) and unlocked ITMX. While I was there, I looked around at BSC2 for possible rubbing, and checked ITMY for loose masses but found nothing. Will try running tf's at BSC3 today, but the activities out there might make it a futile attempt.
H1 General
andres.ramirez@LIGO.ORG - posted 10:13, Friday 25 July 2014 (12984)
Installation Meeting Minutes

Attendees: Bubba, Jeremy, Matt, Dugh, Robert, Jeff K, Mike, Hugh, Stuart, Jason, Terry, Jodi, Vern, John, Travis, Guillermo, Mitchell, Arnaud, Aaron, Keita, Jeff B, Jim, Filiberto, Richard, Dale, Gerardo, etc …

Today's Tasks:

•	Work will continue on HAM2/HAM3 today – Matt/Jeremy/Apollo
•	Contamination & Control will be present at HAM2/3 activities– Jeff B
•	Illuminator work at End Y – Aaron
•	Locking/ Unlocking suspensions on BSC1/BSC3 respectively - Travis 
•	Stage Viewport preparation will continue today - Gerardo
•	Mitchell and Mike V will continue with ACB work (Travis will assist)
H1 SUS
stuart.aston@LIGO.ORG - posted 10:02, Friday 25 July 2014 (12966)
SR3 (HLTS) M1, M2 and M3 Phase 3a Power Spectra - exhibit re-injected electronics noise on M1 stage
A set of TFs were previously taken for the SR3 (HLTS) suspension (see LHO aLOG entries 12929 and 12945), to complete Phase 3a power spectra have been taken with damping loops both ON and OFF for all stages. These H1 SR3 power spectra have also been directly compared with equivalent H1 PR3 measurements (allhltss_2014-07-24_Phase3a_H1HLTSs_ALL_Spectra_D*.pdf). The plot key is as follows:-

Black Dashed Line = Expected Sensor Noise
Blue Solid Line = H1SUSPR3 2013−10−07_0800
Green Solid Line = H1SUSSR3 2014−07−24_1030

Summary:

Noise floors for SR3 are consistent with expectations. However, it should be noted that virtually all M1 stage OSEM channels exhibit narrow frequency comb features above ~20 Hz, which are only present in the damped power spectra and could therefore be be re-injected noise from the electronics chain and will need to be further investigated.

All data, scripts and plots have been committed to the sus svn as of this entry.
Non-image files attached to this report
H1 SUS
stuart.aston@LIGO.ORG - posted 09:38, Friday 25 July 2014 (12965)
SR2 & SRM (HSTS) M1, M2 and M3 Phase 3a Power Spectra - exhibit signs of ground loop induced noise on SRM M1 T3 LF and RT channels
A clean set of TFs were previously taken for both SR2 & SRM (HSTS) suspensions (see LHO aLOG entry 12950), to complete Phase 3a power spectra have been taken with damping loops both ON and OFF for all stages. These power spectra measurements have also been directly compared (allhstss_2014-07_24_Phase3a_H1HSTSs_ALL_Spectra_D*.pdf). The plot key is as follows:-

Black Dashed Line = Expected Sensor Noise
Blue Solid Line = H1SUSSR2 2014−07−24_0900
Green Solid Line = H1SUSSRM 2014−07−24_1000

Summary:

Noise floors for both SR2 & SRM are consistent with expectations. However, it should be noted that SRM M1 T3 LF and RT channels exhibit a comb of narrow frequency features above ~20 Hz, which since observed in both damped and undamped power spectra could be induced by ground loops.

All data, scripts and plots have been committed to the sus svn as of this entry.
Non-image files attached to this report
H1 SUS
stuart.aston@LIGO.ORG - posted 09:16, Friday 25 July 2014 (12982)
HAM3 - PR2 & MC2 (HSTS) M1-M1 Phase 3a TFs are clear
After securing doors on HAM3 (see LHO aLOG entry 12975), TFs have been taken overnight as part of Phase 3a testing to check for rubbing or other issues that may have developed as follows:-  

- PR2 M1-M1 undamped (2014-07-24_1090302332_H1SUSPR2_M1_damp_OFF_ALL_TFs.pdf) 
- MC2 M1-M1 undamped (2014-07-24_1090284714_H1SUSMC2_M1_damp_OFF_ALL_TFs.pdf)

HAM3 ISI Status: ISI unlocked, no damping or isolation loops running.

PR2 & MC2 alignment: No offset was applied during this measurement.

The undamped measurements from above have been compared with other H1 HSTS suspensions at Phase 3a of testing as well as the model (allhstss_2014-07-25_Phase3a_H1HSTSs_M1_Doff_ALL_ZOOMED_TFs.pdf).

Summary: 

Both PR2 & MC2 M1-M1 TFs show good agreement with the model and perform consistently with other HSTS suspensions, thus raising no concerns.

All data, scripts and plots have been committed to the sus svn as of this entry.
Non-image files attached to this report
H1 CDS
james.batch@LIGO.ORG - posted 08:54, Friday 25 July 2014 (12983)
Matlab license system changed for Ubuntu workstations
The licenses for Matlab are now being served by a local CDS license server, which should reduce the vulnerability of network interruptions to Caltech in obtaining Matlab licenses.  This applies to new matlab sessions started from newly opened shells, existing open Matlab sessions should be unaffected.  Also this only applies to Ubuntu workstations at this time.

The only change you may see is warning messages on startup referencing non-existing directories in the matlab toolbox path.  We have licenses for more packages than are installed, which causes the warnings.  This will not affect your ability to use Matlab.  
H1 SUS
arnaud.pele@LIGO.ORG - posted 19:11, Thursday 24 July 2014 (12981)
Matlab tfs running overnight on MC1 MC3 PR3 PRM

Undamped transfer functions will start on opsws1 and opsws10 when HAM2 ISI measurements will be done

H1 SUS
stuart.aston@LIGO.ORG - posted 17:56, Thursday 24 July 2014 (12980)
Matlab TFs running on MC2 and PR2 (HSTS) overnight
Matlab TFs are set to run on HAM3 suspensions overnight as follows:-  

- MC2 (HSTS) M1-M1 undamped TFs, Starting at ~6:00pm July 24th (local)
- PR2 (HSTS) M1-M1 undamped TFs, Starting at ~11:00pm July 24th (local)

When complete at ~3:00am July 25th (local), the measurement status will revert to OFF and damping loops will be restored to the ON state.

These measurements have been initiated from the opsws2 workstation.
LHO General
patrick.thomas@LIGO.ORG - posted 17:43, Thursday 24 July 2014 (12961)
Ops Summary
08:45 Matt H. and Jeremy going into HAM2
08:50 Mike V. going into LVEA to help Mitchell with CPB
09:12 Stewart going into HAM3
09:18 Filiberto swapping ITMY and ITMX UIM coil drivers [WP 4748]
09:20 Hugh going to BSC1
09:38 Nathan starting unattended work with laser in OSB optics lab
10:12 Filiberto finished WP 4748
10:19 Mike L. going to LVEA west bay to work with Gerardo on optic charging experiment
10:47 Mitchell and Mike V. going to LVEA west bay to move CPB
10:54 Gerardo going to LVEA west bay to work on optic charging experiment
11:06 Hugh and Jim out of BSC1
11:44 Mitchell and Mike V. out of LVEA
12:51 doors going on HAM3
12:55 Jeff B. and Andres going to HAM3
12:59 Stewart going to HAM3
13:03 Richard going to end Y to take pictures through viewports
13:22 end X transitioning to laser hazard
13:43 Mike L. and Gerardo going to west bay to work on optic charging experiment
14:24 Richard back from end Y
14:45 Manny to end Y to turn off illuminator
15:15 Jim B., Patrick replacing light bulb in right side projector
15:16 Paul and Jordan to end Y to pull cable for accelerometer
15:18 Kyle starting WP 4749, PT343 valved out from beam tube volume
15:33 end X transitioned to laser safe
16:02 Mike L. and Gerardo out of LVEA
16:30 Gerardo and John W. discovered that the right side projector is overheating, taken down
16:45 Nathan will be supervised by Dick G. in the OSB optics lab
H1 INS (SEI, SUS)
matthew.heintze@LIGO.ORG - posted 16:26, Thursday 24 July 2014 - last comment - 17:44, Thursday 24 July 2014(12976)
HAM2 optics unlocked...ISI unlocked

(Matt H, Stuart A, Jeff K, Jeremy B)

 

After getting the okay from SEI, I unlocked the 4 HXTS's on HAM2. TF's were run on All 8 suspensions (4x HXTS, 4x HAM AUX) on the table and all were given the all clear. So SEI TFs should be good to start..once we damp the suspensions of course :-)

 

We took particle counts. Cant remember exact number but Stuart has the numbers and i believe will post

Comments related to this report
stuart.aston@LIGO.ORG - 17:44, Thursday 24 July 2014 (12978)
Attached below is a log and particle counts taken during the HAM2 work covering the period 1500 (local).
Non-image files attached to this comment
H1 AOS (COC, ISC, SUS)
daniel.hoak@LIGO.ORG - posted 00:34, Thursday 24 July 2014 - last comment - 12:11, Friday 25 July 2014(12960)
If the mode matching to the OMC is bad, can we fix it?

Summary: in preparation for beam arriving in HAM6 / ISCT6, I wanted to explore the potential for mode mismatch to the OMC, and how it might be corrected.  I found that for essentially any reasonable combination of errors in optic positions and ROCs, the mode matching can be recovered by a small adjustment to SR2.  (Given the way the SRC is designed, I don't think this is surprising to anyone -- it may even be intentional! -- but it was an interesting exercise.)

Details:

At L1 they observe a mode mismatch to the OMC of ~25%, depending on which ITM supplies the bounce.  Lisa found that this could be caused by a small (1.5cm) change to the SR2-SR3 distance, assuming the PRC length is nominal.  At LHO we are a 2-3 weeks away from measuring the beam arriving in HAM6.  In principle, there may be errors in the position of any of the optics on the order of 1cm, and errors to the ROC for the curved mirrors (of order ~few cm?).  The question is, if we are very unlucky and the initial mode matching to the OMC is bad, can we correct it in a simple way?

I used Lisa's script from LLO:8565 as a starting point to estimate the mode mismatch that could occur from small errors in the positions and ROCs for optics in the output path, SR3 to OMC.  At LHO the PRC length has been measured to better than 1mm; it's very close to nominal, so for now I assume the positions of the PRs, the BS, and the ITMs are correct.  That leaves six optical components with un-verified positions: SR3, SR2, SRM, OM1, OM2, and the OMC.  (I fold errors in the position of OM3 into the position of the OMC.)

Modeling a beam subject to small variations in eleven optical parameters is a lot to keep track of in closed-form, so I implemented a Monte Carlo approach: for 10k trials I independently varied the longitudinal position and ROC of the six optics in the output path, and calculated the mode overlap with the OMC waist (w0=490um).

Errors in position were drawn from Gaussian random variables with sigma = 2.0cm; these were applied to SR3, SR2, SRM, OM1, OM2, and the OMC.  Errors in radius of curvature were drawn from a Gaussian distribution with sigma = 5.0cm; these were applied to SR3, SR2, SRM, OM1, and OM2.  I'm not sure if these values are reasonable (2cm in position sounds like a lot), but they seemed like fair conservative guesses, based on the as-built dimensions for L1 in E1200274-v3, compared to the nominal values in T0900043-v11.

For 10k trials, the median overlap with the OMC waist after varying the parameters of the optics was 0.85; the distribution is shown in Fig2.  This median is better than what's observed at L1, which may mean they got unlucky, or the magnitudes of my errors are too small.  (NOTE: for simplicity I am using a single bounce off ITMX with the nominal ROC of 1934m.)

Next, I used a la mode's optimizePath() function to correct the mode mismatch by varying the position of SR2.  Based on table layouts this seemed to be the easiest optic to move.  The range on the optimization of SR2's position was +/-5cm.

The result is that even for very bad mode overlaps, the errors can be compensated by moving SR2.  And, whether or not the overlap can be completely recovered is only a function of how far you can move SR2.  (I.e., if we are terribly unlucky at H1, maybe we can move it by more than 5cm.)  This might be known already to optics experts, but it was surprising to me that even for large errors in optic ROCs the mode can be corrected by changing a single degree of freedom.  I guess this is what you gain when your beam-reducing telescope has a short Rayleigh range?  (Flip side: we're really sensitive to the position of SR2 and SR3.)

In the attached: Fig1 is the distribution of mode overlap to the OMC, for 10k trials with independently varied parameters.  Fig2 is how well you can improve things by moving SR2; the horizontal coordinate is starting (mis)match, and the vertical coordinate is corrected (mis)match, after at most a +/-5cm change to SR2.  Fig3 is a comparison of how much you need to move SR2 vs how much you get back.  The scripts I used are there too.  It's not a very elegant implementation, for 10k trials it takes way too long to finish, something like an hour.



Notes:

 - This is all fine from a mode-matching perspective, but I don't know enough about optical cavities to say whether changing the SRC length by 5cm is okay or a complete disaster.  Also, I think that a la mode's optimization procedure changes only the position of the optic in question, and doesn't take into account the changes to relative lengths.  So, when it moves SR2 by 5cm, a la mode is increasing the distance from SR3 to SR2, and decreasing the distance from SR2 to SRM.  This would be fine if SR2 was a lens, but it's a mirror; if the position changes by 5cm the SR3-SR2 and SR2-SRM distances should change in the same direction.  (I think that since the SR3-SR2 distance is the important one, this is does not change the results, but I haven't checked in detail.)

  - I belatedly realized that the ROCs for the SR optics have been measured and they're listed on the core optics website (galaxy.ligo.caltech.edu/optics).  So, errors in the ROC of 5cm are probably way too generous.  I'm not sure about the OM1 and OM2 optics.

 - Of course in order to correct something you need to measure it first.  If the mode mismatch is bad we'll have to characterize the beam on ISCT6 with Chris M's beam scan technique or something similar.  It might be worth modeling how accurately we can measure the necessary correction to SR2's position.

Images attached to this report
Non-image files attached to this report
Comments related to this report
daniel.hoak@LIGO.ORG - 12:11, Friday 25 July 2014 (12990)

I modified the script to more realistically handle changes to optic position; now when SR2 is moved by x distance away from SR3, the SR2-SRM distance changes by the same amount.  Also I went through some sanity-checking and made plots to visualize how the beam profile is changed when various parameters are adjusted.  I'm still surprised that changing a single degree of freedom (SR2 position) can adjust what amounts to two degrees of freedom (waist size and position), but maybe if I look into the form of the ABCD for a beam-reducing telescope it will be clear.

In the first plot attached I have re-run the same study as above, 1000 trials, but moving SR2 up to +/-20cm; this is to demonstrate that large moves in SR2 really will fix even the largest mis-matches.  The second plot is an example beam profile, before and after adjusting SR2's position; the 'before' plot (top) has a too-small waist about half a meter in front of the OMC.  The 'after' plot (bottom) is after moving SR2 by 4.4cm, now the waist is in just about the right place and is the right size (490um).

Again I suspect that this is *NOT* a good way to fix the mode matching, probably changing the length of the SRC by more than a millimeter is really bad news.  But, there is a knob to turn if we need it.  (I haven't studied how to adjust the mode matching while preserving the SRC length, e.g. by moving SR2 and SRM (x2) together.  Not sure if there's enough room on the tables for this.)

Images attached to this comment
Displaying reports 64581-64600 of 77212.Go to page Start 3226 3227 3228 3229 3230 3231 3232 3233 3234 End