Displaying reports 66261-66280 of 83224.Go to page Start 3310 3311 3312 3313 3314 3315 3316 3317 3318 End
Reports until 11:05, Tuesday 24 March 2015
H1 CDS
patrick.thomas@LIGO.ORG - posted 11:05, Tuesday 24 March 2015 - last comment - 13:38, Tuesday 24 March 2015(17425)
Conlog down again
This time I caught it on the test stand with better error reporting.

Test stand code error:

Mar 24 10:14:29 conlog-test-master conlogd: Channel Access Exception: Channel Name: Unavailable, Native Type: Unavailable, Native Count: 0, Read Access: Unavailable, Write Access: Unavailable, IOC: Unavailable, Message: Virtual circuit disconnect, Context: h1asc0.cds.ligo-wa.caltech.edu:60755, Requested Type: TYPENOTCONN, Requested Count: 0, Source File: ../cac.cpp, Line Number: 1214
Mar 24 10:55:15 conlog-test-master conlogd: ../database.cpp: 661: insert_dbr_string_value_execute: Error executing m_p_insert_dbr_string_value_prep_stmt. Parameters: H1:SYS-MOTION_Y_SHUTTER_A_NAME, 1427219715488583185, 0, �, 0, 0.
Mar 24 10:55:15 conlog-test-master conlogd: ../conlog.cpp: 314: process_cac_messages: MySQL Exception: Error: Incorrect string value: 'xC0' for column 'value' at row 1: Error code: 1366: SQLState: HY000: Exiting.
Mar 24 10:55:16 conlog-test-master conlogd: ../conlog.cpp: 346: process_cas: Exception: boost: mutex lock failed in pthread_mutex_lock: Invalid argument Exiting.

Seems to have non ascii characters in the value of the H1:SYS-MOTION_Y_SHUTTER_A_NAME channel.

Production code error:

Mar 24 10:14:29 h1conlog1-master conlog: Channel Access Exception: Channel Name: Unavailable, Native Type: Unavailable, Native Count: 0, Read Access: Unavailable, Write Access: Unavailable, IOC: Unavailable, Message: Virtual circuit disconnect, Context: h1asc0.cds.ligo-wa.caltech.edu:60755, Requested Type: TYPENOTCONN, Requested Count: 0, Source File: ../cac.cpp, Line Number: 1214
Mar 24 10:17:01 h1conlog1-master CRON[21576]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 24 10:39:01 h1conlog1-master CRON[21583]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 24 10:55:25 h1conlog1-master conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Incorrect string value: 'xEC>xBF' for column 'value' at row 1: Error code: 1366: SQLState: HY000: Exiting.
Mar 24 10:55:26 h1conlog1-master conlog: ../conlog.cpp: 331: process_cas: Exception: boost: mutex lock failed in pthread_mutex_lock: Invalid argument Exiting.

They may have failed on different channels, but this narrows it down.
Comments related to this report
patrick.thomas@LIGO.ORG - 13:38, Tuesday 24 March 2015 (17431)
Rescanned the channel list, no changes. Restarted Conlog. 28 unmonitored channels:

H1:ALS-X_REFL_B_DC_GAINSETTING
H1:ALS-X_REFL_B_DC_HIGH
H1:ALS-X_REFL_B_DC_LIMITS
H1:ALS-X_REFL_B_DC_LOW
H1:ALS-X_REFL_B_DC_NOMINAL
H1:ALS-X_REFL_B_DC_OFFSET
H1:ALS-X_REFL_B_DC_RESPONSIVITY
H1:ALS-X_REFL_B_DC_SPLITTERR
H1:ALS-X_REFL_B_DC_TRANSIMPEDANCE
H1:ALS-Y_REFL_B_DC_GAINSETTING
H1:ALS-Y_REFL_B_DC_HIGH
H1:ALS-Y_REFL_B_DC_LIMITS
H1:ALS-Y_REFL_B_DC_LOW
H1:ALS-Y_REFL_B_DC_NOMINAL
H1:ALS-Y_REFL_B_DC_OFFSET
H1:ALS-Y_REFL_B_DC_RESPONSIVITY
H1:ALS-Y_REFL_B_DC_SPLITTERR
H1:ALS-Y_REFL_B_DC_TRANSIMPEDANCE
H1:GRD-TCS_ITMY_LOGLEVEL
H1:GRD-TCS_ITMY_MODE
H1:GRD-TCS_ITMY_NOMINAL_S
H1:GRD-TCS_ITMY_REQUEST
H1:GRD-TCS_ITMY_REQUEST_S
H1:GRD-TCS_ITMY_STATE_S
H1:GRD-TCS_ITMY_STATUS
H1:GRD-TCS_ITMY_TARGET_S
H1:SUS-SR2_LKIN_P_OSC_SW2R
H1:SUS-SR2_LKIN_Y_OSC_SW2R
H1 AOS (DetChar, ISC, PEM, PSL, SEI, SUS)
gabriele.vajente@LIGO.ORG - posted 10:32, Tuesday 24 March 2015 (17423)
Coherences

