Displaying reports 45141-45160 of 88367.Go to page Start 2254 2255 2256 2257 2258 2259 2260 2261 2262 End
Reports until 13:24, Friday 12 October 2018
H1 CDS
david.barker@LIGO.ORG - posted 13:24, Friday 12 October 2018 (44523)
front end syslog logs, ensuring /var/log does not get filled

Looking at the syslog log files on the front end computers shows:

  1. All systems have 2% utilization of /var/log except for h1psl0 (31%) and h1seih45 (30%)
  2. All syslog files have many lines related to inability to log to the central syslogger on occassion
  3. All syslog files have lines related to ntp not able to write to the drift file
  4. h1psl0 and h1seih45 have many lines from monit warning about high system loads

item 4 has been resolved by reconfiguring the /diskless/root/etc/monitrc file on h1boot1 to increase the high loading limit to 8, and not warn on memory or cpu usage. To install this I restarted monit on these systems.

Carlos and I are working on item 2 (central syslogger)

Keith has a solution in place at LLO for item 3 (ntp drift file) which we will implement here.

 

 

H1 DetChar (DetChar, Lockloss)
jeffrey.bidler@LIGO.ORG - posted 11:42, Friday 12 October 2018 (44521)
Lock loss and POP A RF45 Q on 10-4-2018

Jeffrey Bidler, Josh Smith, Andy Lundgren, TJ Massinger, Alex Urban

Following up Keita's Alog post 44420 we check other lock loss times on 10-4-2018 for POP A RF45 Q saturations.
- Out of 8 lock losses on 10-4, 6 show POP A RF45 Q saturating shortly before lock loss.
- It also saturates during lock sometimes
- According to the Alog the filtering of this channel has been changed to fix this problem.
- Summary page overflows page:https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20181004/detchar/overflows/
- Python code to make these plots: CIT: ~lundgren/aDQ/PreO3/FastLocklosses/H1locklosses_20181010.ipynb

we will update soon to add OMC DCPD sum to the plots.

See attached for full conclusions.

Non-image files attached to this report
H1 AOS
robert.schofield@LIGO.ORG - posted 11:27, Friday 12 October 2018 (44520)
ISCT1 motion at sway resonance almost limiting DARM

The highest vibration coupling I have found so far is at ISCT1. The figure shows that, when the motion is increased, especially around the broad 12 Hz resonance, we see noise in DARM in the 30 to 100 Hz region that suggests that we may now or soon be limited by this table motion. The first page shows a broad band injection and the second shows 12 and 70 Hz line injections.

Non-image files attached to this report
H1 SEI (ISC)
brian.lantz@LIGO.ORG - posted 09:07, Friday 12 October 2018 (44516)
study of the SRCL cavity motion inputs

FYI -

I've started to look at the some SRCL questions which Peter F asked. There are some plots in the SEI log 1393 using H1 data from Aug 17, 2017.

Short version - The BW of the SRCL loop is limited by the motion of the SusPoint of the SRM, SR2 and SR3 in the ~ 1-3 Hz region, and this comes from the rx (tilt) motion of HAMs 4 & 5.

I don't see a quick fix for this, but we are talking about it.

-Brian

 

H1 ISC
gabriele.vajente@LIGO.ORG - posted 08:51, Friday 12 October 2018 - last comment - 15:05, Friday 12 October 2018(44513)
Morning lock report
Comments related to this report
gabriele.vajente@LIGO.ORG - 09:20, Friday 12 October 2018 (44515)
  • Another unknown lock loss at abut 8:50am
  • Went directly to NOMINAL_LOW_NOISE
jenne.driggers@LIGO.ORG - 09:21, Friday 12 October 2018 (44518)

DHARD_P gain this last lock was just a bit too high.  I lowered it from -40 to -35.  This gain has been bouncing up and down the last few days, since we started going to 20W.  We need to measure this loop when we have a chance, and also tune the radiation pressure compensation for 20W (it's currently tuned for 10W, and we don't have power-dependent code in there). 

I did not put this gain change into the guardian, since -40 worked earlier today and all yesterday.

haocun.yu@LIGO.ORG - 15:05, Friday 12 October 2018 (44527)

Jenne, Sheila (Sheila, logged in as Haocun by mistake)

We think the problem with DHARD that Jenne is talking about above is due to a bounce mode being rung up a bit. Now that we have dampers they ring down on their own within a couple of minutes so we haven't tried to do anything about this, but if needed we could monitor the amplitude and wait for it to ring down before increasing the DHARD gain. 

