Displaying reports 1721-1740 of 77270.Go to page Start 83 84 85 86 87 88 89 90 91 End
Reports until 17:12, Monday 13 May 2024
H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 17:12, Monday 13 May 2024 - last comment - 17:51, Monday 13 May 2024(77817)
Lockloss

Lockloss @ 05/14 00:09UTC

Pretty confident that this was due to the wind - it really jumped up this past 1/2 hour

Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 17:34, Monday 13 May 2024 (77818)

Winds currently hitting 40mph and up to 45mph at EY. Going to try relocking for a bit

Images attached to this comment
oli.patane@LIGO.ORG - 17:51, Monday 13 May 2024 (77819)

00:46 Sitting in DOWN until the wind reduces - ALS wouldn't catch

LHO General
ryan.short@LIGO.ORG - posted 16:32, Monday 13 May 2024 (77814)
Ops Day Shift Summary

TITLE: 05/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Mostly quiet day with just one lockloss. Easy relock followed by retuning of SQZ angle, then observing for the afternoon.

H1 has now been locked for 7 hours.

LOG:

Start Time System Name Location Lazer_Haz Task Time End
15:10 FAC Kim MX n Technical cleaning 15:58
15:11 FAC Karen MY n Technical cleaning 16:31
16:21 CAL Rick, Francisco PCal Lab n Checks 16:48
21:34 SQZ Terry, Kar Meng Opt Lab Local SHG work 00:34
H1 General
oli.patane@LIGO.ORG - posted 16:15, Monday 13 May 2024 (77816)
Ops EVE Shift Start

TITLE: 05/13 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 11mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

Observing and Locked for 6.5 hours. Wind is changing  quite a bit but is currently around 20mph.

H1 General
minhyo.kim@LIGO.ORG - posted 15:32, Monday 13 May 2024 (77815)
Updated RANGE_BLRMs ndscope plot

Minhyo

Following the changing of the gain value of the low pass filter in the range BLRMs (OAF_RANGE_RLP#, refer to alog 77346), I modified the ndscope template of 'BLRMS together'.
The original template showed the output of each RLP in one panel and BNS range (H1:CDS-SENSMON_CAL_SNSW_EFFECTIVE_RANGE_MPC and H1:CDS-SENSMON_CLEAN_SNSW_EFFECTIVE_RANGE_MPC) in the other panel. For visibility, I separated the RLP output panel into two parts (RLP_1~5 / RLP_6,7) in the left part of the whole screen and added the BNS range corresponding to each frequency band in the right part of the screen. 

The template is saved in userapps/isc/h1/ndscope/DARM_BLRMS_together.yaml.
(The old one is copied as named DARM_BLRMS_together_old.yaml in the same directory) 

After changing the gain value of each RLP, the outputs and the ranges for each bandwidth show better correspondence to the actual BNS range, which will be useful to see the contribution of each bandwidth range.

Screenshots are: 1) Old plot of DARM_BLRMS_together, 2) same plot with new template.

Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 13:59, Monday 13 May 2024 - last comment - 14:21, Monday 13 May 2024(77812)
angle to length decoupling may need retuning

It looks like CHARD P coherence with DARM is rather high, this might be contributing to the low range at the moment.

I've added this dtt template to userapps/isc/h1/templates/DARM_coherence_check.xml, so that operators can use it to check coherences with LSC, ASC, and jitter any time that the range is low. 

 

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 14:21, Monday 13 May 2024 (77813)

Adding to this an example of using the sqz blrms template to look at the level of the 350 Hz (yellow BLRMS 3 trace) and 1.7kHz (purple BLRMS 6 trace) now compared to a time of good range.

It looks like Ryan's running SCAN_ALIGNMENT and SCAN_SQZANG earlier today did help improve the squeezing level.

This template can be found in userapps/sqz/h1/Templates/ndscope/sqz_blrms_range_2days.yaml  or from the SQZ_OVERVIEW medm screen.

Images attached to this comment
LHO VE
david.barker@LIGO.ORG - posted 10:17, Monday 13 May 2024 (77811)
Mon CP1 Fill

