Displaying reports 49441-49460 of 86137.Go to page Start 2469 2470 2471 2472 2473 2474 2475 2476 2477 End
Reports until 09:11, Tuesday 25 July 2017
H1 PSL
jason.oberling@LIGO.ORG - posted 09:11, Tuesday 25 July 2017 (37761)
PSL Weekly FAMIS Tasks (FAMIS 3660 & 8432)

This morning I completed the weekly PSL FAMIS tasks.

HPO Pump Diode Current Adjustment (FAMIS 8432)

With the ISS OFF, I adjusted the HPO operating currents.  All currents were raised by 0.1 A, changes summarized in the table below:

  Operating Current (A)
Old New
DB1 49.0 49.1
DB2 52.0 52.1
DB3 52.0 52.1
DB4 52.0 52.1

I did not adjust the operating temperatures this week.  I have attached a screenshot of the main PSL Beckhoff screen for future reference.  The ISS is now turned back ON, and the HPO is outputtting ~154.9 W.  This completes FAMIS 8432.

PSL Power Watchdogs Reset (FAMIS 3660)

I reset both PSL power watchdogs at 16:02 UTC (9:02 PDT).  This completes FAMIS 3660.

Images attached to this report
LHO General
thomas.shaffer@LIGO.ORG - posted 08:26, Tuesday 25 July 2017 (37759)
Ops Day Shift Transition

TITLE: 07/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY: Maintenance Day has begun.

H1 General
travis.sadecki@LIGO.ORG - posted 08:01, Tuesday 25 July 2017 - last comment - 01:18, Wednesday 26 July 2017(37758)
Ops Owl Shift Summary

TITLE: 07/25 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  After the initial lockloss of the shift, I have been unable to get past REDUCE_RF45_MODULATION_DEPTH without OMC DCPD saturations.  After the first couple of locklosses at this point, I went stepwise through each guardian state from DC_READOUT_TRANSITION.  While watching the ISC_LOCK log at REDUCE_RF45_MODULATION_DEPTH, it seems that the CHARD P loop never really converges.  It vacillates between converged and waiting for convergence.  If you select any higher guardian state, it will immediately move on when it registers converged and OMC DCPD saturation alarms start.  SRC1_Y error signal on the StripTool starts running away from zero once the DCPD saturations start.  Performed IA after 3rd lockloss during relocking; did not help.  ETMy violin mode 5 has been an unresponsive nuisance during this saga, but I can't say for sure that it is entirely responsible.

On the bright side, PCAL X RX PD seems to have fixed itself at the lockloss from the step at another lockloss reported in alog 37726.  See attached screenshot.
LOG:

Prior to 13:20, see Shift Summary above.

13:20 Called Keita for help

14:25 Lockloss while Keita was working to remove OMC whitening.  We decide to forego trying to relock since maintenance day is starting in 35 minutes.

14:51 JeffB to diode room, then to cleaning area

14:59 JeffK starting TFs on BS and PR3

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 10:35, Tuesday 25 July 2017 (37762)

To operators:

The reason why I wanted to remove whitening was because OMC DCPDs were railing for whatever reason (violin?). As soon as DCPD starts constantly railing it becomes hard to damp violins and PI (Travis had a hard time taking care of PI).

I tried to manually punch in 0 to PDB gain and 2000 to PDA gain quickly enough but it took me longer than I wanted, IFO didn't like it.

I could have written a script to do it quicker, but JeffK later showed me that you can do it in the guardian.

Open OMC_LOCK, then ALL, then MANUAL, then REMOVE_WHITENING (or ADD_WHITENING), and get back to MANAGED.

 

corey.gray@LIGO.ORG - 01:18, Wednesday 26 July 2017 (37783)

Another note (July14th) for REMOVE_WHITENING steps when violins rung up (with note about Manager of OMC_LOCK node):  here.

H1 General
travis.sadecki@LIGO.ORG - posted 02:14, Tuesday 25 July 2017 (37757)
Lockloss 9:10 UTC

All appeared quiet prior to lockloss.  Cause unknown.