H1 ISC
gabriele.vajente@LIGO.ORG - posted 07:31, Friday 12 October 2018 (44514)
OSA script fixed

The OSA script was not working anymore,  due to the recently upgraded workstations:  the new version of matplotlib needed (of course!) different commands to update the figure in real time.

The working script can be found at /opt/rtcds/userapps/release/isc/h1/scripts/osa.py

gabriele.vajente@zotws2:/opt/rtcds/userapps/release/isc/h1/scripts$ ./osa.py --help
usage: osa.py [-h] [-f FILENAME] [-t TIME] [-o OUTPUT] [-r REPROCESS]

optional arguments:
  -h, --help            show this help message and exit
  -f FILENAME, --filename FILENAME
                        File where the time series of sideband and carrier
                        powers will be saved
  -t TIME, --time TIME  Duration of plotting window in seconds
  -o OUTPUT, --output OUTPUT
                        Name of a folder where the average OSA scans will be
                        saved
  -r REPROCESS, --reprocess REPROCESS
                        Reprocess scans from a folder, and save a
                        reprocessed.txt file in there

 

LHO VE
kyle.ryan@LIGO.ORG - posted 21:52, Thursday 11 October 2018 - last comment - 09:14, Friday 12 October 2018(44510)
Noticed low instrument air pressure (< 60 psi) at the Corner Station

I am monitoring from home.  GV5, 6, 7 and 8 will "sag" if this falls below 50 psi. 

Comments related to this report
kyle.ryan@LIGO.ORG - 09:14, Friday 12 October 2018 (44517)

See attached -> I hope to fix today (if we have the parts)

Non-image files attached to this comment
H1 AOS
robert.schofield@LIGO.ORG - posted 21:39, Thursday 11 October 2018 - last comment - 02:47, Friday 12 October 2018(44509)
Some vibration injecting

I am working on a quick check of vibration sensitivity to make sure there are no major issues. I got some injections done tonight. The worst low frequency coupling spot seemed to be ISCT1 (the beam diverter was reportedly closed), but I didn’t get a chance to inject lines in the 100 Hz region. The interferometer lost lock and, at first wouldn’t lock DRMI, but after aligning BS it got up to “DRMI to POP” and lost lock at that stage several times.

Comments related to this report
craig.cahillane@LIGO.ORG - 00:34, Friday 12 October 2018 (44511)
This is likely because of the gain increase added to CARM_TO_ANALOG.  You can safely comment out the last step in that stage.
jenne.driggers@LIGO.ORG - 02:47, Friday 12 October 2018 (44512)

The REFL beam diverter will have been closed, but in O2 we left the POP beam diverter open so we could use the in air POP WFS.  Now that our recycling gain is consistently high, I'd like to transition back to using the in vac REFL WFS for the PRC, as we did in O1. This will allow us to close the POP been diverter for the beam that goes to ISCT1, and hopefully eliminate some of this noise. 

H1 CAL (CDS, DetChar, ISC)
jeffrey.kissel@LIGO.ORG - posted 19:02, Thursday 11 October 2018 (44507)
CAL Group Update
J. Kissel, E. Goetz

Apologies for our lack of reports thus far, but here's an update since we last logged (LHO aLOG 44459).

= Tuesday (10/09)
- Installed a ton of new infrastructure in order to improve the calibration pipeline in prep for O3. This is installing the changes as per ECR E1800246 and IIET: 11305, 5205.
- Worked hard on building MEDM screens in order to identify bugs in our new installation. This resulted in several restarts of the PCAL and CALCS models and the DAQ (see LHO aLOG 44440) that took us to the end of the day.

= Wednesday (10/10)
- Continuing to create / update MEDM screens to reflect the forward looking changes mentioned above
- Measured the actuator transfer functions for the current DARM control configuration (EX L3 ESD with PCALX as reference, EY L2 Coils, EY L1 Coils with PCALY as reference)
- Began to exercise python processing the actuator transfer functions (similar to the python processing of the sensing transfer functions; LHO aLOG 44364), updating the code to work with the new infrastructure.

