Displaying reports 78021-78040 of 81692.Go to page Start 3898 3899 3900 3901 3902 3903 3904 3905 3906 End
Reports until 10:51, Thursday 09 August 2012
H1 DAQ
james.batch@LIGO.ORG - posted 10:51, Thursday 09 August 2012 (3775)
Restarted daqd process on h1fw1
Found that the daqd process had quit on h1nds1.  Last error message in the log file:

Invalid broadcast received; seq=17427618 tp_seq=17427618 gps=1028550222 tp_gps=1028550222 gps_n=62500000 tp_gps_n=125000000

Restarted daqd process.

Note that the daqd process failed in a similar manner on h2nds0 August 6, 2012
H2 AOS
jeffrey.kissel@LIGO.ORG - posted 09:12, Thursday 09 August 2012 (3773)
New Calibration installed into Optical lever path
J. Kissel, T. Vo

Now that we've [cleaned up/corrected] our analysis of the optical lever calibration (see LHO aLOG 3758), I've installed the new numbers into the appropriate gain field in the optical lever path, H2:SUS-${OPTIC}_L3_OPLEV_${DOF}_GAIN.

The optical levers need centering before new spectra of the calibrated channels can be taken, though.

BUT, the calibration factor has been reduced by 
DOF        Before / After
ITMY P         22.359
ITMY Y         22.382
ETMY P         30.556
ETMY Y         30.544
because we fixed the controller counts to translation stage calibration (from 0.6 [mm/ct] to 6 [um/ct]), used more accurate lever arms (2*L, from 70 [m] and 6 [m] to 56.4 [m] and 6.6 [m]), and threw out some outlier data to get a better linear fit.

Reducing the expected RMS spot motion (on the ETMY, in Pitch, see LHO aLOG 3727 for full explanation of calculation) to 

| dx | = | dTheta_E * L * g / (1 - g^2) + dTheta_I * L / (1 - g^2) |
       = (50e-6/30.556) [rad] * 4e3 [m] * -0.8 [] / (1 - (-0.8 [])^2 ) + (5e-6/22.359) [rad] * 4e3 [m] / (1 - (-0.8 [])^2)
       = 0.012 [m]

or 1.2 [cm], which albeit still large from a performance stand point, is much more believable given what is visible on a camera.
H1 TCS
aidan.brooks@LIGO.ORG - posted 06:59, Thursday 09 August 2012 (3770)
ETMY Ring Heater ON at 30W

I just turned on the ETMY ring heater to 630mA for each segment to measure the thermal lens with the Hartmann sensor beam.

X1 SUS
jeffrey.garcia@LIGO.ORG - posted 21:43, Wednesday 08 August 2012 (3769)
X1 MC3 SAGM1 WhiteNoise TFs with damping ON & OFF
The first attachment contains plots of all DoFs on MC3 SAGM1 taken last week with DAMPING OFF.  The second attachment plots data from last night with SAGM1 DAMPING ON.   
Non-image files attached to this report
H1 SUS
betsy.weaver@LIGO.ORG - posted 19:42, Wednesday 08 August 2012 - last comment - 16:06, Thursday 09 August 2012(3767)
HAM2 install work

Today, Filiberto re-routed the external MC2 (and the 1 shared PR2 cable) from the chamberside test area to the chamber feed thru.  From there we spent a little time finding a cable swap and remedying.  ( I *think* the switch is related to the callout of "flooring" positions of the cabble connectors in the cable table brackets.)  We then set the 6 TOP BOSEMs to 50% OLV.  We can now run TFs to kick off SUS Phase 3a testing here.  Not entirely sure who will do this - possibly me when I get in midday.

PR2 glass install chamberside was stalled another day as we discovered contamination on the AR surface in many places (smudges as well as FirstContact overspray?).  We will need to spend some time drag wiping this tomorrow and and then re-attemp the install.

UFl and SEI should feel free to spend some morning time working on table payload if they want/need.  Any MC2 TFs in-progress will be posted or announced.

Images attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 19:44, Wednesday 08 August 2012 (3768)