H1 General
travis.sadecki@LIGO.ORG - posted 23:58, Monday 24 July 2017 (37755)
Ops Owl Shift Transistion

TITLE: 07/25 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:  No issues handed off.  Lock is 19.5 hours old.

H1 AOS
edmond.merilh@LIGO.ORG - posted 23:55, Monday 24 July 2017 (37754)
Shift Summary - Eve

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

 

 

H1 SEI (DetChar, ISC)
jeffrey.kissel@LIGO.ORG - posted 22:58, Monday 24 July 2017 - last comment - 09:48, Wednesday 02 August 2017(37752)
Test Mass BSC ISI ST2 Drive (i.e. QUAD Cage) Noise Projection to DELTA L EXTERNAL
J. Kissel

Still hunting for what's limiting our range, we took Valera's suggestion to drive stage 2 (ST2) the test masses' BSC-ISIs to check for, among other mechanisms,
  (a) scattered light problems, 
  (b) charge coupling issues, or
  (c) mechanical shorting / rubbing

The measurements indicate that ETMX and ITMY are the worst offenders, in that their ambient noise falls as ~1/f^{1/2} between 10 and 100 Hz, with some resonant features at 70 and 92 Hz. The features are presumably the first few cage bending modes, for which we have Vibration Absorbers that have already knocked down the Q of the ~70 Hz modes, thankfully.

I've used the measurements to "calibrate" the error point of the ISI's ST2 Isolation Loops, and project the ambient noise to equivalent DARM displacement noise (a.k.a. primitive noise budgeting), see first attachment.
Each come within a factor of 3-5 at their worst parts during ambient conditions; too close for comfort.
Also, of course, there should be no such coupling at all if the cage were properly isolated from the suspension, and this appears to be a straight-forward linear coupling.
Note that the precision of the projection is not great -- I did not try hard to get it right. There are addendum plots that show the residual between model and measurement.

I don't think this is a / the limiting source now, since there is little coherence during ambient conditions, but this will certainly be a problem in the future if the coupling remains this bad for ETMX and ITMY. It definitely deserves a more careful calibration, further study with other degrees of freedom, and mapping out a broader frequency band. Perhaps we should check the coherence with these ST2 ISI channels after Jenne's subtraction of jitter (see LHO aLOG 37590) -- though the slope doesn't quite match up (from eye-ball memory).

ITMX's coupling is about 1/2 as bad, and ETMY does not show any visible signs of bad coupling at this excitation level (which is damning evidence that it's related to charge, since ETMY has the largest effective bias voltage at the moment).

%%%%%%% Details %%%%%%%%
Measurement Technique (all while in nominal low noise):
- choose obvious, simply to imagine coupling degrees of freedom: the longitudinal axis for the optics in the arm cavity (X for ETMX and ITMX, Y for ETMY and ITMY)
- measure ambient error signals in those directions using DTT.
- In the same DTT template, create a band-passed excitation where you suspect you're having problems (10-100 Hz), shape it to look roughly like that ambient spectra you see. I used
    ellip("BandPass",4,1,40,10,100)zpk([0.1],[1; 10],1,"n")gain(0.159461)gain(1e-4)
copied and pasted to the 4 excitation banks (thanks Daniel!) so that I can pick and chose what I'm driving, and with what amplitude.
- Grab a bunch of relevant response signals; the excitations, the error signals, the calibrated displacement (the pre-calibrated SUSPOINT signals are especially nice -- though the suffer from spectral leakage up to above 10 Hz).
- Slowly creep up the drive (I started with 0.001 [ct] to be extra careful) until you start to see hints of something / coherence.
- In case the coupling is non-linear, record the results at three different drive levels (I chose factors of three, 500 ct, 1500 ct, and 4500 ct, filtered by the above band-pass.)

Analysis Techniques
- Remember, to calibrate DELTA L EXTERNAL, one must apply the transfer function from
     /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/ControlRoomCalib/caldeltal_calib.txt
