Displaying reports 341-360 of 85505.Go to page Start 14 15 16 17 18 19 20 21 22 End
Reports until 17:24, Wednesday 22 October 2025
H1 SUS (SEI)
oli.patane@LIGO.ORG - posted 17:24, Wednesday 22 October 2025 - last comment - 20:17, Wednesday 22 October 2025(87659)
PR3 and SR3 L and P Estimators turned off for now

Turns out that I had forgotten to turn the input on for the PR3 P estimator contribution from L (H1:SUS-PR3_M1_EST_P_FUSION_MODL_DRV_L_2GAP) (thanks to Edgard and Brian for having us even consider the estimators!), and that was causing the 0.6 Hz ASC ringups (87658). Even though we're pretty sure we found the cause, we've decided to temporarily turn off the PR3 and SR3 L and P estimators until we're back up and can verify that they are now working correctly.

Images attached to this report
Comments related to this report
brian.lantz@LIGO.ORG - 20:17, Wednesday 22 October 2025 (87670)

Thanks for catching this, Oli. I made a note in FRS ticket 35410 reminding us to make an installation script which automatically sets all the epics variables so we are more likely to get all the right settings from the beginning. 

H1 General
oli.patane@LIGO.ORG - posted 17:21, Wednesday 22 October 2025 (87663)
Ops Day Shift End

TITLE: 10/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Currently relocking and at LOWNOISE_COIL_DRIVERS. Still struggling with a 1 Hz oscillation(87658), but we've solved issues with MICH phase margin and with a 0.6 Hz oscillation caused by incorrect estimator settings, so 2/3 of the issues solved?
LOG:

14:30UTC Started relocking
    Initial alignment
    Lockloss from OMC_WHITENING due to 1 Hz ringup
    Multiple locklosses from DRMI and under due to ALSX getting noisy and ALSY having some glitchy drops in power
    Locklosses from LOWNOISE_LENGTH_CONTROL, MOVE_SPOTS, etc.                                                                                                                                                                

Start Time System Name Location Lazer_Haz Task Time End
15:45   Matt JOAT n Putting stuff away 15:50
15:49 FAC Kim OptLab n Tech clean 16:10
16:48 FAC Randy XTube n Caulking more tube 20:40
17:26   Tony CER n Putting laptop away 17:31
20:18 VAC Travis MX, MY n Taking measurements 23:43
20:18   Keita OptLab y(local) ISS Array 21:44
20:39 FAC Randy Yarm n More Caulking of the BTE, starting at EY 22:08
20:40 IO Rahul Opt Lab y(local) ISS array 21:44
20:58 SEI/CC Jim, Mitch Ends n Wind fence, HEPI, and dust mon pump FAMISs 00:27
21:17   Tyler, Shinji OptLab y(local) Meeting with Keita 21:44
21:47   Jenne, +PAC Roof n Overlooking the arms 22:08
22:38 PCAL Tony PCAL Lab y(local) Setting up measurement 22:38
H1 ISC
elenna.capote@LIGO.ORG - posted 16:48, Wednesday 22 October 2025 - last comment - 18:41, Wednesday 22 October 2025(87658)
0.6 Hz oscillation due to estimator, 1 Hz oscillation still causing lockloss

We managed to track down the source of the 0.6 Hz oscillation that we see at move spots and full power. It seems to be the result of the new pitch and length estimators on PR3 and SR3 that were installed on Tuesday. We tested this by sitting at move spots (after the spots converged), and turning on and off the estimators for a few minutes at a time. When turning ON the estimators, the 0.6 Hz ringing is not immediately apparent- it will slowly grow. However, once the 0.6 Hz oscillation is visible in the controls, turning OFF the estimator immediately stops the ringing. Therefore, we think this is the culprit for this instability. Oli will be turning off the length and pitch estimators for PR3 and SR3 for now. The yaw estimators are still on because they have been operating stably for a long time and were not changed this Tuesday.

We have also put the factor of 2 increase of MICH2 gain into the guardian, since we kept forgetting to add it in. Several locklosses that we thought were due to various other things were actually due to the MICH loop ringing up.

