Jim, Arnaud

Today we commissioned the CRS laser controls to allow turning on/off and changing the laser power from the control room. 

With this plus the work on the TEC from yesterday, we created a new CRS_LASER guardian with requestable states LASER_ON and LASER_OFF.

A summary of this guardian logic was written up by Claude under T2600470-v1. The main element of this logic is to make sure that the TEC is engaged before the laser is turned on.

Jim made a new laser medm screen accessible from the crs overview screen with all the new monitor channels he added on tuesday maintenance (alog, fig1) and the new guardian screen. The nominal values for the laser driver and the tec loop are shown in the ndscope attached (and the medm screenshot).

CRS_LASER.py Guardian (commited under the svn): /opt/rtcds/userapps/release/isi/common/guardian/CRS_LASER.py
crs_laser.py python script (commited under the svn): /opt/rtcds/userapps/release/isi/common/guardian/crs_laser.py (use with arguments "on" or "off")

Left to do : 

* Update the SOP with the new instructions on how to turn on/off the laser M2600128
* Finish the detailled write up of this new laser control scheme here T2600471
* Check on stability of the TEC loop overtime

TITLE: 10/02 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: None
SHIFT SUMMARY: Not much to report, there's an issue with the TR_CARM states to be further addressed tomorrow. Jim and Arnauld worked on some CRS damping.  ISC_LOCK is being held in down. Arnaud might touch the CRS a little more tonight.
LOG:                                                                                                                                                                           

00:15 UTC A few HAM3 ISI trips from CRS testing

Marc, Jennie, Fil, Richard,

Summary: Ruled out problems with QPD B or its in-chamber wiring. Pulled TIA chassis and fixed a loose cable but still not sure what is causing the high noise of QPD B segment 4. Might be time to reconnect the ground pin we pulled on the input cable to see if this somehow caused this problem?

Marc and I tried swapping the pins for segments 4 and 3 at the input to the TIA chassis variant 2 by using a breakout board. This means swapping the anodes (pins 9 and 10) and the cathodes (pins 22 and 23). I re-measured the ASD of QPD B dark noise, where reference 32-35 are today's measurement and 12-15 are the reference measurement from the 24th September. Before and after this change, segment 4 as readout in CDS has a higher noise than the other segments. Since swapping the channels at the TIA input made no change to this we can safely conclude that the problem is not with the in-vacuum equipment and instead with the TIA chassis.

Marc then tried unplugging the connections for both quadrants at the TIA input and, as we have seen previously, the excess noise disappears. References 12-15 are from 24th September and 40-43 are the measurement with the cables unplugged.

Then we pulled the chassis out to see if we could find any obvious problems. Fil and Marc noticed that the cable that connects the PCBs (D1001974) to the output of the chassis was not crimped properly at the inside of the output conenctor. Fil replaced this cable and recrimped the ends.

Marc and I then measured the noise of the chassis in the lab, first with no current sources connected to the input, then with a current source of 1uA at the TIA input.

Every channel had similar noise, with and without the current cource connected.

For no input, every channel has a noise of around 650 nVrms/root Hz at 10 Hz, except for segment 4 which had 900 nVrms/ root Hz. Note this is much smaller than the noise difference between the segments we saw in CDS when the chassis was plugged into the QPDB.

For a 1uA source, every segment has a noise level of around 60-80 uVrms/ root Hz.

We also checked the 4 inputs for the measurement and reference PDs (channels 1-17 at output of chassis) when no current source was attached. and these looked were all a similar level. See the pin in and out diagram here.

After replacing the chassis back in the rack and plugging in all the cables again I remeasured the spectra and did not see much change. The live traces are the measurements from today and refs 12-15 are the dark noise measurement from 24th September.

To sanity check myself I made one pot of various measurements of QPD B segment 4 over time (all with light shuttered and offsets on the QPD filter banks so that the average QPD sum stays the same as whent the shutter is open).

