Displaying reports 21-40 of 75307.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 15:36, Wednesday 01 May 2024
H1 SEI
thomas.shaffer@LIGO.ORG - posted 15:36, Wednesday 01 May 2024 - last comment - 15:53, Wednesday 01 May 2024(77554)
Picket fence station transient cause earthquake mode transition

Jim, Ryan C, TJ

The picket fence station NEW had a large transient that put us into earthquake mode during observing. The code did not register this transient as a glich at first which caused the SEI_ENV mode transition. Looking to the picket fence code it looks like we might be able to tune the glitch settings a bit, but we would have to try out some values over a period of time. It might be worth checking with picket fence experts before we play with this code too much.

This isn't the first time we've seen this, but perhaps the first time we've aloged it. After the 10minute cool down period SEI_ENV returned back to a CALM mode.

Images attached to this report
Comments related to this report
ryan.crouch@LIGO.ORG - 15:53, Wednesday 01 May 2024 (77555)

The transient impulse happened a 2nd time shortly after from the same NEW station over by Spokane. It reached the glitch threshold about 5 minutes after the first impulse. Could there be work ongoing on this seismometer?

Images attached to this comment
H1 ISC (DetChar)
jennifer.wright@LIGO.ORG - posted 14:41, Wednesday 01 May 2024 - last comment - 14:50, Wednesday 01 May 2024(77551)
Ran Bruco on 43 minutes of observing time with new OMC ASC offsets

I ran a bruco starting at 1398626829 for 2580 seconds to see what channels are coherent with DARM after our adjustment of the output mode cleaner angular control loop offsets were changed.

It can be found here.

Elenna's instructions for running them are here.

Comments related to this report
sheila.dwyer@LIGO.ORG - 14:50, Wednesday 01 May 2024 (77552)

It looks like we need to continue the manual A2L tuning for yaw DHARD Y and CHARD Y, and conitnue working on SRCL FF.

H1 General (Lockloss)
thomas.shaffer@LIGO.ORG - posted 13:40, Wednesday 01 May 2024 - last comment - 14:17, Wednesday 01 May 2024(77549)
Lock loss 2010UTC

1398629440

This lock loss had that the weird ETMX wiggle just before the lock loss that we've seen in past lock losses.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 14:17, Wednesday 01 May 2024 (77550)

Back to Observing. Full auto relock but there was an SDF diff for the ITMY CP that was changed during commissioning in the Observe.snap, and came back after this last lock loss. I saved the new values in the safe.snap as well.

H1 General
thomas.shaffer@LIGO.ORG - posted 12:30, Wednesday 01 May 2024 (77547)
Back to Observing 1926 UTC

Back to Observing at 1926 UTC after a planned comissioning period. We were unable to get calibration measurements since the IFO lost lock just before planned commissioning  and during commissioning.

H1 ISC
jennifer.wright@LIGO.ORG - posted 12:02, Wednesday 01 May 2024 (77543)
OMC ASC offsets changed to ones that increase our optical gain

Jennie W, Gabriele

 

I tested the offsets calculated by Gabriele's code that we used to analyse line dithers in the OMC ASC loops here.

We tested them during the commissioning period and put the following offsets into OMC-ASC_QPD_{A,B}_{PIT,YAW}_OFFSET. Since the offsets here were turned off by default I zerod them and then stepped them up slowly so we didn't saturate the OMC ASC loops.

See the attached ndscope showing kappa c improve after we finished putting these offsets in.

We lost lock about 15 minutes after I finished ramping these in due to unrelated issues.

Sheila suggested we put the all the offsets for the QPDs in one place. Since we already had offsets in the filter blocks: H1:ASC-OMC_{A,B}_{PIT,YAW}_OFFSET, I added the offsets for Gabriele's code in these filter banks instead.

I accepted these in safe.snap and OBSERVE.snap as well as the zero values for the OMC-ASC_QPD_{A,B}_{PIT,YAW}_OFFSETs.

offset = exisiting + offset from Gabriele's code

A_PIT = -0.25 - 0.12

A_YAW = 0.1 + 0.15

B_PIT = -0.05 - 0.12

B_YAW = 0.07 - 0.18

 

We will re-evaluate once we are thermalised.

 

Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 11:52, Wednesday 01 May 2024 (77539)
manually tuned A2L

I ran the A2L script descirbed here at the start of commissoning time this morning, and immediately after manually tuned P2L coefficents for the ETMs.  I was able to improve the CHARD P to DARM coupling by about 25dB compared to the script's result. I tried tuning the ITM coefficents, but there wasn't much room to improve them. 

