Displaying reports 40581-40600 of 88906.Go to page Start 2026 2027 2028 2029 2030 2031 2032 2033 2034 End
Reports until 11:37, Tuesday 11 June 2019
H1 CAL (CAL)
madeline.wade@LIGO.ORG - posted 11:37, Tuesday 11 June 2019 - last comment - 11:46, Tuesday 11 June 2019(49810)
GDS calibration pipeline filter file update

I pointed the GDS calibration pipeline to the filters file (H1GDS_1243387557.npz) that has been running on the test machine for about a week or so and restarted the GDS calibration pipeline around GPS time 1244312463.  These filters are documented in alog 49587. This restart will also pick up the new installation of gstlal-calibration-1.2.10, which is expected to fix the power mains line subtraction issues seen so far in the run.  The new configuration file is located in 

aligocalibration/trunk/Runs/O3/GDSFilters/H1GDS_1244311784.ini

Comments related to this report
gregory.mendell@LIGO.ORG - 11:46, Tuesday 11 June 2019 (49811)

This completes the install of gstlal-calibration-1.2.10 on the DMT production computers, as per WP 8241.

H1 PSL
jason.oberling@LIGO.ORG - posted 11:08, Tuesday 11 June 2019 (49809)
PSL Power Watchdog Reset (FAMIS 10714)

I reset both PSL power watchdogs at 17:41 UTC (10:41 PDT).  This completes FAMIS 10714.

H1 SUS (PSL)
edmond.merilh@LIGO.ORG - posted 10:20, Tuesday 11 June 2019 - last comment - 08:00, Thursday 13 June 2019(49808)
OpLev Centering - Weekly FAMIS #11325

OpLev centering was done on both ETMS and ITMX. I'm experimenting with compensating the alignments of these to the degrees that they are driven by the loops during an extended NLN lock. I was able to do EX at NLN and get a good 0/0. Unlocked/Aligned I compensated EY with +2u rad in P and +4u rad in Y. ITMX was compensated with +3u rad in P and nothing in Y. Below is a shot of the positions in NLN.

Images attached to this report
Comments related to this report
edmond.merilh@LIGO.ORG - 11:55, Tuesday 11 June 2019 (49813)

So the final settings mentioned in the initial log seem to be relatively accurate. I'm curious to see if these spots move closer to center with alignment convergence.

Images attached to this comment
edmond.merilh@LIGO.ORG - 08:00, Thursday 13 June 2019 (49884)

Looks like my compensatory alignments worked to my favor. After an 18+ hr lock all but one are reasonably well centered.  EY is off but this doesn't surprise me much.

Images attached to this comment
LHO VE
chandra.romel@LIGO.ORG - posted 09:47, Tuesday 11 June 2019 - last comment - 15:04, Monday 17 June 2019(49807)
PT-524 EX vacuum gauge tripped

PT-524 cold cathode vacuum gauge tripped at end-X for unknown reason. Bubba reports that Hanford fire dept was not at that location (their radios sometimes trip gauges). I reset the gauge and waiting for it to come back online.

Comments related to this report
corey.gray@LIGO.ORG - 14:21, Monday 17 June 2019 (50001)VE

Looks like this sensor came back on Friday night at around 5:30pm PDT.

Images attached to this comment
corey.gray@LIGO.ORG - 15:04, Monday 17 June 2019 (50003)
H1 CDS
david.barker@LIGO.ORG - posted 08:52, Tuesday 11 June 2019 (49805)
Fire pump cell phone alarms bypassed until end of maintenance.

Bypass will expire:

Tue Jun 11 12:50:55 PDT 2019

For channel(s):

    H0:FMC-CS_FIRE_PUMP_1

    H0:FMC-CS_FIRE_PUMP_2

 

LHO General
corey.gray@LIGO.ORG - posted 08:19, Tuesday 11 June 2019 (49803)
Transition to DAY Log

TITLE: 06/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Unknown
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 14mph Gusts, 12mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

H1 was not in observing due to SUS computer issue overnight, so we were not in OBSERVING.  Maintenance Day is well under way.

H1 General
jim.warner@LIGO.ORG - posted 07:55, Tuesday 11 June 2019 (49802)
Shift Summary

TITLE: 06/11 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Unknown
INCOMING OPERATOR: Corey
SHIFT SUMMARY: It was fine. Now it's hosed.
LOG:
13:38 The OS on the SUS HAM2 computer crashed, now we're in the weird state where we are locked, but can't go to observe

H1 General
jim.warner@LIGO.ORG - posted 06:48, Tuesday 11 June 2019 - last comment - 13:59, Tuesday 11 June 2019(49799)
Something just crashed in SUS, knocked out of observing

