Displaying report 1-1 of 1.
Reports until 17:05, Friday 11 March 2022
H1 CAL (ISC, SUS)
brad.ratto@LIGO.ORG - posted 17:05, Friday 11 March 2022 - last comment - 14:12, Monday 14 March 2022(62191)
Compensating for ETMY, ITMX, and ITMY PUM Driver **UPDATED**

Brad Ratto 

The purpose of this aLOG is to update the results from the *now* corrected modeling script used to determine the incurred systematic error as a result from the PUM driver models in the different operating states. This aLOG is also intended to support the conclusions made in (LHO:62152), which, quoting Jeff, are:

In order to keep true to Jeff's word, "Brad's going to work through correcting my mistake in the modeling scripts and redo the conclusions from LHO aLOGs 61729 and 61985." Let me now walk through the results from the updated script. (Some notes on the updated script will follow as well)

In similar fashion to LHO:61729, and as a reminder, the plots are produced using data from the following dates:
ETMX-PUM: 2022-01-14
ETMY-PUM: 2022-01-17
 ITMX-PUM: 2022-01-10
 ITMY-PUM: 2022-01-11

This time around, I will only present the results from ETMX. The full list of plots for all the states and TMs can be found here under the folders with the same dates noted above. To begin, we review the "goodness" of our models versus the measurements taken. As a quick reminder State 1 (no switchable response on) and State 2 (highest range, high gain, "Acquire ON" state), and State 3, "Low Pass ON". 

State 1: 2022-01-14_H1SUSETMX_PUMDriver_S1000343_40Ohm_State1_ALL_CoilCompensationComparsion.pdf
State 2: 2022-01-14_H1SUSETMX_PUMDriver_S1000343_40Ohm_State2_ALL_CoilCompensationComparsion.pdf
State 3: 2022-01-14_H1SUSETMX_PUMDriver_S1000343_40Ohm_State3_ALL_CoilCompensationComparsion.pdf

The color legend:
(BLUE) The the measured data, normalized the unity, we are not interested in the DC gain for this analysis, by dividing out the magnitude of the measured data at the lowest frequency point, 0.2 Hz.
(ORANGE) Shows the full zero-pole response, this includes the super-nyquist zeros and poles.
(GREEN) If we were to ignore the super-nyquist zeros and poles and only compensate with the zeros and poles at sub-nyquist frequencies.

It is important to note that we no longer "fold in" the response of the AOSEM in our measurement for models, hence the *only* difference between the full (ORANGE) and the reduced (GREEN) is the exclusion of super nyquist frequency pole and zeros (As noticed in State 2). However, there is an important note to take into account, opening up the plots for State 3 relieves that there is infact a difference between the full and reduced models when there should NOT be (The reason as to why there should NOT be a difference is because there are NO super nyquist frequency poles present in State 3 to get "rid of"). Rather the difference is in how State 3 is constructed in the modeling script. The "full" model for State 3 is taken as given by the fitter, where as the reduced model is constructed from the measurment fits of State 1 and the LP filter, remember State 3 is simply a superposition of "Low Pass ON" and "Acquire OFF" (State 1). The important conclusion to draw from the State 3 model comparision plots is that it is infact "better" in terms of model accuracy to use the superposition of the indvidal states rather than relying on the fitter, see the right panels of the State 3 plots in which the residual is plotted between the measurment and each of the models.

I will now pivot to showing plots of the modeled magnitude and phase systematic error in the PUM actuation transfer function in State 3 and how it then later affects the response function. See bullets (2)-(5) LHO:61729 for the rationale on how this is done. And again, the results for all the other states and TMs are found here.

The plot for the systematic error as seen in the PUM actuation between the two models is seen here: 2022-01-14_H1SUSETMX_PUMDriver_S1000343_40Ohm_State3_etaPUM_Comparison.pdf

And finally in the response function itself: 2022-01-14_H1SUSETMX_PUMDriver_S1000343_40Ohm_State3_etaR_w_etaPUM_Comparison.pdf

As you can see in the plots for the response function the systematic error in the magnitude is no larger than four hundredths of a percent in magnitude and no larger than six hundredths of a degree in the phase. Armed with these plots and results, it can be said the "old" compenstation method still holds wrt to the PUM drivers.

Some comments regarding the script. I made a few changes so that it is *easier* to use, rather than having four seperate copies for each TM, the script now runs using a #TM#_PUM_config.ini file. See the ETMX_PUM_config.txt as an example of what the format is for ETMX below. A few important notes about the format, when listing poles and zeros there must be a space after the comma, complex numbers must be type WITHOUT any spaces (ie 5+4j) and the coils must be listed in the same order for each state and must have the following order: UL, LL, UR, LR. 

The script and the other TM .ini files live here

Non-image files attached to this report
Comments related to this report
brad.ratto@LIGO.ORG - 14:12, Monday 14 March 2022 (62202)

A comment with the intent to further clarify the statement found above. "The "full" model for State 3 is taken as given by the fitter, where as the reduced model is constructed from the measurement fits of State 1 and the LP filter, remember State 3 is simply a superposition of "Low Pass ON" and "Acquire OFF" (State 1)."

The ‘full’ model and corresponding residual for State 3 is the fit of total measured response of the driver in State 3, and the residual is the product of this measurement and (1/fit). The reduced model and corresponding residual is constructed from the measurement fits of State 1 alone, and the ratio of State 3 / State 1 measurements, which isolates the LP filter separately, and the residual is the total measured response as the measurement as before, but now multiplied by (1/fit) of State 1 along and by (1 / fit) of State 3 / State 1. This is done to reflect how the frequency response is compensated, where when the user requests ’State 3’ the ’State 1,’ ‘Acquire OFF’ filters are left ON and the ‘LP ON’ filters are switched in/on on top of the ‘Acquire OFF' filters. While one would not expect any difference between the two compensation scheme, there is indeed a small, subtle difference.

A few comments with respect to where to find things: 
As I mentioned above, the data I used is found under the parent svn directory: https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Common/Electronics/H1/Results/SUSElectronics/

From there you can navigate to the data for the individual TMs by further navigating to the these subfolders from the parent directory:    

ETMX/PUM/2022-01-14/
ETMY/PUM/2022-01-17/
 ITMX/PUM/2022-01-10/
 ITMY/PUM/2022-01-11/


One last comment, I pointed to the wrong location for the script and supporting files, they are *actually* found in the git repository HERE. (I'm sure this time)

The script I am referring to/used to produce the results above is named: model_TM_PUM_driver_systematicerror.py

Again, to reiterate, the config.ini file must follow the formatting conventions detailed above. As for the script itself, the only thing you need to change/specify is the location of where the .ini file resides, its the first line right after the FILE READ IN section header. (specifically the line reads, configFILE = 'ITMX_PUM_config.ini')  

Displaying report 1-1 of 1.