As you can see the noise was worse between 3rd and 4th of September, but only by a small amount. The noise became worse by an order of magnitude after the grounding pin was pulled on the TIA input cable on 16th September (LHO alog #91934).

I am now wondering if us pulling the ground pin on the input cable is what is causing this problem as we did not see it until after we did this. No idea why it would only affect one segment though.

I realized I hadn't alogged the model changes that were made last Tuesday to the CRS proc model. Most of the changes were to move the thermal controls off the commercial TEC we had plugged into 120v ac in the TCS rack to the frontend. This requires borrowing spare adc and dac channels from the HAM6 model, but also required adding a new LASER subsystem to the CRS library part. I also added a filter module that we will use for monitoring the CRS velocity. First screenshot shows the new LASER sub-block on the bottom edge, the new VEL filter module is highlighted in blue on the top right. Second image is inside the LASER block, we added 3 new epics mons for the low frequency laser monitor, high frequency and a photodiode in the laser. We also added a filter module that takes the TEC read back temperature as an input and outputs to the laser's peltier chip for thermal control. The DRIVE filter bank is used to drive the laser power. Arnaud is working on an alog for the guardian code. Channels for the laser block will be prefixed with H1:ISI-HAM3_CRSRY_LASER_*

(Sheila, Elenna, Luis, and Caroline)

This morning:

•  Elenna C, Camilla C, Sheila D, Corey G, and TJ S worked on ALS X/Y alignment (alog 92143). They ran the alignment baffle scripts, then ran a manual initial alignment of X-arm IR, PRX, MICH Dark, SR2 align and SR-Y.  (Note: SR2 guardian script can be used to align, but everything else needed to be aligned manually.)
• When locking ALS, we had some issues because the gate valve flags were not set properly. Once this was corrected, they were able to lock ALS.
• At the end of the alog, PRMI was locked and DRMI locking was in progress...

After Lunch:

• DRMI was locked on 1F. Elenna held us in ISC DRMI guardian state ACQUIRE_DRMI_1F so that we could measure the OLG and ensure that the digital gains were set correctly.

• ndscope:
  • DRMI RF 18 -> 196 cts
  • DRMI RF 90 -> 33 cts
  • PRMI -> 167 cts
• Mode hopping was an issue when locking DRMI 1F. To avoid this, the offset was applied. However, when we tried to transition to DRMI 3F, the offsets needed to be switched off and the mode hopping became an issue again. To fix the mode hopping, Elenna went back to PRMI to touch up the SRM and BS alignment, then brought us back to DRMI. This solved the mode hopping issue and allowed us to transition to DRMI 3F.
• Note: At around 2:48 pm Pacific, Elenna switched the SR3 heater to 1 W.
• The guardian was then transitioned to START_TR_CARM and began working on the CARM_TO_TR state. Once the guardian was brought to CARM_TO_TR state, we noticed that there were these large LSC Y transmission spikes. So, we backed off from continuing on and are unsure what caused these large spikes.

(Elenna C, Camilla C, Sheila D, Corey G, TJ S)

With both gate valves opened up last night at EX, work on recovery of EX for green arm locking began this morning.  RyanC mentioned in his summary last night that the ALSx laser was OFF, but  TJ found that it was ON this morning (as well as PCal laser and also High Voltage).  

ALSx Work

With the return of the X-arm, started out looking alignment for the Xarm with Baffle Alignments.

• 1513:  Tried running the  new BAFFLE_ALIGN_TMS via guardian twice, but it did not work (TJ also tried running it)
• TJ then tried running Baffle Align scripts, but got the note:  "PZT X TRIGGER NOT ON!"
• 1544:  Getting TMSx back in the ballpark by looking at a recent time [~3weeks ago] when ALSx green was locked)--->
  • Moved TMSx in ONLY Pitch (from -110 to -163).
• 1555:  (in parallel) CHANGE POL run for ALSX guardian by TJ
• 1602:  Shiela then started moving TMSx while watching the ALS Green QPDs (i.e. H1:ALS-X_QPD_[A/B]_[PIT/YAW] ), but it was a BIG move.  Suspecting something was bumped at this point (possibly ISCTEX in-air table or the TMSx). 
  • Template for this saved at: /opt/rtcds/userapps/release/als/h1/templates/ndscope/GreenQPDs_pointing_TMSx.yaml
• 1615 sheila/tj went to EX to check on alignment.
• 1630 Restored TMS pointing to undo the big yaw move Sheila needed earlier.
  • Camilla helped them with the pointing of TMSx from the Control Room
• TMS was eventually restored to a point close enough for locking; Sheila said only a very small move on the table of a mirror mount was needed (see TJs alog 92144)
• 1715 Tried BAFFLE ALIGN TMS via the guardian again, but still had no flashes.
  • Also no success running the script by hand (but got further than the attempt earlier in the morning)
