Displaying reports 36701-36720 of 89200.Go to page Start 1832 1833 1834 1835 1836 1837 1838 1839 1840 End
Reports until 14:03, Tuesday 24 December 2019
H1 SUS (ISC)
jenne.driggers@LIGO.ORG - posted 14:03, Tuesday 24 December 2019 - last comment - 14:49, Tuesday 24 December 2019(54093)
MICH_BRIGHT troubleshooting - ETM misalignment offsets were incorrect

[Corey, Jenne]

Corey was struggling with the MICH_BRIGHT step of initial alignment.  He let me know that the guardian kept looping through that set of states, and that MICH wouldn't lock.

Things in general looked fine (as in, the past things that have been struggles with this state), so I started looking at the MICH error signal.  It didn't look fine, even though the beam was reasonably well centered on the AS_A WFS diode.  There were PDH-looking jumps in the error signal, when we expect a MICH-only error signal to be a nice smooth signal.  That pointed me toward looking at the misalignment of various optics (PRM, SRM, ETMs), at which point I noticed that the OFFSET values for the TEST filter banks on the ETMs were zero rather than the ~10urad we normally have (one of the 4 was 0.5, but that's essentially zero for the purposes of intentional misalignment).  I realized afterward that this is why we were seeing IR flashes in the arm cavities according to the front wall TV - we shouldn't see those during MICH-only time, so we'll try to remember that that is a clue as to what is wrong.

These OFFSET values are also used by the new INCREASE_POWER INCREASE_FLASHES states that are helping to get the green arms locked when the optics are quite misaligned (this new state is probably related to why we haven't had to do very many initial alignments lately, which is awesome!).  Perhaps these OFFSET values weren't reverted after the testing work done yesterday with this state or they were left over from some other work or losing lock part way through the new state, so when the ALIGN_IFO guardian tried to misalign the ETMs it correctly turned on the OFFSET, but nothing really happened since the offsets were zero.

I reverted the values via SDF (SDF knew that the values were wrong, but it's hard to know which things that SDF says are differences are the things that are actually causing the problem...), and the initial alignment continued forward as normal.

Since this (incorrect offset values) is something that has caused us trouble a few times lately, TJ has been in contact with StuartA at LLO about modifying the suspension guardian to ensure that the offset values are set correctly every time we request the misaligned state.  We had decided to push this modification to January, but this is a good reminder that we should pick it up soon after the holidays, just in case this happens again.

EDIT: Corrected state name - thank you Corey!

Comments related to this report
corey.gray@LIGO.ORG - 14:49, Tuesday 24 December 2019 (54095)

A Couple of Notes:

1) Above, I believe Jenne means INCREASES FLASHES (vs INCREASE POWER).

2) After getting to NLN, had SDF diffs for SUS ETMy Test Offsets (see attached sdf screenshot).  With Jenne looking over my shoulder we decided to ACCEPT them.

Images attached to this comment
H1 SEI
jenne.driggers@LIGO.ORG - posted 11:19, Tuesday 24 December 2019 - last comment - 14:47, Tuesday 24 December 2019(54091)
CPS DIFF back on, only in the LVEA, not down the arms

Jim suggested this a while ago, and it looks like he and TJ prepared a guardian state for it, but I've just set the nominal for the SEI_DIFF guardian to be CORNER_CPS_DIFF.  This state has all of the vertex CPS DIFF turned on (HAM2-HAM3, HAM4-HAM5, and ITMX-BS-ITMY), but no CPS diff down the long arms. 

The microseism isn't quite high enough right now to see lots of low frequency glitches when the system is on including the arms, so I don't have a good on/off plot to show.  The microseism is increasing though, so hopefully we'll see throughout the day that the low frequency glitches don't increase.

Offline, we'll continue trying to understand how we can use the CPS diff up at higher frequencies to cover the microseism, as well as how we can have it on the arms without causing extra noise.

Comments related to this report
jenne.driggers@LIGO.ORG - 14:47, Tuesday 24 December 2019 (54094)OpsInfo

Operators: This means that (hopefully) there will not be low frequency glitches even with the CPS diff on with these settings, so there should be no need to turn off CPS diff if the microseism gets high.  However, if you find that there are lots of low frequency glitches when the microseism is very high, you could still consider taking the SEI_DIFF guardian to DOWN, which will turn off the whole system and keep it off. 

