Displaying reports 44061-44080 of 88572.Go to page Start 2200 2201 2202 2203 2204 2205 2206 2207 2208 End
Reports until 17:38, Tuesday 11 December 2018
H1 IOO (IOO, PSL)
cheryl.vorvick@LIGO.ORG - posted 17:38, Tuesday 11 December 2018 - last comment - 15:30, Thursday 03 January 2019(45853)
PZT swapped on the PSL

The mount for the PZT in the IO path on the PSL, IO_MB_M4, was swapped from the 2" mirror and the damped mount to the new PZT mount.

Aligning with the new PZT mount is challenged by having to remove the entire mount from the table, to access the bolts underneath, to adjust the +/-X position.  There was also a change of the beam alignment when securing the bottm plate to the table.  The beam was carefully aligned to IO GigE camera 2 and camera 3, and when the bottom plate of the new mount was secured to the table, the beam was gone from both cameras, and an offset was introduced into the IMC_IN beam.  With the PZT it was possible to restore a beam to IO GigE 2, the camera that is on the bottom periscope transmitted beam.  It was not possible to restore both camera images with the PZT.  This indicates that the change in IMC_IN position and angle are due to the PZT swap.  It was past noon, so the decision was to leave this change as is, lock the IMC, and evaluate how it and the beam downstream was affected, instead of using M3 and the PZT on the PSL, to restore an image to both cameras.  The change in IMC_IN on the iris at the bottom periscope was identifiable as yaw with an IR viewer.

The reference beam from the shutter (between the PSL and HAM1) was recorded before and after the PZT swap.  Those pictures show the difference is between the before and after beams is 1mm and 2mm in pitch and yaw (image attached).

Sheila and JeffK moved IMC DOF, Corey and JeffK started an initial alignment, and now the effort is to lock.

BEFORE reference time 12/11 18:00 UTC, AFTER reference time 12/12 1:24 UTC.  A snapshot showing IMC WFS, IM4 Trans, and ISS Second Loop QPD signals is attached.

- Cheryl, Jason, Keita

Images attached to this report
Comments related to this report
cheryl.vorvick@LIGO.ORG - 03:05, Wednesday 12 December 2018 (45864)IOO

Two drawings.  The first shows the layout of the IO GigE cameras 2 and 3, both on the bottom periscope transmitted beam (IMC_IN).  The second shows the change (exaggerated for clarity) of the front face of the PZT mirror (placed on the table vs secured).

Non-image files attached to this comment
stephen.appert@LIGO.ORG - 15:30, Thursday 03 January 2019 (46227)

This mount swap is in reference to IIET Ticket 5132.

The new mount is documented by the below details:

LHO General
corey.gray@LIGO.ORG - posted 16:00, Tuesday 11 December 2018 (45834)
DAY Operator Summary

TITLE: 12/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: None
SHIFT SUMMARY:

CDS Notes:  (1) Reservation System would randomly go blank.  (2) Camera system would switch to access system at inopportune times (icon on bottom would flash orange & then stay solid...maybe for alarm?).
LOG:

H1 TCS (TCS)
corey.gray@LIGO.ORG - posted 14:27, Tuesday 11 December 2018 (45848)
TCS Chillers FAMIS Task (#11469)

Addressed TCS Chillers (14:12-14:22 PST today)

H1 CAL
richard.mccarthy@LIGO.ORG - posted 14:23, Tuesday 11 December 2018 (45847)
PCAL X Temperature Glitches

I disconnected the existing temperature sensors and installed a temporary units right at the 9 pin connectors on the interface chassis.  Monitoring the channels indicated they were much quieter with this setup so I do not think it is the ADC.  Next Tuesday will attempt another experiment with neighboring channels to test for source of glitches.

H1 ISC
marc.pirello@LIGO.ORG - posted 14:13, Tuesday 11 December 2018 (45845)
ESD Driver 48V medium voltage power supply implemented at EY and EX.

Ed, Marc, Richard

The ESD Driver (D1500129) LED limiting resistors were increased to handle 48V per WP7993.  The new +/-48V and +/-18V supplies were also connected and powered up.

The LED modification was applied to the following chassis:

S1500073 - EX

S1500066 - EY

S1500070 - Spare

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 14:09, Tuesday 11 December 2018 (45844)
CDS Maintenance Summary: Tuesday 11th December 2018

WP7984 h1lsc add fast channel

Daniel, Dave:

a new h1lsc model was installed, adding a missing 16k channel to the DAQ.

WP7995 OMC drumhead beason alignment

Keita, Dave:

New h1omc and h1omcpi models were installed.

WP8003 HAM6 Septum Accelerometer

Richard, Dave:

h1pemcs model was changed to add H1:PEM-CS_ACC_HAM6VAC_SEPTUM_Y (acquired at 4kHz). We are using the 11th channel of the 6th ADC.

WP8002 Fader code debugging, temporary add ISI ETMY fast to DAQ

T.J. Dave:

h1isietmy model was changed to add two temporary fast channels for debugging.

Beckhoff SQZ code change:

Daniel, Patrick, Dave:

h1ecatc1plc4 code was changed, and new DAQ INI file was created.

DAQ Restart:

Dave

DAQ was restarted at 13:25 for new h1lsc, h1omc, h1omcpi, h1pemcs, h1isietmy, h1ecatc1plc4 code.

H1 SUS
patrick.thomas@LIGO.ORG - posted 13:58, Tuesday 11 December 2018 (45843)
ETMX charge measurements
Corey, Patrick

I was able to get four measurements without reported errors:

data_2018-12-11-20-23-10
data_2018-12-11-20-37-18
data_2018-12-11-20-51-21
data_2018-12-11-21-05-21

There were a number of errors running the long trend script. I have copied the output into the attached long_trend_log.txt.
Images attached to this report
Non-image files attached to this report
H1 CDS
patrick.thomas@LIGO.ORG - posted 12:03, Tuesday 11 December 2018 (45841)
Changed link in Beckhoff for HAM1 illuminator
Patrick, Ed, Richard

I moved the link in the h1ecatc1 system manager for 'I/O Devices -> Vertex Auxiliary -> Auxiliary LVEA Hub 1 -> Illuminators Input -> Channel 1 -> Output' from 'PLC1 -> Standard -> Outputs -> PslNoiseEaterOut -> IlluminatorRelayOn' to 'PLC1 -> Standard -> Outputs -> HAM1IlluminatorOut -> IlluminatorRelayOn'. I committed the change to svn and restarted. I ended up having to restart the computer, as the LIGO TwinCAT Target Configuration GUI was taking a really long time on 'Activate and run'.

I tested turning on and off the HAM1 illuminator through MEDM, and light appeared and disappeared on some of the camera images.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 11:34, Tuesday 11 December 2018 - last comment - 07:54, Wednesday 19 December 2018(45840)
ITM Photos

Took pictures of face of ITM-X and ITM-y under green light as the IFO unlocked while setting up. Will try to get a set of shots under IR at at least 20W before the holiday break.

There are two shots of each optic at different exposures and focus points.

Optic Frame # Shutter ISO Focus
ITM-Y 111 1.0 sec 6400 1725
  112 1.6 sec 6400 1725
IYM-X 110 3 sec 800 1745
  117 3 sec 800 1625

 

Images attached to this report
Comments related to this report
rana.adhikari@LIGO.ORG - 21:10, Tuesday 11 December 2018 (45857)AOS, COC

to do precise image subtraction in the future (to detect small movement in the point scatterers) we would like the camera position to remain the same. It would be nice, therefore, to design a camera holding jig that would get us back to the same place w.r.t. the viewport. Would be easier to make that analysis quantitiative this way rather than do a lot of image scaling/aligning with camera at different positions.

jeffrey.bartlett@LIGO.ORG - 07:54, Wednesday 19 December 2018 (46065)
   Rana, Very good points. 

   The camera/lens assemblies are bolted to the Viewport Camera Housing (D1500073), which allows for positioning the cameras. This assembly is attached to the viewport on the Spool Flange via the Viewport Guard Assembly (D080367). This provides a rigid and locked positioning of the cameras. The whole mounting assembly is then covered by a light and dust proof housing. 

   The cameras are controlled, focused, and fired remotely, so there is no touching of the actual camera assembly. Unless the system is disturbed is some way the image should not shift in the frame. Also the edges of the baffles and the EQ stop mountings are present in the image, which should provide a fixed point of reference.  

   These are just being deployed and any input to make the system more useful would be greatly appreciated.        

H1 AOS (AOS, SUS)
corey.gray@LIGO.ORG - posted 11:17, Tuesday 11 December 2018 - last comment - 16:22, Tuesday 11 December 2018(45839)
Optical Lever 7 Day Trends (FAMIS #11195)

Have a few oplevs which are approaching their +/-10urad limits, so these could be centered.  Mentioned this to Ed, so it is on his list for next target of opportunity (which could be today for some...)

Pitch Notes:

Yaw Notes:

Comments related to this report
edmond.merilh@LIGO.ORG - 16:22, Tuesday 11 December 2018 (45851)

I re-centered ITMX and ITMY OpLevs. ITMX gain was changed due to an unexplained, post-vent jump in sum cts upwards of 120K. The new value of that sum is ~21K cts. There wasn't enough opportunity today to address other suspensions. Updating of DCC documents regarding new settings to follow.

H1 AOS
daniel.sigg@LIGO.ORG - posted 11:10, Tuesday 11 December 2018 - last comment - 17:41, Tuesday 11 December 2018(45838)
Squezeer laser power drift due to polarization and EOM birefringence

Nutsinee Daniel

We identified some of the laser power drift that we observed after the (red) EOM to be due to a small polarization error and the birefringence of the EOM. Due to a manufacturing error in the Faraday isolator preceding the EOM we need to rotate the polarization prior to the EOM. We are using a lambda-half plate but it is not easy to adjust, since we don't have a convenient polarizer in the path. This introduces a small polarization error incident to the EOM. The birefringence of the EOM will then introduced a drift in the polarization due to temperature variations, it will introduce polarization noise due to the TTFSS feedback path to the EOM, and it will introduce RFAM for the SHG modulation frequency. Variations in the polarization angle are then converted into intensity variations by downstream polarizers—compounded by the waveplates which are used for power adjustments.

Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 17:41, Tuesday 11 December 2018 (45846)SQZ

A PBS cube has been installed after the 35MHz EOM in order to 1) minimized the wrong polarization coming out of the EOM and 2) Clean up the polarization before it hits other half-waveplate and cubes downstream. See attached photo for the setup. 

 