Just got a bunch of SW watchdog tripped notifications and got kicked out of observe, but we are still locked. All of the fields for the large HAM2 suspensions on the CDS overview are white, as well as H1IOPSUSH2A. I've called Dave, he's looking into it.

Comments related to this report
david.barker@LIGO.ORG - 07:11, Tuesday 11 June 2019 (49800)

The general core on h1sush2a (the one which runs the operating system) has crashed, but the five locked cores which run the models (h1iopsush2a, h1susmc1, h1susmc3, h1susprm and h1suspr3) continue to function. This means the suspensions are still working, but the EPICS reporting has failed. Because the SDF channels are no longer available for these models, Guardian will not allow H1 to go into observation mode.

We have seen this type of crash before, the only recovery action is to isolate h1sush2a from the Dolphin fabric and reset the computer using its front-panel switch. Given that maintenance starts in less than an hour and LLO has just dropped out, we will fix this problem during maintenance.

Images attached to this comment
david.barker@LIGO.ORG - 07:19, Tuesday 11 June 2019 (49801)

image shows that DAQ data from h1sush2a is frozen from 13:37 UTC (06:37 PDT). 

Images attached to this comment
jonathan.hanks@LIGO.ORG - 09:28, Tuesday 11 June 2019 (49806)
Snapshot of the console w/ the kernel crash dump.
Images attached to this comment
david.barker@LIGO.ORG - 13:59, Tuesday 11 June 2019 (49817)

opened FRS13004. Then closed it as resolved (h1sush2a was rebooted).

H1 General
cheryl.vorvick@LIGO.ORG - posted 00:01, Tuesday 11 June 2019 (49798)
OP Eve Summary:

TITLE: 06/11 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:
LOG:

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 21:10, Monday 10 June 2019 (49786)
homodyne measurements today

The preliminary message from today's squeezing measurements on the homodyne is that it seems like we do not have any large extra losses or phase noise when we are measuring using the homodyne, using the PSL as a local oscillator.  I will continue and do these measurements for a few different nonlinear gains during tomorrow's maintenance window.

Earlier today I went to HAM6 while Jenne and Georgia were working on increasing the input power to make some squeezing measurements on the squeezer.  I mostly followed Haocun's procedure on the git wiki: Measurement procedure

Since I used the PSL LO, there was only about 0.75mW of total LO power available, so that is what I used.  The table below shows visibility measurements taken in both the positive and negative homodyne arms, the first set was after my first attempt, I then realized that I had messed up the balancing of the homodyne, and went to a couple of meetings.  After I came back, I got the second set of measurements.  In both cases the asymmetry between the two arms I think indicates that the balancing isn't that good, but since the shot noise spectrum looked flat I went ahead with the measurements anyway.  

I noticed that when I looked at the intensity noise on the LO, in either arm of the homodyne, there is a large whistling line.  It also shows up in the squeezing spectrum, although much smaller. 

dark offset = -1.3e-3V        
max -3.56 3.3 2.93 -3.15
min -80e-3 66e-3 24e-3 -40e-3
vis 96% 96% 98% 98%

For the nonlinear gain I measured 79.5 counts on the OPO IR diode without green, and locked the maximum amplification gave 139 counts, de-amplification gave 56.5 counts, so that is a nonlinear gain of 1.75 or x=0.244

The data is saved on a floppy disk, so plots can be produced.  I read off the display 3.5dB of squeezing and 4.7dB of anti squeezing.  With the total efficiency of 0.9 (escape efficiency= 0.98, VIP transmission= 0.96, visibility^2 = 0.96, quantum efficiency=0.99), and no phase noise, we would expect 3.6dB of squeezing and 4dB of anti squeezing, so this is actually a little bit too much anti squeezing.  

For the homodyne visibility measurements, I used the guardian state LOCKED_SEED_HIGH, but made some changes to thresholds, and added those thresholds to the sqzparams file.  I had trouble using the LO guardian for the homdyne, and since it is difficult to debug guardian code on the imacs, I just closed and opened the LO loop manually.  

H1 ISC
georgia.mansell@LIGO.ORG - posted 18:38, Monday 10 June 2019 (49795)
A quick frequency noise to DARM measurement

During our commissioning window today I re-ran the noise budget template for frequency noise coupling to DARM, to check if anything changed when we increased the input power from 35W to 37W (and also increased the CO2X power from 0.7W to 0.8W last week).

The first attachment shows a REFL_A to DARM TF, comparable to the purple trace in Sheila's comment here. These transfer functions look the same which is good.

The second attachment shows DARM, REFL_B and REFL_A spectra during the noise budget injection, the traces currently used in the noise budget currently are shown in black (data taken in early May). Note squeezing was not being injected during these times. Today I ran two sets of frequency noise injections:

  1. with REFL_A and REFL_B sensors both in the CARM loop (mint green and blue traces)
  2. with REFL_A only in loop, so that REFL_B can be used as an out-of-loop frequency noise sensor (pink, and brown traces) - this is what we actually use in the noise budget.