The summary of all coherences can be found here:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1111224016

Here is my personal summary: still a lot of coherence with MICH/SRLC/PRCL, angular motion at low frequency, PSL periscope

In general, there are many frequency bands where there is coherence with signals, so it's worth scanning though the main table to see if yopu favorite bump is coherent with something. The list would be too long to be included here.

Images attached to this report
H1 CDS
patrick.thomas@LIGO.ORG - posted 09:53, Tuesday 24 March 2015 - last comment - 10:02, Tuesday 24 March 2015(17421)
Conlog error
Conlog exited with the following error:

Mar 24 09:36:28 h1conlog1-master conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Incorrect string value: 'xB8xEDxFBx99xE8x05...' for column 'value' at row 1: Error code: 1366: SQLState: HY000: Exiting.

Unfortunately the code to do better error reporting with the channel name that caused it is still only in trunk.
Comments related to this report
patrick.thomas@LIGO.ORG - 10:02, Tuesday 24 March 2015 (17424)
Restarted. Also started the test stand computer with the same channel list for better error reporting if it goes down again.
H1 General
edmond.merilh@LIGO.ORG - posted 08:59, Tuesday 24 March 2015 (17419)
Morning Meeting Summary - Maintenance Day

SEI - Jim is installing new osolation filters on BS.  McCarthy may install a new power supply for te EX HEPI pump controller.

SUS - Charge measuring in EY

CDS - RF cab;le pulling between TCS racks. Discuss plugging in rotation stage

Matt is working on TCS X and Y and clearing errors on TCS-X AOM

Bubba found a bad bearing on one of the axial fans. He will be repairing.

3IFO- Bubba installing dewpoint sensors on containers. Jodi ad Gary tagging ISC and Baffle stuff.

Corey working in Squeezer bay

HFD - in LSB doing tests.

H1 General
edmond.merilh@LIGO.ORG - posted 08:12, Tuesday 24 March 2015 - last comment - 16:47, Tuesday 24 March 2015(17417)
IFO RELOCK at LOWNOISE_ESD_ETMY

08:08 IFO fully locked @ ~ 18Mpc  (according to SensMon).

Comments related to this report
edmond.merilh@LIGO.ORG - 08:42, Tuesday 24 March 2015 (17418)

