Displaying reports 61441-61460 of 85600.Go to page Start 3069 3070 3071 3072 3073 3074 3075 3076 3077 End
Reports until 10:55, Saturday 09 January 2016
H1 CAL (CAL)
richard.savage@LIGO.ORG - posted 10:55, Saturday 09 January 2016 (24802)
Pcal/DeltaL comparison at high frequencies - driving the Xend Pcal

We are using the Xend Pcal to drive the ETM with single-frequency excitations at high frequencies.

Last night, we got about 8 hours at 4001.3 Hz (roughly 8 PM to 4 AM local time)
We then shifted to 2501.3 Hz at approximately 4 AM local time and got about 6 hours in this configuration before JeffK just switched to 2001.3 Hz..
 
Here is a  proposal for frequencies and excitation times, all assuming we are driving the Pcal at close to full range (35,000 - 40,000 counts, in this case)
Note that the S/N ratio in DeltaL_external will scale as approximately the inverse of the cube of the frequency.
Also note that for each frequency one should scrutinize the DeltaL spectrum to ensure there are no features within a few Hz of the excitation frequency, in which case the excitaiton frequency could be adjusted.
 
1001.3* Hz    1 hour
1501.3 Hz     1 hour
2001.3 Hz     1 hour
2501.3 Hz     2 hours
3001.3* Hz    4 hours 
3501.3 Hz     6 hours
4001.3 Hz     8 hours
4501.3 Hz     12 hours
 
Note that we already have data near this frequency, so this should be saved until the end, if time allows.
 
I suggest we run through the lower frequencies (and shorter times) during the days when calibration folks are around to make the changes, then leave the higher frequencies for the evenings with instructions for the operator to make the changes after enough good locked data is obtained.
 
Instructions for changing Pcal drive frequency:
    Take ifo out of observing mode
    Set Sin Ampl to 0.00, hit return (this should ramp down to zero amplitude, hopefully)
    Set frequency to 2501.3 Hz, hit return
    Set Sin Ampl to 40000.0, hit return
    Accept changes in the SDF system
    Set ifo back into observing mode
H1 ISC (CDS)
jeffrey.kissel@LIGO.ORG - posted 10:53, Saturday 09 January 2016 - last comment - 12:24, Saturday 09 January 2016(24803)
Tried my favored placebo for RF45 Noise
J. Kissel, E. Merilh,

Though we know it *should* have no effect, and there has been no conclusive evidence that it does, while out of intent to change the PCALX line, we moved the set point of the EOM 45 MHz control servo (H1:LSC-MOD_RF45_AM_RFSET) breifly down to 22.4, then up to 23.4, and then back down to its nominal value of 23.2. As usual, it's unclear whether this has done anything. We're now back into observation mode, with the intent bit set. Though the hefty bit of large features has gone away, there remains a bit of broad-band bnoise from 30 to 200 [Hz], and an harmonic streak of glitches in the OMICRON triggers.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 11:33, Saturday 09 January 2016 (24804)
And probably coincidentally, the noise subsided around 19:30 UTC. #facepalm
jeffrey.kissel@LIGO.ORG - 12:24, Saturday 09 January 2016 (24806)
And it's back, since 20:00:00 UTC. #doublefacepalm. I'll stop live tweeting the IFO's noise at this point, 'cause it's only getting me into trouble.
H1 CAL
jeffrey.kissel@LIGO.ORG - posted 10:46, Saturday 09 January 2016 (24801)
PCALX Line Moved to 2001.3 [Hz]
J. Kissel, R. Savage, E. Merilh

While the IFO is screeching with RF45 noise, we've removed the intent bit and changed the 2501.3 [Hz] to 2001.3 [Hz]. In between, to exhonerate the PCALX from the excess noise and gltiching, we left all X-End lines OFF for 5 minutes between 18:26:10 and 18:30:15 UTC. No change in IFO noise characteristics -- still terrible.

The new line is at amplitude 35000 [ct] in the PCAL X oscillator (H1:CAL-PCALX_PCALOSC1_OSC_SINGAIN), and has been on since 18:30:15 UTC (with ramp of 30 secs prior). Attached is the SDF screen shot before we accepted the new values.
Images attached to this report
H1 CAL (DetChar)
jeffrey.kissel@LIGO.ORG - posted 10:09, Saturday 09 January 2016 (24800)
On the thoughts that the temporary(ish) new PCALX Lines are causing excess glitching
J. Kissel

