aLIGO LHO Logbook

Displaying reports 37481-37500 of 89099.Go to page Start 1871 1872 1873 1874 1875 1876 1877 1878 1879 End

Reports until 13:28, Tuesday 12 November 2019

H1 DAQ (DAQ)

Print this report.

jonathan.hanks@LIGO.ORG - posted 13:28, Tuesday 12 November 2019 (53197)

WP 8461 expanding nds1 connection limits

I installed a new daqd to test raising the connection count for nds1. The server h1nds2 is running a daqd build with a higher connection limit. The code was build from the branch-3.2.x-consumer-limits branch of advLigoRTS. I had to cherry pick 54fca2af32c1643ae2f571cb360526616ea0b158 to update the comm.y file to work with a 'newer' version of bison. It has passed the initial test of running 80 simultanious streams (the fix is not a rearchitecting of the connection and buffer tracking code which would be needed to make it truely arbitrary, but an expanding of the current way of tracking things to hold a few more conenctions).

To test against this server run the following in your shell/console and then launch your program (from that same shell/console):

export LIGONDSIP=h1nds2
export NDSSERVER=h1nds2:8088

or manually connect to h1nds2:8088

H1 CAL (CAL)

Print this report.

richard.savage@LIGO.ORG - posted 13:14, Tuesday 12 November 2019 - last comment - 08:54, Tuesday 10 December 2019(53195)

Update to Pcal

The "Phase" of the OSC9 line for the PCALY excitation at 1153.1 Hz was changed from -15 deg to 0 deg.

The amplitude of the 1153.1 line for PCALX was changed from 5000 to 5007.

The 5007 ct amplitude was determined by looking at the ratio of the Xend to Yend Pcal Rx signals and adjusting the amplitude to bring it clost to 1.