Broke lock @ 08:41 :( Not bad for a maintenance day!

sheila.dwyer@LIGO.ORG - 16:47, Tuesday 24 March 2015 (17440)

It seems as though after dropping lock the IFO came back twice (on its own or with some help from Ed?), with one locking attempt that failed in locking DRMI_1F.  

The attached plots show the guardian state from 13:20 UTC to 16:20, the longest steps in the relocking process are still finding IR and locking DRMI, the long DRMI lock was about 8 minutes, the total time to recover from the lock loss was about 40 minutes (inlcuding the failed attempt), and the second time it took 15 minutes.  

I think we can say that we now have some "one click" locks, unless Ed had to intervene in some way to lock this.    

Images attached to this comment
H1 ISC (DetChar, ISC)
lisa.barsotti@LIGO.ORG - posted 02:28, Tuesday 24 March 2015 - last comment - 22:19, Tuesday 24 March 2015(17411)
ETMY low noise ESD, MICH feed-forward, ASC cut-offs, low noise coil drivers (started), 28 Mpc
Evan, Sheila, Dan, Kiwamu, Lisa 

SUMMARY 

The wind dropped below 20 mph in the evening, and we started locking. After some roll, bounce and violin damping, we made it to DC readout @ 8W. We successfully transitioned DARM to ETMY with low noise ESD and got some MICH feed-forward cancellation going. We improved the noise between 30-200 Hz, and reached  28 Mpc  (according to SensMon). 

The noise was more stationary than  previously observed . 

However,  the OMC is still shaking , and it is not good. Dan has a resonant gain for DARM ready to be tested to reduce the noise around 3 Hz, but we didn't manage to get that done tonight. 

We leave the interferometer locked at 28 Mpc starting at March 24, 2015 9:17 UTC . 


DARM control on ETMY with low noise ESD  

We did the transition from ETMX to ETMY L2 for DARM, but the interferometer was very glitchy, and we decided to abandon L2 control and try the new  Den's strategy  to do the feed-forward to ITM(Y) L2. 
Evan got about a factor of 10 subtraction (FM9 has BS plant inversion in LSC-MICHFF filter bank, gain +0.048). 

ASC cut-off filters 

Since none of the ASC loops had cut-offs, we decided to add  some . They are now engaged by the Guardian. A more fine tuning will happen at some point. 

Started switching coil driver to low noise  

We started switching the coil driver to  low noise . Evan will post a table later with the successful switches we did after acquiring the DRMI lock. We need to do more work on this, some failed.
Comments related to this report
evan.hall@LIGO.ORG - 02:35, Tuesday 24 March 2015 (17412)

Spectra attached.

Images attached to this comment
daniel.hoak@LIGO.ORG - 02:38, Tuesday 24 March 2015 (17413)

Here is a plot of the lingering coherences with LSC DOFs.

Images attached to this comment
gabriela.gonzalez@LIGO.ORG - 05:15, Tuesday 24 March 2015 (17414)
Very nice progress! 
albert.lazzarini@LIGO.ORG - 05:53, Tuesday 24 March 2015 (17415)
Excellent news. Great progress. 
thomas.massinger@LIGO.ORG - 09:48, Tuesday 24 March 2015 (17420)DetChar

This is fantastic progress, congratulations!

For anyone that would like to look at the data quality or run any DetChar tools on this data, the following GPS times can be used:

1111223896 - 1111239923

Duration: 16027 seconds

nergis.mavalvala@LIGO.ORG - 11:52, Tuesday 24 March 2015 (17426)
This entry should make Lisa a contender for her "best log entry" prize. Nice going, everyone!
evan.hall@LIGO.ORG - 22:19, Tuesday 24 March 2015 (17449)

These are the coil driver states that we've been using so far:

OLD PRM PR2 SRM SR2 PR3 SR3 BS
M1   1 1 1 1 1 1
M2   2 2 2 1 1 1
M3 2 2 2 1 1 2

 

OLD IX IY EX EY
R0 1 1 1 1
M0 1 1 1 1
L1 3 3 2 2
L2 2 1 1 1

Now we've managed to switch to the following configuration for acquisition (following the tables in LLO#16565):

ACQ PRM PR2 SRM SR2 PR3 SR3 BS
M1 2 2 1 2 2 2 1
M2 2 3 2 3 3 3 2
M3 2 2 2 2 2 2

 

ACQ IX IY EX EY
R0 1 2 1 1
M0 1 2 1 1
L1 3 4 2 2
L2 2 1 1 1
 

Green indicates a low-noise state, and red any other state. So far we have encountered the following things:

  • If any stage of the SRM is switched to a low-noise state, it will start to saturate. We are trying to figure out whether this is a problem with the LSC (which feeds back to M2 and M3) or the ASC (which feeds back to M1).
  • ITMX M0 appears to be miswired; changing the state request appears to affect the test/coil bits instead, resulting in an error. Jeff and Richard are looking into this.
H1 ISC
daniel.hoak@LIGO.ORG - posted 22:08, Monday 23 March 2015 - last comment - 09:56, Tuesday 24 March 2015(17409)
history of OMC RIn around 1-5Hz

Lisa, Dan, Sheila, Evan, Kiwamu

We checked the evolution of the flickers in OMC TRANS over time.  It appears that the features between 1-5Hz have always been there, but the amplitude has grown by a factor of ~3-6 in the past two weeks.

In the attached plot, the ampltiude of the 3Hz peak on Mar 6 was about 0.004 / rt[Hz], and today it is 0.02 / rt[Hz].

We've added rolloffs to the ASC loops, turned on the 'resg1' filter in the ETMY_M0_DAMP_L filter bank (this adds a RG at 1Hz and an overall gain of +6dB), and looked accusingly at the OMC TRANS camera image.  No change so far.  Next idea is to try a boost in the DARM loop gain at low frequency.

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 22:10, Monday 23 March 2015 (17410)SUS

The cut offs we added are elliptical low passes at about a factor of 10 above the ugf of several of our ASC loops (INP1, PRC1, PRC2, SRC1, SRC2 pitch and yaw). These are engaged in the gaurdian now.  We do not see anylarge changes in the noise, neither the low frequency noise that dominates the OMC DC PDs nor in the bucket.  With all of these loops and CHARD (cETM) off we saw that the noise bellow 10 Hz was a little better.  We attempted to add a ELP30 to MICH pitch, which broke the lock. 

Also, for SUS SDF, we have added notch filters for the Bounce and roll mode to the ITM L2 stages, as well as compensation for the new ESD low passes in ETMY L3 ESDOUTF

gabriele.vajente@LIGO.ORG - 09:56, Tuesday 24 March 2015 (17422)DetChar, ISC

The OMC transmitted power fluctuations at frequencies below 20 Hz is completely coherent with the power fluctuations before the OMC (see for example ASAIR_A_LF or ASAIR_B_LF), as shown by the attached plots taken from the brute force coherence report.

I believe this is telling us that the OMC flicker is due to power fluctuations inside the IFO, and not generated by the OMC control. Maybe improving the longitudinal and angular stability will help.

Images attached to this comment
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 19:36, Monday 23 March 2015 (17406)
high wind today, Y green PDH kept unlocking

Lisa, Evan, Sheila, Keita, Jim W, Kiwamu,

Today we had an issue in which the Y end PDH loop kept unlocking due to a high longitudinal motion (more than 12 um peak-to-peak at 50 mHz). The wind was high at 20 mph on average with 40 mph at highest most of the time today starting from 9 am local. In this report I attempt to summarize the issue associated with today's windy condition.

 


(Y arm motion was too high)

When we started fully locking the interferometer, we noticed that the ALS loops frequently dropped their locks in the middle of the locking sequence. It turned out that the Y arm motion was so high the end VCO saturated in every several minutes. The X PDH also had a similar amplitude but it was slightly smaller than that of the Y arm by ~ 20% which barely allowed the X arm to stay locked. The attached is a 5 minutes trend of relevant channels under a condition that:

As shown in the plots, the Y arm PDH control signal (ALS-Y_REFL_CTRL_OUT_DQ) went up and down at a frequency of 50 mHz. This channel is calibrated into the Y arm displacement in um. When it went below -7 um or above 7 um it unlocks essentially because the end VCO rails. The X arm showed a similar amplitude, but amplitude was not as big as that of the Y arm. The X arm dropped the lock less frequently than the Y arm.

 

(Some attempt with a high band width tidal)

We then started increasing the bandwidth of the local tidal feedback which picks up signals from the end PDH control and offload it to the L1 stage of ETMY. The idea is that we wanted to physically quiet down the ETMY motion so that the VCO can stay within the range. We increased the gain of both X and Y local tidal loops by a factor of 3. So their UGFs are now 0.1 Hz.  At the end the attempts, the wind incidentally came back down to 10-30 mph so we can not really say if this scheme helped.

Images attached to this report
H1 ISC (DetChar, ISC)
gabriele.vajente@LIGO.ORG - posted 11:55, Monday 23 March 2015 - last comment - 20:34, Monday 23 March 2015(17397)
Brute force coherence

Following up on Kiwamu's report, here is the summary page for the coherences during the low noise lock:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1110961816/

As usual, here is my digest.

In brief: we need MICH/SRCL subtraction, check SRC angular controls, they might be injecting noise, better tune the IMC longitudinal offset if possible

More details:

P.S. Why are you sending DARM signal into the CARM filter bank?

Images attached to this report
Comments related to this report
daniel.hoak@LIGO.ORG - 12:03, Monday 23 March 2015 (17399)

Ahh you caught on to our hacky audio setup, Gabriele.  The OMC-DCPD --> CARM matrix element is enabled so that we can filter OMC-DCPD in the CARM bank before sending it to speakers in the control room.  (Actually I'm not sure anyone is using this anymore, we can probably discontinue it.)

daniel.hoak@LIGO.ORG - 20:34, Monday 23 March 2015 (17407)

Also I have modified the ITMX violin mode damping so that there is 50x less gain at 450Hz.  (There is an 8th order butterworth bandpass now, instead of a 4th-order.)  This might make the noise a little worse between 480-510Hz, but I think that band is a lost cause anyway.

H1 SEI
jim.warner@LIGO.ORG - posted 10:59, Monday 23 March 2015 - last comment - 21:48, Monday 23 March 2015(17395)
Blends changed on EX/EY ISI's due to wind

Commissioners were complaining of excess arm motion, so I've changed the blends on the beamline directions on St1, from the nominal 45mhz blends to 90mhz. To review for those not in the seismic know, this is done by opening the St1 Blend screen from the BSC ISI overview and clicking on the 90mhz blend in the appropriate direction (i.e. X for ETMX, Y for ETMY). Attached screens show overview with circled blend screen, St1 Blend overview, close up the blend X bank. It's not perfectly clear that we need to be using the 45mhz blend or if the 90mhz blend is good enough, but I've been talking to some of the commissioner about maybe doing an assessment when it's convenient.

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 21:48, Monday 23 March 2015 (17408)

They are switched back since the wind died down

Displaying reports 66261-66280 of 83224.Go to page Start 3310 3311 3312 3313 3314 3315 3316 3317 3318 End