I worked a bit more on the analysis codes that Jeff has written (alog 21015 and alog 21049). I was not able to finish deriving the suspension scale factors. Tomorrow, Jeff and Darkhan will pick up them at the point where I left and will continue working on it.

Major updates:

• DARMOLGTFmodel now incorporates not only each ESD driver circuit measurement but also each PUM coil driver measurement.
  • Darkhan is going to alog some detail of the PUM driver measurement and fitting.
• The ALS Diff measurements are now analyzed using the latest DARMOLGTF model.
• Also, the Pcal measurements are now analyzed using the latest DARMOLGTF model.
  • By eyeballing the resultant plots, I see that the inclusion of the ESD driver and PUM coil driver circuits made the model more accurate. This is encouraging.

Next steps:

• We need to include the latest DARMOLGTF model in the free-swinging Michelson analysis.
• UIM driver circuit needs to be updated. DARMOLGTF still assumes a perfect cancelation between the digital and analog filters.

Some notes:

In the course of the code update, I changed the file organization structure of the ALS diff and Pcal scripts so that they have only one analysis code which can be invoked by specifying a set of data parameters. This organization approach is the same as those for the DARM open loop analysis.

As for ALS diff, the core analysis code is

aligocalibration/trunk/Runs/ER8/H1/Scripts/ALSDiff/Matlab/analyze_alsdiff.m

and the parameter files are in the same directory and named as

H1ALSDIFFparams_20150826.m

H1ALSDIFFparams_20150828.m

H1ALSDIFFparams_20150829.m

As for Pcal, the core analysis code is

aligocalibration/trunk/Runs/ER8/H1/Scripts/PCAL/analyze_pcal.m

and the parameter files are in the same directory and named as

H1PCALparams_20150826.m

H1PCALparams_20150828.m

H1PCALparams_20150829.m

Each parameter file loads H1DARMOLGTFmodel_ER8 with the latest electronics information and subsequently returns the parameter structure, or the familiar variable "par". As usual the parameter structure can be then fed to the analysis code (e.g. analyze_alsdiff.m or analyze_pcal.m) as an input argument. I have not carefully thought about the final return variables from the core analysis codes, but in principle we can write them such that they return the calibrated suspension transfer functions in meters/counts together with some error bars and also perhaps some statistical values. In this way, the final step of performing apple-to-apple comparison between various measurements from various dates can be less painful.

I tried propagating the same file organization structure to the free-swinging Michelson codes, but apparently I am running out my energy for the night and did not finish it yet.