Hugh and Mitch adding Ballast Masses to HAM3-West.

Images attached to this comment
hugh.radkins@LIGO.ORG - 07:48, Thursday 09 August 2012 (3771)
Thanks Betsy--We added the first layer of 10kg masses (D0901075) at nine locations per D1000907-v1.  These are all on the West side to aide in cable routing.  Apologies for the interference for some that these will present.  These masses are not bolted down but they are accurately placed.  We will add the second layer soon to locations deemed out of the way and to others when work needing better access is complete.
filiberto.clara@LIGO.ORG - 16:06, Thursday 09 August 2012 (3780)
Here is a list where the cables were landed for MC2 and PR2 to the feedthrus. 

Feedthru D6-1C1 MC2 BOT H1:SUS_HAM-20
Feedthru D6-1C2 MC2 TOP H1:SUS_HAM-1
Feedthru D6-2C1 MC2 MID H1:SUS_HAM-19
Feedthru D3-1C1 MC2/PR2 H1:SUS_HAM-2
Feedthru D3-1C2 MC2 BOT H1:SUS_HAM-26
Feedthru D3-2C1 MC2 TOP H1:SUS_HAM-3
Feedthru D3-2C2 MC2 MID H1:SUS_HAM-25

Documents that show the feedthrus and cabling: D1002874 and D1000599.
H1 AOS
bram.slagmolen@LIGO.ORG - posted 18:59, Wednesday 08 August 2012 (3766)
TMSY needs new medm screens

Can we get new MEDM screens for the TMSY (incl. the little DRIVE CAL screens!). Also, maybe we want to update the safe.snap file ...

LHO General
patrick.thomas@LIGO.ORG - posted 18:51, Wednesday 08 August 2012 (3765)
plots of dust counts
Attached are plots of dust counts > .5 microns in particles per cubic foot. Also attached is a plot of the mode of the dust monitor in the clean room over HAM3 (H0:PEM-LVEA_DST15_MODE). This shows when the dust monitor was swapped (see earlier entry).
Non-image files attached to this report
H2 ISC
bram.slagmolen@LIGO.ORG - posted 18:22, Wednesday 08 August 2012 - last comment - 19:21, Thursday 09 August 2012(3764)
OAT locking performance

Attached is a spectrum from last night (7 August 2012), starting a ~23:30h.

There seems to be a narrow spike at 700mHz, while the 2.74 Hz peaks are still there. I guess we nudging downwards ...

Images attached to this report
Comments related to this report
bram.slagmolen@LIGO.ORG - 19:21, Thursday 09 August 2012 (3790)

I added the RMS to the latest spectrum.

Images attached to this comment
H2 CDS
david.barker@LIGO.ORG - posted 17:37, Wednesday 08 August 2012 - last comment - 18:04, Wednesday 08 August 2012(3762)
many front end restarts

After syncing up the userapps/release SVN files on h2build I rebuilt most of the H2 models during Tue maintanance and restarted most models.

A problem with the folding mirror sus models was resolved with a new BSFM_MASTER file. We will install new h2susfmy code tomorrow.

New Dolphin and RFM IPC between ISI and SUS was installed today by Vincent, replacing the EPICS comms link.

New slow channels for PEM (DUST monitor) and HWS were added to the H2 frame.

h2iscey model was changed for ISC -> ALS name change. Please see Bram's alog for details.

Comments related to this report
bram.slagmolen@LIGO.ORG - 18:04, Wednesday 08 August 2012 (3763)

That will be Jamie's entry 3759

H1 CDS
david.barker@LIGO.ORG - posted 17:32, Wednesday 08 August 2012 (3761)
IOP sus watchdog alarms being installed

I have installed the sender part of the new H1 IOP SUS watchdog system, making changes on h1sush2a and h1sush34. I'm also creating the new MEDM screen.

Tomorow I'll work on the h1seih23 receiver part and start testing of this system. This will be the first use of the H1 Dolphin IPC system.

