Displaying reports 45061-45080 of 88380.Go to page Start 2250 2251 2252 2253 2254 2255 2256 2257 2258 End
Reports until 10:55, Wednesday 17 October 2018
H1 ISC
gabriele.vajente@LIGO.ORG - posted 10:55, Wednesday 17 October 2018 (44620)
Automatic measurement of LSC sensing matrix

I wrote a script that automatically inject lines at 138 Hz in MICH, PRCL, SRCL, and measures the sensing matrix to POP and REFL RF signals.

The script is available in /opt/rtcds/userapps/release/isc/h1/scripts/lsc_sensing_matrix.py

Options are set at the beginning of the file. In particular excitations amplitudes and measurement time. The current excitations are tuned for full IFO in "high noise" state, i.e. before DC readout and before coil drivers to low noise.

The script outputs a matrix of the transfer functions from MICH2/PRCL2/SRCL2 _OUT to the POP_RF* and REFL_RF* signals. Also, it outputs a matrix of coherence of all signals with the excitation. The output is both in ASCII format and in HTML format, so that it can be easily copied and pasted into the logbook. The script saves the ASCII and HTML outputs to a file named lsc_sensing_DATE_TIME.txt and lsc_sensing_DATE_TIME.html.

A measurement performed at 2 W, before DC readout, it shown below:

Trans.func. [sigs / LSC_*2_OUT] MICH PRCL SRCL
H1:LSC-POP_A_RF9_I_ERR_DQ 5.55e-02 + 1.56e-02j 2.39e-02 + -1.04e-02j 1.09e-04 + 1.43e-05j
H1:LSC-POP_A_RF9_Q_ERR_DQ -2.50e-04 + 7.33e-05j -7.90e-05 + 1.02e-04j -4.50e-05 + -5.48e-06j
H1:LSC-POP_A_RF45_I_ERR_DQ -2.96e-04 + -7.45e-05j -6.55e-05 + 3.27e-05j -5.03e-05 + -7.17e-06j
H1:LSC-POP_A_RF45_Q_ERR_DQ -5.70e-04 + -1.71e-04j -4.10e-06 + -1.23e-06j 1.45e-05 + 2.01e-06j
H1:LSC-REFL_A_RF9_I_ERR_DQ 2.64e-06 + 4.66e-07j 9.27e-07 + -3.27e-07j -3.65e-09 + -5.16e-10j
H1:LSC-REFL_A_RF9_Q_ERR_DQ -8.92e-05 + -2.82e-05j -3.92e-05 + 1.54e-05j 1.75e-06 + 2.33e-07j
H1:LSC-REFL_A_RF45_I_ERR_DQ -5.40e-06 + -1.54e-06j -2.42e-06 + 1.04e-06j 6.85e-08 + 9.86e-09j
H1:LSC-REFL_A_RF45_Q_ERR_DQ 3.12e-06 + 8.99e-07j 1.05e-06 + -4.48e-07j -2.66e-08 + -3.79e-09j

 

Trans.func. [sigs / LSC_*2_OUT] MICH PRCL SRCL
H1:LSC-POP_A_RF9_I_ERR_DQ 5.76e-02 / 16 deg 2.61e-02 / -24 deg 1.10e-04 / 7 deg
H1:LSC-POP_A_RF9_Q_ERR_DQ 2.61e-04 / 164 deg 1.29e-04 / 128 deg 4.54e-05 / -173 deg
H1:LSC-POP_A_RF45_I_ERR_DQ 3.05e-04 / -166 deg 7.32e-05 / 153 deg 5.08e-05 / -172 deg
H1:LSC-POP_A_RF45_Q_ERR_DQ 5.95e-04 / -163 deg 4.29e-06 / -163 deg 1.47e-05 / 8 deg
H1:LSC-REFL_A_RF9_I_ERR_DQ 2.68e-06 / 10 deg 9.83e-07 / -19 deg 3.69e-09 / -172 deg
H1:LSC-REFL_A_RF9_Q_ERR_DQ 9.36e-05 / -162 deg 4.21e-05 / 159 deg 1.76e-06 / 8 deg
H1:LSC-REFL_A_RF45_I_ERR_DQ 5.61e-06 / -164 deg 2.64e-06 / 157 deg 6.92e-08 / 8 deg
H1:LSC-REFL_A_RF45_Q_ERR_DQ 3.25e-06 / 16 deg 1.14e-06 / -23 deg 2.69e-08 / -172 deg

 