i.e. copy and paste that file into the "Trans. Func." tab of the calibration for the channel, after creating a new entry called (whatever) with units "m".
- For calibrated transfer functions of ISI displacement in local meters to DELTA L in global differential arm meters, just plot transfer functions between SUSPOINT motion (which comes pre-calibrated) and DELTA L EXT.
- Store the transfer function between the ISI ST2 ISO error point and DELTA L EXT for the loudest injection
- For "good enough" calibration of the error point, make a foton filter (in some junk file) that looks like the transfer function of error point to DELTA L EXT, and install into DTT calibration for that channel. Guess the gain that makes the driven error-point spectra line up well with the DELTA L spectra. For ETMX this was
    foton design: resgain(70 Hz, Q=8, h=8) * resgain(92 Hz, Q=30, h=10) * zpk(100,1,1)
    equiv zeros and poles: z=[10.6082+/-i*69.1915, 3.42911+/-i*91.9361, 100], p = [4.2232+/-i*69.8725, 1.08438+/-i*91.9936, 1], g = 1
    dtt calibration: 
        Gain: 1e-14 [m/ct]
        Poles: 4.2232 69.8725, 1.08438 91.9936, 1
        Zeros: 10.6082 69.1915, 3.42911 91.9361, 100
For ITMY this was the same thing, but without the 92 Hz resonant feature:
    foton design: resgain(70 Hz, Q=8, h=8) * zpk(100,1,1)
    equiv zeros and poles: z=[10.6082+/-i*69.1915, 100], p = [4.2232+/-i*69.8725, 1], g = 1
    dtt calibration:
        Gain: 1e-14 [m/ct]
        Poles: 4.2232 69.8725, 1
        Zeros: 10.6082 69.1915, 100
This calibrates the channel, regardless of if there's excitation or not (assuming all linearity and good coherent original transfer function) --- in the region where your transfer function is valid, then this will calibrate the ambient noise.

Since I didn't take enough data to really fill out the transfer function, I only bother to do this in the 10-100 Hz, and did it rather quickly -- only looking for factors of ~2 precision for this initial assessment.

So as to not confuse the main point of the aLOG, I'll attach supporting plots as a comment to this log.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 23:05, Monday 24 July 2017 (37753)DetChar, ISC
I attach support plots that show 
For each test mass: The DELTA L EXTERNAL spectra during excitations, along with calibrated displacement of each excitation, the resulting transfer function, and coherence.

For those who may have to repeat the measurement, I attach screenshots of the DTT configuration and what channels I used explicitly. The template's too big to attach, but it lives in 
     /ligo/home/jeffrey.kissel/2017-07-242017-07-24_BSCISI_ST2_BB_Injections.xml

Also, shown for ETMX and ITMY, the projected ST2 Error Point both under excitation and during ambient conditions, with the residual transfer function shown below to expose how poor the calibration is.
Images attached to this comment
sheila.dwyer@LIGO.ORG - 14:40, Tuesday 25 July 2017 (37770)

Jeff and I added his data to the simple noise budget.  We are still using a pre-EQ darm noise in this plot, and you can see that the couplings he found explain some of our unexplained noise around 60-70 Hz.   

Images attached to this comment
jim.warner@LIGO.ORG - 15:33, Tuesday 25 July 2017 (37772)

Adding a couple plots to show that ETMX ST2 coherence to CAL_DELTAL has changed, but measured motion doesn't seem to have changed. First plot is the coherence for 500 averages from the long lock on June 22, 2017 from 18:00 UTC on (in blue) to a similar window from the lock last night (red). The lump at 70-ish hz in red is new, not visible in the pink trace from June. Second plot shows the ST1 L4Cs and ST2 GS13s (both in meters) for the same periods (the June measurement is red and blue, last night are green and brown). The ST2 motion especially is nearly identical around the lump at 70 hz. Talking to Sheila, this maybe implies that scatter at EX is worse now than before.

I looked at all of the other BSCs as well for the lock segment last night, but none of the them showed the same coherence as ETMX.

Images attached to this comment
anamaria.effler@LIGO.ORG - 12:04, Wednesday 26 July 2017 (37791)DetChar, INJ, SEI