Mon May 13 10:14:59 2024 INFO: Fill completed in 14min 55secs

Gerardo confirmed a good fill curbside.

Images attached to this report
H1 General (Lockloss, PEM, SEI)
ryan.short@LIGO.ORG - posted 10:06, Monday 13 May 2024 - last comment - 10:09, Monday 13 May 2024(77809)
Lockloss @ 15:37 UTC

Lockloss @ 15:37 UTC - link to online lockloss tool

Looking at the lockloss tool, the ETMs really started shaking about a second before the lockloss, possibly due to increased ground motion at EX as seen by the BRS. According to the wind direction monitor, wind at EX is coming from the northeast, meaning it would be missing the wind fence and possibly making the relatively medium-low wind speeds have a greater effect.

The LSC signals show generally things were shaking a bit more than normal as well as an oscillation buildup in DARM and PRCL right before the lockloss.

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 10:09, Monday 13 May 2024 (77810)SQZ

H1 back to observing as of 16:56 UTC.

Once H1 relocked and before going into observing, Sheila recommended running the automated SQZ alignment scans with the SQZ_MANAGER Guardian, which all took about 8 minutes total. This created SDF diffs for the ZM4 and ZM6 sliders, which I accepted (screenshot attached).

Images attached to this comment
H1 DetChar (DetChar)
dishari.malakar@LIGO.ORG - posted 10:01, Monday 13 May 2024 (77808)
DQ shift report from 6th May - 12th May 2024

Summary of the report:

Full link to the report: Report.

H1 PSL
ryan.short@LIGO.ORG - posted 07:50, Monday 13 May 2024 (77804)
PSL 10-Day Trends

FAMIS 20028

As Jason pointed out with last week's trends (alog77649), temperature changes in the past week (I suspect thanks to the sudden rise in temps this weekend) line up with changes seen in the amplifiers, PMC, and RefCav. Even after alignment adjustments made last week (alog77685), the PMC transmitted power has continued to fall while reflected power increased.

Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 07:31, Monday 13 May 2024 (77803)
Ops Day Shift Start

TITLE: 05/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY: H1 has been locked and observing for 15 hours. Range has been hovering around 150Mpc, slightly lower than it has been in recent days.

H1 General
oli.patane@LIGO.ORG - posted 01:02, Monday 13 May 2024 (77802)
Ops EVE Shift End

TITLE: 05/13 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Currently Observing and we have been locked for 8.5 hours. Quiet evening overall with no issues besides the tail end of relocking when I first got in.
LOG:

23:00 Detector relocking at ENGAGE_ASC_FOR_FULL_IFO
    - Past few days we've been seeing IFO_out saturations at the end of POWER_25W and into the first few seconds of MOVE_SPOTS
    - Paused between each state between TRANSITION_FROM_ETMX and LOWNOISE_LENGTH_CONTROL because I was worried we would get a LL like Ryan had earlier from LOWNOISE_LENGTH_CONTROL
23:37 NOMINAL_LOW_NOISE
23:38 Observing

 

H1 General
oli.patane@LIGO.ORG - posted 20:42, Sunday 12 May 2024 (77801)
Ops Eve Midshift Status

We are Observing and have been Locked for 4 hours. Quiet evening

LHO General
ryan.short@LIGO.ORG - posted 16:36, Sunday 12 May 2024 (77798)
Ops Day Shift Summary

TITLE: 05/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Several earthquakes today have made trouble for H1 locking today and caused a lockloss this morning, and H1 has been having trouble relocking this afternoon (but things might still be fine).

Relocking has been tricky so far; I've seen the 100Hz PRCL buzzing twice when locking DRMI mentioned in alog77583 (but was not quick enough to catch it before SRM saturated and we lost lock) and the arms have been randomly dropping out while trying to acquire DRMI. The current attempt has gone without issue, though, so I'm unsure if there's an underlying issue I'm not seeing or the IFO is just being fussy on this warm afternoon. Currently up to ADS_TO_CAMERAS.