Dripta is keeping an eye on the summary pages, to see if we start seeing the low freq glitches.

H1 CAL
vladimir.bossilkov@LIGO.ORG - posted 09:26, Tuesday 24 December 2019 - last comment - 13:25, Friday 03 January 2020(54087)
Update to H1CALCS filters

I have prepared an update to the H1CALCS filterbank, for the L1,L2,L3 stages for ETMX and ETMY - as LLO did last month.

The changes incorporate:

I have included a plot of what the new filter for the uim will look like in foton. In the minimum realization step of simplifying this new feature of the model to be foton friendly, a lot of features were cut away, and we're basically left with a single feature at 152 Hz.

If there is some downtime today (like an earthquake from Paraguay), I will be implementing this update, and enabling the new uim filter in the frontend.

Images attached to this report
Comments related to this report
vladimir.bossilkov@LIGO.ORG - 12:54, Tuesday 24 December 2019 (54092)

Turns out other changes need to be made in parallel with this, so this will have to wait until the new year.

vladimir.bossilkov@LIGO.ORG - 13:25, Friday 03 January 2020 (54263)

I made some futher improvements the new new foton transfer functions to better model the UIM changes I had added. See attached plots

Images attached to this comment
LHO General
corey.gray@LIGO.ORG - posted 08:43, Tuesday 24 December 2019 - last comment - 09:38, Tuesday 24 December 2019(54084)
Transition to Day Summary

TITLE: 12/24 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 2mph Gusts, 1mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.26 μm/s 

Microseism is at about 0.2um/s (so will keep CPS Diff ON).  
QUICK SUMMARY:

Niko just finished the PEM Injection.  Since this was slated to be a "Maintenance Day Light", decided to go back into OBSERVING (L1 & V1 were in OBSERVING).

I waived OFF Karen's cleaning at the end stations & LVEA since it wasn't on our list of activities for today.  Speaking of which....

Will transition to PREVENTATIVE MAINTENANCE as soon as we have Accepted Activities begin.  Here are items listed on the board:

* For measurements out on the floor, I was not totally sure as to how to handle BRS.  Texted Jim and he suggested going to:  WINDY_NO_BRSY

Comments related to this report
corey.gray@LIGO.ORG - 09:24, Tuesday 24 December 2019 (54088)

Of course the Earth had to make it interesting on #MaintenanceDayLight! 

While Gerardo and Kyle will be doing work in EY, we just gott an alert for an 6.0 earthquake from northern Argentina.  So we'll have to see how this plays out (since I'll probably be going to the WINDY_NO_BRSY  state for the EY work).  Stay tuned to see how this Maintenance/EQ dance goes! 

corey.gray@LIGO.ORG - 09:38, Tuesday 24 December 2019 (54089)

NOTE:  For Maintenance Day Light, I will be stationed more near the Site Cameras to observe activies there "with my peripheries".  If I observe anything (i.e. entry into EY VEA) which should take us out of Observing, I will certainly do so.  

H1 General
yannick.lecoeuche@LIGO.ORG - posted 08:03, Tuesday 24 December 2019 (54083)
Shift Summary - Owl

TITLE: 12/24 Owl Shift 08:00 – 16:00 (00:00-08:00), all times posted in UTC

STATE of H1: Preventative maintenance

INCOMING OPERATOR: Corey

SHIFT SUMMARY: Quiet shift, nothing to report. Locked 14.5 hours.

LOG:

15:45 (07:45) Leaving Observing to run PEM magnetic injection

H1 General
yannick.lecoeuche@LIGO.ORG - posted 00:07, Tuesday 24 December 2019 (54081)
Ops OWL Shift Transition

Ops Shift Transition: 12/24/2019, Owl Shift 08:00–16:00 (00:00-08:00) - UTC (PT)

State of H1: Locked

Intent Bit: Observing

Weather: 0-5 mph wind

Primary 0.03 – 0.1Hz: 0.01 um/s

Secondary 0.1 – 0.3Hz: 0.3 um/s

Outgoing Operator: Jeff