Both CLF launch and SHG GR PD spectrum got better at >1kHz as they should be. All the funny features are gone. Sadly there were some other noise today that can't be explained by the EOM (the EOM/PZT crossover is at 38kHz). Could it be temperature drifts due to table open/close? There were also some locking issue today after Beckhoff restart (wrong error signal fed to laser PZT while OPO is locked, fixed now). I'll take another set of data tomorrow morning (this should also let temperature related things stabilize a bit). Note that IR DCPD looks at Mephisto power (the diode was right after the newly installed cube). That one hasn't changed from before (see alog45774). Also attached TTFSS fast path transfer function -- looks normal again.

 

 

 

Images attached to this comment
H1 General
corey.gray@LIGO.ORG - posted 10:50, Tuesday 11 December 2018 (45837)
No Operational EY VEA Phone (Reporting for Rick)

PCal crew not able to call control from from EY VEA (eventually used phone at entrance of EY).

H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 10:02, Tuesday 11 December 2018 (45836)
PSL Weekly Report (FAMIS #10990)

Laser Status:
Front End Power is 32.61W (should be around 30 W)
70W Output Power is 71.3W
Front End Watch is RED
70W Watch is GREEN

PMC:
It has been locked 2 days, 17 hr 3 minutes (should be days/weeks)
Reflected power = 13.38Watts
Transmitted power = 51.76Watts
PowerSum = 65.15Watts.

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

ISS:
The diffracted power is around 2.8%
Last saturation event was 0 days 0 hours and 29 minutes ago (should be days/weeks)
Possible Issues:  No issues to report.

H1 ISC
jenne.driggers@LIGO.ORG - posted 09:23, Tuesday 11 December 2018 (45802)
Monday AM locking

Alog from yesterday morning, forgot to post.  No exciting details though.

Hang and I tried a few more times to set up the SOFT dither loops, without success / understanding so far. We'll try again this afternoon after maintenance.

LHO General
corey.gray@LIGO.ORG - posted 08:03, Tuesday 11 December 2018 (45833)
Morning Status: Tues Maintenance!

TITLE: 12/11 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.42 μm/s
QUICK SUMMARY:

H1 dropped out 15:42utc (Richard said it was him installing temperature sensor on PCal at EX, but we also have Chris moving scaffolding...but that was probably a little bit later).

Pfieffer is onsite for MX VAC work.

H1 ISC (ISC)
craig.cahillane@LIGO.ORG - posted 06:01, Tuesday 11 December 2018 - last comment - 13:40, Tuesday 11 December 2018(45831)
DARM offset vs Frequency Noise
This is a follow up on 45768.

I plotted the TF from frequency noise to DARM with different DARM offsets from two nights ago in hopes of understanding our high-frequency frequency noise to DARM coupling.  This has only raised more questions.
Our freq to DARM coupling appears to be moving at both high and low frequency by about a factor of 2 on the order of 5 minutes.  Unclear why.

Some details about the measurements:
REFL SERVO ERR Calibration 
(the ADC and whitening gain of 200 are accounted for in the filter module now)
--------------------------------
SumNode = dB2Mag(8.0) # V/V
REFL9Trans = 2900. # V/W
REFL_A_B_BS = 0.5 # W/W, half light on REFL A
CARMgainDC = 15.5e-3 # W/Hz
CARMpole = 0.6 # Hz

Injection Time per Measurement: ~200 s 

The measurements were not really taken in a sensible order, I took the 15.9 pm offset measurements all first, then the 1000-7000 Hz 11.4 pm meas, then the 1000-7000 Hz 3.8 pm meas, then the rest of the 11.4 pm. I mention this because the freq to DARM coupling seems to change more with the time the measurement was taken than anything else.

Questions
1) The linear coupling appears to change significantly between measurements.  While the DARM offset changes may be able to explain some of the coupling change, there are swings completely independent of the DARM offset.  These measurements were taken ~two hours after we had locked at 20 W, so the swings are probably not thermal either.
2) There are changes in the linear coupling at both low and high frequency.  The low frequency is thought to be dominated by radiation pressure/contrast defect effects.  The high frequency coupling is not understood, and thought to be dominated by higher-order-modes, but we have no theory of this.
3) The nonlinear low-frequency coupling for the 1000-7000 Hz injections is probably due to excess OMC length control sensing noise from the frequency noise.  However, it doesn't decrease fast enough with increased DARM offset.  More data needed.
4) These injections used an elliptic filter with 150 dB attenuation.  This was the max attenuation that foton allowed me.  However, I still caused some massive upconversion in the CARM loop when injecting from 20 to 50 Hz.  Unclear why.