LHO General
cheryl.vorvick@LIGO.ORG - posted 16:55, Wednesday 08 August 2012 (3760)
OPS day summary:
MC2 - got external cables - Filiberto
HEPI models updated - Vincent
Renaming ISC to ALS at EY - Daniel/DaveB
HAM2/HAM3 - update models - Hugo/DaveB
Craning in the LVEA - Kyle and Apollo
EY - misc. work - OATers
EX - Apollo
HAM3 work - Betsy/Travis
Cleanup under H1 input beam tube - LIGOites
H1 PSL work - MichaelR
H2 ISC
jameson.rollins@LIGO.ORG - posted 16:34, Wednesday 08 August 2012 (3759)
h2iscey channel renaming complete

We have completed the rename of all of the H2 ISC channels to conform to the new standard:

H2:ISC-ALS_  -->  H2:ALS-
H2:ISC-ASC_  -->  H2:ASC-

While we were at it we renamed the _EY_ to be just _Y_.

This involved a couple of steps:

Modify h2iscey model

This was basically just a matter of putting the ALS and ASC library part blocks in top level sub blocks that use top_names, and then giving them the appropriate names ("Y") to ggenerate the correct channels.  The recompiled model then generated the correct names.

We did run into one issue which might be a bug in the RCG.  The auto-generated ADC screens (e.g. H2ISCEY_MONITOR_ADC0.adl) are not being generated with the correct channels. For instance, "ASC_Y_TR_A_SEG1 (adc_0_0)" is pointing to "H2:C-ASC_Y_TR_A_SEG1_INMON". The channel should be "H2:ASC-Y_TR_A_SEG1_INMON". I have no idea what is trying to do there, but we need to file a bug against the RCG

Update MEDM screens

We modified the following adl files:

isc/h2/medm/OAT.adl
isc/common/medm/QPD_OVERVIEW.adl
isc/common/medm/ISC_CUST_ALS_WFS_SETTINGS.adl
isc/common/medm/ALS_CUST_WFSDC_FE.adl

Mostly it was simple sed string replacements:

sed -i -e 's/:ISC-ALS_EY_/:ALS-Y_/' -e 's/:ISC-ASC_EY_/:ASC-Y_/' OAT.adl

There was a little bit of itteration, since we had to fix macro, screen links, channels, etc., but it wasn't bad.

Update filter files

This was also pretty simple:

sed -i -e 's/ALS_EY_/ALS_Y_/' -e 's/ASC_EY_/ASC_Y_/' H2ISCEY.txt

Restore EPICS values

We restored all the EPICS values by taking a burt snapshot file from this morning, and again performing a simple sed replace on the channel names:

sed -i -e 's/H2:ISC-ALS_EY/H2:ALS-Y/' -e 's/H2:ISC-ASC_EY/H2:ASC-Y/' h2isceyepics.snap

The updated snapshot file then burt restored all the new channels to their corresponding values before the change.

All in all, things went pretty smoothly and quickly.  I'll let the on-site guys comment on recovery of the lock after the changes.

H2 ISC
eleanor.king@LIGO.ORG - posted 16:15, Wednesday 08 August 2012 (3757)
Open-loop transfer funcion of PLL

Attached are plots of the OLTF of the PLL, taken from 1 to 50kHz, with a 200mV excitation.  The unity gain frequency is 28.7Hz at a phase of 229 degrees.  I've also included plots of a scan from 40-45kHz  where we were seeing a peak in the TF magnitude at 42.5kHz.

Images attached to this report
H2 SUS
szymon.steplewski@LIGO.ORG - posted 12:49, Wednesday 08 August 2012 (3748)
Suspension Coil Driver noise testing

Around 2:30 on August 7, 2012 I attached 5 grounding plugs to the "TEST IN" connections at the Y end station.  At this time, all ITMY and ETMY coil driver boxes (for TOP, UIM, and PUM) have grounding plugs connected to each of the TEST IN connections.  I then took some power spectra measurements of the coil driver NoiseMonitor channels to see what effect the grounding plugs have on the coil driver noise.