I've come in to Ed mentioning that we've had intermittent RF45 glitching (see LHO aLOG 24789, LHO aLOG 24797), and there are concerns that the new PCAL lines are the source of the problem. I don't think this can be true. Here's why:

(1) The PCAL system is in no way related to the control servo for the 45 [MHz] modulation depth.
(2) The 2.5 [kHz] line (and 4 [kHz] line) had been on for ~6 hours before the first evidence for excess glitch rate / noise from RF45.
(3) The noise/glitchiness from the 45 [MHz] servo is taking on the "classic" behavior of intermittency (~15 minutes from Patrick, on and off for Ed).
(4) The amplitude of the PCAL line (with a ~0.1 [Hz] BW ASD) is just barely above the noise floor, much lower than any other sharp feature (i.e. the violin modes) above 1 [kHz], so I don't think it's a case of these new lines, say, saturating the OMC DCPDs (which is known to cause elevated noise / gltiching, etc.)
(5) The region surrounding these lines is feature free, so it's not a case of these new lines interacting with violin modes and ringing *them* up.

However, in order to get this "high" an amplitude, we are having to drive the Xend PCAL near the limit of it's range. It's not out of the realm of possibility that the PCAL's optical follower servo (OFS) is glitchy / non-linear near the edge of it range. However, again, because both the 4 and 2.5 [kHz] lines had been running for hours before any excess noise or glitchiness had shown up, I don't think this is the case either.

Images attached to this report
H1 General
edmond.merilh@LIGO.ORG - posted 09:09, Saturday 09 January 2016 - last comment - 09:28, Saturday 09 January 2016(24797)
Range glitching

It seems to me that there is a visible amount of noise happening in PRCL and MICH Live between 7Hz and 30Hz. This seems to be a constant state as there is no "breathing" to this condition, at this point. I'll keep watching.

Images attached to this report
Comments related to this report
edmond.merilh@LIGO.ORG - 09:21, Saturday 09 January 2016 (24798)

The RF45 Depth stabilization control, as far as I can see isn't really showing lare glitches but the coherence, in my opinion, looks like its exhibiting a little foolery in the LF area. Is this the EX P-Cal issue?? 

Images attached to this comment
corey.gray@LIGO.ORG - 09:28, Saturday 09 January 2016 (24799)
H1 General
edmond.merilh@LIGO.ORG - posted 08:28, Saturday 09 January 2016 (24796)
Shift Summary -Day Transition

TITLE: Jan 9 DAY Shift 16:00-00:00UTC (08:00-14:00 PDT), all times posted in UTC

STATE Of H1: Observing

OUTGOING OPERATOR: Patrick

QUICK SUMMARY: IFO and environment look to be ok. µSei is at 90th%ile.

LHO General
patrick.thomas@LIGO.ORG - posted 08:22, Saturday 09 January 2016 (24795)
Ops Owl End Shift Summary
TITLE: 01/09 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC

STATE Of H1: Observing @ ~ 77 MPc.
SHIFT SUMMARY: Remained locked entire shift. Took out of observing briefly to change the end X PCAL frequency as requested by Rick. Possible RF45 noise for ~ 15 minutes. A couple of large SUS ETMY saturation glitches.
INCOMING OPERATOR: Ed
H1 DetChar (DetChar, ISC)
andrew.lundgren@LIGO.ORG - posted 05:12, Saturday 09 January 2016 (24794)
DARM noise earlier looks like another manifestation of RF 45
The noise reported earlier in log 24789 looks like another case of RF 45 problems that were not picked up by the monitor.

The first attachment is a spectrogram of DARM showing the burst of noise then a moving comb of lines. We've seen the RF 45 trouble manifest this way before - see log 23269.  Looking carefully at the monitor channel (second plot), one of the lines does appear there, though the burst of noise does not. POP_A_9Q does a good job of witnessing the problem (third plot).
Images attached to this report
H1 General (CAL)
patrick.thomas@LIGO.ORG - posted 04:13, Saturday 09 January 2016 (24793)
Changed end X PCAL frequency
Per Rick's request I changed the end X PCAL frequency from 4001.3 to 2501.3. I went out of observing from 12:01:46 - 12:08:13 UTC to do this. I accepted the SDF difference from doing this (see attached). I followed his instructions:

On the Cal/PcalX/Excitation MEDM screen

    Take ifo out of observing mode
    Set Sin Ampl to 0.00, hit return (this should ramp down to zero amplitude, hopefully)
    Set frequency to 2501.3 Hz, hit return
    Set Sin Ampl to 40000.0, hit return
    Accept changes in the SDF system
    Set ifo back into observing mode