For the record, here are two alogs from LLO on tests we've done: 

BSC injections before O2 (when we found the problem with ITMY). We plan to repeat these before the end of the run.

O2 HAM injections (all clear to at least x10 above ambient).

richard.mittleman@LIGO.ORG - 13:08, Friday 28 July 2017 (37851)

If we are making a budget of the stage 2 motion to DARM then we should take into account the rotation motion also, since the bottom of the cage has ~2 meter lever arm

jeffrey.kissel@LIGO.ORG - 13:11, Friday 28 July 2017 (37852)DetChar, SEI
For off-site interested parties, I've committed the above template to the seismic repository here:
    /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/2017-07-24_BSCISI_ST2_BB_Injections.xml
and corresponding key to all of the 100+ references in the template (as well as documentation of measurement times) is in the same location, with a similar name:
    /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/2017-07-24_BSCISI_ST2_BB_Injections_ReferenceNotes.txt
    
richard.mittleman@LIGO.ORG - 09:48, Wednesday 02 August 2017 (37966)

I've replotted some of Jeff's data for the stage to beam direction drive to Darm and added a plot from Ryan and Valera's (24820) similar data. 

  There are the four stage 2 motion to Darm  transfer functions from H1 (I made the ETMY data dotted because it has no coherence)

  There is a 1/f^2 line (light blue) which is what you might expect for the coupling from a charged path on the test mass to a moving charge (not quite a matching slope, but the transfer function phases all look like 0 degrees)

   I wasn't able to recover transfer functions from the LLO data so I plotted the amplitude ratio for the one platform where there is excess signal in Darm (ITMY in green). The vertical black lines mark the limits of where there is excess signal and where you can believe that we have a decent estimate of the transfer function.  The sensitivity on the other LLO chambers is much less (at least a factor of 5)

  One more plug for a rotation measurement, a good measurement of the rotation to Darm transfer function on ETMX and/or ITMY would let us do some geometry to guess at the height of the coupling location (again assuming a point like integration between the cage and the suspension cage)

 

Images attached to this comment
H1 General
edmond.merilh@LIGO.ORG - posted 20:19, Monday 24 July 2017 (37749)
Mid-Shift Summary - Eve

H1 locked for 16 hrs @ 52Mpc. Nothing to report other than some commissioning work that took place.

23:56 a2l/commissioning work

01:05 Intention bit "Undisturbed"

 

H1 PSL (PSL)
edmond.merilh@LIGO.ORG - posted 16:59, Monday 24 July 2017 (37747)
PSL Weekly Report - 10 Day Trends FAMIS #6158

There is evidence of the NPRO trip and current tweaking from last week. Head flows/pressures are being monitored closely on a regular basis, currently. Also included, for your entertainment is a plot of the power stability into the IFO from the rotation stage from the previous 12 hours of lock. Gerardo was questioning the "bouncy" (+/- .1W) numbers of the input power showing on the Ops overview, so we trended it.

Images attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 16:56, Monday 24 July 2017 - last comment - 17:31, Monday 24 July 2017(37748)
Running a2l

23:54 as a segue into some commissioning work. LLO was notified.

Comments related to this report
edmond.merilh@LIGO.ORG - 17:08, Monday 24 July 2017 (37750)

00:07 a2l done. It was a long one. YAW was distinctly out of sorts.

edmond.merilh@LIGO.ORG - 17:31, Monday 24 July 2017 (37751)

00:31 I just realized i hadn't moved the Observatory Mode from Observing to Commissioning.

H1 General
edmond.merilh@LIGO.ORG - posted 16:07, Monday 24 July 2017 (37746)
Shift Transition - Eve

TITLE: 07/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 5mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:

 

LHO General
thomas.shaffer@LIGO.ORG - posted 16:01, Monday 24 July 2017 (37741)
Ops Day Shift Summary

TITLE: 07/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: 11.5 hour lock at 50Mpc, not much else going on.
LOG:

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 15:59, Monday 24 July 2017 (37745)
CDS O2 model restart report: Monday 17th - Sunday 23rd July 2017