Starting with ETMY, the UIM driver board didn't exhibit any significant change between COIL IN and TEST IN configurations.  This is because the noise in the coil drivers is dominated by component noise, and selecting the TEST IN state allows one to see the component noise without the added DAC noise.

The ETMY PUM driver board is dominated by DAC noise, since the PUM driver is not filtered as much as the UIM board in the lowest noise mode.  Therefore when we switch to the TEST IN state, the expectation is that the noise in all coil drivers should drop to the component self-noise level.  This is what we are seeing now, as compared to Jeff K's alog #3111 when the noise levels increased and the frequency dependence was different for those channels.

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=3111

For the ITMY, the UIM behavior is generally the same as on ETMY coil drivers.  However, the ITMY PUM driver shows an increase in noise after switching to the TEST INPUT with grounding plug attached.

Non-image files attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 11:38, Wednesday 08 August 2012 (3755)
dust monitor in clean room over HAM3 swapped
Due to a calibration error, the dust monitor at location 15 in the LVEA (in the clean room over HAM3) was swapped. It was removed around Aug. 8 17:20 UTC and the new one put in around Aug. 8 18:01 UTC.
H2 ISC
jaclyn.sanders@LIGO.ORG - posted 09:31, Wednesday 08 August 2012 - last comment - 08:05, Thursday 09 August 2012(3746)
Cavity Characterization: Preliminary Results

This is the transfer function between the phase-frequency discriminator and the FET IQ demodulator while the cavity is locked. The blue trace is "initial" conditions, i.e., with a well-aligned cavity and standard modulation sidebands. The green "sb shift" trace was taken with the RF modulation sideband frequency tuned 200 Hz higher than its initial value. The red "alignment shift" trace was taken with the ITM yaw misaligned. 

The FSR is 37.512 kHz, with a higher-order FSR peak at 75.018 kHz. Given this FSR, the cavity length is 3995.95 m.

The peaks due to the RF modulation sidebands are at 54.432 kHz and 58.098 kHz in the initial trace. These peaks shift 200 Hz in the green trace.

Additional structure is observed at 46.301 kHz, 55.325 kHz, 57.252 kHz, and 66.229 kHz. The peaks at 46.301 kHz and 66.229 kHz increase for the case of yaw misalignment and are thus likely to be (1,0) modes. 

The separations between these peaks are:

75.018 - 66.229 = 8.789 kHz

66.229 - 57.252 = 8.977 kHz

46.301 - 37.512 = 8.784 kHz

55.325 - 46.301 = 9.024 kHz

The mean modal spacing is 8.8935 kHz.

From this modal spacing, the g-factor is 0.540532, corresponding to approximate mirror radius of curvature of 2302.86 m. 

The FWHM of the FSR peak is approximately 94 Hz. Finesse is thus 37512/94 = 399.064. This would occur for a reflectivity of about 99.2%.

There's a follow-up of this in the works for characterizing cavity properties during ring heater use.

Images attached to this report
Non-image files attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 08:05, Thursday 09 August 2012 (3772)
The RF frequency is 24.515730 MHz and was shifted to 24.515930 MHz for the second measurement. Making the ansatz

f_SB = (N - 1) * f_FSR + f_mease 

with f_FSR ~ 37.51kHz, N an integer, and f_meas = 58.098 kHz, we determine 

N = 653

Now, we can go back and recalculate f_FSR = 37511.71 Hz with a few ppm precision. This then yields L_arm = 3995.985m.
H2 AOS
thomas.vo@LIGO.ORG - posted 17:15, Thursday 26 July 2012 - last comment - 16:26, Wednesday 08 August 2012(3614)
H2 ITMY/ETMY Optical Lever Calibration
Jeff K. , Thomas V.

Below are the calibration parameters for the H2 ITMY Optical Lever:
        Slope          Y-intercept
Pitch [ 580.41229822  -11.51774017]
Yaw  [ 689.70532274  -13.3345144 ]


And here are the calibration parameters for the H2 ETMY Optical Lever:
         Slope           Y-intercept 