I've updated the guardian values for ETMX, ETMY and ITMX (for a very small improvement on ITMX). 

Compared to the script, my adjustments were fairly coarse.  The script adjusted ETMX P2L from 3.1715 to 3.0875, while I then adjusted it to 3.35.  For ETMY the script adjusted it from 4.682 to 4.7747, I adjusted it to 4.5.  This resutls in the improvement shown in the attachment. 

Editing to add: we relocked with these new P2L values, and the CHARD P to DARM coupling is still fairly low early in the lock (3rd attachment).  The A2L coefficents aren't very sensitive to thermalization, which is good news.

Images attached to this report
H1 SUS (CDS, ISC)
jeffrey.kissel@LIGO.ORG - posted 11:24, Wednesday 01 May 2024 (77545)
Calibration for QUAD/Triple Top Coil Drivers' FASTIMON (assuming Broadband Monitor Board)
J. Kissel, A. Effler

Executive Summary:

The calibration for all QTOP (D1001782) and TTOP (D1001242) coil driver's FASTIMON channels that are using the frequency-independent "current monitor" circuit of the broadband coil driver monitor circuit (D0902747) is 
    QTOP = 0.0114 [mA/ct] and 
    TTOP = 0.0153 [mA/ct],
respectively with the "[mA]" being current across the coil, and "[ct]" being "straight off the ADC" counts.

Derivation