LOG:

No log for this shift.

H1 General
oli.patane@LIGO.ORG - posted 16:15, Sunday 12 May 2024 (77799)
Ops EVE Shift Start

TITLE: 05/12 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 15mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

Currently relocking and at ENGAGE_ASC_FOR_FULL_IFO. Ryan's had to deal with a good number of lower level locklosses today, so we will see how my shift goes!

H1 General (Lockloss)
ryan.short@LIGO.ORG - posted 14:20, Sunday 12 May 2024 - last comment - 16:52, Sunday 12 May 2024(77797)
Lockloss @ 21:13 UTC

Lockloss @ 21:13 UTC - link to online lockloss tool

No obvious cause; earthquakes had passed and wind is still relatively low. ETMX L3 (as usual) saw first motion.

Comments related to this report
ryan.short@LIGO.ORG - 16:52, Sunday 12 May 2024 (77800)

H1 back to observing at 23:38 UTC.

H1 PEM
michael.landry@LIGO.ORG - posted 02:09, Saturday 11 May 2024 - last comment - 09:29, Monday 13 May 2024(77777)
Aurora over LHO

The May 10 CME impact on Earth's magnetic field has produced a category G5 geomagnetic storm event, yielding magnificent aurorae here in the Tri-Cities and the world over.  Photos attached.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:29, Monday 13 May 2024 (77807)EPO
Nice photos! Tagging EPO!
H1 CAL (CDS, ISC)
jeffrey.kissel@LIGO.ORG - posted 14:08, Friday 10 May 2024 - last comment - 09:27, Monday 13 May 2024(77735)
Update on OMC DCPD Transimpedance Amplifier Characterization Post OMC Swap: No Forward Progress, Only Sideways Progress and Broken Electronics
J. Kissel [with support from L. Dartez, F. Llamas, and D. Schaetzl]

Executive Summary
In Feb 2024, we identified that both the DCPDA and DCPDB channels of the in-vacuum OMC DCPD transimpedance amplifier (TIA) frequency response dropped by 0.3% below ~25 Hz (LHO:75986) and that the frequency-dependent balance of the DCPDs changed in a different way at the 0.2 dB or 10^(0.2/20) = 2.5% level (LHO:76232). Since then, with what limited person power we had, we've been scrapping together ~2 hours of time during maintenance days to try to re-characterize the response of the TIA in order to fit and re-compensate the response, and then re-re-balance the DCPDs. We've also done a lot of thinking in between. This aLOG covers the saga since then, and executive summary is that we don't have good enough measurements of the TIA response yet, we have broken the functionality of the TIA monitor path in the S2300003 D2200215 whitening chassis, and it needs to be replaced in order to move forward with characterizing the in-vacuum TIA.

Timeline
    Editorial note: You'll find that the story is fraught with missing institutional knowledge due to lack of person power and interferometer time. It would pay for us to have had a spare TIA system *out* of vacuum to test our characterization methods and train new staff.

    . 2024-02-26: In LHO:75986 after measuring twice to ensure we weren't being fooled by vacuum pressure and thermalization, we use the remote, DAC driven characterization setup -- measuring the product of the TIA, the whitening, the whitening compensation, and the TIA compensation -- we conclude that the response of the TIAs has changed, and is no longer as flat as it was the last time we measured it, which was Jul 2023 (LHO:71225).
  
    . 2024-02-26: That same day, we measured the TIA response "alone" using the same remote, DAC driven measurement, but instead turning OFF the analog whitening, and the compensation for both -- as the first attempt to "just get the data we need quickly in order to get the job done." We never processed this data because (a) we didn't have the person power, and (b) we later remember that it's not good enough to use for updating the compensation because this measurement doesn't contain the TIA response "alone," but instead also 
        - several computational delays,
        - the anti-imaging chassis from the DAC,