Quick Summary: Locked and Observing almost 7 hours.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 00:07, Tuesday 24 December 2019 (54080)
Ops Evening Shift Summary
Ops Shift Log: 12/23/2019, Evening Shift 00:00 – 08:00 (16:00 - 00:00) Time - UTC (PT)
State of H1: Locked at NLN, range of 116.1Mpc
Intent Bit: Observing
Support: N/A
Incoming Operator: Niko
Shift Summary: LHO has been Observing for the past 6.5 hours. Although microseism remains high, the round of earthquakes from earlier in the evening has mostly subsided. There are no outstanding issues or problems to report at this time.  
 
Activity Log: Time - UTC (PT)
00:00 (16:00) Take over from Corey
01:19 (17:19) Relocked at NLN & back in Observing
08:00 (00:00) Turn over to Niko
H1 DetChar (DetChar)
sudarshan.karki@LIGO.ORG - posted 21:51, Monday 23 December 2019 (54078)
DQ Shift Report Summary

Sumamry of DQ Shift for the week of 12/16- 12/22.

H1 AOS
jeffrey.bartlett@LIGO.ORG - posted 20:11, Monday 23 December 2019 (54077)
Ops Evening Mid-Shift Summary
 Since relocking at the start of the shift, all has been smooth sailing. We have been triple Observing for the past 2.5 hours. The range is 118.0Mpc. Winds are Light Air. Microseism is still elevated, but the slope is flat. 
H1 General
jeffrey.bartlett@LIGO.ORG - posted 17:39, Monday 23 December 2019 (54076)
Relocked after Vancouver Island Aftershock
   Lost lock at 23:45 (15:45) after a mag 4.9 EQ near Vancouver Island. The IFO was relocked at 01:19 (17:19) without operator intervention. Lost lock twice at INCREASE_POWER. The third time through, made it to NLN and back in Observing. 
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:50, Monday 23 December 2019 (54075)
Ops Evening Shift Transition
Ops Shift Transition: 12/23/2019, Evening Shift 00:00 – 08:00 (16:00 -00:00) - UTC (PT)
State of H1: Unlocked
Intent Bit: Locking
Weather:  Skies are partly overcast. There is a 20% chance of precipitation overnight. The winds are Gentle Breeze. The temperatures are in the lower 40s.    
Primary 0.03 – 0.1Hz: 0.02um/s
Secondary 0.1 – 0.3Hz: 0.2um/s
Outgoing Operator: Corey
Quick Summary: The IFO is relocking after several earthquakes on the Canadian coast. Have lost lock at INCREASE_POWER twice. Microseism is still elevated.    

 

LHO General
corey.gray@LIGO.ORG - posted 16:24, Monday 23 December 2019 - last comment - 15:29, Tuesday 24 December 2019(54074)
Back to OBSERVING: SEI_CONF to WINDY, CPS DIFF is ON

H1 was in OBSERVING for about 40min this afternoon (until a smaller aftershock knocked us out yet again!).  But when we were at NLN, had a couple of SDF Diffs (see attached for channels) for: 

  1. ISI ITMx TRamp (chose to NOT MONITOR)
  2. SEI PROC (ISI_DIFF was in ON state.  This basically means we have the new CPS Diff in the ON state (I phoned Jim and he walked me through this new system).  He suggested we NOT MONITOR this channel, but I think in a rush to get back to OBSERVING, I ACCEPTED instead.)

Note On CPS Diff

This had been OFF, but for some reason it was ON for my most recent lock.  I called Jim and so he could help me out---this is a new system from Jenne, Chiari, & Jim.  I mentioned that with all the EQs, I had tried to transition the SEI_CONF to EARTHQUAKE & Large EARTHQUAKE a few times.  Thinking possibly this is how CPS Diff was turned ON, but that's a guess on my part.  Anyway, it was ON according to SDF & Jim explained it to me.

For better performance in the wind/earthquake bands, we run with CPS DIFF--->  ON (see alog).  Jim suggested to leave CPS Diff ON.  It is good to leave ON as long as the microseism is below 0.4um/s (we are currently at about 0.15um/s).  