The DARM BLRMS suggest that I caught a low-frequency glitch at the end of my injection with REFL_A only in loop, hence the extra noise below 80Hz in the pink trace. So I won't put this data in the noise budget but we should re-do this measurement, since the frequency noise coupling looks much better above ~300Hz now compared to what we measured in May.

Images attached to this report
H1 CDS
thomas.shaffer@LIGO.ORG - posted 17:53, Monday 10 June 2019 (49794)
External Alerts now received from LVAlert

WP8234

Jonathan set me up with systemd monitoring of the LVAlert listener that I have been running for the past month. This will replace the GraceDb polling that we used to get candidate events, GRBS, etc. We will continue to run the GraceDb polling in parallel for now, but it will be stopped in the near future.

For more information about this system see: https://cdswiki.ligo-wa.caltech.edu/wiki/ExternalAlertNotification

H1 OpsInfo
jenne.driggers@LIGO.ORG - posted 16:50, Monday 10 June 2019 (49793)
Instructions for reverting powerup, if required

Operators, if the IFO is having trouble tonight, particularly due to PI modes (you could check a spectrum of H1:OMC-PI_DCPD_64KHZ_AHF_DQ versus the beginning of the lock), you can revert the PSL power back to 35W. 

I copy here the instructions that Sheila left in alog 49680, since they are the same:  "We are going to leave the input power request set to 37W, if there are any problems with this it can be undone by going to userapps/h1/guardian/lscparams.py and changing NLN power to 35 on line 17 and hit load on ISC_LOCK, and on LASER_POWER."

H1 ISC
jenne.driggers@LIGO.ORG - posted 16:45, Monday 10 June 2019 - last comment - 15:12, Wednesday 12 June 2019(49783)
Power up today

Summary: IFO running at 37 W PSL input.  ETM ring heaters increased to avoid PI ring ups (so far, successful). LSC FF measurements done. CAL sensing function measurements done. (Note: New feedforward filters are not installed, I've just taken measurements for the fits).

Comments related to this report
georgia.mansell@LIGO.ORG - 19:43, Monday 10 June 2019 (49796)TCS

I took a quick look at the ITMY HWS, comparing last night's lock (first attachment) and today's lock (second attachment). Last night we had 35W input power, today we have 37W and new spot positions (A2L gains shown in the attachments).

The two point absorbers are clearly visible in the contour and quiver plots. It looks like with the updated spot positions we might have moved further from the main absorber and are sitting between it and the smaller absorber above it. This seems consistent with the ITMY P2L gain being further from zero.

The other Hartmanns are not as clear as ITMY.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 15:12, Wednesday 12 June 2019 (49859)CAL
Sensing function measurements have been saved and committed to here:
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/
        2019-06-10_H1_DARM_OLGTF_LF_SS_5to1100Hz_15min.xml
        2019-06-10_H1_PCAL2DARMTF_LF_SS_5t1100Hz_10min.xml
LHO General
patrick.thomas@LIGO.ORG - posted 16:14, Monday 10 June 2019 (49792)
Ops Day Shift Summary
TITLE: 06/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Commissioning for majority of the day. Jenne worked on 37 W. Sheila worked on squeezer measurements. Taking calibration sensing function measurement at end of shift.
LOG:

15:58 UTC Rick and Sundae to optics lab
Jeff B. working in receiving bay, opening rollup door
16:24 UTC Karen to mid Y
16:39 UTC Jeff B. done in receiving bay
16:59 UTC Changed to commissioning mode, Sheila to HAM6 area to start squeezer measurements, Jenne working on increasing power
17:08 UTC Lock loss
17:09 UTC Ed taking car to shipping and receiving
17:16 UTC Jason to optics lab
17:19 UTC Karen leaving mid Y
17:25 UTC Jason back
17:25 UTC SEI_CONF to EARTH_QUAKE
17:43 UTC Kyle to mid Y
18:00 UTC GRB alert (E335886), not locked, ignoring
18:09 UTC Gerardo back from HAM5
18:11 UTC Gerardo to mid X
18:53 UTC Gerardo back
19:06 UTC Kyle back
19:23 UTC Hugh to roof, staying on observation platform
19:28 UTC Hugh back
20:00 UTC GRB alert (E335892), in commissioning, ignoring
20:26 UTC Amber filling LN2 dewar from tank
20:31 UTC Niko and Sundae to laser lab
20:42 UTC Lock loss
21:56 UTC Sheila to HAM6
22:07 UTC Gerardo to mid X
Displaying reports 40581-40600 of 88906.Go to page Start 2026 2027 2028 2029 2030 2031 2032 2033 2034 End