Finally, we just had a lockloss after moving to camera servos because the 1 Hz oscillation began to grow. Here is everything I tried to stop the ringing (none of it worked):

I then had an idea to go to high bandwidth ASC using the seismic script, but we lost lock as soon as I thought of that.

Next plan: go to lownoise length control, skip lownoise asc, go to the final spots and camera servos, stay in HBW ASC and wait for the 1 Hz ring up and see if we can ride it out this way.

Attached scope screenshot shows the 0.6 Hz oscillation disappearing as soon as Oli flipped the length and pitch estimator switches OFF.

Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 17:18, Wednesday 22 October 2025 (87661)

Here's the measurements taken for MICH that show the phase margins at different points in the locking sequence

Images attached to this comment
elenna.capote@LIGO.ORG - 17:19, Wednesday 22 October 2025 (87662)

We have been thinking that maybe the MICH UGF is too low (I had a memory that it was supposed to be 8 Hz). Then I found this alog from Evan where he designed it to be 5.5 Hz and the phase margin looks about the same 76631. Note that Oli's measurement was taken after we DOUBLED the gain, so somewhere along the way we lost 6 dB of gain.

elenna.capote@LIGO.ORG - 17:52, Wednesday 22 October 2025 (87665)

I held us at high bandwidth ASC for 9 minutes and there was no 1 Hz oscillation. A few minutes after running lownoise ASC the 1 Hz oscillation came back. It begins first in DHARD P. I stopped the oscillation by running the ASC HI GAIN script that we set up for earthquakes. It looks like the oscillation stopped as soon as DHARD P was put into HBW state. After waiting a few minutes, I put us back into the lownoise state. I have previously been suspicious of DHARD P for being the culprit causing the 1 Hz ring up. My recommendation is that if we see this again, try turning OFF FM8 in the DHARD P filter module (labelled GVBoost). If that doesn't work, just run the HI GAIN ASC script like you would for an earthquake, on the IS sensor config screen.

 

EDIT: I posted this comment too soon- the 1 Hz ringing came back. I tried just turning off DHARD P FM8, but that did nothing. However, going to Hi Gain ASC worked again, so that seems to be a good way to get around this (for now).

elenna.capote@LIGO.ORG - 18:20, Wednesday 22 October 2025 (87667)

I've been flipping back and forth between high and low bandwidth DHARD P. The 1 Hz definitely begins when we are in LBW, and it seems to actually be the lowpass/reshaping in FM4 that is the issue.

I also noticed that there is a glitch in DARM whenever FM4 is turned on or off, so I increased the filter ramp time from 15 to 20 seconds.

To take DHARD P to HBW, disengage FM8, wait for the filter to ramp, then disengage FM4.

To take DHARD P to LBW, engage FM4, wait for the filter to ramp, then engage FM8.

elenna.capote@LIGO.ORG - 18:41, Wednesday 22 October 2025 (87669)

I tried to measure DHARD P to understand what the instability is but we had a lockloss. Looks like it's an ETM glitch?

My recommendation is to put DHARD P in HBW if the 1 Hz starts oscillating again.

H1 General
ryan.crouch@LIGO.ORG - posted 16:21, Wednesday 22 October 2025 - last comment - 18:23, Wednesday 22 October 2025(87657)
OPS Wednesday EVE shift start

TITLE: 10/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 21mph Gusts, 17mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.30 μm/s 
QUICK SUMMARY:

Comments related to this report
ryan.crouch@LIGO.ORG - 17:52, Wednesday 22 October 2025 (87664)

00:43 UTC We reached OMC_WHITENING where we will sit to damp violins for a bit.

ryan.crouch@LIGO.ORG - 18:07, Wednesday 22 October 2025 (87666)SUS

IX13 has been the problem mode, I've set its' gain to 0 in lscparams and reloaded the VIOLIN node. I think I have found a new setting for IX13, I changed the phase from -60 to-30 and used a negative gain. Its damping, slowly...

ryan.crouch@LIGO.ORG - 18:23, Wednesday 22 October 2025 (87668)

We've also noticed that the ETMY roll mode is ringing up, turning off the damping made it ringup faster.