If microseism gets above 0.4um/s (and it looks like we are getting glitches in DARM), then we should transition CPS Diff to OFF.  Jim suggested one can do this by going to the SEI_DIFF Guardian Node and taking it from FULL_DIFF_CPS state to the DOWN state.  Alternatively, one can also turn the CPS Diff bit to the OFF state on the Output Limiters medm.  The attached screenshot shows ISI_CONFIG, the SEI_DIFF guardian node, and the LSC Output Limiters medm  (the ways to turn CPS Diff OFF are circled in green & have arrow pointing to them.).

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:14, Tuesday 24 December 2019 (54090)

Thank you, Corey and Jim. 

Jim is right, and I should have used the guardian to turn off CPS DIFF.  Because I had just turned off the DIFF control switch rather than using the guardian, the guardian was able to turn CPS DIFF back on by itself. 

Jim and I implemented at the end of November a decorator in the SEI_DIFF guardian to turn off all SEI DIFF control if any ISI platforms are not in their nominal states.  So, when the platforms tripped due to the recent earthquakes, the SEI DIFF guardian correctly went to its DOWN state.  Since the request was still set to FULL_CPS_DIFF, once all the platforms were back online the guardian turned the CPS DIFF back on.  If I had done the more correct thing, and used the guardian to turn off CPS DIFF when we had high microseism (which would have required a guardian code change to the nominal state), then the guardian would have just stayed in the DOWN state when the ISIs were back online.

corey.gray@LIGO.ORG - 15:29, Tuesday 24 December 2019 (54098)OpsInfo

Tagging OpsInfo.

LHO General
corey.gray@LIGO.ORG - posted 16:19, Monday 23 December 2019 (54061)
DAY Operator Summary

TITLE: 12/23 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 110Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:

Today's shift was dominated by EQs!!!  Only about 52mins of OBSERVING!!! When the Earth gave us a quiet window, H1 would certainly go to NLN, but then we'd get another EQ!


LOG:

LHO General (VE)
kyle.ryan@LIGO.ORG - posted 15:44, Monday 23 December 2019 - last comment - 05:45, Tuesday 24 December 2019(54071)
Corner Station air compressor duty cycle reduced significantly

Upon being made aware that the Corner Station instrument air compressor(s) were creating a measureable noise in the IFO (see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=53248), we have made various attempts to reduce or eliminate this.

Recall that 50 -100 psi is required to hold the 44" pneumatic gate valves GV5, GV6, GV7 and GV8 open.  To do this, we use air compressors and dryers remotely located in the chiller yard and then route this to the LVEA via piping.  The compressors are isolated from the ground via spring mounts and are isolated from the building via a flexible connection to the piping.  Our first attempt at noise reduction was to shut-down the mechanical compressors and dryer, isolate them from the building piping and to then substitute regulated compressed bottled gas (N2) on the building side of the isolation.  This is the preffered solution as it is the quietest but the numerous small leaks-to-atmosphere currently present in the building piping rendered this a maintenance nuisance - requiring frequent bottle changes (see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=53271). 

Next, we realized that the piping leaks which proved a significant loss when using the bottle-supplied gas were quite insignificant when compared to the constant loss-to-atmosphere associated with the continuous regeneration of the "swing style" desiccant dryer when using the compressor system.  For this system, one desiccant tower dries the a majority fraction of the air supplied from the compressors and then routes this dry air the LVEA.  Simultaneously, a minority fraction of the air supplied from the compressors gets routed through the 2nd tower during its regeneration phase.  This "regeneration" air exhausts to atmosphere.  This system works excellent as a drier but is wasteful and requires that a constant supply of compressed air be exhausted to atmosphere.  

The recent configuration changes incude the addition of check valves downstream of the dryer (prevents building air from backflowing to atmospher via regenerating drying tower when the compressor is off), moving the pressure switch sampling from the compressor receiver tank to downstream of the newly installed check valves (prevents compressors from starting if the auto drain depressurizes the compressor receiver tank), the addition of a NC solenoid valve between the compressors and the dryer (prevents compressor receiver tank from supplying regerating drying tower when the compressor is off) and the rewiring of the auto drain solenoid valve such that it only becomes energized when the compressor is running (prevents unnecessarily depressurization of the compressor receiver tank during off periods). 

Non-image files attached to this report
Comments related to this report
chandra.romel@LIGO.ORG - 05:45, Tuesday 24 December 2019 (54082)