Coherence [sigs / LSC_*2_EXC] MICH PRCL SRCL
H1:LSC-POP_A_RF9_I_ERR_DQ 1.000 1.000 1.000
H1:LSC-POP_A_RF9_Q_ERR_DQ 0.924 0.984 0.999
H1:LSC-POP_A_RF45_I_ERR_DQ 1.000 1.000 1.000
H1:LSC-POP_A_RF45_Q_ERR_DQ 1.000 0.990 1.000
H1:LSC-REFL_A_RF9_I_ERR_DQ 0.542 0.956 0.722
H1:LSC-REFL_A_RF9_Q_ERR_DQ 1.000 1.000 1.000
H1:LSC-REFL_A_RF45_I_ERR_DQ 1.000 1.000 1.000
H1:LSC-REFL_A_RF45_Q_ERR_DQ 1.000 1.000 1.000

The script also produces a I/Q radar plot, which is saved in lsc_sensing_DATE_TIME.png. However, I have not (yet) calibrated the LSC_*2_OUT signals in meters. Since those signals are going directly to BS, PRM and SRM suspensions, the numbers that Craig posted should be fine.

 

Images attached to this report
H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 10:22, Wednesday 17 October 2018 (44622)
Weekly PSL Chiller Reservoir Top-Off (FAMIS 10479)

Topped off Crystal Chiller with 125mL.
Crystal Chiller filter is more discolored than the Diode Chiller's filter; will send Jeff B. an email.

LHO General
kyle.ryan@LIGO.ORG - posted 10:08, Wednesday 17 October 2018 (44621)
Operated crane in the LEAA

~0930 - 0935 and ~0945 - 0955 hrs. local

H1 PSL
edmond.merilh@LIGO.ORG - posted 09:16, Wednesday 17 October 2018 (44619)
PSL Weekly Report - 10 Day Trends FAMIS #10579

Better late than never. All plots look to be nominally sound.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 08:13, Wednesday 17 October 2018 - last comment - 08:19, Wednesday 17 October 2018(44611)
Morning Status

TITLE: 10/17 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY:

Commissioners working on H1 after a quiet night seismically, & an ALL-GREEN CDS overview.

Comments related to this report
corey.gray@LIGO.ORG - 08:19, Wednesday 17 October 2018 (44612)

Jim reports BRS has been drifting out of range & this is mostly related to EX temperature drifts (see alog #44597).  He's going to talk to Richard to see about HVAC adjustments for EX.  We'll see if Commissioners can make headway with what we have; if BRS EX causes too much grief, Jim will need to re-center/damp at EX.

H1 ISC
jenne.driggers@LIGO.ORG - posted 07:51, Wednesday 17 October 2018 - last comment - 16:37, Wednesday 17 October 2018(44609)
DRMI ASC back on in acquisition sequence

This morning I put the DRMI ASC engagement back in, so that we're not only doing MICH ASC but all vertex ASC loops are closed and get offloaded before we start the CARM offset reduction sequence.  This should remove the need for us to constantly be adjusting the alignment of mirrors by hand in DRMI. 

So far this morning, however, I can't sit at full RF lock with the ASC loops closed.  I didn't try before I put the DRMI ASC back in, but the change in optic position is pretty small (as one would expect) when they get offloaded, so I don't see a reason why this would cause trouble.  Both by hand and with ASC engaged, I cannot get the POP18_I_NORM above 85, when normally (before yesterday's TCS tunings) we could reliably get to 93.  So, not a big difference, but certainly noticeable. 

The oscillation we see happens after we've finished SRC_ASC, after several tens of seconds.  It's about 1Hz, so not the same as the 20Hz oscillation that they were seeing last night at 20W.  Under investigation...

Comments related to this report
jenne.driggers@LIGO.ORG - 08:38, Wednesday 17 October 2018 (44615)

In full lock right now, we're hitting the ADC limit of 32k counts on the AS_C segment inputs.  Each time we hit the limit, the SRC2 error signals get a glitch.  I have lowered the analog gain of the AS_C segments by 9dB, which is one default-sized click on the analog gain slider. Now the inmons go about +- 20k counts.

I have not yet reset the dark offsets with this new analog gain. 

sheila.dwyer@LIGO.ORG - 12:05, Wednesday 17 October 2018 (44626)

The high violin modes can cause AS_C to saturate the ADC.

Jeff K and I talked about adding a monitor for all the violin modes (or all the fundamentals, 1st harmonics, second harmonics, ect) in the new OAF model.  That way the guardian can check the level of these monitors before engaging the SRC ASC (to check that we are not high enough to saturated the AS_C ADC) and before going to DC readout (to check that we are not saturating the DCPDs). 

For now the monitor is in ETMY MODE9.  the gain is set so that the amplitude of the monitor is roughly the amplitude of the highest individual mode monitor.  I added a check in ENGAGE_SRC_ASC that will notify the user if the amplitude is above 6.3, the threshold might need adjustment (this threshold might be too strict).

jenne.driggers@LIGO.ORG - 16:37, Wednesday 17 October 2018 (44636)

After Sheila's reminder, I have reverted my change to the analog gain of AS_C.