From the math outlined in the "Other Files" of the older, "broadband" coil driver monitor circuit, D070480 and stitching together how various voltage signals passed around from page to page of the drawings, one can compute the calibration of the FASTIMON channels for a given coil driver as 

    FASTIMON ADC [ct] = voltage measured across two legs worth of output impedance in the coil driver board drawing
                        * ( [differential legs' voltage to single-ended output voltage converter node in the monitor board drawing]
                             * "single-ended voltage piped into only one leg of differential ADC" factor of two its DB25 output J1 in the interconnect drawing
                             * general standards 16-bit differential ADC calibration)
where
           calibration = (the stuff in parentheses)

         ADC [ct]        [                         "R1" [V_SE] ]    2 [V_DF]    2^16 [ct]      
    ----------------   = [ 2 * Z_OUT [V_DF / A] *  ----------- ] *  -------- * ----------- 
    Coil Current [A]     [                         "R2" [V_DF] ]    1 [V_SE]    40 [V_DF]     

where "R1" = R25, R35 = 10e3 [V/A], and "R2" = R24, R27, R29, R33 = 30e3 [V/A].


So, for the QUAD / Triple TOP coil driver (see circuit diagram D0902747 of chassis assemblies QTOP = D1001782 and TTOP = D1001242), that's, the output impedance of one leg is
    Z_OUT   = (R5+R1) || (R90+R91) 
            = (R5+R1) * (R90+R91) / (R5+R1 + R90+R91)

    Z_OUT^(QTOP) = (44 * 440) / (44 + 440) = 40.00 [V/A]
    Z_OUT^(TTOP) = (32 * 440) / (32 + 440) = 29.83 [V/A]
which makes the calibration

calibration_QTOP [ct/A] = 2 * 40.00 [V/A] * (10e3 / 30e3) * 2 * (2^16 / 40 [ct/V])
                        = 8.7381e+04 [ct/A]
      or 87.381 [ct/mA]
      or 0.0114 [mA/ct]

calibration_TTOP [ct/A] = 2 * 29.83 [V/A] * (10e3 / 30e3) * 2 * (2^16 / 40 [ct/V])
                        = 6.5165e+04 [ct/A]
      or 65.165 [ct/mA]
      or 0.0153 [mA/ct]

Q.E.D.
H1 ISC (SUS)
camilla.compton@LIGO.ORG - posted 11:03, Wednesday 01 May 2024 - last comment - 15:22, Wednesday 01 May 2024(77542)
ETMX and ETMY PUM to DARM TFs taken

Gabeiele, Sheila, Camilla

After struggling to fit the LSCFF in 77420 even with the L2L3LP filter in ETMY L2 DRIVEALIGN L2L off 77236, today we took transfer functions between ETMX and ETMY PUM to DARM.
Used ellip("BandPass",4,1,40,8,1000)gain(-60,"dB") with amplitude of 10,000 into H1:SUS-ETMX/Y_L2_LOCK_L_EXC. Saved in /ligo/home/camilla.compton/Documents/ISC/ETMX_PUM_to_DARM.xml  and ETMY_PUM_to_DARM.xml.
 
Started with excitation much smaller than normal _INMON channels, increased until coherence good while watching SUS MASTEROUTs don't get near saturating.
 
Note on calibrating CAL-DELTAL in DTT: mainly followed instructions from Dana in  74477 but Louis has most recent calibration files now located in /ligo/groups/cal/H1/reports/ as deltal_external_calib_dtt.txt.
To add to diaggui: Calibration > Choose H1:CAL-DELTAL channel > New > Name the reference, unit =m, time = yesterdays date > Tran. Func. tab > select and click edit... > open newest deltal_external_calib_dtt.txt > select default > Set > Okay.
Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 15:22, Wednesday 01 May 2024 (77553)

Here's an analysis of those injections. In brief, the coil and mechanical responses are the same for ETMX and ETMY as expected. The differences are all due to filters in the L2 LOCK and DRIVEALIGN filter banks.

First plot shows a comparison of the L2 LOCK L EXC to CAL-DELTAL transfer functions for ETMX and ETMY: they look different.

In the second plot I plot the filter chain from the L2 LOCK EXC to the COILOUT. They are different, probably because ETMX is used for DARM control, and ETMY is in some legacy configuration (note that Camilla turned off the LPL2L3 filter). The third plot shows the ratio of the ETMY  / ETMX transfer functions as measured, and what we expect from the different filters that are engaged. They match very well.

If we compensate the EXC to CAL-DELTAL transfer functions with the LOCK and DRIVEALIGN filter, and take the ratio, we get a transfer function pretty much at 1, as shown in the fourth plot.

Finally, I calibrated CAL-DELTAL_EXTERNAL in meters using Louis' file from /ligo/groups/cal/H1/reports/ and the fifth plot shows that the DARM / COIL transfer functions are pretty much the expected 1/f^2, with only a sign difference between X and Y.

In conclusion, there isn't anything wrong with ETMY PUM drive. More thinking is needed to understand why the LSC FF have a phase rotation much that is much larger at LHO than LLO, and how to better tackle that problem.

Images attached to this comment
H1 SEI (SEI)
corey.gray@LIGO.ORG - posted 10:26, Wednesday 01 May 2024 (77540)
H1 ISI CPS Noise Spectra Check - Weekly (Famis 25989)

FAMIS Link:  25989

Only CPS which looks higher at high frequencies (see attached) would be:

  1. ITMx St1 V1 & V2
  2. ITMy St1 V2
Non-image files attached to this report
LHO VE
david.barker@LIGO.ORG - posted 10:24, Wednesday 01 May 2024 (77541)
Wed CP1 Fill

Wed May 01 10:13:10 2024 INFO: Fill completed in 13min 6secs

Gerardo confirmed a good fill curbside.

Images attached to this report
H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 10:13, Wednesday 01 May 2024 (77538)
Lockloss at 17:12 UTC during comissioning

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1398618745

PRM and SR3 saturations before the lockloss, 2.5 hours into the lock so we still haven't been able to take a thermalized calibration measurement. The only invasive/potential LL causing work going on was some PEM tests by Robert.

LHO General
thomas.shaffer@LIGO.ORG - posted 08:00, Wednesday 01 May 2024 - last comment - 13:12, Wednesday 01 May 2024(77536)
Ops Day Shift Start

TITLE: 05/01 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY: Just got back into Observing after a lock loss, fully auto relock. Planned commissioning today from 9-12 PT

Comments related to this report
camilla.compton@LIGO.ORG - 08:34, Wednesday 01 May 2024 (77537)SQZ

After yesterday's SQZ realigning 77530 we're nearly back to the squeezing levels we had before the output arm alignment shift 77427: 4.3dB above 1kHz, 3.3dB ~350Hz.  Plot attached.

Images attached to this comment
ryan.crouch@LIGO.ORG - 13:12, Wednesday 01 May 2024 (77548)

I made a small change to verbal_alarms tests in test.py to ignore the TEST node being in error as I plan on creating another state to test/learn some camera stuff and I don't want to annoy everyone in the CR with it going into error. Verbal alarms could use a restart to reflect these changes.

H1 General
oli.patane@LIGO.ORG - posted 00:05, Wednesday 01 May 2024 (77535)
Ops EVE Shift End

TITLE: 05/01 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: We are Observing and have been Locked for 1.5 hours. Overall quiet night with two almost fully automated relocks. Reminder that LVEA is still Laser Hazard
LOG:

LVEA is still in LASER HAZARD

22:49 Detector Locked for 52 mins and just got into Observing
22:50 Lockloss after 1m 14s Observing

22:56 Lockloss at LOCKING_ALS
23:08 Lockloss from TRANSITION_DRMI_TO_3F
23:49 NOMINAL_LOW_NOISE
23:52 Observing

03:35 Superevent S240501an

04:34 Lockloss
04:49 Lockloss from TURN_ON_BS_STAGE2
05:38 NOMINAL_LOW_NOISE
05:40 Observing                                                                                                                                                          

Start Time System Name Location Lazer_Haz Task Time End
23:07 VAC Jordan, Janos EY n Turn off pump 23:26
23:46   Betsy, Brian OReilly MY n Approved activity 00:46
H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 21:51, Tuesday 30 April 2024 - last comment - 22:41, Tuesday 30 April 2024(77533)
Lockloss

Lockloss 05/01 04:34UTC

Comments related to this report
oli.patane@LIGO.ORG - 22:41, Tuesday 30 April 2024 (77534)

05:40 Observing

H1 ISC
camilla.compton@LIGO.ORG - posted 14:19, Thursday 25 April 2024 - last comment - 12:16, Wednesday 01 May 2024(77420)
LSC FF Meassuremnts taken with ITMY L2 L2L DRIVEALIGN LP filter off.

In  77236, Gabriele found the ETMY L2 DRIVEALIGN L2L filter bank has a "L2L3LP" engaged that might be making it harder for us to fit the LSC FF. Today we re-measured the LSC FF, not interatively, with both FF's off and the "L2L3LP" filter off.

Nothing changed but we hope to refit the feedforward and implement them later. When installed, we would need to turn "L2L3LP" filter off after the ISC_LOCK states have been transitioned back to ETMX (77240).

  1. ISC_LOCK to NLN_CAL_MEAS
  2. Turned off both MICH and SRCL FF.
  3. Measured MICH_excitation.xml and SRCL_excitation.xml (used half the nominal exc amplitudes as the FF's were off, saved with full exc amp)
  4. Turned off ETMY L2_L2L_DRIVEALIGN L2L3LP filter, see 77236
  5. Set up for FF injections, see readme. (turn off F filter and input, but turn on filter to allow excitation though)
  6. Measure NoLP_MICHFF_excitation_ETMYpum.xml and NoLP_SRCLFF_excitation_ETMYpum.xml (have adjusted exc shape for L2L3LP being off, used half nominal amplitude)
  7. Undo set-up for FF injections, see readme. Keep FF's off as L2L3LP filter's still off.
  8. Turn on L2 L2L3LP filter
  9. Turn on both MICH and SRCL FF.
  10. ISC_LOCK to NLN

All code saved to /opt/rtcds/userapps/release/lsc/h1/scripts/feedforward/

Comments related to this report
camilla.compton@LIGO.ORG - 17:28, Thursday 25 April 2024 (77431)

Struggling to fit these.

I have a MICHFF (pasted below) that's a factor of 10 worse than usual (plot attached). We may need to try to put this in and measure iterativly next week.

zpk([-6.816742648521258+i*81.77990170298034;-6.816742648521258-i*81.77990170298034;-77.88634028587184+i*89.33349468557826;-77.88634028587184-i*89.33349468557826;-718.113182677264+i*694.9426298748548;-718.113182677264-i*694.9426298748548;900.2096672125509+i*1208.040185682559;900.2096672125509-i*1208.040185682559;44.6571105273674;-170.8240187509259;-448.0004789051675;-596.150964242976],[-7.116688087177324+i*81.29900739837851;-7.116688087177324-i*81.29900739837851;-310.9419719288208+i*548.6326527169308;-310.9419719288208-i*548.6326527169308;-27.13254150394529;-30.48270823801881;-135.6924431195733;-151.8787517615438;-191.3877206479833;-2313.589507955138;-2602.376933025248;-2783.911401801387],-3.94153891134724)

Somethings wrong with the SRCL data I  exported (even after re-exporting), plot attached. Data prepared using NotItter_LSC_FF_PrepareData.ipynb

Images attached to this comment
camilla.compton@LIGO.ORG - 12:16, Wednesday 01 May 2024 (77546)

Gabriele found that the SRCL data was fine if (DELTA_L / SRCLFF_IN2) was exported but that the SRCLFF was even harder to fit than previously. We have taken TFs in 77542 to try to understand why.

Displaying reports 21-40 of 75307.Go to page 1 2 3 4 5 6 7 8 9 10 End