model restarts logged for Sun 23/Jul/2017 - Mon 17/Jul/2017 No restarts reported

H1 General (DetChar)
kentaro.mogushi@LIGO.ORG - posted 11:14, Monday 24 July 2017 - last comment - 15:39, Monday 24 July 2017(37740)
Thursday 20th 00:00 UTC - Sunday 23rd 23:59 UTC
The full report can be found on the detchar wiki: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20170720

Below I summarize the main highlights of this shift:

-The duty cycle was 78.5%, the range was stable around 53Mpc.
-We went to out of observation intentionally at 19:13UTC to dump violin mode on Thursday.
-The glitches around 20Hz at 10:00 UTC seem to be due to overflows in all of the test mass L2 coils
, perticularly the pitch motion of soft mode in cavity, similarly at 8:00UTC on Thursday.
-GRB alert occured at 01:49 UTC, 02:48 UTC, 04:31 UTC, 16:16 UTC and 21:11UTC.

Comments related to this report
jeffrey.kissel@LIGO.ORG - 15:39, Monday 24 July 2017 (37744)DetChar, ISC, Lockloss, SUS
Note we also took the IFO out of observation at 1p PT local on Friday (Jul 21 2017 20:00:00 UTC) for planned maintenance and commissioning. Observation down time was 3 hours, and we were back up by July 22 2017 01:00 UTC.
H1 ISC (ISC)
jenne.driggers@LIGO.ORG - posted 12:59, Tuesday 18 July 2017 - last comment - 00:42, Tuesday 25 July 2017(37585)
Only using OMC DCPD B for last 2.5 days

Keita pointed out that we have only been using OMC DCPD B for at least the last lock.  I trended the relative gains of DCPD A and DCPD B, and it looks like we've been in this situation since 16July2017 at around 05:30 UTC.

The attached is a 5 day trend of the gains.  The 2 spikes earlier are when we were either adding or removing a layer of whitening, due to the violin modes being too high.  On the 16th, it looks like the guardian was started to switch the whitening, but then maybe got stopped halfway.  This explains why it has looked like the shot noise was too high the last few days.

Clearly we need to write into the READY_FOR_HANDOFF OMC lock state to ensure that the 2 gains are both at their nominal values.  Also, it looks like someone accepted the wrong values into the Observe SDF file, so we've been able to go to Observing with the wrong values :(  No good.  The safe SDF file was correct.  I'll fix the Observe file.

EDIT:  Looking through the guardian log file, it looks like the code gets a bit confused when you try to use these states before we're using the DCPDs for DARM.  So, now if we're at DC_Readout_Transition or before (and don't need to do any gain ramping), we skip the gain changes and just change the whitening.  If we're on DC_Readout or after, the change will happen as before.  Either way, at the end of the state is now a check to see if the DCPD gains are equal (they should both be 1000).  The new code is in the svn and has been reloaded, although not actually used.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 12:47, Tuesday 18 July 2017 (37587)CAL, DetChar, ISC, OpsInfo
Tagging CAL and DetChar.
jeffrey.kissel@LIGO.ORG - 15:32, Monday 24 July 2017 (37743)CAL, DetChar
The exact time of departure from this configuration is
	Jul 16 2017 05:24:00 UTC (1184217858)
and return to normal is
	Jul 18 2017 18:58:00 UTC (1184439498)

We (the calibration group) have recommended that any observation time within the period be marked with a CAT1 veto, citing that the detector was in a non-O2-standard configuration and the calibration is suspect. 

Yes, it is plausible to reconstruct the calibration during these times, but given our limited person-power we have elected to abandon the effort at this time.
laura.nuttall@LIGO.ORG - 00:42, Tuesday 25 July 2017 (37756)

No problem, I made a flag and inserted it in to the segment database. H1:DCH-CAL_NON_O2_STANDARD_CONFIG:1 captures this time.

Displaying reports 49441-49460 of 86137.Go to page Start 2469 2470 2471 2472 2473 2474 2475 2476 2477 End