Images attached to this report
H1 General (DetChar)
patrick.thomas@LIGO.ORG - posted 02:03, Saturday 09 January 2016 - last comment - 02:10, Saturday 09 January 2016(24789)
Appearance of large amplitude noise in DARM
09:56:32 UTC SUS ETMY saturated. As DARM spectrum came back down, a large amplitude series of peaks has appeared up to ~ 1 kHz.
Comments related to this report
patrick.thomas@LIGO.ORG - 02:10, Saturday 09 January 2016 (24790)
~ 10:10 UTC Noise appears to have disappeared. There were no obvious changes in any of the other FOMs. RF45 remained on reference. Control signals did not change. No changes in seismic or winds. Violin modes not rung up.
LHO General
patrick.thomas@LIGO.ORG - posted 00:25, Saturday 09 January 2016 (24787)
Ops Owl Beginning Shift Summary
TITLE: 01/09 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC

STATE Of H1: Observing @ ~ 78 MPc.
OUTGOING OPERATOR: Cheryl
QUICK SUMMARY: 
From the cameras:
The lights are off in the LVEA, PSL enclosure and end Y.
I can not tell if the lights are on or off at mid X, mid Y or end X.

Winds are less than 10 mph.

From pinging:
CDS WAP is off at the LVEA, end X and end Y.
CDS WAP is on at mid X and mid Y.

Screenshots of the seismic bands and ISI blends are attached.
Images attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 00:15, Saturday 09 January 2016 (24788)
Ops Eve Summary:

Ops Eve Summary: 00-08:00UTC, 16:00-23:59PT

State of H1: Observe

Fellow: Rick

Incoming Operator: Patrick

Shift Details:

H1 General
richard.savage@LIGO.ORG - posted 23:48, Friday 08 January 2016 (24786)
Eve Fellows Shift

Quiet and uneventful shift (as far as we can tell).   Cheryl kept the ifo. locked the whole time at close to 80 Mpc.  The range has trended down a few Mpc over the past seven hours or so.

We had a large tour group in the control room at around 7 pm.

H1 CAL
jeffrey.kissel@LIGO.ORG - posted 20:09, Friday 08 January 2016 - last comment - 23:27, Friday 08 January 2016(24784)
Calibration Finished For the Day
J. Kissel, R. Savage, E. Goetz, D. Tuyenbayev

We've finish the afternoon's worth of full IFO calibration measurements, including broad-band white noise excitation with PCAL into DARM (like LLO aLOG 22191) and true DARM / CARM excitations at given frequencies (like LLO aLOG 23184). We'll analyzed the data in the future, but the times for the injections are as follows:

(All times are 2016-01-09 UTC day)
36.7, 331.9, and 1083.7 [Hz] excitations of CARM 02:00:30 to 02:07:00 UTC
36.7, 331.9, and 1083.7 [Hz] excitations of DARM 02:10:00 to 02:17:00 UTC

Broad-Band excitation from PCALY 18:19:00 UTC to 18:34:00 UTC

Although we plan to analyze the data offline looking at much longer integration times, but .xml templates live here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/PCAL/
A       2016-01-08_H1DARM_PCALY_BBEXC.xml
A       2016-01-08_H1PCAL_TrueDARMCARM_Drive.xml
A       2016-01-08_H1PCAL_TrueCARM_Drive.xml
A       2016-01-08_H1PCAL_TrueDARM_Drive.xml

In addition, we also grabbed 5 minutes of data where we drive the 331.9 [Hz] line in both PCALX and Y, again in CARM and DARM, but *much* harder than normal, such that we can calculate the PCAL's relative calibration with excellent SNR and precision.

We've also turned on an X-end PCAL calibration line at 4001.3 @ 40000 [cts], which we intend to leave in place overnight (i.e. we'll accept in the SDF sysetm, and run it over night). This was turned on at roughly 04:02:00 UTC, attached is the screen shot. 
331.9 excitation of CARM 03:31:00 UTC to 03:36:00 UTC
331.9 excitation of DARM 03:38:00 UTC to 03:43:00 UTC
Images attached to this report
Comments related to this report
richard.savage@LIGO.ORG - 23:27, Friday 08 January 2016 (24785)CAL

Attached is an ASD plot of the DeltaL_external and Xend Pcal Tx PD  signals (both calibrated in meters of displacement) showing the temporary injection at 4001.3 Hz.

Note that the frequency isn't quite right in this DTT plot, apparently a DTT issue - the center frequency of the peak changes slightly as a function of the integration time,  but not centered around 4001.3 Hz.