(note that the "Cos Ampl" field was bland for this excitation at Xend; it was updated to match the "Sin Ampl" value.

WIth 0.1 Hz BW and 50 averages, the X/Y ratio of the line amplitudes at 1153.12 Hz was (1.00002236, 1.00005868, 0.999899413) for three consecutive 50-avg measurements.

The original configuration of these lines can be found in entry 51915 in this log from Sept. 11, 2019.

Comments related to this report

jeffrey.kissel@LIGO.ORG - 08:54, Tuesday 10 December 2019 (53791)

On 2019-12-10, the phase change from -15 to 0 deg on PCALY has been accepted in its safe.snap file.

H1 CDS (VE)

Print this report.

filiberto.clara@LIGO.ORG - posted 13:07, Tuesday 12 November 2019 (53194)

HAM4 & HAM6 cabling for signal monitoring of RGA's

Ran cabling from LY vacuum rack to HAM4 and HAM6 RGA's. Slow Controls Vacuum Chassis will need to be modified for new signals.

Network cable was pulled from HAM6 RGA to SUS-R3 patch panel for remote monitoring of the RGA.

H1 PEM

Print this report.

jeffrey.bartlett@LIGO.ORG - posted 12:49, Tuesday 12 November 2019 (53192)

Bi-Monthly Dust Monitor Vacuum Pump Checks (FAMIS #13000)

All three dust monitor vacuum pumps are working great. Made no adjustments to pressures. All temps were well within the specified operations range. Noted no carbon dust accumulation on the mufflers.

Closing FAMIS Task #13000

H1 SEI

Print this report.

jeffrey.bartlett@LIGO.ORG - posted 12:44, Tuesday 12 November 2019 (53191)

Bi-Monthly HEIP Fluid Level Check (FAMIS #13490)

Check of the HEPI fluid levels:

CS at 6 4/16", up 1/16".

End-Y at 8 8/16, no change,

End-X at 7 14/16th, no change.

No apparent leaks and no problems observed.

Closing FAMIS #13490

H1 CAL (CAL)

Print this report.

sudarshan.karki@LIGO.ORG - posted 12:33, Tuesday 12 November 2019 - last comment - 13:48, Wednesday 19 February 2020(53188)

Pcal Simulink model/MEDM updates with new Pcal calibration Coefficients

Vlad, S.Karki, D. Barker

We pushed the Pcal Simulink model and MEDM screen that Shivaraj generated at LLO (LLO alog 49839). The updated suspension filter files (LHO alog 53155) have been loaded into the corrponding Pcal filter banks as well.

The new calibration coefficients have been uploaded to the appropriate EPICS variable using the txt files linked below:

aligocalibration/trunk/Runs/O3/H1/Results/CALCS_FE/lho_yend_pcal_epics_created-20191111.txt

aligocalibration/trunk/Runs/O3/H1/Results/CALCS_FE/lho_xend_pcal_epics_created-20191111.txt

While quacking the susmodel we encounted a number of issues:

1) The filterfile had to be copied to a local directory and qucked there, as the quacking script would give errors concerining the new SOS coefficients (reason unknown)

2) The quack script only updates gains and SOS coeffcients of the respective filter modules. It does NOT update the desgng strings (the commented out lines that describe what the filter is). Attemting to run "foton -c" (something that needs to be done to parse the foton filters correctly) on the filter file would result in foton detecting a difference between the design string and the real filter, and would take the design string and overwrite your brand new filters.

The workaround to the second problem (thanks to Shivaraj) was to delete the design string before running "foton -c", forcing foton to regenerate it.

Comments related to this report

jeffrey.kissel@LIGO.ORG - 11:52, Monday 13 January 2020 (54471)

The first observation ready segment that had these updates included started on Nov 12 2019 at 22:58:33 UTC, i.e. 1257634731.

Thus, prior to these updates, in O3 (i.e. from April 1 2019 to Nov 12 2019) the LHO PCAL Y RX PD (the PCAL PD we use for our absolute displacement reference) had a systematic error of +0.43% -- see the "change" field for LHO Y_end of the RXPD table pg 9 of G1902259. In those slides, the +0.43% is defined as 
    
    xi = [ (after - before) / before ]*100 = [(after/before) - 1]*100.                                    (1) 

*** Note that this definition has been defined previously in Eq. (1) of LHO aLOG 52837.
Which means that the previous relationship between xi and eps still holds,

                          AFTER          NOW           TRUTH            dL_pcal'
           (1 + xi/100) = -----     = ---------   =  ---------   =    --------    = eps.                  (3)
                          BEFORE       EARLIER        APPARENT          dL_pcal
(and I've used the same equation numbering from that aLOG)

This means, for PCAL data prior to Nov 12 2019, should be corrected by 
   PCAL_nosyserror = eps * PCAL_withsyserror = (1.0043) * PCAL_withsyserror                               (2) 
where I've again used the same equation numbering scheme as in LHO aLOG 52837, for consistency.

That means for all measurements taken and processed before Nov 12, they need the following action taken (assuming that I've already applied the necessary 1/f^2 "anti-whitening" filter and AA filter corrections to PCAL_RXPD):

             PCAL_RXPD    DARM_IN1
    A_i  ==  --------- * ----------
              DARM_IN1    i_SUSEXC

                 PCAL_RXPD(TRUTH)    DARM_IN1      eps * PCAL_RXPD(APPARENT)    DARM_IN1
>> A_i(TRUTH) =  ---------------- * ---------- =   ------------------------- * ---------- = eps * A_i(APPRARENT)
                     DARM_IN1        i_SUSEXC                DARM_IN1           i_SUSEXC      

  or
   A_i(NO PCAL SYS ERR) = eps * A_i(W/ PCAL SYS ERR)

      DARM_IN1    DARM_EXC
C ==  --------- * --------
      PCAL_RXPD   DARM_IN2

                    DARM_IN1       DARM_EXC     1           DARM_IN1        DARM_EXC       1
>> C(TRUTH) ==  ---------------- * -------- = ----- * ------------------- * --------   = ----- * C(APPARENT)
                PCAL_RXPD(TRUTH)   DARM_IN2    eps    PCAL_RXPD(APPARENT)   DARM_IN2      eps

  or
   C(NO PCAL SYS ERR) =  (1/eps) * C(W/ PCAL SYS ERR)

The reason I call this out explicitly, is because in O3A (i.e. for LHO aLOG 52837), *ALL* sensing and actuation measurements used to produce the uncertainty budget were "corrupted" by this PCAL systematic error.
This is why, in that aLOG, we could "get away" with just multiplying the *entire response function* and/or h(t) by eps (as shown in Eqs. 6-8 of that aLOG).
 
With the new 2020-01-03 model that's to be installed today we cannot. We've *re*processed data from O3A, and some of the measurements from O3B which are prior to Nov 12 are being used as well -- in the same estimate of A_i and C systematic error as those measured *after* the PCAL fix on Nov 12. 

So, before feeding the A_i and C's from each measurement before Nov 12 in to the measurement collection pool that informs the GPR fitting, I need to correct for eps.

ling.sun@LIGO.ORG - 13:48, Wednesday 19 February 2020 (55183)

I'm not sure I agree with the following eqn:

                 PCAL_RXPD(TRUTH)    DARM_IN1      eps * PCAL_RXPD(APPARENT)    DARM_IN1
>> A_i(TRUTH) =  ---------------- * ---------- =   ------------------------- * ---------- = eps * A_i(APPRARENT)
                     DARM_IN1        i_SUSEXC                DARM_IN1           i_SUSEXC

--> A_i(NO PCAL SYS ERR) = eps * A_i(W/ PCAL SYS ERR)

It seems to me that it should be the other way around. And so does sensing C(truth).

Since eps >1, PCAL_RXPD(truth) is higher than we thought during measurement. And hence the A_i(apparent) is higher than it should be. Hence A_i(truth) should be A_i(apparent)/eps. Or if we regard "eps" as a PCAL "clipping factor" but larger than 1, the A_i measurement should be corrected by 1/eps (see eqn 17 in https://arxiv.org/pdf/1708.03023.pdf).

i.e., A_i(NO PCAL SYS ERR) = 1/eps * A_i(W/ PCAL SYS ERR)

In that case, the kappa_T and kappa_P might have been over estimated (seems that the hard coded kappas before 2019-11-12 are generally >1, while the last three are <1). Then when stacking them together in GPR, because of the higher kappas, the data points before 2019-11-12 are pulled below unity. And 1.0043*1.0043 happen to produce an error about 1%. (e.g., GPR TST, GPR PUM from alog 54907)

H1 GRD (OpsInfo)

Print this report.

sheila.dwyer@LIGO.ORG - posted 11:50, Tuesday 12 November 2019 (53187)

threshold changed for ALS fine tune IR search

Operators have been running into a situation where the ALS IR serach is very sensitive to the dark offsets in the transmon QPDs being wrong. We (Jenne, Betsy and I) discussed raising the threhsold that is used in the fine_tune_IR states (for both comm and diff) I've reset the threshold in ISC_gen_states so that IR fine tune only happens when we have a normalized transmission above 0.1 (10% of on resonance transmission). Previously the threshold was 0.02

I've loaded both ALS_COMM and DIFF guardians, we will see if this helps us avoid operators needing to reset dark offsets in FIND_IR

H1 PSL

Print this report.

jason.oberling@LIGO.ORG - posted 11:31, Tuesday 12 November 2019 (53186)

PSL Power Watchdog Reset (FAMIS 10736)

I reset both PSL power watchdogs at 19:27 UTC (11:27 PST). This completes FAMIS 10736.

H1 AOS

Print this report.

conor.mow-lowry@LIGO.ORG - posted 11:28, Tuesday 12 November 2019 (53181)

PRCL calibration update

Chiara, Conor

We checked CAL_PRCL and despite implementing the M1 calibration change:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=53160
The low-frequency calibration seems to be much improved, right down to the 8mHz AC-coupling cut-off.

There is still the problem of high-frequency excess noise, but for now this will be useful for PRCL/CPS-diff control tests.

Images attached to this report

H1 SUS

Print this report.

rahul.kumar@LIGO.ORG - posted 11:28, Tuesday 12 November 2019 (53183)

OPLEV charge measurements on ETMX and ETMY

Last week the effective bias voltage on the test mass mirrors were showing an upwards trends, hence we decided to take another measurements this week to see how things are going (else this is a monthly exercise now). Seems like ETMX seems to have improved (or rather say distributed the charge) for some quadrants. Overall everything looks to be within limits (which is +-50V). Similarly, on ETMY, there is drop in the charge accumulation (except for the 1nd quadrant for the Pitch, which is above 50V).

All the slider values were restored after the measurements and SDF difference checked and removed.

Images attached to this report

H1 ISC

Print this report.

marc.pirello@LIGO.ORG - posted 11:22, Tuesday 12 November 2019 (53184)

Repaired faulty readback, ASC AS_B_RF72 DEMOD

F. Clara, M. Pirello

We tested the readback channels out of the I&Q Demod chassis (S1001015) located at ISC-R3 position 11. The outputs looked correct, so we followed the signal back to the concentrator chassis located in ISC-R5. We discovered gender changers for both outputs of this chassis which were poorly attached. This loose connection was the cause of the faulty readback. We replaced the DB9 cables and eliminated the gender changers. The new cables are ISC_SQ_306 and ISC_SQ_307 they were both changed from M-M to M-F. This closes WP8465 and solves ALOG53030.

H1 SQZ

Print this report.

daniel.sigg@LIGO.ORG - posted 11:07, Tuesday 12 November 2019 (53182)

Intensity servos

Marc Daniel

Today we checked on a voltage offset problem in the OPO ISS. This manifested itself with a control monitor readback that was several volts different from the drive point input, when the servo was off.

While hooking up the tester we noticed that the gain stages were cross wired through software. This required a TwinCAT fix and restart. Finally, we traced the voltage offset to a busted OmAmp in the ramp input. This device was replaced and the chassis is now working correctly.

LHO VE (DetChar, PEM)

Print this report.

chandra.romel@LIGO.ORG - posted 09:25, Tuesday 12 November 2019 - last comment - 13:48, Tuesday 12 November 2019(53180)

pneumatic gate valves in corner & interesting observation

I increased the pressure at GV 6,8 gate piston from 55 psig (GV6) and 52 psig (GV8) to maximum (~ 85 psig) and then valved out instrument air from compressor and valved in instrument air from bottled N2 in mechanical room. Kyle has already maximized pressure at GV 5,7. GV5 is reading ~90 psig, but GV7 is sitting at 60 psig.

Worth noting that when I increased the pressure at GV6, I heard a noise of the gate moving, suggesting it wasn't fully lifted. A wiggly gate could have been a noise source. Request for DetChar/PEM to measure affects of instrument air (what we've been calling compressor noise) after this change this morning at around 8:30 am local (16:30 UTC). The compressor is not off, but now GV6 gate is fully lifted.

I will monitor the bottle pressure every hour and valve it out and compressor back in before I leave today. We are keeping a spreadsheet of bottle consumption.

Comments related to this report

chandra.romel@LIGO.ORG - 13:01, Tuesday 12 November 2019 (53193)

Valved out bottled gas and valved back in compressor air at 1pm local.

vladimir.bossilkov@LIGO.ORG - 13:48, Tuesday 12 November 2019 (53198)

So I did a little bit more looking around in the Summary pages.

The noises I am talking about here were absent in September (eg, 27th). They are: ~32 Hz and ~11 Hz

I mean ... there are countless other lines above that frequency around there that visually look slimiar, and exist looking back to September. But they do not couple to GW strain (high enough frequecny to be suppressed?)

In just about every single Corner-station related accelerometer in the PEM, you will see (at least) two very bright signals

[https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20191112/pem/accelerometers_corner_beam_tube/]

32Hz visible in all beamtubes

11Hz not visible in Y directions on SRTUBE and MCTUBE

[https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20191112/pem/accelerometers_corner_bscs/]

All BSC 1-3, X and Y

[https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20191112/pem/accelerometers_hams/]

All HAMS 1-6, X, Y, Z

[https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20191112/pem/accelerometers_psl/]

PSL tables and periscope X,Y, Z

We are not locked yet, so I can't speak for the bottom line: the GW strain - but for the time being the noises do not appear to have changed much since 16:30 UTC, at the readout of the accelerometers.

H1 CAL

Print this report.

ling.sun@LIGO.ORG - posted 08:39, Tuesday 12 November 2019 (53179)

Early O3b onlinePE calibration envelopes

This is to document that at the beginning of O3b, before the new O3b uncertainty envelope is ready, onlinePE is using the last C00 O3a envelope:

https://ldas-jobs.ligo.caltech.edu/~ling.sun/Calibration/Uncertainty/O3/LHO/2019-10-01/2019-10-01_O3_LHO_GPSTime_1253974528_C00_RelativeResponse1SigmaUncertainty.png

https://ldas-jobs.ligo.caltech.edu/~ling.sun/Calibration/Uncertainty/O3/LHO/2019-10-01/2019-10-01_O3_LHO_GPSTime_1253974528_C00_RelativeResponseUncertainty_FinalResults.txt

modelparams_H1_20190909

O3_H1_A_MCMC_20190404.hdf5

O3_H1_A_GPR_20190909_multi.hdf5

O3_H1_C_MCMC_20190904_nomconfig_fmin20Hz_finaltrial.hdf5

O3_H1_C_GPR_20190909_nofsQcorr_fmin20Hz_lengthscaleZp5_withPCALXHFdata.hdf5

Also see history in PE git: https://git.ligo.org/pe/O3/calibrationenvelopes/tree/master/LIGO_Hanford

LHO General

Print this report.

patrick.thomas@LIGO.ORG - posted 08:14, Tuesday 12 November 2019 (53178)

Ops Day Shift Transition

TITLE: 11/12 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_CONF state: SC_OFF_NOBRSXY
    Wind: 3mph Gusts, 1mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.24 μm/s 
QUICK SUMMARY: Maintenance has begun. Wind fence work at end X, dismantling of scaffolding at HAM6, charge measurements.

LHO General

Print this report.

corey.gray@LIGO.ORG - posted 08:00, Tuesday 12 November 2019 (53174)

OWL Operator Summary

TITLE: 11/12 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:

Nice night (couple of days) for H1 with it purring along and we had to take it out of Observing for Maintenance.
LOG:

8:52 "GRB Long" received. Will not stand down since it was confirmed to be long (4.096s)
13:00 Control Room computers autobooting.
14:45 got an early PEM Injection alert!
15:06 Wind fence truck arrives (jeff j escorting)
- 15:16 Passing LVEA
- 15:27 arrive at EX
15:45 PEM Injection script run (H1 taking out of OBSERVING & Observatory Mode switched to CALIBRATION for this & will be switched
- This Failed! See alog about this. :(
15:54 Switched Observatory Mode to Preventative Mainteance & transitioned SEI_CONF to SC_OFF_NOBRSXY.
15:55 Everything noticeably got noisier on H1 (i.e. LSC, ASC, tidal signals). Was this due to the SEI_CONF change & noisy truck at EX?
15:56 H1 Lockloss....MAINTEANCE Begins!!

H1 General

Print this report.

edmond.merilh@LIGO.ORG - posted 22:36, Monday 11 November 2019 - last comment - 13:28, Tuesday 12 November 2019(53171)

Late Mid-Shift Report

Craig and I noticed that the 500-1Khz StripTool BLRMS had started angling skyward so I repositioned the legend on the main DARM screen and found the 2nd order harmonics off the top of the range.
With Rahul's damping page I was able to obtain virtually instant results - Changing to DAMPING_ON_SIMPLE changed the intent bit to Commissioning, unfortunately.
- ETMX Mode 13 - turned on gain of +30
- ETMX Mode 16 - turned on gain of +20
- ETMX Mode 11 - turned on gain of +20
  - However, after returning the Violin Guardian node back to nominal and setting the Intent bit back to Observing I looked again at my gain settings to write this aLog and all of the gains are set to their max of 30. ??
All growing violin mode are sufficiently crushed and H1 is back to a comofrtable quiet range of ~166-120Mpc.

Images attached to this report

Comments related to this report

edmond.merilh@LIGO.ORG - 22:47, Monday 11 November 2019 (53172)

5:26UTC H1 to Commissioning

5:48UTC H1 back to Observing

rahul.kumar@LIGO.ORG - 13:28, Tuesday 12 November 2019 (53189)

I had a look at the Guardian state when the damping was applied. It looks like it went from DAMPING_ON_SIMPLE (-13) to TURN_OFF_DAMPING_ALL state (30). The right way is to go from DAMPING_ON_SIMPLE (-13) to IDLE (-15) state and then to Damping_ON_DC (-11). This way Guardian is able to recollect the current status (else the information might be lost).

Images attached to this comment

H1 CAL (ISC)

Print this report.

jeffrey.kissel@LIGO.ORG - posted 16:04, Monday 11 November 2019 - last comment - 13:27, Tuesday 12 November 2019(53162)

Calibration Measurements: Full Suite Today -- First After PCAL Coeffs Updated, Some Exploration of UIM L2A2L

S. Dwyer, S. Karki, J. Kissel 

We gathered the full suite of calibration measurements today; measurement templates listed below. Analysis and commentary to come! 
We're at 38W of PSL input power (33.5 W input to PRM), SRCL offset is at 50 ct. DARM cavity pole (according to calibration line TDCFs) is 411 Hz.

Sensing Function:
2019-11-11_H1_DARM_OLGTF_LF_SS_5to1100Hz_15min.xml

2019-11-11_H1_PCALX2DARMTF_LF_SS_5t1100Hz_10min.xml
2019-11-11_H1_PCALY2DARMTF_LF_SS_5t1100Hz_10min.xml

2019-11-11_H1_PCALX2DARMTF_BB_3min.xml
2019-11-11_H1_PCALY2DARMTF_BB_3min.xml

Actuation function: 
2019-11-11_H1SUSETMY_L1_iEXC2DARM_8min.xml
2019-11-11_H1SUSETMY_L1_PCAL2DARM_5min.xml
2019-11-11_H1SUSETMX_L1_TESTEXC_iEXC2DARM_5to100Hz_17min.xml

2019-11-11_H1SUSETMX_L2_iEXC2DARM_12min.xml
2019-11-11_H1SUSETMX_L2_PCAL2DARM_6min.xml

2019-11-11_H1SUSETMX_L3_iEXC2DARM_12min.xml
2019-11-11_H1SUSETMX_L3_PCAL2DARM_6min.xml

Comments related to this report

sudarshan.karki@LIGO.ORG - 13:27, Tuesday 12 November 2019 (53196)CAL

We did actuation measurement of the UIM stage to see if any angle to length coupling shows up in DARM. We measured the DARM signal by once driving through the L1 TEST that bypasses the drivealign filter bank and later through L1 CAL EXEC that goes through the drivealign filter bank. We didnot see any significant difference between the two measurements as shown in the plots attached below. Another null result but a step towards trying to understand the low frequency calibration.

The scripts used to analyze and generate these plots can be found here:

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Scripts/FullIFOActuationTFs/process_actuationmeas_UIM_DRIVEALIGN_20191111.py

Non-image files attached to this comment

2019-11-11_TESTEXC_H1_UIM_actuationMeasurement_FullMeasvsModel.pdf

Displaying reports 37481-37500 of 89099.Go to page Start 1871 1872 1873 1874 1875 1876 1877 1878 1879 End