= Thursday (10/11)
- Diverted attention from completing MEDM screen upgrades and filling in new infrastructure (apologies again, this means the calibration screens are in complete [visual] disarray, and downstream data analysis products will continue to be broken. Thank you for your patience.)
- Continued and finished processing actuator measurements for all actuation stages
    :: Identified that we do not have accurate compensation of the ETMX ESD Driver low pass filters (resulting in a linear-ish frequency-dependent systematic error from 5% too high at 20 Hz to 5% too low at 800 Hz), slightly confusing our estimate of the scalar actuation strength of the stage.
    :: (Re-)Identified that we have the same systematic error above ~30 Hz in our dynamical model of the UIM stage due to non-1/f^6 dynamics known to be present in all QUADs (see LHO aLOG 38295), so we only use ~5 data points to fit.
- Reviewed the MESS of confusing signs to keep track of given our using two PCALs and two QUADs to drive DARM
- Updated the front-end parameters to reflect all new information, including
    :: updating and triple checking the replicas of all digital control filters and gains
    :: updated physical actuator strength coefficients
    :: better and more explicit definitions of each sign flip in each path
    :: newly calculated Sensing to Actuation relative delay
and sadly this failed to produce an accurate low-frequency calibration (with our metric being the PCAL Y 36.7 Hz line showing a discrepancy with DELTAL_EXTERNAL of ~2.6; 331.9 Hz line is still very good after last week's sensing function update [LHO aLOG 44364])
- Measured the PCALX vs. PCALY RX PD (and TX PD) transfer function, worried that PCALX reference calibration is wrong thus giving us a wrong answer for the ETMX ESD actuation strength (merely superstitiously, because we recall the PCAL team's recent work on the PCAL EX laser; see LHO aLOG 44305). Using the same drive frequency, and the same drive *amplitude* (in DAC counts to the AOM), the transfer function ratio between X-end RX and Y-end RX (and similarly in the TXs) was 1.36 (or 0.73). However, we realized that we don't calibrate the drive amplitude, so the same counts amplitude does not necessarily result in the same laser power going out to the test mass (say, if the optical follower servo loop gain surrounding the AOM was different between transmitters).
- Tried adjusting the updated ETMX L3 ESD strength by the 30 Hz discrepant factor of 2.6. Didn't work.
- Remeasured the actuator transfer function of EX L3 ESD with PCALY as reference. The answer is the same within ~3%. No dice. The PCALs are exonerated from the "factors of 2" level problems we're having.

We have reverted all changes to have the calibration it was before we started making actuator changes today (10/11). 
This leaves the calibration wrong at 36.7 Hz by ~25% , and the 331.9 Hz line within 2%.

We'll resume our efforts to understand the discrepancies tomorrow.
Images attached to this report
H1 ISC (IOO, PEM)
sheila.dwyer@LIGO.ORG - posted 17:54, Thursday 11 October 2018 - last comment - 09:53, Friday 12 October 2018(44475)
IMC WFS calibrations and centering

Robert, Sheila

During the long earthquake yesterday afternoon we centered the IMC WFS.  (We didn't measure the spot positions in the IMC before and after because of a problem with the script, which Craig has now fixed.) Then Robert and I calibrated them by making a PZT excitation with the IMC unlocked and MC2 misaligned, and repeating the measurement with the IMC locked at 2W input power.  

We used the ratio of the transfer function of the PZT to the DC signals when the IMC is unlocked (multiplied by sqrt(pi/8)) over the measured transfer function to counts of the RF signals (or locked DC signals) to calibrate counts of the locked signals into beam diameters. 

The templates that we used are in /ligo/home/robert.schofield/templates/IMC_PZT

We found: 

  pit (beam diameters/count) yaw (beam diameters/count)
A I -2e-3 -6.8e-3
B I 5e-5 -1.3e-4
A DC when IMC is locked 8.3e-2 8.3e-2
B DC when IMC is locked 4.0e-2 4.2e-2

 

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 09:53, Friday 12 October 2018 (44519)

In the past, see alog 34845, the difference between locked and unlocked was closer to 1/3. Here it is closer to 1/2. Could this be power dependent?

H1 AOS
jenne.driggers@LIGO.ORG - posted 16:50, Thursday 11 October 2018 - last comment - 17:57, Thursday 11 October 2018(44481)
Thurs AM locking
Comments related to this report
sheila.dwyer@LIGO.ORG - 17:57, Thursday 11 October 2018 (44505)

We added back in the filters in REFLDC BIAS in the TR_CARM step.  If we increase the gain in the IMC board input, we change the gain of the input for CARM, this was probably the cause of problems.  

H1 DetChar (DetChar, ISC, PEM)
andrew.lundgren@LIGO.ORG - posted 14:58, Thursday 11 October 2018 - last comment - 08:02, Thursday 25 October 2018(44495)
56.84 Hz and harmonics in h(t)
During the low noise lock at 4:50 UTC today (Oct 11), there is a comb of lines in h(t) at 56.84 and multiples. They are quite narrow lines. The most interesting characteristic is that they have extreme amplitude modulation.

The first attachment is the h(t) spectrum with the lines marked. The second shows narrow BLRMS around each of the lines. The fundamental at 56.84 Hz has a half-period of about 24 minutes. The amplitude goes very close to zero, and looks very periodic. Each multiple n has zeros in the same place, but the period is n times shorter. Maybe this could be all generated from the fundamental with the right kind of nonlinearity. I'm not sure what would give such a slow but extreme modulation - maybe some centering servo?

The BRUCO results show a lot of channels at End-X coherent. Accelerometers on BSC9 seem to see it, but without amplitude modulation. PCal X sees it in the TX and RX PDs, but stronger in RX; but it doesn't seem anywhere near the level to get into h(t).

Images attached to this report
Comments related to this report
keith.riles@LIGO.ORG - 15:13, Thursday 11 October 2018 (44497)DetChar
The 56.84 Hz comb is a blast from the past.  Here is an entry from March 2013 concerning H2 one-arm data suggesting that the comb could be purely DAQ-related:

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=5806

aidan.brooks@LIGO.ORG - 18:44, Thursday 11 October 2018 (44508)

This one is close enough to the 57Hz ETM HWS that we've seen in the past that I thought I should mention it here. However, we've recently overhauled that system and I've not confirmed what the new frame-rate is yet.

Here's the old analysis: https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=14778

john.zweizig@LIGO.ORG - 00:48, Tuesday 16 October 2018 (44579)DAQ, DetChar
I Looked at an empty EX ADC channel (H1:PEM-EX_ADC_0_08_OUT_DQ) and found that the 58.64 Hz comb is there too, indicating that the comb comes from some source independent of the interferometer (i.e. in the DAQ or RF pick-up). I have attached ASDs of the empty ADC in 0.1mHz bins both for the entire spectrum (0-1024Hz) and near to the 14th 56.84 harmonic (~795.76Hz). I was slightly surprised that a second nearby line (that would explain the amplitude modulation) was not seen even with the 0.1mHz resolution. 
Images attached to this comment
aidan.brooks@LIGO.ORG - 12:59, Wednesday 17 October 2018 (44627)

Yes - the ETM HWS are running at 57Hz. This doesn't mean that this is the issue since it appears to be DAQ related, buuuut .....

aidan.brooks@zotws11:~$ caget H1:TCS-ETMX_HWS_SYNC_FREQUENCY

H1:TCS-ETMX_HWS_SYNC_FREQUENCY 57 Hz

aidan.brooks@zotws11:~$ caget H1:TCS-ETMY_HWS_SYNC_FREQUENCY

H1:TCS-ETMY_HWS_SYNC_FREQUENCY 57 Hz

 

edwin.son@LIGO.ORG - 22:48, Sunday 21 October 2018 (44717)
I've searched EX channels and found some channels where amplitude modulation is seen:

H1:SUS-ETMX_L3_DRIVEALIGN_L_OUT_DQ
H1:SUS-ETMX_L3_ISCINF_L_IN1_DQ
H1:SUS-ETMX_L3_LVESDAMON_LL_OUT_DQ
H1:SUS-ETMX_L3_LVESDAMON_LR_OUT_DQ
H1:SUS-ETMX_L3_LVESDAMON_UL_OUT_DQ
H1:SUS-ETMX_L3_LVESDAMON_UR_OUT_DQ
H1:SUS-ETMX_L3_MASTER_OUT_LL_DQ
H1:SUS-ETMX_L3_MASTER_OUT_LR_DQ
H1:SUS-ETMX_L3_MASTER_OUT_UL_DQ
H1:SUS-ETMX_L3_MASTER_OUT_UR_DQ

Attached plots are BLRMS and zoomed spectrum of H1:SUS-ETMX_L3_DRIVEALIGN_L_OUT_DQ as an example.
The vertical line (orange, dotted) in the zoomed spectrum is at 568.404 Hz (10th harmonics).
Images attached to this comment
rana.adhikari@LIGO.ORG - 20:59, Wednesday 24 October 2018 (44805)AOS, COC, DetChar, INJ, TCS

NO

we moved the Hartmann sync frequency and the lines moved accordingly - its Hartmann, not DAQ.

Why does the Hartmann sensor so strongly couple to DARM?

daniel.vander-hyde@LIGO.ORG - 21:35, Wednesday 24 October 2018 (44806)
Images attached to this comment
aidan.brooks@LIGO.ORG - 08:02, Thursday 25 October 2018 (44815)

With regards to the coupling, the ETM HWS are served by the same power supply as the ring heaters. It's a long shot but it might be worthwhile to try disconnecting the ring heaters from the driver while the to see if the coupling of the 57Hz to DARM is changed.

https://dcc.ligo.org/LIGO-E1100891

 

 

 

Images attached to this comment
H1 ISC (ISC)
craig.cahillane@LIGO.ORG - posted 04:19, Thursday 11 October 2018 - last comment - 17:33, Thursday 11 October 2018(44480)
Frequency Noise Suppression
Locking was very smooth tonight, only two locklosses with three hour or more long lock stretches.  
The excitation test points are broken now for some reason, so I pressed forward with the IMC and CARM noise seen in DARM.

I turned on IMC Boost 2 (zero = 20kHz, pole = 1kHz), paused the IMC_LOCK guardian, and increased the IMC gain by +3 dB at IMC IN1.  This probably put the IMC OLG at around 84 kHz from 40 kHz earlier tonight.

I then increased the CARM gain by +12 dB at IMC IN2 and MCL GAIN, and +3 dB at LSC IN1 for a total of +15dB.  This put the CARM OLG at 12 kHz.  Also noticeable was the drop in optical gain after two hours of being locked vs directly after locking.

I put the increase in IMC gain (IMC IN1 from +25 to +28) in the guardian so I could unpause it overnight, but nothing else is in there yet.  Should probably go in LOWNOISE_LENGTH_CONTROL along with feedforward.

The frequency noise we saw in DARM at 5 kHz has been effectively suppressed.  I could probably push it further, but wanted to leave it locked overnight with these settings.

Other things that are happening or did not happen:
- Did not enable FF in the guardian yet.
- ETMX glitches are relatively frequent, but not causing locklosses
- During LOWNOISE_COIL_DRIVERS, DHARD P rung up super hard but did not cause a lockloss.  This could be the same issue Jenne and Gabriele had earlier.
Images attached to this report
Comments related to this report
craig.cahillane@LIGO.ORG - 17:33, Thursday 11 October 2018 (44503)ISC
The above steps have been added to CARM_TO_ANALOG.  Does not seem to have hurt the locking process, even though this is early in the locking process (2 W).
H1 CDS
jenne.driggers@LIGO.ORG - posted 11:00, Wednesday 10 October 2018 - last comment - 17:44, Thursday 11 October 2018(44465)
DTT not ramping excitations down when using noise injection

DaveB is looking into it, but DTT isn't ramping down excitations using noise injection.  This is something we've been seeing, but usually it just causes saturations.  I think it *may* have caused a lockloss a week or so ago, but it definitely killed a lock today.

I attach an ndscope showing that the excitation just suddenly stops, as well as 2 screenshots showing my excitation and measurement settings.   You can see in the Measurements tab that I've got a rampdown time set for the excitation.

For now, since these are noise injections, I can use awggui for the injection, which doesn't seem to have these same ramp down problems.

I append these screenshots to FRS ticket 11367.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 15:32, Thursday 11 October 2018 (44499)

This could be a repetition of a problem two years ago where the output filter rings for a long time such that at the time the excitation is turned off the output amplitude is still non-zero.

We could only come up with a work-around, using diag to manually control the output gain stage of the awgtpman excitation channel to ramp the output down to zero over a ramp time.

Here is the wiki page describing the work around:

wikipage

Here are the original alogs from 2016:

alog-30258

alog-30315

I was able to reproduce the problem on a PEM-MY test channel (attached plot)

This current problem is covered by FRS FRS-11367

 

Images attached to this comment
jameson.rollins@LIGO.ORG - 17:44, Thursday 11 October 2018 (44504)

I think awggui does ramp down correctly (or at least someone should check) so a good option is for people to just use that for their excitations until dtt can be really properly fixed.

Displaying reports 45141-45160 of 88367.Go to page Start 2254 2255 2256 2257 2258 2259 2260 2261 2262 End