Displaying reports 46621-46640 of 86444.Go to page Start 2328 2329 2330 2331 2332 2333 2334 2335 2336 End
Reports until 13:43, Monday 12 March 2018
H1 CAL (CAL)
richard.savage@LIGO.ORG - posted 13:43, Monday 12 March 2018 - last comment - 10:06, Tuesday 13 March 2018(40968)
X-end Pcal beam alignment (at Receiver Module) way off

NikoL, Rick S

We switched on the the Pcal laser to check the beam pointing after the vibration damper and baffles installation work last week.

We (with Corey's help) pointed the ETM to center the optical level signals.

With this alignment the Pcal spots are way off, more than 1 cm (see attached photo, both beams should be (and were earlier last week) centered on the integrating sphere aperture).

Keita is going to check on the TMS alignment so we can try to discriminate between the possibility that the Pcal periscope shifted during the alignment work and the possibility that the ETM pointing (or OptLev) has changed.

If the ETM pointing is off, it would be on order 10 mm over 10 m, or about 1 mrad.

 

 

Images attached to this report
Comments related to this report
richard.savage@LIGO.ORG - 10:06, Tuesday 13 March 2018 (40986)

TravisS, NikoL, RickS

It appears that the Pcal periscope structure moved (top pitched back, away from the ETM) during the "Baffles and Shields" installation.

The attached photos show the spot positions on the ETM target both before (last Wed.) and after (this morning) the installation of the vibration absorbers, Mt. Brackets, and barrel baffle panels.

Also attached is a detail of the Pcal ETM target (D1301014) showing the dimensions of the features on the target.

It appears that the upper beam moved up about 3.5 mm and the lower beam moved right about 3.5 mm. 

The gaps between the centers of the upper flexures and the A7 adapter wall were slightly more than 0230".  Our goal was to keep them below 0.220".  We set them significantly below 0.220" last week (maybe 0.210") but apparently the additional mass of hte hardware added reduced the compression (as expected, see LIGO-T1800047-v2).

Images attached to this comment
H1 SUS (GRD, SQZ)
thomas.shaffer@LIGO.ORG - posted 11:45, Monday 12 March 2018 (40967)
SUS_ZM1 Guardian Node Created and Started

This morning I started the ZM1 Guardian node. I had made the code changes for it back with ZM2 (alog40256), so it was just an easy create and start.

It is also on the Guardian overview screen, and while I was there I checked that all nodes were on it. All good!

H1 TCS (TCS)
cheryl.vorvick@LIGO.ORG - posted 11:27, Monday 12 March 2018 - last comment - 11:41, Monday 12 March 2018(40965)
TCSY glitching signals - an update to previous alog 40843
Images attached to this report
Comments related to this report
cheryl.vorvick@LIGO.ORG - 11:41, Monday 12 March 2018 (40966)
  • lasertempvbridgeIN, which looks very flat for a real signal
  • lasertempvbridgeOUT, which looks real, and drops in DC level at the same time the chiller flow glitches (see above plot)
Images attached to this comment
H1 General
edmond.merilh@LIGO.ORG - posted 10:38, Monday 12 March 2018 (40960)
Shift Summary - Day

17:00 Chris to LVEA to inner receiving for scaffold gathering

16:00 Vent meeting

16:36 Mto MY to move a ladder

17:00 Betsy and Travis out to EY

17:10 Tour group into CR

17:34 Tour group into CR

17:45 Corey sitting in for the remainder of my shift to allow my work in the PSL

H1 General
edmond.merilh@LIGO.ORG - posted 09:35, Monday 12 March 2018 (40958)
Morning Meeting Minutes

VAC - pumping down in the corner station. Bake is going slow at MY

PSL - ongoing 70W installation work. Mode matching into the new amplifier is the plan for today.  Camera work in PSL; moving GigE cameras to new locations

SQZ - squeezer work will continue. If there's a break in it SEI will take the advantage to do balancing

SUS - OPO Model work (Tues)

SEI - Target of opportunity work contingent on squeezer work. ISI model changes contingent on ECR

CDS Ele - Access control work will be going on at MY

EX - Extraction of the Quad

EY - Pcal maintenance work this week. Vac work this week.  SUS closeout w/doors today.

HVAC- work ongoing in optics lab

HAM6 - Target of opportunity work: 