H1 ISC
jenne.driggers@LIGO.ORG - posted 06:13, Wednesday 17 October 2018 (44608)
CHECK_MICH_FRINGES now locks MICH length

I just finished adding a few lines to the ISC_LOCK guardian to lock the MICH length degree of freedom in the CHECK_MICH_FRINGES state, with the same settings we use during initial alignment.  When the BS is poorly aligned (as it was this morning, but things were good enough that I didn't feel the need to do a full initial alignment) and one needs to check the BS alignment, it can be quite slow, waiting for fringes to come and go.  So, now MICH locks and the AS Air camera exposure is increased so that we can align the BS by hand more easily.  Eventually we'll add ASC to this state if it's needed, but this should already be an improvement.

H1 TCS (AWC, TCS)
daniel.vander-hyde@LIGO.ORG - posted 23:26, Tuesday 16 October 2018 - last comment - 23:34, Tuesday 16 October 2018(44606)
TCS adjustments at 10 W

Sheila, Jenne, Gabriele, Hang, and Danny

 

Comments related to this report
sheila.dwyer@LIGO.ORG - 23:34, Tuesday 16 October 2018 (44607)

As Danny says, the interferometer isn't stable with 20W of input power and these TCS settings, but we think that these settings have reduced the sideband imbalance.  

In our first attempt to power up to 20W with these settings, (SRC still uncontrolled) we saw an oscillation in DSOFT pitch at around half a Hz.  With the SRC uncontrolled we could have a worse coupling of differential arm power to the test mass pitch.  This is why Hang implemented a version of DSOFT P which is similar to our higher bandwidth DSOFT P. 44602

The next time we powered up there was a large oscillation in our vertex LSC loops at around 20 Hz.  Since we have seen that the sideband imbalance is better and that the ration of 9 to 45 is lower with these TCS settings, we probably need to retune the LSC phases and input matrix.  

H1 ISC (GRD, Lockloss)
sheila.dwyer@LIGO.ORG - posted 23:14, Tuesday 16 October 2018 (44605)
Interferometer locking itself sunday evening

On October 15th Danny and I left the interferometer locked with the request set to low noise when we left.  It was left this way from 3:20 UTC to around 13 UTC when Gabriele and Jenne arrived and re-aligned it. Summary page 

There were 9 locking attempts over the 10 hour period, the interferometer made it to low noise 6 times, lost lock once from the state park ALS VCO (currently this happens right after the transition to RF DARM and engaging the DHARD WFS), once while closing the beam diverters, and once while trying to transition the common arms onto the transmitted IR signals.  

The lockloss page makes it easy to look up things like this.  All of these locks were short.  

H1 AOS
sheila.dwyer@LIGO.ORG - posted 23:12, Tuesday 16 October 2018 - last comment - 09:14, Wednesday 17 October 2018(44604)
violin modes

Today the violins were rung up again, either because of the large earthquake in New Caledonia last night or because of some maintence day activity.  

I've added ITMX mode1 (504.145Hz) to the guardian, it is damped using yaw with a positive gain and no phase shift.  

We are still having difficulties with the close pair of modes at 510.714 (ETMYMODE1) and 510.723Hz (called ETMY mode6).  I haven't seen any impact on 510.714 by actuating on ETMY in pit or yaw.  I am starting to wonder if that mode is really on ETMY. Mode1 is really on ETMY and can really be damped with a positive gain, although it is rung up badly right now.  

 

Comments related to this report
jenne.driggers@LIGO.ORG - 09:14, Wednesday 17 October 2018 (44618)

This pair is extremely rung up right now, above the 1e-12 level, so we're sitting at full 2W RF lock for a while to damp it. 

It looks like, as Sheila mentioned, that the mode6 is being well damped, and mode1 is just not going anywhere.

Images attached to this comment
H1 ISC (ISC)
hang.yu@LIGO.ORG - posted 23:07, Tuesday 16 October 2018 (44602)
HBW DSOFT Pit loop

Sheila, Hang

During power-ups today we saw some ~0.5 Hz oscillations in DSOFT Pitch that kept causing locklosses. Therefore we copied our CSOFT P setup to DSOFT P to increase its bandwidth. Specifically, we blended in to original DSOFT P signal (a comb of 4 trans QPDs that decouples the TMS drift) another comb of trans QPDs that are insensitive to DHARD. The blending freq is at 0.03 Hz, same as CSOFT. After the blending, for DS P we were able to engage the HBW control filters we used for CS P and pushed the filter bank gain up to 30. We also noticed that the input matrix for DS was a factor of 2 higher than the CS value, thus our current DS P loop should have a BW twice that of CS P, sufficient to damp the 0.5 Hz oscillation.

We have put the new setup in guardian and it seems fine to engage the soft loops with this new config.

H1 FMP (SEI)
jim.warner@LIGO.ORG - posted 16:15, Tuesday 16 October 2018 - last comment - 09:05, Wednesday 17 October 2018(44597)
BRSX is drifting out of range, looks like partly because of building temps

Attached plot shows 30 day trends of both BRSs DC positions and a temperature sensor in each box. Plots on the left are the DC position, plots on the right are the temps, EY is on top, EX is on bottom. It looks like both buildings have been heating up for a while, but BRSX is closer to it's limit and the temperature drift if pushing BRSX close to it's limits. The temperature in the box at EX is also about a half deg C higher than 30 days ago and that temperature is less stable now. This was going bad on it's own over the last two weeks, but the EX situation is made worse by my incursion today. I could re-balance if needed, but that's not a zero risk activity.

Images attached to this report
Comments related to this report
jim.warner@LIGO.ORG - 09:05, Wednesday 17 October 2018 (44616)

I'm attaching trends comparing both endstations for the last 30 days. For each plot, bottom left subplot is DC position of the BRS, top left is the temperature sensor in the box, and right side subplots are FMCS temperature sensors that seemed to have the strongest relationship to the BRS. First plot is EY, the upward tick in BRS temperature is me adding the thermos packs to the enclosure last week, this seems to have caused the equilibrium temp in the box to have moved up about .2 deg C, the building temps have been pretty stable over the whole period though. The second plot is the same for EX, with all the subplot ranges scaled to match the EY plot. Every sensor at  EX sees about a factor of 2 greater peak to peak daily range than EY. Additionally, the EX temperatures see a couple of temperature bumps over the last two weeks and the day to day variation seems to have gotten worse over that same time period.

I probably still have to rebalance BRSX after the work yesterday, but this isn't something we want to be dealing with every month, and this could be increasing BRS noise at very low frequencies.

Filed FRS ticket 11660.

Images attached to this comment
H1 IOO (IOO, PSL)
cheryl.vorvick@LIGO.ORG - posted 15:36, Tuesday 16 October 2018 - last comment - 13:44, Saturday 20 October 2018(44591)
IO Cooling Hoses Moved - some PSL accelerometor peaks are eliminated

I have long been concerned about the IO High Power Beam Dump (IO HPBD) at the North End of the PSL table, and it's cooling hoses hanging down from the beam dump, as a source of PSL table vibration.

I talked to Jason about doing a quick test, buy putting strain relief on the IO HPBD, and then looking at the PSL accelerometers.  The hoses are taped the side of the NE corner of the PSL table, wrapped in foam, so no direct contact with the table, and the hoses are not touching each other.

The results are clear, this change reduced the accelerometers broadband noise, and eliminated peaks in the Periscope accelerometers at 413Hz.  There are some peaks and broadband noise that increased, but I'm not worried about that, since we literally used tape, and the decrease and elimination of other peaks shows that careful strain relief of cooling lines will have a positive effect on the PSL table motion.

The IO HPBD also needs a better mount, as it's a very heavy component, made from metal plates and SiC plates, and currently it is mounted with a post and fork clamp.

No a bad result, for three pieces of tape, a small bit of foam.

Plots show power spectrums for all PSL ACCs, and coherence between the Periscope X and Y ACCs and the table Accs.

In the plots, all data from yesterday, 10/15, at 19:17UTC are shown in black, and data from today, 10/16, at 19:17UTC are shown in colors other than black.

- Jason, Cheryl

Images attached to this report
Comments related to this report
stephen.appert@LIGO.ORG - 09:05, Wednesday 17 October 2018 (44617)

Neat result, and thanks for the description and plots!!

Would it be too much to ask for a before photo and after photo overlaid onto a plot of the most insightful channel(s), with clear before/after labels? I am having trouble sifting through the >10 plots and trying to make sense of the various channels and states - some plots that I would expect to see no peak I see peaks, and I suspect I am just misinterpreting the state of the system when the data was captured.

H1 DetChar
gabriele.vajente@LIGO.ORG - posted 13:01, Tuesday 16 October 2018 - last comment - 14:16, Wednesday 17 October 2018(44585)
Sensitivity trend during locks

During all lock stretches, the sensitivity steadily degrades over time. The plot below shows the range trend over one of the last locks.

I picked a few times during the lock, when there were likely no actions on the IFO, and computed the DARM spectrum. The evolution is shown below

Clearly, what degrades the sensitivity is very well approximated by a 1/f displacement noise.

Here's a comparison of degrading sensitivity over another long lock stretch. Similar 1/f noise

 

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 23:07, Tuesday 16 October 2018 (44603)

This seems to be the same noise that we saw when the CARM noise gain was accidentally low.  As the high frequency noise get worse (presumably because the frequency noise coupling get worse) the noise at 100 Hz gets worse. 

gabriele.vajente@LIGO.ORG - 11:29, Wednesday 17 October 2018 (44623)

BruCo is running again on ldas-pcdev12. Here are two scans comparing the "low" and "high" noise times:

Low noise: https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1223676058/
High noise: https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1223680111/

keita.kawabe@LIGO.ORG - 13:47, Wednesday 17 October 2018 (44629)DetChar, ISC

It's CM settings that were somehow screwed up on Sunday evening. (Craig, Keita)

As noted in alog 44533 CM gain used to be low (that's what Sheila was talking about when she wrote "CM gain was accidentally low") before  Craig changed in on Oct/11, and after the change the frequency noise (in kHz range) as well as 100Hz noise got better.

It stayed that way for 3.5 days or so, but the bad behavior came back on 2018/Oct/14 23:30 UTC and it stayed bad since then (first attachment.) That's Sunday 16:30 Pacific or so.

It turns out that CM settings were somehow changed (second attachment) at that time though people were not working on CM at all (second attachment).

I and Craig are trying to figure out what happened.

Note that when it was really bad the excess noise was not smooth, it had a bump (e.g. look at  this plot from alog 44533).

Images attached to this comment
craig.cahillane@LIGO.ORG - 14:16, Wednesday 17 October 2018 (44632)ISC
Somehow, between the time Keita pointed out as "Something Happened" and the previous lock, there was an error added to step 13 of CARM_TO_ANALOG:


if self.counter == 13 and self.timer['wait']:
    if ezca['IMC-REFL_SERVO_IN2GAIN'] < 0:
        ezca['IMC-REFL_SERVO_IN2GAIN'] += 1 # from -12 to 0 dB
        ezca['LSC-MCL_GAIN'] *= round(10**(1./20),4) # from 34.6 to 47.6 dB
    else:
        self.timer['wait'] = 0.5
        self.counter += 1
    self.counter += 1


This error basically caused CARM_TO_ANALOG to skip this step without adding an additional 11 dB of gain to CARM.  
The line highlighted in red has been removed.  Our frequency noise suppression should return.  

As a test of 1/f noise, we can get to NOMINAL LOW NOISE and reduce the CARM gain to see if this low frequency coupling changes somehow.
Images attached to this comment
H1 CAL (CDS, DetChar)
jeffrey.kissel@LIGO.ORG - posted 12:40, Tuesday 16 October 2018 - last comment - 08:32, Wednesday 17 October 2018(44588)
List of New/Updated Channels for GDS Consumption regarding Calibration
D. Barker, J. Kissel
WP 7850
ECR E1800246
IIET 11305

Some more belated documentation in support of the front-end model changes that we made last week in order to support new / updated calibration code for O3:
Below is an explicit list of front-end generated channels that need to be removed from the GDS broadcaster, and a list of the new channels that should be used instead and/or replaced. It's also attached for any user's convenience.
One can cross-reference the list of new (slow) channels in our documentation that supports the new calculation for time-dependence, T1700106.

Channels to be removed:

FAST CHANNELS:
    CAL-CS_LINE_SUM_DQ                           # Agreed, disappears (DARM_LINE no longer exists)
    CAL-DARM_CTRL_WHITEN_OUT_DBL_DQ              # Agreed, replaced by simply DARM_CTRL_DQ (which is, yes, whitened, and stored as a double)
    CAL-DARM_ERR_WHITEN_OUT_DBL_DQ               # Agreed, replaced by simply DARM_ERR_DQ (which is, yes, whitened, and stored as a double)
    CAL-INJ_ODC_CHANNEL_OUT_DQ                   # Agreed, removed because we'll never do hardware injections from the cornerstation (i.e. on the ESD)

SLOW CHANNELS:
    CAL-CS_TDEP_DARM_LINE1_REF_A_TST_IMAG        # Agreed, disappears (no more DARM_LINE)
    CAL-CS_TDEP_DARM_LINE1_REF_A_TST_REAL        #      |
    CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_IMAG       #      |
    CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_INV_IMAG   #      |
    CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_INV_REAL   #      |
    CAL-CS_TDEP_DARM_LINE1_REF_A_USUM_REAL       #      V
    CAL-CS_TDEP_DARM_LINE1_UNCERTAINTY           #      --
    CAL-CS_TDEP_ESD_LINE1_REF_A_TST_NOLOCK_IMAG        # Agreed, disappears (renamed to SUS_LINE1)
    CAL-CS_TDEP_ESD_LINE1_REF_A_TST_NOLOCK_REAL        # Agreed, disappears (renamed to SUS_LINE1)
    CAL-CS_TDEP_ESD_LINE1_REF_C_IMAG                   # Agreed, disappears (renamed to SUS_LINE1)
    CAL-CS_TDEP_PCALY_LINE1_UNCERTAINTY                # Agreed -- made generic to P    CAL_LINE1
    CAL-CS_TDEP_PCALY_LINE2_REF_A_TST_IMAG             # Agreed -- made generic to PCAL_LINE2
    CAL-CS_TDEP_PCALY_LINE2_REF_A_TST_REAL             #     |
    CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_IMAG            #     |
    CAL-CS_TDEP_PCALY_LINE2_REF_A_USUM_REAL            #     |
    CAL-CS_TDEP_PCALY_LINE2_REF_C_NOCAVPOLE_IMAG       #     |
    CAL-CS_TDEP_PCALY_LINE2_REF_C_NOCAVPOLE_REAL       #     |
    CAL-CS_TDEP_PCALY_LINE2_REF_D_IMAG                 #     |
    CAL-CS_TDEP_PCALY_LINE2_REF_D_REAL                 #     V
    CAL-CS_TDEP_PCALY_LINE2_UNCERTAINTY                #     --
    CAL-CS_TDEP_PCALY_LINE3_UNCERTAINTY                # Agreed -- made generic to PCAL_LINE3
    CAL-CS_TDEP_PCALY_LINE4_REF_A_TST_IMAG             # Agreed -- made generic to PCAL_LINE2
    CAL-CS_TDEP_PCALY_LINE4_REF_A_TST_REAL             # Agreed -- made generic to PCAL_LINE4
    CAL-CS_TDEP_PCALY_LINE4_REF_A_USUM_IMAG            #     |
    CAL-CS_TDEP_PCALY_LINE4_REF_A_USUM_REAL            #     |
    CAL-CS_TDEP_PCALY_LINE4_REF_C_NOCAVPOLE_IMAG       #     | 
    CAL-CS_TDEP_PCALY_LINE4_REF_C_NOCAVPOLE_REAL       #     |
    CAL-CS_TDEP_PCALY_LINE4_REF_D_IMAG                 #     V
    CAL-CS_TDEP_PCALY_LINE4_REF_D_REAL                 #     --
    CAL-CS_TDEP_REF_CLGRATIO_CTRL_IMAG                 # Agreed -- no longer needed
    CAL-CS_TDEP_REF_CLGRATIO_CTRL_REAL                 # Agreed -- no longer needed             
    CAL-CS_TDEP_REF_INVA_CLGRATIO_TST_IMAG             # Agreed -- renamed to (for a given SUS_LINE) INVA_$(ISOSTAGE)_RESPRATIO 
    CAL-CS_TDEP_REF_INVA_CLGRATIO_TST_REAL             # Agreed -- renamed to (for a given SUS_LINE) INVA_$(ISOSTAGE)_RESPRATIO 


New Channel List:

FAST CHANNELS: 
('IFO generic channel name' 'sample rate' 'data storage type')
(when sample rate not listed, rate is 16384 Hz)
   CAL-CS_DARM_ERR_DQ double
   CAL-CS_DARM_CTRL_DQ double

   CAL-CS_DELTAL_RESIDUAL_DQ double
   CAL-CS_DELTAL_CTRL_DQ 4096 double
   CAL-CS_DELTAL_CTRL_TST_DQ 4096 double
   CAL-CS_DELTAL_CTRL_PUM_DQ 4096 double
   CAL-CS_DELTAL_CTRL_UIM_DQ 4096 double
   CAL-CS_DELTAL_EXTERNAL_DQ

   CAL-CS_CFTD_DELTAL_RESIDUAL_DQ double
   CAL-CS_CFTD_DELTAL_CTRL_DQ 4096 double
   CAL-CS_CFTD_DELTAL_CTRL_TST_DQ 4096 double
   CAL-CS_CFTD_DELTAL_CTRL_PUM_DQ 4096 double
   CAL-CS_CFTD_DELTAL_CTRL_UIM_DQ 4096 double
   CAL-CS_CFTD_DELTAL_EXTERNAL_DQ

SLOW CHANNELS:
   CAL-CS_TDEP_PCAL_LINE1_CORRECTION_REAL
   CAL-CS_TDEP_PCAL_LINE1_CORRECTION_IMAG
   CAL-CS_TDEP_PCAL_LINE2_CORRECTION_REAL
   CAL-CS_TDEP_PCAL_LINE2_CORRECTION_IMAG
   CAL-CS_TDEP_PCAL_LINE4_CORRECTION_REAL      # yes 4, not 3
   CAL-CS_TDEP_PCAL_LINE4_CORRECTION_IMAG
   CAL-CS_TDEP_SUS_LINE1_REF_INVA_UIM_RESPRATIO_REAL 
   CAL-CS_TDEP_SUS_LINE1_REF_INVA_UIM_RESPRATIO_IMAG
   CAL-CS_TDEP_SUS_LINE2_REF_INVA_PUM_RESPRATIO_REAL 
   CAL-CS_TDEP_SUS_LINE2_REF_INVA_PUM_RESPRATIO_IMAG
   CAL-CS_TDEP_SUS_LINE3_REF_INVA_TST_RESPRATIO_REAL 
   CAL-CS_TDEP_SUS_LINE3_REF_INVA_TST_RESPRATIO_IMAG
   CAL-CS_TDEP_PCAL_LINE2_REF_C_NOCAVPOLE_REAL 
   CAL-CS_TDEP_PCAL_LINE2_REF_C_NOCAVPOLE_IMAG
   CAL-CS_TDEP_PCAL_LINE4_REF_C_NOCAVPOLE_REAL 
   CAL-CS_TDEP_PCAL_LINE4_REF_C_NOCAVPOLE_IMAG
   CAL-CS_TDEP_PCAL_LINE2_REF_D_REAL 
   CAL-CS_TDEP_PCAL_LINE2_REF_D_IMAG
   CAL-CS_TDEP_PCAL_LINE4_REF_D_REAL 
   CAL-CS_TDEP_PCAL_LINE4_REF_D_IMAG
   CAL-CS_TDEP_PCAL_LINE2_REF_A_UIM_REAL   
   CAL-CS_TDEP_PCAL_LINE2_REF_A_UIM_IMAG
   CAL-CS_TDEP_PCAL_LINE2_REF_A_PUM_REAL  
   CAL-CS_TDEP_PCAL_LINE2_REF_A_PUM_IMAG
   CAL-CS_TDEP_PCAL_LINE2_REF_A_TST_REAL  
   CAL-CS_TDEP_PCAL_LINE2_REF_A_TST_IMAG
   CAL-CS_TDEP_PCAL_LINE4_REF_A_UIM_REAL  
   CAL-CS_TDEP_PCAL_LINE4_REF_A_UIM_IMAG
   CAL-CS_TDEP_PCAL_LINE4_REF_A_PUM_REAL  
   CAL-CS_TDEP_PCAL_LINE4_REF_A_PUM_IMAG
   CAL-CS_TDEP_PCAL_LINE4_REF_A_TST_REAL  
   CAL-CS_TDEP_PCAL_LINE4_REF_A_TST_IMAG
   CAL-CS_TDEP_SUS_LINE1_REF_UIM_NOLOCK_REAL  
   CAL-CS_TDEP_SUS_LINE1_REF_UIM_NOLOCK_IMAG
   CAL-CS_TDEP_SUS_LINE2_REF_PUM_NOLOCK_REAL  
   CAL-CS_TDEP_SUS_LINE2_REF_PUM_NOLOCK_IMAG
   CAL-CS_TDEP_SUS_LINE3_REF_TST_NOLOCK_REAL 
   CAL-CS_TDEP_SUS_LINE3_REF_TST_NOLOCK_IMAG


This should help alleviate some of the problems that folks have been having with the GDS Broadcaster since last week's upgrade (e.g. LHO aLOG 44454).
Non-image files attached to this report
Comments related to this report
aaron.viets@LIGO.ORG - 16:05, Tuesday 16 October 2018 (44596)CDS, DetChar

In addition to Jeff's list, the GDS calibration pipeline also needs these:

Fast channels:

  • ODC-MASTER_CHANNEL_OUT_DQ (16384 Hz)   (Note - we may no longer need this in the near future.)
  • SUS-ETMY_L3_CAL_LINE_OUT_DQ (512 Hz)
  • SUS-ETMY_L2_CAL_LINE_OUT_DQ (512 Hz)
  • SUS-ETMY_L1_CAL_LINE_OUT_DQ (512 Hz)
  • CAL-PCALY_RX_PD_OUT_DQ (16384 Hz)
  • CAL-PCALY_TX_PD_OUT_DQ (16384 Hz)
  • PEM-EY_MAINSMON_EBAY_1_DQ (1024 Hz)
  • IMC-WFS_A_DC_PIT_OUT_DQ (2048 Hz)
  • IMC-WFS_B_DC_PIT_OUT_DQ (2048 Hz)
  • IMC-WFS_A_DC_YAW_OUT_DQ (2048 Hz)
  • IMC-WFS_B_DC_YAW_OUT_DQ (2048 Hz)
  • PSL-DIAG_BULLSEYE_YAW_OUT_DQ (2048 Hz)
  • PSL-DIAG_BULLSEYE_WID_OUT_DQ (2048 Hz)
  • PSL-DIAG_BULLSEYE_PIT_OUT_DQ (2048 Hz)
  • ASC-DHARD_P_OUT_DQ (512 Hz)
  • ASC-DHARD_Y_OUT_DQ (512 Hz)
  • ASC-CHARD_P_OUT_DQ (512 Hz)
  • ASC-CHARD_Y_OUT_DQ (512 Hz)
  • LSC-SRCL_IN1_DQ (16384 Hz)
  • LSC-MICH_IN1_DQ (16384 Hz)
  • LSC-PRCL_IN1_DQ (16384 Hz)

Slow channels (all 16 Hz):

  • CAL-CS_TDEP_SUS_LINE1_UNCERTAINTY
  • CAL-CS_TDEP_SUS_LINE2_UNCERTAINTY    
  • CAL-CS_TDEP_SUS_LINE3_UNCERTAINTY 
  • CAL-CS_TDEP_PCAL_LINE1_UNCERTAINTY
  • CAL-CS_TDEP_PCAL_LINE2_UNCERTAINTY
  • CAL-CS_TDEP_PCAL_LINE4_UNCERTAINTY
john.zweizig@LIGO.ORG - 18:45, Tuesday 16 October 2018 (44598)CDS, DetChar
The following channels in the list of channels to be added do not ppear in the H-H1_R frames:

CAL-CS_DARM_ERR_DQ
CAL-CS_DARM_CTRL_DQ
CAL-CS_DELTAL_RESIDUAL_DQ
CAL-CS_DELTAL_CTRL_DQ
CAL-CS_DELTAL_CTRL_TST_DQ
CAL-CS_DELTAL_CTRL_PUM_DQ
CAL-CS_DELTAL_CTRL_UIM_DQ
CAL-CS_DELTAL_EXTERNAL_DQ
CAL-CS_CFTD_DELTAL_RESIDUAL_DQ
CAL-CS_CFTD_DELTAL_CTRL_DQ
CAL-CS_CFTD_DELTAL_CTRL_TST_DQ
CAL-CS_CFTD_DELTAL_CTRL_PUM_DQ
CAL-CS_CFTD_DELTAL_CTRL_UIM_DQ
CAL-CS_CFTD_DELTAL_EXTERNAL_DQ
CAL-CS_TDEP_SUS_LINE1_REF_UIM_NOLOCK_REAL
CAL-CS_TDEP_SUS_LINE1_REF_UIM_NOLOCK_IMAG
CAL-CS_TDEP_SUS_LINE2_REF_PUM_NOLOCK_REAL
CAL-CS_TDEP_SUS_LINE2_REF_PUM_NOLOCK_IMAG
CAL-CS_TDEP_SUS_LINE3_REF_TST_NOLOCK_REAL
CAL-CS_TDEP_SUS_LINE3_REF_TST_NOLOCK_IMAG

But these do, and were in the list I originally compiled from lists I received from Maddie and Aaron...

CAL-CS_TDEP_SUS_LINE1_REF_A_UIM_NOLOCK_IMAG
CAL-CS_TDEP_SUS_LINE1_REF_A_UIM_NOLOCK_REAL
CAL-CS_TDEP_SUS_LINE2_REF_A_PUM_NOLOCK_IMAG
CAL-CS_TDEP_SUS_LINE2_REF_A_PUM_NOLOCK_REAL
CAL-CS_TDEP_SUS_LINE3_REF_A_TST_NOLOCK_IMAG
CAL-CS_TDEP_SUS_LINE3_REF_A_TST_NOLOCK_REAL
CAL-DARM_CTRL_DBL_DQ
CAL-DARM_ERR_DBL_DQ
aaron.viets@LIGO.ORG - 19:30, Tuesday 16 October 2018 (44600)

These channel names (similar to the names Jeff suggested) do appear in the H-H1_R frames:

  • CAL-CFTD_DELTAL_CTRL_DBL_DQ 4096
  • CAL-CFTD_DELTAL_CTRL_PUM_DBL_DQ 4096
  • CAL-CFTD_DELTAL_CTRL_TST_DBL_DQ 4096
  • CAL-CFTD_DELTAL_CTRL_UIM_DBL_DQ 4096
  • CAL-CFTD_DELTAL_EXTERNAL_DQ 16384
  • CAL-CFTD_DELTAL_RESIDUAL_DBL_DQ 16384
  • CAL-DELTAL_CTRL_DBL_DQ 4096
  • CAL-DELTAL_CTRL_PUM_DBL_DQ 4096
  • CAL-DELTAL_CTRL_TST_DBL_DQ 4096
  • CAL-DELTAL_CTRL_UIM_DBL_DQ 4096
  • CAL-DELTAL_EXTERNAL_DQ 16384
  • CAL-DELTAL_RESIDUAL_DBL_DQ 16384

Perhaps Jeff or Evan can confirm whether these are the correct channels.

jeffrey.kissel@LIGO.ORG - 08:32, Wednesday 17 October 2018 (44614)
Yes -- apologies -- I'd forgotten that the RCG adds "_DBL" to channels stored at double precision. Aaron's list is correct.
Displaying reports 45061-45080 of 88380.Go to page Start 2250 2251 2252 2253 2254 2255 2256 2257 2258 End