Images attached to this comment
Non-image files attached to this comment
H1 General
fred.raab@LIGO.ORG - posted 16:15, Friday 25 December 2015 - last comment - 03:40, Saturday 09 January 2016(24477)
Christmas Day LIGO Fellow Report
Nutsinee had a tough time on OWL shift with H1 behaving badly until approx. 15:10 UTC, when it mysteriously improved. But the bad behavior returned around 17:00 UTC for about 30 minutes and I spent some time investigating its cause during this interval. Microseism was not too bad and wind was calm. There was no indication of excess noise on H1:LSC-MOD_RF45_AM_CTRL_OUT_DQ or coherence of that channel with DARM. Looking at a spectrogram of H1:CAL-DELTAL_EXTERNAL_DQ one can see broadband bursts across the bucket turning on and off suddenly (1-s resolution), with durations verying from a few seconds to about 30-40 seconds. Sometimes these were accompanied by loud bursts in the 10-20 Hz region, other times not. I looked for burstiness in other chnnels that was correlated with this. 

There was nothing well correlated in seismometers or microphones (either on the floor or in e-bays) or OPLEVs.  There were strong similarities on ASC-MICH_P and _Y, weaker on DHARD_P and Y, nothing on DSOFT_P and _Y, nothing on CSOFT, very weak similarities on CHARD and SRC2 P and Y. I am not familiar enough with the LSC/ASC couplings to know if this is just leakage of the length fluctuations onto ASC channels or if alignment is causing the problem. I looked at IMC_F an _L, MC2 TRANS which showed no indication that the cause came into the IFO on the light from the IMC. I tried looking at PRC ASC signals but they looked crazy in frequency with no time dependence (??). However SUS-PRM_M3_NOISEMON has large burst in the 10-30 Hz region on all OSEMS. HVETO finds these good for veto channels.

Travis was not finding anything bumping against its limits.

At 19:42:12 we lost lock. This coincides with the arrival of the maximum ground shaking in the 0.03-0.1 Hz from an EQ in Afghanistan, although the 1-3 Hz region showed sharp elevated shaking several minutes earlier. We are having a hard time getting back to locking.
Images attached to this report
Comments related to this report
andrew.lundgren@LIGO.ORG - 03:25, Saturday 09 January 2016 (24791)DetChar, ISC
It looks like the RF45 monitor sometimes does not see the RF45 noise. We will consider three times on the 25th. The reference time is 4 UTC, when there was nothing bad in DARM and the RF 45 was quiet. At 7:30, the RF 45 is obviously bad as seen by the monitor channel. At 17:04, there's very similar noise in DARM, but now the RF45 monitor stays at its reference.

The first plot is DARM for the three times. The shape and amplitude of the excess noise for the two bad times is very similar. The second plot is the spectra of the RF 45 monitor at these times. It easily sees the problem the first bad time, but at the second bad time (corresponding to a burst of noise in Fred's spectrogram) it stays at the reference.

The ASC-MICH channels look to be good witnesses of this noise. I think they're made from RF36, but that should be sensitive to RF45 issues. The third plot is the coherence with h(t) of RF45 and MICH_Y during the reference time. It has a few lines but is otherwise zero. The next plot shows high coherence with both during the first bad time. The last plot is coherence during the second bad time. There's just a tiny bit of coherence with the RF 45 witness. The MICH_Y coherence is basically the same as the other bad time.

This is worrisome because the RF 45 monitor is not always a good witness of the noise in DARM (and other channels). But it doesn't seem to be a problem with noise in the witness channel masking the RF 45 junk. Maybe this points to the problem being somewhere that the monitor is not always able to see.
Images attached to this comment
andrew.lundgren@LIGO.ORG - 03:40, Saturday 09 January 2016 (24792)DetChar, ISC
The reason that there's excess noise in PRM_M3_NOISEMON is just because of the control signal from PRCL. The attached spectrum shows that PRCL gets worse during the bad times, and that's just getting fed to PRM_M3.

In fact, MICH, PRC, and SRC all have a similar noise shelf up to 30 Hz during the bad time. They all involve some RF 45 signal in their production. The POP_A RF9 and RF45 photodiode signals, in the I and Q quadratures, all have similar shelves except for 9Q (second plot). That's the only one that's not used for control, so I think it's seeing the noise impressed by the MICH/PRC/SRC loops all suppressing the RF 45 noise.
Images attached to this comment
Displaying reports 61441-61460 of 85600.Go to page Start 3069 3070 3071 3072 3073 3074 3075 3076 3077 End