Good work, and nice visual!

H1 General
cheryl.vorvick@LIGO.ORG - posted 09:01, Friday 20 December 2019 - last comment - 22:40, Monday 23 December 2019(54008)
OPS Owl Summary:

TITLE: 12/20 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Camilla
SHIFT SUMMARY: an active night for H1, in and out of Observe, currently in Observe
LOG:

Violin Current State:

Comments related to this report
cheryl.vorvick@LIGO.ORG - 22:40, Monday 23 December 2019 (54079)
There's some confusion about verbage in my alog, so to clarify, verbal alarms has only two modes, "observe" and "commissioning," and when I listed H1 in commissioning, I was refering to that distinction in verbal alarms.  For the Observatory Mode, which is is seaparate from verbal alarms, the H1 time out of Observe was Corrective Maintenance.
 
Updated log:
  • 08:53 - H1 in Observe (Intention Bit: Observing) 
  • 11:57 - H1 in commissioning - lockloss, alog 54006 (Intention Bit: Commissioning, Observatory Mode: Corrective Maintenance)
  • 13:52 - H1 in Observe (Intention Bit: Observing) 
  • 14:16 - H1 in commissioning - ITMX mode8 rung up (Intention Bit: Commissioning, Observatory Mode: Corrective Maintenance)
  • 14:43 - H1 in Observe - range at 110Mpc, and violins damping, though beginning of this stretch stil has excess violin mode noise (Intention Bit: Observing) 
  • 15:04 - H1 in commissioning - beam diverter /  SQZ, H1 out of Observe (Intention Bit: Commissioning, Observatory Mode: Corrective Maintenance)
    • this corrected itself for about 3 minutes, then 9 more cycles in about 20 minutes
  • 15:37 - H1 in Observe (Intention Bit: Observing) 
  • 15:38 - H1 in commissioning - beam diverter /  SQZ, H1 out of Observe (Intention Bit: Commissioning, Observatory Mode: Corrective Maintenance)
    • manually cycled the beam diverter, SQZ locked
  • 15:53 - H1 in Observe (Intention Bit: Observing) 
  • 15:55 - H1 in commissioning - beam diverter /  SQZ, H1 out of Observe (Intention Bit: Commissioning, Observatory Mode: Corrective Maintenance)
    • took every SQZ guardian to Down, then Init, then relock
  • 16:00 - H1 in Observe (Intention Bit: Observing) 
H1 ISC (CAL, ISC)
sudarshan.karki@LIGO.ORG - posted 16:44, Thursday 05 December 2019 - last comment - 09:06, Tuesday 24 December 2019(53714)
A2A and A2L to DARM Transfer function

In order to understand the angle to length coupling, we made some A2A and A2L to DARM transfer function measurements, few weeks ago,  using broadband excitations and noticed some phase mismatch between the measurement and the model as seen in the first attachement [AngletoDARM_20191126.png].

In order to make sure the phase mismatch, we observed, was not due to some non-linear coupling due to the high coherence excitations, we made additional measurements using sinusoidal exciations with few different amplitudes. The second and third attachment [ 2019-12-04_A2LEXC_DARM_38W.png and 2019-12-04_A2AEXC_DARM_38W.png] below show similar phase offset that we saw in our broadband injections ( ~10 deg compared to model) for both A2A  to DARM and A2L to DARM measurement. 

Images attached to this report
Comments related to this report
vladimir.bossilkov@LIGO.ORG - 09:06, Tuesday 24 December 2019 (54086)

Since I've been poking around with pyDARM code for a little bit, I notice that there are a lot of corrections for delays. Perhaps the phase error you are seeing comes about from the combition of delays: totalUserDelay, DAC delay,  actuation delay and a specific "unknownPUMDelay"...  there are few more delays maybe.

Have a read in the

/ligo/svncommon/CalSVN/aligocalibration/trunk/Common/pyDARM/src/actuation.py (computeDARM function)

You can use output from that function (actProd), to spit out the transfer functions of the relevant delays, to evaluate at your data points and subtract away.

Displaying reports 36701-36720 of 89200.Go to page Start 1832 1833 1834 1835 1836 1837 1838 1839 1840 End