• TJ & Sheila worked on TMS pit & yaw + offsets to improve alignment by hand while also watching camera & ndscope.  After a few iterations there was light on the ALSx camera, and... 
• Ran through Baffle Align states via guardian again but still had some issues (mainly not finding PDs as noted below)  
  • BAFFLE_ALIGN_TMS completed & both pd 1 & 4 found
  • BAFFLE_ALIGN_ITMx could NOT find pd1, but PD4 was found
    • Running by hand later:
      • able to find pd1 later
      • and working on pd4, but had to move itmx more by hand
      • TJ updated the paramaters for the BAFFLE Align guardians and this should be better next time.
  • BAFFLE_ALIGN_ETMx found pd1 but not pd4
• Finally, after the guardian fixes by TJ & Sheila, and with Baffle Align completing, ETMx was then tweaked by hand to improve flashes and then ALSx locked up.
• Elenna also took ITMx Green Camera Offsets after X-arm was aligned. (sdf is attached)

Overall:  It's thought the issue was mianly due to small misalignments for ISCTEX and the TMS

ALSy Work

Had good flashes for the Y-arm this morning same as noted by RyanC last night.  RyanC mentioned ITMy might not be in a good spot because he couldn't lock the y-arm.  But TJ was able to lock up the y-arm this morning (took ALS-Y guardian to LOCKED_SLOW_WFS_ETM_TMS). 

Separately from ALSx work, Elenna looked at Green Camera Offsets for ALSy:  "Since the baffle align script ran successfully for the y arm, I set the new green camera offsets for ITMY. This screenshot shows the SDF [attached]. The y arm ASC had converged properly before I reset the offsets. This alog: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=91841 you can reference for how this procedure is done."

Alignment Notes

Since we have no WFS (need to get rephased), still need to run a Manual Initial Alignment.  