Pitch [ 1666.80728788   -33.14694715]
Yaw  [ 1727.67131855     23.41350328]

Both sets of calibrations were attained via the same process of moving the QPD along a translation stage and measuring the output signal.  All four sets of slopes are in units of radian*meters.
Images attached to this report
Comments related to this report
thomas.vo@LIGO.ORG - 14:40, Friday 03 August 2012 (3713)
Jeff K. Thomas V.

We have found a non-linear relationship between the way the translation stage moves and the way we were reading out the measurements.  We need to double check the calculations as well as the methodology on retrieving data.  This latter is difficult because even though there is a micrometer on the translation stage it is covered by the laser enclosures, which if we take off, it will introduce ambient light onto the QPD.  We are currently investigating solutions.
jeffrey.kissel@LIGO.ORG - 11:59, Monday 06 August 2012 (3736)
T. Vo, J. Kissel

Pulling out a spare translation stage and measuring the displacement response (in [mm]) to controller demands (in [ct]), we found the following attached relation. Immediately turned off by the non-linearity seen, from our experience with the controlers jolting the translation stage upon power on/off, and from Kissel's recollection of the controllers in i/eLIGO (of which these controls are the same), we've launched into a more sophisticated characterization of the controllers. Given that the non-linearity is roughly 1 [um] over the 1 [mm] range measured, we might be barking up the wrong tree and just be over-reacting, but it should be a quick round of measurements to assess it in more detail.

It should also be noted that the controller can demand from 0 to ~8600 [ct], and we've thus far only exercised it from 0 to 150, since we only need ~1 [mm] range given the size of the Oplev QPD.
Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 13:03, Monday 06 August 2012 (3737)
T. Vo, J. Kissel

Here're the results from the more detailed characterization. It looks like, within a small range of operation the controller is indeed linear to the desired level. However, over the full range of the controller, there's certainly some non-linearities present.


Notes:
Linear UP -- commanding the stage to move from 0 (4000) up to 150 (4150), in linear 10 [ct] increments.
Linear DOWN -- commanding the stage to move from 0 (4000) up to 150 (4150), in linear 10 [ct] increments.
Random -- going to each data point in a random order

Each of these should yield the same answer if it's a truly linear system.
Non-image files attached to this comment
thomas.vo@LIGO.ORG - 16:26, Wednesday 08 August 2012 (3758)
Jeff Kissel Thomas Vo

After reviewing the linearity of the translation stage as shown in ALOG 3737, we found that the non-linear regime of the translation stage resides near the end of the rails of the stage but the approximate middle yielded linear results.  We're confident that the increments that we used to translate the stage during calibration for both test masses were small enough and far enough away from the edges so that the non-linearity would have a small affect on our results, this will require further testing to truly be valid (in progress).  That being said, after correcting some errors in the calculations and double checking our numbers, we used the original data to apply to the calibration.  

A noteworthy point: Jeff Kissel used the edrawing from the solidworks model in,

LHO Corner Station: D0901469-v5 
LHO EY Station: D0901467-v6 

to find a more accurate number for the lever arms than previously used, ITMY = 56.4m and ETMY = 6.6m, as opposed to 70m and 6m respectively.  This was taken into account for our last calculation.

Onto the good stuff, the values of the slopes below are in micro-radians*meters:

ITMY
        Slope         Y-Intercept
Pitch [ 25.93274501  -0.51461109]
Yaw   [ 30.81584154  -0.5957635 ]



ETMY
        Slope         Y-Intercept
Pitch [ 54.53112025  -1.01505634]
Yaw   [ 56.56393367   0.79879263]


Attached are the graphs of the linear response curves, the python fitting scripts and the EXCEL spreadsheets to help visualize the underlying calibration calculations. In particular, the excel spreadsheets shows the conversion from controller units into millimeters and then into meters and micro-radians.  Hope this is the last time we'll need to repeat this post, sorry for the troubles!
Images attached to this comment
Non-image files attached to this comment
Displaying reports 78021-78040 of 81692.Go to page Start 3898 3899 3900 3901 3902 3903 3904 3905 3906 End