Next I would like to do a long-term injection at high frequency and make a spectrogram of the ordeal.  I tried making some spectrograms of these 200 second injections, but was unable to see much change in that time.

EDIT: Question (4)
Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 13:40, Tuesday 11 December 2018 (45842)

When we change the DARM offset we haven't been compensating for the change in the OMC length locking loop ugf.  

About the downconversion:

Since the OMC dither uses the normalized DCPD sum, the ugf of the OMC length loop stays the same as the DARM offset is changed.  This means that for smaller DARM offsets, the OMC length servo imposes more length noise on the OMC for the same amount of DCPD intensity noise caused by a frequency noise injection.  

 

H1 TCS
daniel.brown@LIGO.ORG - posted 04:38, Tuesday 11 December 2018 - last comment - 07:16, Tuesday 11 December 2018(45830)
ETM ring heater common change

Tonight during the PI measurements we switched on the ETM ring heaters commonly to 2.5W. This made our arm-prc mode matching worse shown by a drop in the PRG.

During this time the ITMY HWS measured a reasonable drop in lensing, whereas ITMX did not, which has introduced a differential lensing. I'm not sure why ITMY has been so sensitive to this change. Currently we are down to about 45 and the arm power/RF18/PRG has become choppy looking, previously during large TCS changes when this has happened the choppiness has got worse and we lose lock more readily. However it looks like it might be leveling off around 45 now. Previously when dropping CO2Y power compared to CO2X I also a RF18 increase.

Images attached to this report
Comments related to this report
terra.hardwick@LIGO.ORG - 07:16, Tuesday 11 December 2018 (45832)

We did another step of both ETM RHs up to 4W total each at 14:22 UTC; all ETM RHs off at 15:14 UTC.

H1 CDS (CDS, ISC)
keita.kawabe@LIGO.ORG - posted 16:34, Monday 10 December 2018 - last comment - 06:02, Thursday 13 December 2018(45825)
preview of omc and omcpi model change for drumhead beacon dither

h1omcpi and h1omc were changed and compiled but not installed (that's for Tuesday).

In h1omcpi, a decimation filter was put between the drumhead mode RMS (64kHz) and shared memory as the omc model works at 16kHz.

Alignment dither oscillators are common for deacon and normal dither. An input matrix is used for selecting the source of demod. This makes it cumbersome to switch between low frequency dither for deacon and high frequency dither for normal dither, but once deacon works it won't be an issue.

WP7995

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 16:42, Tuesday 11 December 2018 (45852)

Done.

For now demod matrix is set up to use old dither (H1:OMC-ASC_DEMODMAT_1_1=0, H1:OMC-ASC_DEMODMAT_1_2=1).

Assuming that deacon needs dithering on the order of Hz, I put a 3rd order Butterworth LP at 0.1Hz for power normalization.

For passing drumhead RMS from 64kHz to 16kHz frontend, I used an equivalent of x4 decimation filter in  T1600059 (but the data rate is 64kHz), in this case ellip("LowPass",6,0.3,60,7372.8).

Images attached to this comment
terra.hardwick@LIGO.ORG - 06:02, Thursday 13 December 2018 (45901)

I've populated the control filters in OMC_CUST_DRUMHEAD_EXC with bandpasses around each drumhead mode (I've not set up any of the other control filters). I also cleaned up that medm screen a bit so that drives now go to all test masses correctly. In the main PI screen, I've allocated and set up the 8th downconversion and upconversion blocks for these drumheads. If I populate the BEACON_DRIVE_MTRX, I see signal in the PI drive channels, but I haven't tested beyond that yet.

Modes are: ITMX 8156.7 (A), ITMY 8163 (B), ETMX 8158.6 (C), ETMY 8153.5 (D)

Displaying reports 44061-44080 of 88572.Go to page Start 2200 2201 2202 2203 2204 2205 2206 2207 2208 End