and it's limited by the 16 kHz sampling frequency of the DAC system so we can't characterize everything we need for the TIA, given that there are 
        - 2x 10kHz poles in the TIA itself, and
        - 1x 44kHz pole in the whitening chassis, even with the z:p = 1:10 Hz whitening filter turned OFF.

    . From 2024-02-26 thru 2024-04-29: I worked offline with Dean to try to understand the electrical grounding paths in the OMC DCPD signal chain, because it's the only think I can imagine that could cause a *common* change in frequency response to both channels. I now have a much better understanding of the electrical grounding in the OMC signal chain, have produced G2400755, and Dean has made an update to the O4 OMC DCPD wiring diagram accordingly D2100716-v3. However, I conclude that any potential change in the in-vacuum electrical grounding during the OMC swap just is not possible, and the DCPDs are tied to earth ground by and at the in-air whitening chassis, so this is likely NOT the source of the frequency dependent change.

    . 2024-04-02: Louis and Francisco finally muster up the person power to go out to the HAM6 ISC-R5 rack to repeat the long, arduous, measurement needed. However, they misinterpret my diagrams from the 2023-03-06 and 2023-03-10 measurements (LHO:67801 and LHO:68167) against the reality of the D2200215-style whitening chassis, and drive 1 [V_pk] source voltage backwards against the monitor path's buffer amplifiers. The first attachment shows
        - page 1: how one should characterize the TIA response, buffer amplifiers, and measurement setup
        - page 2: how one should characterize the measurement setup and buffer amplifiers in order to divide it out of the page 1 measurement, and
        - page 3: how the measurement setup and buffer amplifier characterization was misinterpreted on 2024-04-02.
      Further, as is standard practice, they took SR785 setup notes from "the most recent good measurement available in the SVN," which was the 2023-03-10 data set where Hsiang-yu and I were exploring options. Thus, they used some settings that were meant for testing rather than those which get the best results out of the measurement. More on this later.

    . 2024-04-09: With Louis and Francisco away for the Solar Eclipse, I head out to the floor to take another crack at it. While I get the measurement setup right, I don't know yet, but I still use bad SR785 settings from the 2023-03-10 date. As such, I get results that are too noisy below 50 Hz to make fits. In the second attachment, I show a quad bode-plot of the DCPDA (page 1) and DCPDB (page 2) where I divide 
       - the Last Best Good measurement -- the 2023-03-06 data and
       - the 2024-04-09 data
      against the model fit from that data (see poles and zeros listed in LHO:67809). While one can see hints of the ~0.3% change, it's just too noisy to be confident that we can get a good fit from it.

    . from 2024-04-09 thru 2024-04-23: With review from Louis, we think hard about why the measurement is noisy. I get a hunch about the SR785 parameters' settle time and settle cycles vs. step (or impulse) response of the TIA response itself, insisting that the settle time of 100 [msec] we've been using since 2022 is not long enough for what the impulse response of the TIA circuit is (because we're perpetually trying cut corners and speed up this measurement). I make a bunch of plots that show the step response of the TIA compared with the bad 2023-03-10 settle settings, but while looking back through my notes I also discover that a difference between the 2023-03-06 and 2023-03-10 measurements is that I had decreased the SR785 source voltage from 4 V_pk to 1 V_pk. The third attachment shows plots that show the good vs. bad SR785 settings and why.

       - page 1: this compares the settle parameters, visually showing the crossover frequency where, as the swept sine measurement sweeps down in frequency, the SR785 switches over from using settle time to settle cycles, given that it takes the larger of (settle time) vs. (settle cycles / frequency). The dashed lines are the *bad* too little settle time or cycle parameters, and the solid lines are the good, just long enough, settle parameters. Turns out the cross-over frequency isn't that different, but it's important to understand *where* it is, so that you understand *where* in the frequency response this switch happens so you know which parameter to increase when you see noise in the TIA response at a certain frequency.

       - page 2: Now thinking about the *amplitude* of the excitation vs. the step response of the circuit, I show the magnitude of the modeled response of the TIA with a few points highlighted. Note that, rather than displaying the TIA response magnitude in its "fundamental" units of [Volts output / Amps of current from DCPDs] = [V/A], I display it in the units of this characterization measurement, which is through the 100e3 [V/A] series resistance of the "test" input. Given the intellegent design of the circuit, that means than this measurement of the TIA -- which has transimpedance of 100e3 [V/A] in the gravitational wave band -- has a magnitude of 1 [V/V] in the gravitational wave band. 
            :: the blue "x" and yellow "o" are the cross-over frequencies of the "too little" BAD and the "just enough" GOOD settle params. Good to know that these are *not* in the middle of the 25 Hz resonance feature. But, these cross-over frequency that are the lower bound of a region where we must compare the "desired response" amplitude with the "step response" amplitude after the chosen amount of settle time -- if the "step response" amplitude is still a large fraction of the "desired response" amplitude after (settle cycles/frequency) amount of time, then the data is going to be incoherent (since the circuit is still "ringing" from the incoherent "excitation" that is the step-change in frequency).
            :: the red square, at 102.4 kHz represents the lowest magnitude point in the "settle time" regime. This is where, again we'll need to make sure that amplitude of the "desired response" amplitude at that frequency is larger than the step response amplitude after the total settle time is complete.
            :: the black triangle, at "DC," in this case 0.1 Hz, shows the magnitude of the TIA response at low frequency, at 0.002 [V/V]. This is relevant because the step response will asymptote to this value. Also it's the lowest magnitude point of the whole transfer function, but it still needs to be extremely well resolved -- just as much as the ~1.2 [V/V] region around 25 Hz. So one needs to be conscious of the excitation amplitude (be it 1V, or 4V), filtered through this circuit (thus 0.002 [V_pk] or 0.008 [V_pk]) with respect to the ADC noise of the SR785 at the given input range. Note, the input "range" (which really the amount of attenuation of the input) for the A and B inputs of CH2 has been auto-ranged in the past with 4 [V_pk] source (and locked as static during the measurement once found) to be +16 [dBVpk] == 6.3 [V_pk]. The noise floor at the range setting, at this low of frequency is ~0.1 [mV] (see e.g. figure B3 of Hoffman 2009), so a non-negligible fraction of 0.002 [V_pk] response to 1 [V_pk] source, which is why increasing the source amplitude by a factor of 4 is necessary.

        - Page 3: This shows the full step response of the TIA circuit as a function of time. One can see, as expected, since the maximum gain of the circuit is ~ 1 [V/V], the maximum amplitude of the step response roughly hits the value of the source input within ~100 [usec] of the step. However, we can see that the step response doesn't appreciable attenuate until 0.1 [sec], or 100 [msec]!

        - Page 4: Here, I zoom in on the amplitude and time of the step response, and compare the BAD SR785 settings with the good SR785 settings. Namely, at the two interesting frequency points from page 2 -- the settle time/settle cycle crossover, and the lowest magnitude point in the settle time region. With 1 V input (page 4), at the bad 101 [msec] settle time, and (1/crossover freq) = 101 [msec] crossover frequency cycle duration, the "desired response" amplitude of circuit is comparable to step response at 100 [msec]. This is why the ~25 Hz region of the measurement has been "noisy" all these years we've been measuring the TIA, and why we need to increase the settle time to 250 [msec]. The 102.4 kHz region was still OK, because there's upwards of 10e3 cycles in 100 [msec], oodles of averages to get good SNR. 

        - Page 5: This shows the same plot, but with 4 [V_pk] source voltage step input and settle time of 250 [msec] and 2 settle cycles. Here, we see that it's not an awesome amount of margin between the step response and the desired circuit response at the interesting frequencies, but it's *definitely* better than 100 [msec] and 1 cycle.

     . 2024-04-23: So -- we're good right? We take the hit in patience / IFO time, and increase the settle time from 101 [msec] to 250 [ms], settle cycles from 1 to 2, and increase the excitation amplitude from 1 to 4 [V_pk], and we'll get the bet measurement ever, right?  No. The fourth attachment shows my utter dismay in that -- yes, while the measurement is much less noisy after having improved the SR785 settings -- BUT the magnitude and frequency response of the 2024-04-23 is subtlety different than the 2023-04-09 and 2023-03-06 measurements at the 0.5 [%] / 1 [deg] level. And that one can trace that difference down to that the measurement setup characterization has a non-linear response to excitation voltage.
        - Pages 1 and 3 show the quad bode the same quad bode plot, but now it shows the 2023-03-06, 2024-04-09, and the 2024-04-23 measurement all together. See the ~1% magnitude discrepancy?
        - Pages 2 and 4 show a regular bode plot showing the measurement setup response for all three 2023-03-06, 2024-04-09, and the 2024-04-23 measurements. See the overall magnitude discrepancy, the high-frequency response discrepancy? Maddening.

     As long as we're going insane, Louis and I convince ourselves (via the data sheet) that the AD8672 op amps in this monitor path on the front-interface board, D2200043 of the D2200215 whitening chassis assembly (which are the same used in the main gravitational wave path on the primary functional board, D2200044) that "there's no way this op-amp can drive +/-4V with an input range of +/- 2.5V and an output drive of +/-3.7V!" ... but we were looking at the table for +/-5V operational state, rather than the +/-15 V operational state, which can happily receive +/-12V and drive +/-13V. But that's what drove me to the EE lab...

     . 2024-04-24 and 2024-04-25: Since we have spares of these OMC Whitening Chassis in the EE lab, I repeated this "measurement setup" characterization on both channels of spare chassis serial numbers S2300002 and S2300004. 
         - The fifth attachment shows the results the results of these 2x chassis, each with 2x channels, measurements as a function of input voltage. The spare chassis show no evidence of non-linearity in scale, or frequency-dependent magnitude or phase from 0.5 [V_pk] to 5 [V_pk], to the level of the ratio of the 0.5 [V_pk] to all other amplitude excitations being noisy around the 1.0 +/- 0.0001 (or 0.01 [%] or 1 [HOP]) magnitude and 0 +/- 0.02 [deg] in phase across a 10 Hz to 102.4 kHz span.
         - The sixth attachment compares across all four of these channels at 4.0 [V_pk] source amplitude. All four instantiations of this monitor path in spare chassis show no difference from each other at the same level, using S2300002 CHA as the reference, the ratio of the other channels to it is within 1 +/- 0.0001 in magnitude and 0.1 [deg] in phase.

     . 2024-04-30: To put the nail in the coffin, I go out and measure the S2300003 chassis' monitor path as a function of input voltage. 
         - The seventh attachment shows the damning evidence -- that the frequency response and scale of this monitor path on the S2300003 chassis changes with input voltage, where the other two instantiations do not.
         - The eigth attachment shows that the response to 1 [V_pk] source has changed over time, as I compare the 2023-03-10 measurement setup characterization to the 2024-04-30 results.

And, while I can't definitely say that the incorrect measurement setup from 2024-04-02 borked the op-amps in the monitor path, it's the only smoking gun I have.

"OK, Jeff. You're lost. Why do we care so much about measuring 1.0 from the monitor path of this whitening Chassis?"
I hear you, I feel lost. But, in the world where we're trying to update the TIA compensation at the 0.3% level, and the scale and frequency dependence of the measurement tools you're using are non-linear and frequency dependent at the 0.5 [%] / 1.0 [deg] level in the 1 to 100 kHz region, and you're trying to fit for poles at ~10 kHz, then you're gunna get the wrong answer.

As such, to restate the executive summary we need to replace the S2300003 D2200215 OMC whitening chassis with one of the spares, in order to get a re-characterization of the OMC TIA after the OMC swap.

*sigh*
Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:27, Monday 13 May 2024 (77806)CDS
The scripts used to analyze the data and create the plots from the above aLOG live in
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/Electronics/H1/
        DCPDTransimpedanceAmp/OMCA/S2100832_SN02/20240423/Data/
            quick_compare_data_20240423.m (rev 12938)

        DCPDWhitening/OMCA/S2300002/20240424/
            quick_plot_data_20240424.m (rev 12940)

Even though the name and location indicates that the script should only be a "quick plot/comparison of the data" from that measurement date, it does in fact contain the measurement-date- and whitening-chassis-serial-number- spanning analysis from this aLOG. 

Similarly, the data used in the above aLOG lives scattered across the folder structure,
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/Electronics/H1/
        DCPDTransimpedanceAmp/OMCA/S2100832_SN02/
            20230306/Data/                         # Pre-OMC-swap data that was used for fitting. Does not have "measurement setup" data to divide out of measurement
            20230310/Data/                         # Pre-OMC-swap data where we tried to gather the measurement setup characterization, and also explored the excitation amplitude parameter space.
            20240402/Data/                         # Diagrams of bad measurement setup, and some notes about it (no data was saved)
            20240409/Data/                         # Noisy data and measurement notes with bad SR785 parameters from 20230310, and suspect TIA pickoff monitor path response in whitening chassis
            20240423/Data/                         # Good Data/SR8785 params, measurement notes, analysis scripts and suspect TIA pickoff monitor path response in whitening chassis
        
        DCPDWhitening/
            S2300002/20240424/Data/                # EE Shop, benchtop measurement to show TIA monitor pickoff path response is excitation amplitude independent
            S2300003/20240430/Data/                # With chassis still installed, in-situ measurement to show TIA pickoff path response depends on excitation amplitude
            S2300004/20240425/Data/                # EE Shop, benchtop measurement to show TIA monitor pickoff path response is excitation amplitude independent


Apologies for the mess. 
H1 ISC
sheila.dwyer@LIGO.ORG - posted 09:20, Monday 06 May 2024 - last comment - 09:10, Monday 13 May 2024(77641)
DRMI PRCL gain change

Sheila, Jenne, Tony, Camilla

We've had locklosses in DRMI because the PRCL gain has been to high when locked on REFL1F.  Tony looked and thinks that this started on 77583, the day of our big shift in the output alignment.

Today we acquired DRMI with half the gain in the PRCL input matrix for 1F, this one acquisition was fast.  I've attached the OLG measurements for PRCL and MICH after the change. 

Tony is working on making histograms of the DRMI acquisition times, before the 23rd, from the 23rd to today, and eventually a histogram from today for the next few weeks to evaluate if this change has an impact on the DRMI acquisition times.

Jenne also found that it seems out POP18 build up seems higher in DRMI since the 23rd.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:45, Friday 10 May 2024 (77763)

I'm no longer quite so sure about the conclusion that Pop18 is higher, or at least enough to really matter.

Here are 2 screenshots that I made extremely quickly, so they are not very awesome, but they can be a placeholder until Tony's much more awesome version arrives.  They both have the same data, displayed 2 ways.

The first plot is pop18 and kappaC versus time.  The x-axis is gpstime, but that's hard to interpret, so I made a note on the screenshot that it ranges from about April 20th (before The Big Shift) to today.  Certainly during times when the optical gain was low, Pop18 was also low.  But, Pop18 is sometimes high even before the drop in optical gain.  So, probably it's unrelated to The Big Shift.  That means that the big shift in the output arm is not responsible for the change in PRCL gain (which makes sense, since they should be largely separate).

The second plot is just one value versus the other, to see that there does seem to be a bit of a trend that if kappaC is low, then definitely Pop18 is low.  But the opposite is not true - if pop18 is low kappaC isn't necessarily low.

The last attachment is the jupyter notebook (you'd have to download it and fix up the suffix to remove .txt and make it again a .ipynb), with my hand-typed data and the plots.

Images attached to this comment
Non-image files attached to this comment
sheila.dwyer@LIGO.ORG - 09:10, Monday 13 May 2024 (77805)

I actually didn't load the guardian at the time of this change, so it didn't take effect until today.

So, we'd like histograms of DRMI acquitisiton times from before April 23rd, from April 23rd until today, and for a few weeks from today.

Displaying reports 1721-1740 of 77270.Go to page Start 83 84 85 86 87 88 89 90 91 End