H1 ISC (ISC, OpsInfo)
jennifer.wright@LIGO.ORG - posted 11:38, Wednesday 22 October 2025 - last comment - 11:54, Wednesday 22 October 2025(87648)
Incorrect Calibration for H1:OMC-REFL_A_LF channel

Jennie W, Sheila

I noticed yesterday that the power reported as being reflected from the OMC is more than the power reported entering HAM6 (see this alog #87629). This does not affect any controls, but it does affect anyone who is using this channel to do comissioning tests.

Sheila checked this alog for the calibration of OMC-REFL_A PD, alog #65082. It looks like there should be a -20dB switch on in the filter bank when the gain is set to 20dB:

FM7/8 should be the inverse of H1:OMC-REFL_A_DC_GAINSETTING (e.g. enable "-20dB" if the gain is 20dB)

Checking the screen we found the gain setting was set to 0 on the front-end side but the '-20dB filter bank is still turned on. We have turned this filter bank off (see image with relevant parts circled), but the front-end H1:OMC-REFL_A_LF_OUT value still does not match the Beckhoff value, H1:OMC-REFL_A_DC_POWER.

Looking back at our last long lock (when the -20dB filter was still on) you can see that the OMC-REFL_A_LF_OUT16 and OMC-REFL_A_DC_POWER are off by a factor of 100 even though they are both supposed to be in mW. Therefore our switch off of the -20dB filter will not correct this problem and the rest of the calibration of this PD in the front-end filters needs more investigation.

 

Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 11:54, Wednesday 22 October 2025 (87650)

TJ found that this filter bank was monitored in the H1 LSC model so we accepted the diff in OBS and SAFE sdf tables.

LHO VE
david.barker@LIGO.ORG - posted 10:42, Wednesday 22 October 2025 (87646)
Wed CP1 Fill

Wed Oct 22 10:08:38 2025 INFO: Fill completed in 8min 34secs

Gerardo confirmed a good fill curbside

Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 09:37, Wednesday 22 October 2025 - last comment - 15:46, Wednesday 22 October 2025(87645)
reverted changes to ASC gains, increased MICH LSC gain

Sheila, TJ, Oli, Matt

We reverted the ASC gain changes (87582) setting INP1 P to 1 and CSOFT P to 25 at MAX power (rather than 30).  Most of our locklosses overnight were from states before Max power, so the CSOFT P gain can't have been the problem, but we are undoing it for now just for the sake of reverting recent changes. 

We looked at one of the overnight locklosses, it seems that MICH is ringing up at 4.7 Hz.  Since Oli is sitting at 2W DCreadout to damp violin modes, we measured the MICH OLG there, and we see it is pretty close to unstable at 5Hz, with low coherence there.  We added a factor of 2 gain in LSC MICH2, to bring the UGF to 10 Hz similar to the references, and give us 35 degrees phase margin. 

Next we checked the SRCL UGF, which is also locked on POP45, and it's gain looks low by a factor of 5 compared to the reference.  This loop has a large phase bubble so it's still stable. POP 45 whitening gain and filters seem to be the same as a few days ago, and the POP LF power is the same as it was a few days ago at 2W.  PRCL gain also looks low compared to the reference, but is stable.  

We were able to get to OMC_WHITENING (almost to low noise), but while we were sitting there we had the old ring up.  We tried manually increasing the CSOFT P gain to 30, but the osciallation had already grown large and we lost lock anyway.  I've now put the csoft P gain back to 30 in max power in the guardian.  

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 15:39, Wednesday 22 October 2025 (87655)

To add to today's mysteries, I tried raising CHARD P gain by 20% in HBW to see if that would stabilize us, but that caused a lockloss, indicating that maybe CHARD P HBW is marginal.

We also had a lockloss while I was measuring the CHARD P HBW OLG, but I was running an injection that I had run earlier today, so that also doesn't make sense to me as being the cause.

We just tried powering up without moving the spots, but had a lockloss as soon as we got to 60 W.

 

david.barker@LIGO.ORG - 10:49, Wednesday 22 October 2025 (87647)

Following the reversion of gains in lscparams.py and the reload of ISC_LOCK, I also reloaded the nodes which import this file but do not use the modified lines in order to green-up GRD-CFC. Nodes loaded are:

ALIGN_IFO,ALS_COMM,ALS_DIFF,ALS_XARM,ALS_YARM,CAMERA_SERVO,H1_MANAGER,IMC_LOCK,INIT_ALIGN,ISC_DRMI,LASER_PWR,LOCKLOSS_SHUTTER_CHECK,OMC_LOCK,SEI_CONF,SEI_ENV,SQZ_FC,SQZ_MANAGER,SUS_CHARGE,TCS_ITMX_CO2_PWR,TCS_ITMY_CO2_PWR,TEST,THERMALIZATION,TMS_SERVO,VIOLIN_DAMPING

oli.patane@LIGO.ORG - 11:11, Wednesday 22 October 2025 (87649)

The ringup and lockloss in OMC_WHITENING was indeed the usual 1 Hz ringup 

Images attached to this comment
sheila.dwyer@LIGO.ORG - 12:50, Wednesday 22 October 2025 (87651)

We've had a lot of 0.6Hz wobbling in the move spots state, so Elenna made the move spots a2l gains different from final (undoing a change from this spring), and made the move spots ones the same a2l gains as they were before the camera bump (87473)

Attached is a comparison of the build ups in the move spots states before and after this change, things look about the same, so this hasn't fixed the wobbles.  

This isn't our main locking problem today, it doesn't seem to be causing our locklosses and gets better as we power up. 

Images attached to this comment
elenna.capote@LIGO.ORG - 15:46, Wednesday 22 October 2025 (87656)

Actually, we just realized we've been forgetting to change the MICH LSC gain before powering up, and looking back the last several locklosses have been due to MICH ringing up. I added a line in DRMI_TO_POP to increase the MICH2 gain to 2. I'm not sure if this is the best permanent solution, but it means we won't forget for now.

H1 SEI
jim.warner@LIGO.ORG - posted 18:35, Tuesday 21 October 2025 - last comment - 13:32, Wednesday 22 October 2025(87634)
BRSY not damping like it should, bypassed, not used for now

Something happened with BRSY this morning during maintenance that caused it to ring up more than normal and now the damping is not behaving quite as expected. For now, I have paused the ETMY sensor correction guardian with the BRSY out of loop and turned off the output of the BRS so it won't be used for eq mode, should that transition happen.

So far today, I did a bunch of "recapturing frames" in the BRS C# code, which has usually fixed this issue in the past. We also restarted the beckhoff computer, then the plc, C# and epics ioc. This did not recover the BRS either. Marc, Fil and I went to EY and looked at the damping drive in the enclosure and I think it was behaving okay. When the drive came on, the output would reach ~1.8V, then go to 0V when it turned off.

I've contacted UW and we will take a look at this again tomorrow. 

Comments related to this report
jim.warner@LIGO.ORG - 13:32, Wednesday 22 October 2025 (87653)

Looked at this with Michael and Shoshana and the BRS is damped down now. Still not sure what is wrong but we have a theory that one side of the capacitive damper is not actuating. This seems to work okay when the velocities are either low or very high, but if they are moderate the high gain damping doesn't work well enough to get the BRS below a certain threshold, and instead keeps the BRS moderately rung up. We adjusted the damping on/off thresholds so the high gain damping will turn off at a higher velocities.

I will try to do some tests with it next week to see if we can tell if one side of the damper is working better than the other. For now, we should be able to bring the BRS back in loop.

H1 DetChar (DetChar)
joan-rene.merou@LIGO.ORG - posted 13:51, Friday 10 October 2025 - last comment - 13:16, Wednesday 22 October 2025(87414)
Witness channels of the set of near-30Hz and near-100Hz combs at LHO
[Joan-Rene Merou, Alicia Calafat, Anamaria Effler, Sheila Dwyer, Robert Schofield, Jenne Driggers]

We have looked at the near-30 Hz and near-100 Hz combs (Detchar issue 340) in all of LHO Fscan channels (Full 148 channels list can be found in O4_H1_Fscan_ch_info.yml) to find witnesses and also channels where the amplitude and coherence change at the same dates as DARM.

The list of combs is the following one:

spacing (Hz) offset (Hz)
29.96951388880
99.9984548612570.02888889
99.998456790
99.9984629.9694
99.998472222589.90847222
99.998650
99.9984510.08992
29.96952520.17208
29.9695211589.9007589
29.96951374760.22840625
As reported by Xuanye Fan in Detchar issue 296, "it can be determined that the high-order harmonics disappeared on April 8, 2024, and reappeared on July 7, 2024". Hence, we have compared coherence with DARM in all the channels and the difference between July 1st and July 7th 2024. Following the findings by Xuanye, we have redone the comb time-evolution plots for all of these combs in order to check for dates where their amplitude changed. As can be seen in the plots below, there are two clear dates where changes in the behavior of the combs took place, April ~4th 2024 and July ~7th 2024. The attached plots to this post are similar to the ones generated by Fscan using FscanFineToothPlot plots, however, they have two differences: They use data from the non-normalized spectras instead of from the time average plots. Additionally, they compute the relative harmonic amplitude with respect to the median of the surrounding 1 Hz spectrogram. The attached plots confirm that there is a significant change in comb amplitude between April 4th and July 7th 2024. One clear example is shown here: Comb 99.9985 Hz Offset 29.9694 Hz amplitude evolution in O4 in DARM We list here the channels that do show most of these Combs. These same channels do show changes in coherence between July 1st and July 7th 2024, but do not show changes in the amplitude of the combs. - H1_IMC-F_OUT_DQ - H1_LSC-MCL_IN1_DQ - H1_LSC-MICH_IN1_DQ - H1_LSC-SRCL_IN1_DQ - H1_PEM-CS_MAG_EBAY_LSCRACK_X_DQ - H1_PEM-CS_MAG_EBAY_LSCRACK_Y_DQ - H1_PEM-CS_MAG_EBAY_LSCRACK_Z_DQ - H1_PEM-CS_MAG_LVEA_INPUTOPTICS_X_DQ - H1_PEM-CS_MAG_LVEA_INPUTOPTICS_Y_DQ - H1_PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ In most channels, the comb amplitude tends to get quite low after ~1500 Hz. The following sets of channels show differences between X, Y and Z: - H1_PEM-CS_MAG_EBAY_SUSRACK_X_DQ (Higher amplitudes and towards higher frequencies) - H1_PEM-CS_MAG_EBAY_SUSRACK_Y_DQ (Lower comb amplitudes) - H1_PEM-CS_MAG_EBAY_SUSRACK_Y_DQ (Lower comb amplitudes) Regarding CS_MAG_LVEA_OUTPUTOPTICS, these combs can be seen best in X, weaker in Y and almost non-existent in Z. (In CS_MAG_LVEA_INPUTOPTICS they look roughly the same height) - H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_X_DQ (Strongest) - H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_Y_DQ (Weaker lines) - H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_Z_DQ (Almost no lines) Same behavior at: - H1_PEM-CS_MAG_LVEA_VERTEX_X_DQ (Strongest lines) - H1_PEM-CS_MAG_LVEA_VERTEX_Y_DQ (Weaker lines) - H1_PEM-CS_MAG_LVEA_VERTEX_Z_DQ (Almost no lines) We can see that these combs mostly appear in the corner station. The combs do not appear in neither EX nor EY channels. However, comb 99.99865 Hz offset 0.000 appears in many EX, EY channels and does become more coherent after July 7th. However, it is very close to 100 Hz so it may be influenced by other round-number combs (?)
Images attached to this report
Comments related to this report
joan-rene.merou@LIGO.ORG - 11:04, Monday 20 October 2025 (87583)
Looking at the 52 additional channels listed in LHO ADC channels list, we have found the following information:

The combs appear in the following channels with high peaks and high coherence:
- H1:PEM-CS_ADC_5_18_2K_OUT_DQ 
- H1:PEM-CS_ADC_5_21_2K_OUT_DQ
- H1:PEM-CS_ADC_5_26_2K_OUT_DQ ! All combs appear here and with high peaks

Some combs appear in the following channels with low peaks and low coherence:
- H1:PEM-CS_ADC_5_22_2K_OUT_DQ
- H1:PEM-CS_ADC_5_23_2K_OUT_DQ
- H1:PEM-CS_ADC_5_24_2K_OUT_DQ

The following channels do not show the peaks but show an increase in coherence from July 1st to July 7th 2024:
- H1:PEM-CS_ADC_5_25_2K_OUT_DQ
- H1:PEM-CS_ADC_5_27_2K_OUT_DQ
- H1:PEM-CS_ADC_5_30_2K_OUT_DQ
 
Only the 99.99 Hz offset 0 combs appear in the following channels:
- H1:PEM-CS_ADC_4_27_2K_OUT_DQ
- H1:PEM-CS_ADC_4_28_2K_OUT_DQ
- H1:PEM-CS_ADC_5_19_2K_OUT_DQ
- H1:PEM-CS_ADC_5_20_2K_OUT_DQ
- H1:PEM-CS_ADC_5_31_2K_OUT_DQ

In the arms, the following channels show coherence with only the 99.99 Hz offset 0 combs:
- H1:PEM-EX_ADC_0_09_OUT_DQ
- H1:PEM-EX_ADC_0_13_OUT_DQ
- H1:PEM-EY_ADC_0_11_OUT_DQ
- H1:PEM-EY_ADC_0_12_OUT_DQ
- H1:PEM-EY_ADC_0_13_OUT_DQ
- H1:PEM-EY_ADC_0_14_OUT_DQ

The following channels show the unexpected behavior of showing the 99.99 Hz peak in July 1st with coherence, but it disappears on July 7th:
- H1:PEM-EX_ADC_0_12_OUT_DQ

In summary, after investigating the Fscan channel list and the additional channels. The ones that seem more promising as showing most of the lines with high coherence and high amplitude peaks are:

- H1:PEM-CS_ADC_5_18_2K_OUT_DQ 
- H1:PEM-CS_ADC_5_21_2K_OUT_DQ 
- H1:PEM-CS_ADC_5_26_2K_OUT_DQ 
- H1:IMC-F_OUT_DQ 
- H1:LSC-MCL_IN1_DQ 
- H1:LSC-MICH_IN1_DQ 
- H1:PEM-CS_MAG_EBAY_LSCRACK_X_DQ 
- H1:PEM-CS_MAG_EBAY_LSCRACK_Y_DQ
- H1:PEM-CS_MAG_EBAY_LSCRACK_Z_DQ
- H1:PEM-CS_MAG_LVEA_INPUTOPTICS_X_DQ
- H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Y_DQ
- H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ
- H1:PEM-CS_MAG_EBAY_SUSRACK_X_DQ
- H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS_X_DQ

Of these, channel H1:PEM-CS_ADC_5_26_2K_OUT_DQ appears to be the one with the highest amplitudes. The following figure illustrates its ASD and Coherence with DARM on the date of July 7, 2024, showing the peaks for the harmonics of the combs in this study. As can be seen in the ASD, the highest peaks are those in the list of the near-30 and near-100 Hz plots. The only peaks higher than these are the power mains at powers of 60 Hz. This channel shows all the combs listed. Most of these combs also show very high coherence with DARM.

H1:PEM-CS_ADC_5_26_2K_OUT_DQ
Images attached to this comment
joan-rene.merou@LIGO.ORG - 13:16, Wednesday 22 October 2025 (87652)
After determining in which channels the peaks appear present, we have studied the coincidence of changes in the comb heights versus the bias in the H1:SUS-ITMY_L3_ESDAMON_DC_OUT16.

The following figure shows the coincidences between the changes in the relative amplitude of the first harmonic of each comb (sort of SNR) in DARM and the mean counts in H1:SUS-ITMY_L3_ESDAMON_DC_OUT16 across time. It can be seen that previously to May 2nd, the channel count was set to 60. Once it changed to around -223 after that date, the SNR of the peaks overall increased in a sudden way. Afterwards in June 13th when the count was reduced to 0, most peaks got a much lower SNR at the same time.

Images attached to this comment
Non-image files attached to this comment
Displaying reports 341-360 of 85505.Go to page Start 14 15 16 17 18 19 20 21 22 End