H1 PSL
edmond.merilh@LIGO.ORG - posted 08:24, Monday 12 March 2018 (40957)
PSL Weekly Report - 10 Day Trends FAMIS #6191

Trends reflect ongoing work during 70W installation.

Images attached to this report
H1 General (PSL)
edmond.merilh@LIGO.ORG - posted 08:20, Monday 12 March 2018 (40956)
PSL Status Report - Weekly: FAMIS #7481


Laser Status:
SysStat is good
Front End Power is 33.97W (should be around 30 W)
HPO Output Power is -0.04668W
Front End Watch is GREEN
HPO Watch is RED

PMC:
It has been locked 0 days, 0 hr 0 minutes (should be days/weeks)
Reflected power = 0.02522Watts
Transmitted power = -0.02523Watts
PowerSum = -0.001669Watts.

FSS:
It has been locked for 0 days 0 hr and 0 min (should be days/weeks)
TPD[V] = 0.0672V (min 0.9V)

ISS:
The diffracted power is around 3.3% (should be 3-5%)
Last saturation event was 6 days 19 hours and 17 minutes ago (should be days/weeks)

Possible Issues:
FSS TPD is low
LRA out of range, see SYSSTAT.adl

 

H1 CDS
patrick.thomas@LIGO.ORG - posted 08:16, Monday 12 March 2018 (40955)
Conlog crashed, restarted, channel list updated
Same issue with invalid json data. Updated channel list attached.
Non-image files attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 08:14, Monday 12 March 2018 (40954)
Shift Transition - Day

TITLE: 03/12 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:

 

H1 FMP (FMP)
christopher.soike@LIGO.ORG - posted 07:01, Monday 12 March 2018 (40953)
VPW Desiccant cabinet relative humidity readouts for the last month
Attached are the VPW desiccant plots with the last month's added data.  Nothing out of the ordinary shown.
Non-image files attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 07:43, Sunday 11 March 2018 - last comment - 02:39, Monday 12 March 2018(40950)
CP4 bake-out controller in "HOLD" again
Output has been at 100& for days now so this won't impact anything.  If situation were different, i.e. were weren't already at 100% output but still ramping up, then this "bug" could have resulted in an over temperature condition.  The program is behaving as if the "HOLD" condition is a function of run time based on 1C / hour expected rate of rise and time needed to get to SETPOINT value from measured temperature recorded at start of profile.  If so, then this is a novice programmer mistake.  The program should switch to the HOLD segment upon reaching the SETPOINT value as a function of the measured temperature irregardless of time so as to always be limited to the 1C / hour maximum rate of rise.   
Comments related to this report
chandra.romel@LIGO.ORG - 08:30, Sunday 11 March 2018 (40951)

I also witnessed this happen on Friday when the control sensor clearly hadn't reached the set point yet and program transitioned to hold at temp. Heater had been at 100% output overnight.

gerardo.moreno@LIGO.ORG - 02:39, Monday 12 March 2018 (40952)VE

Temperature at GV11 in air for the past 3 days.

Images attached to this comment
H1 ISC (ISC, PEM, SYS)
georgia.mansell@LIGO.ORG - posted 20:57, Saturday 10 March 2018 - last comment - 10:58, Monday 12 March 2018(40949)
Electric field meter noise floor conversion to DARM

Following on from the driven electric field meter (EFM) measurements presented in alog lho-40878, I've made a rough conversion of the EFM noise floor into meters of DARM. It looks like the EFM might just be sensitive enough to see fields which could contribute to DARM. This calibration is very dodgey and is really just an order-of-magnitude (or 3) estimate. Based on the the transfer function from volts-of-ESD-shield-drive to meters-in-DARM, in alog llo-28675 (strongly dependent on which test mass was looked at), the EFM noise floor lies somewhere between the red and purple traces in the first plot.

How I made this plot:

First I fit our measured electric field strength vs volts of ESD shield drive measurement, to get a conversion from Vshield to electric field strength [V/m] (second plot, data read off the plots in Jeff's previous log post)

I fit Anamaria's transfer functions for mDARM per Vshield as shown in llo-28675. I just did a linear fit and extrapolated it to 500Hz, since their measurements only go to 200Hz.

I converted this transfer function into mDARM per electric field [V/m], using the fit in step 1 (shown in the third plot)

Finally I took the EFM noise floor, and multiplied it by the transfer function (x 5 since we drove all 5 shields where LLO only drove 1) to get the EFM noise floor in mDARM (plot 1).

EFM measurements will continue at EX in the future, we still need to look at the frequency-dependence of the ESD shield electric field, and take measurements where we drive the ESD signal/bias, ISI horizontal actuators, and anything else in-chamber that might generate electric fields.

Images attached to this report
Comments related to this report
rainer.weiss@LIGO.ORG - 10:58, Monday 12 March 2018 (40964)SYS
Estimates I made a while ago when deciding that the smaller electric field meter was not adequate are
the sensitivity of the meter had to be 5 e -5 Volts/meter/sqrt(Hz) at 100 Hz to intersect the ambient 
field noise in the chamber. This required that the test mass had acquired a charge of about 3 e -9 coulombs.
LHO General
kyle.ryan@LIGO.ORG - posted 01:49, Saturday 10 March 2018 - last comment - 05:49, Saturday 10 March 2018(40947)
TC1 (used for CP4 bake contoller) displaying invalid value then valid value then .....
I noticed that the displayed value in the TC1 field was "#..." or absent a numeric value this morning at 0110 hrs. during a random check.  I monitored for 10 minutes and noted displayed values as 

TC1="#..." TC2=85.5 TC4=83.0 %(can't determine due to pixel resolution) 

TC1="#..." TC2=85.8 TC4=83.2 %(can't determine due to pixel resolution) 

TC1="#..." TC2=85.7 TC4=83.1 %(can't determine due to pixel resolution) 

TC1="#..." TC2=85.6 TC4=85.2 %(can't determine due to pixel resolution) 

TC1=99.9 TC2=85.5 TC4=85.5 %71 

TC1="#..." TC2=85.9 TC4=83.3 %76  

Thus, displayed value of TC1 is alternating between gibberish and valid values. 
Comments related to this report
chandra.romel@LIGO.ORG - 05:49, Saturday 10 March 2018 (40948)VE

Tagging VE.

It appears it doesn't like to read out three whole #s.

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 20:00, Friday 09 March 2018 (40946)
HAM6 work thursday

This is a late report about the work done in HAM6 on Thursday.  Basically we have aligned things in HAM6, so that we should be able to work on locking the OPO for now. 

In the morning Nico, TJ and Terry pulled off the viewport simulator, and Gerardo and TJ removed the septum window protector so that we could attempt to inject a beam into HAM5. 

TJ and Terry recentered the osems on ZM1, which seems to have improved the performance of the damping loops (TJ is planning to remeasure the damping loops, but our experience in chamber was that it was not swinging around as badly once this was done). 

We reentered the green rejected beam on the DCPD and its reflection onto the black glass dump, which was lost when TJ and Daniel fixed the short in the diode. 

We also added the black glass clip to the last steering mirror before ZM1.  This means that we should be finished making adjustments that might change the balancing of the OPO suspension. 

Nutsinee and I borrowed the Thorlabs PZT driver from the optics lab so that we can scan the OPO PZTs more quickly which makes alignment into the OPO much easier. Nutsinee had installed a thorlabs PDA100A into the homodyne path so that we could look at the OPO transmitted power.  We found that we were not well enough aligned through the apertures on HAM6 so that the flashes we saw on SQZT6 would sometimes be clipped on one of the apperature as the OPO suspension and ZM1 were swinging.   Once we had the beam better aligned through the apertures, we can see the cavity scan for 1064 fairly well.

We decided that it wasn't worth trying to inject this beam into HAM5 and look for it returning to HAM6, since the power was so low it is hard to see the beam while scanning.

We had a hard time finding the green transmitted beam from the OPO, but with help we were able to turn off the cleanroom +LVEA lights.  This allowed us to find the beam and align onto the green TRANS PD. With the OPO suspension locked we were able to align the green into the OPO decently.  We then unlocked the OPO suspension.

LHO VE
chandra.romel@LIGO.ORG - posted 18:11, Friday 09 March 2018 (40945)
Corner pressure & purge air

Three purge air systems operating normal.

Corner pressures trended over six days.

Images attached to this report
Displaying reports 46621-46640 of 86444.Go to page Start 2328 2329 2330 2331 2332 2333 2334 2335 2336 End