• complete XARM_IR_LOCKED
• complete PRX_LOCKED, but 1st go to ACQUIRE_PRX & tweak up PRM  while looking at ASC-AS_A
• complete MICH DARK LOCKED while tweaking BS and looking at ASC-AS_A (to minimize) and get dark spot on AS_AIR
• Go to SR2 ALIGN & tweak up SR2
• Go to ACQUIRE SRY for SRM tweak ups (although Shiela mentioned the triggering was great for locking...or my touch up wasn't enough)

Moved on to DRMI locking

• But there were a few bugs which needed to be addressed (sounded like they were related to undoing changes to guardian to allow commissioning without the ETMs)

[Currently, they have locked PRMI and currently are working on DRMI!]

WP 13674

The anemometer in the corner station was replaced this morning. The wind vane is reporting the wind direction incorrectly. Wind speed seems correct. Looking at how to properly align the wind vane.

J. Kissel

As of 2026-10-01 18:50 UTC, all settings have been turned ON for the H23 and H45 ISI DIFF calculations in their nominal configuration. All settings are captured in the h1seiproc's SDF safe.snap file.

Attached are screenshots of all the screens involved for posterity.

Again, in each of the CPS, GS13, and SS output filter banks, the optional "to_nrad" = gain(0.064935) [1/m] FM1 module is turned ON for the Y and Z degrees of freedom.

See the bottom of LHO:92121 for the list of channels stored in the frames.

J. Kissel

I finished up the work designing the new H23 and H45 ISI DIFF user interface I started in LHO:92121.

You can find the new screen from the sitemap, under the SPI menu (see 1st screenshot).
    /opt/rtcds/userapps/release/spi/common/medm/
    Overview screen:
        ISI_CUST_DIFF_OVERVIEW.adl (2nd screenshot)
    DIFF MATRIX screen (generic screen that uses macro variables to open up each of the three different matrices from the overview)
        ISI_CUST_DIFF_MTRX.adl (3rd screenshot)

    CPS, GS13, and SS output filter banks (generic screens that use macro variables to open up H23 and H45)
        ISI_CUST_DIFF_CPS.adl
        ISI_CUST_DIFF_GS13.adl (4th screenshot)
        ISI_CUST_DIFF_SS.adl

All of the above screens have been committed to the specified userapps repo location as of rev 36168.

This morning we were struggling to get the baffle alignment scripts to run, complaining that the PZT trigger was off. Sheila looked and we only had light on one of the green in vac QPDs, so she and I went down to the table to investigate. The light going through the two irises before the periscope were slightly off center. We first tried moving ALS M9 (table layout) to better center on the iris and get light on QPD B, this didn't really work. Sheila then moved ALS M11 in +pitch by between 1/16-1/8 of a turn and this restored the light on QPD B. 

I did my best to take some pictures of where the beam now sits in relation to the two irises, but it's tough to tell as the image is blown out.

After GV20 had been locked opened, we opened GV19 to connect the EX volume with the beamtubes. The annulus volume was opened to the annulus ion pump before opening, there was a small increase in ion pump current but it quickly returned to normal, and the metal valve to the gate annulus was closed. Both EX gate valves are now open.

WP 13672

TL,DR: We measure SRC gouy phase with no ring heaters, no ifo heating, no SR3 heating to be 18.5 +-0.4 deg. With SR3 at 4 W we measured  22.1 +-0.6 deg.

Louis and I measured the SRC gouy phase using the inertial gouy phase measurement technique previously performed by Stefan. Here is a list of reference alogs: 66211, 52639, 52658 52504

Before O4, with no ring heaters, IFO heating, etc, Stefan measured the SRC single pass gouy phase to be 19.5 +- 0.4 deg.

Measurement procedure:

• I carefully aligned the beamsplitter on the MICH dark fringe, and SRY. I also ran an SR2 align to center us on AS_C
• We ensured PRM was misaligned, and IFO was aligned in an SRMI configuration (but not locked)
• I disengaged all whitening and dewhitening on AS_C
  • there is still some fixed whitening filter that we have to compensate in the analysis with zpk([40],[0.4],1,"n")
• Louis and Sheila set up a SRCL trigger on AS_C with upper threshhold 0.0120 and lower threshhold of -100. I placed an offset in SRCL2 of -1e6
  • Louis looked at where the troughs in AS_C were to ensure that we trigger on the darkest point of the fringe, where the SRC finesse is maximum
• We set up a dtt with IOP channels at the 65kHz rate, as well as the SRCL trigger channel so we can determine when the trigger occurs
  • H1:IOP-ASC0_MADC6_TP_CH8, H1:IOP-ASC0_MADC6_TP_CH9, H1:IOP-ASC0_MADC6_TP_CH10, H1:IOP-ASC0_MADC6_TP_CH11 correspond to AS_C segments 4, 3, 2, 1
• Louis and I ensured we properly captured the trigger by having me start the dtt template and then counting "one mississippi, two mississippi" in unison before Louis set the trigger element
  • later we realized we could just trigger when we saw that the template starts reporting that it is recording data
• It took several tries to get it right, and then we collected this measurement 5 times each: one set with ITM ring heaters at zero power (cooled for >24 hours) and SR3 heater zero, and one with SR3 heater at 4 W (after 3 hours heating) with ITM RH cold

Data analysis procedure:

• We exported the AS_C data and the trigger data into text files
• I used GWPY to apply the anti whitening filter zpk([40],[0.4],1,"n") to the IOP channels 
• I followed Stefan's analysis procedure to identify the 00 and 01 peaks, fit the 00 peaks with a cubic spline, and measure the difference between the 00 and 01 peaks
• Each measurement includes multiple fringes, so the result averages the calculated gouy phase and calculates the standard deviation
• Three of the five measurements from each of the cold and hot SR3 measurements were not very good, so they are not analyzed/analyzed but not reported here
  • "not very good" means either the triggering or alignment was not good enough to create good fringes, or the behavior of the fringes is confusing so I'm not sure if the result makes sense

Measurement systematics concerns:

Because of the low finesse of the SRC, distinctly identifying the 01 mode with peak finding next to the 00 mode can introduce bias. Sheila and I think that the best way to manage this bias is to fit the 00 peak and subtract it from the data, then peak find the 01. This is WIP.

In the meantime, I followed Stefan's method, where I leveraged the different response of each AS_C segment to HOMs, and found that seg1 is the most sensitive to the 00 mode and seg2 is the most sensitive to the 01 mode. I used seg1 to find the 00 mode, and those locations are used for the cubic spline fit. Then, I used the seg2 to find the 01 modes, and calculated the distance between these two modes for the gouy phase. I averaged the distance for all the fringes found in each measurement.

Results:

For cold IFO, no ring heaters, SR3 heater or other heating, the SRC single pass gouy phase is about 18.5 deg. This is one less degree of gouy phase than reported by Stefan in O4.

For cold IFO with SR3 heater set to 4 W (heated for 3 hours before measurement), the SRC single pass gouy phase is about 22.1-22.5 deg.

Plots are attached to this alog showing the fringes and the measured phase.

Some hypotheses:

These results indicate gouy phase has been reduced in the SRC. This could possibly be explained by the new beamsplitter having a different lens than the previous beamsplitter. The reduction in gouy phase could also explain why we are having such a significant mode hopping problem in DRMI 92046.

It appears that the SR3 heater can be used to increase the SRC gouy phase at least back to the O4 level, which may help our locking procedure.

I write that these are hypotheses because several other people are working on related studies that can help us understand if we are correct. Namely, we are using finesse to study if the new BS parameters can explain the loss in gouy phase, we are using what we know about the SR3 heater to see if the increase in gouy phase makes sense (and what heater setting we would need to correct the loss in phase), and we are also looking at data from an inertial PRC gouy phase measurement to see if we measure the same loss in gouy phase in the PRC. Keep an eye out for more information!

TITLE: 10/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 3mph Gusts, 1mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.13 μm/s 
QUICK SUMMARY:

EX is Open.  ALSx Laser needs to be turned ON (then will need to run baffle align GRD.  (also have a note from RyanC that ITMy might need to be put in a better spot).

Travis, Gerardo, Jordan, Betsy, Tyler, Richard

This morning we proceeded with the manual opening of GV20. Tyler had made a nice support for the input shaft on the gearbox to stabilize it while rotating the handwheel. This worked great, no additional oil leaked out of the gearbox after installation.

We had left the valve soft closed overnight, so we started raising the valve at 10:41:59 Pacific by turning the handwheel counter clockwise, stopping every 50 turns to check the ballnut/shaft collar gap. No issues found.

At turn 370, we tested to see if the handwheel would be driven backwards by the weight of the gate. No backwheeling was present, so we continued raising the valve stopping every 50 turns to check ballnut/ball screw height. At turn 620 we decided to increase the interval between stoppages to 100 turns. After turn 1520, the top of the ball screw was about even with the top of the clutch body. At 1920, there was enough exposed ball screw to install the safety plate and the locking collars. Locking collars were torqued to 140 in-lbs. 

We then continued raising the valve 300 turns (2") at a time, adjusting the lock collars at each interval, until the medm screen showed green.

Final turn count: 7161

Final ball screw height, +37.75" from top of clutch body (open position/green on medm) Note: Height stamped on side actuator body read 37 7/8" for the open position.

The interlock pin was then set, and lock collars were moved to top of safety plate, and torqued to 140 in-lbs. The handwheel was left installed on the gearbox with a clamp on it to prevent rotation.

Full set of compiled notes/details will be posted to the DCC with noises/turn counts/timestamps/ball screw heights/etc.  

Jim, Arnaud

wp 13661

We replaced the temporary CRS laser driver with the final version D1500207 (and PCB D1200719-v11) and commissioned the TEC loop. The AC powered Thorlabs TEC is now unplugged from the TCS-R2 rack.

In order of operation: 

• Took the Laser Chassis hosting the RIO Laser to the EE lab, and added screws and thermal paste between the Laser Diode and the butterfly mount, as recommended in section 7.4.2 of the laser user manual (E2600086). 
• Reconnected the Laser Chassis and verified we could still get the same power (and noise) with the temporary setup.
• Swapped the Laser Driver with the new one, still using the Thorlabs TEC and verified we could get to the same power as with the temporary driver. The knob must now be set at 8.5 to reach the max power.
• Turned off the drive to the laser, and commissioned the TEC loop, with the same settings as in 1053. The figure attached (fig1) shows the thermistor readback following the error point request. 
• After reaching stable temperature, we turned the laser back on and verified the hoqi power and noise was the same as before. Will leave in this state for tonight

To note, the plexiglass key protector was mounted in front of the wrong chassis (Laser Chassis instead of Laser Driver, which controls the state of the laser). We swapped it, so it matches the laser SOP. 

TITLE: 09/30 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.15 μm/s 
QUICK SUMMARY:

The XARM is open, there is now a full IFO to work with!

• 23:45 UTC SUSAUXBH234 model restart
• 23:57 UTC GV20 open
  • 00:21 GV19 soft open
  • 00:24 UTC GV19 open
• I started to run the baffle align GRD states before realizing that the ALS laser was not on... 
• The MSR racks temperatures have been rising over the past 12 hours                                                                                                                                                                                                                 

Updating the PCAL Epics variables based on the last few End station measurements. 

Suggested Epics values for H1: 
 

caput H1:CAL-PCALX_FORCE_COEFF_RHO_T 8301.33
Old : H1:CAL-PCALX_FORCE_COEFF_RHO_T 8300
New : H1:CAL-PCALX_FORCE_COEFF_RHO_T 8301.33
caput H1:CAL-PCALX_FORCE_COEFF_RHO_R 10721.3
Old : H1:CAL-PCALX_FORCE_COEFF_RHO_R 10713.3
New : H1:CAL-PCALX_FORCE_COEFF_RHO_R 10721.3
caput H1:CAL-PCALX_FORCE_COEFF_TX_PD_ADC_BG 9.46843
Old : H1:CAL-PCALX_FORCE_COEFF_TX_PD_ADC_BG 8.81815
New : H1:CAL-PCALX_FORCE_COEFF_TX_PD_ADC_BG 9.46843
caput H1:CAL-PCALX_FORCE_COEFF_RX_PD_ADC_BG 0.574209
Old : H1:CAL-PCALX_FORCE_COEFF_RX_PD_ADC_BG 0.56678
New : H1:CAL-PCALX_FORCE_COEFF_RX_PD_ADC_BG 0.574209
caput H1:CAL-PCALX_FORCE_COEFF_TX_OPT_EFF_CORR 0.987685
Old : H1:CAL-PCALX_FORCE_COEFF_TX_OPT_EFF_CORR 0.99331
New : H1:CAL-PCALX_FORCE_COEFF_TX_OPT_EFF_CORR 0.987685
caput H1:CAL-PCALX_FORCE_COEFF_RX_OPT_EFF_CORR 0.989862
Old : H1:CAL-PCALX_FORCE_COEFF_RX_OPT_EFF_CORR 0.9944
New : H1:CAL-PCALX_FORCE_COEFF_RX_OPT_EFF_CORR 0.989862
caput H1:CAL-PCALX_XY_COMPARE_CORR_FACT 1
Old : H1:CAL-PCALX_XY_COMPARE_CORR_FACT 0.99855
New : H1:CAL-PCALX_XY_COMPARE_CORR_FACT 1
caput H1:CAL-PCALY_FORCE_COEFF_RHO_T 7146.49
Old : H1:CAL-PCALY_FORCE_COEFF_RHO_T 7155.15
New : H1:CAL-PCALY_FORCE_COEFF_RHO_T 7146.49
caput H1:CAL-PCALY_FORCE_COEFF_RHO_R 10659.1
Old : H1:CAL-PCALY_FORCE_COEFF_RHO_R 10663.6
New : H1:CAL-PCALY_FORCE_COEFF_RHO_R 10659.1
caput H1:CAL-PCALY_FORCE_COEFF_TX_PD_ADC_BG 18.5852
Old : H1:CAL-PCALY_FORCE_COEFF_TX_PD_ADC_BG 18.3088
New : H1:CAL-PCALY_FORCE_COEFF_TX_PD_ADC_BG 18.5852
caput H1:CAL-PCALY_FORCE_COEFF_RX_PD_ADC_BG -0.635276
Old : H1:CAL-PCALY_FORCE_COEFF_RX_PD_ADC_BG -0.7353
New : H1:CAL-PCALY_FORCE_COEFF_RX_PD_ADC_BG -0.635276
caput H1:CAL-PCALY_FORCE_COEFF_TX_OPT_EFF_CORR 0.983803
Old : H1:CAL-PCALY_FORCE_COEFF_TX_OPT_EFF_CORR 0.99191
New : H1:CAL-PCALY_FORCE_COEFF_TX_OPT_EFF_CORR 0.983803
caput H1:CAL-PCALY_FORCE_COEFF_RX_OPT_EFF_CORR 0.986169
Old : H1:CAL-PCALY_FORCE_COEFF_RX_OPT_EFF_CORR 0.9931
New : H1:CAL-PCALY_FORCE_COEFF_RX_OPT_EFF_CORR 0.986169
caput H1:CAL-PCALY_XY_COMPARE_CORR_FACT 1
Old : H1:CAL-PCALY_XY_COMPARE_CORR_FACT 1.00092
New : H1:CAL-PCALY_XY_COMPARE_CORR_FACT 1