Since LLO went out of lock, Sheila asked if she could complete some measurements that she didn't finish during maintenance. I gave her the OK and went to commissioning mode since we aren't losing any coincident data time.
I updated the GDS calibration correction filters today to reflect the bug fixes to the actuation and sensing time delays (see aLOG #22056). Attached are plots of the residual and control correction filters, which include the updated time delays. I have also attached plots that compare the h(t) spectra from the CALCS and GDS calibration pipelines and the spectrum residuals. There is now a larger discrepency between CALCS and GDS because the time delays that were added to CALCS to bring the two closer together are now no longer as accurate. Updates to the delays in CALCS may be coming as the differences are investigated more.
The new GDS calibration correction filters were generating using
create_partial_td_filters_O1.m
which is checked into the calibraiton SVN (r1560) under
aligocalibration/trunk/Runs/O1/Common/MatlabTools.
aligocalibration/trunk/Runs/O1/GDSFilters
The filters file is called H1GDS_1127593528.npz.
Back to Observing @ 23:50 UTC.
Lockloss @ 23:25 UTC. ITMy saturation.
Laura, Jordan
People have been decreasing the RF45 modulation index as a fix for extreme glitchiness associated with RF45 AM noise (described here among other places). I did a quick check to see if this has any noticeable effect on the rate of background triggers. I made plots of omicron glitchgrams and trigger rates for times where the modulation index was decreased and for nearby times with modulation index at its nominal level and no other obvious issues (many plots ). Attached are rate plots from some recent times.
For reference, the nominal plot is from lock # 31 and the decreased plot is from # 39 according to https://ldas-jobs.ligo.caltech.edu/~detchar/summary/O1
Activity Log: All Times in UTC (PT) 15:00 (08:00) Take over from TJ 15:00 (08:00) Start of maintenance window 15:00 (08:00) Christina & Karen – Cleaning at End-Y 15:00 (08:00) Richard – Going into CER to work on 45Mhz driver 15:10 (08:10) Sprague – On site *Joe D. to escort through LVEA, Mid and End Stations 15:18 (08:18) Peter – Going into LVEA to work with Richard on 45Mhz driver 15:22 (08:22) Ken – Working on the solar power on X-Arm 15:22 (08:22) Leslie – Going to End-X and End-Y for cleaning work 15:24 (08:24) Lockloss – Maintenance 15:25 (08:25) Hugh – Taking down HAM5 ISI for Rouge excitation fix 15:26 (08:26) Keita – Going into PLS to swap 45Mhz driver 15:28 (08:28) Filiberto & Manny – Taking photos of electronics racks at Mid-X 15:42 (08:42) Bubba – Going to End-Y chiller yard to replace vibration dampers on compressor 15:48 (08:48) Filiberto & Manny – Taking photos of electronics racks at Mid-Y 15:50 (08:50) Jim B. – Working on hardware injection computer 15:54 (08:54) Hugh – Going to both end stations to check HEPI fluid levels 15:55 (08:55) Betsy – Running charge measurements at both end stations 16:00 (09:00) Christina & Karen – Cleaning at End-X and End-Y NOTE: A lot of moths at End-Y 16:00 (09:00) Robert & Vinnie – at End-Y glitch hunting 16:05 (09:05) Filiberto & Manny – Taking photos of electronics racks at End-Y 16:07 (09:07) Mitch – In LVEA to place signage – will open receiving roll-up door 16:09 (09:09) Betsy – In LVEA to help Mitch and hunt for parts 16:09 (09:09) Jodi – In LVEA to check 3IFO stuff 16:10 (09:10) Jason & Peter – Moving PSL equipment from OSB to LSB 16:10 (09:10) Filiberto & Manny – Finished at End-Y – heading for the LVEA 16:13 (09:13) Keita – Out of the PSL 16:30 (09:30) Hugh – Shutdown dust monitor at both end stations 16:30 (09:30) Mitch – Finished in the LVEA 16:30 (09:30) Filiberto & Manny – In LVEA by HAM3 taking photos of electronics racks 16:32 (09:32) Hugh – Checking CS HEPI fluid levels 16:33 (09:33) Jodi – Out of the LVEA 16:35 (09:35) Betsy – Out of the LVEA 16:37 (09:37) Filiberto & Manny – Out of the LVEA 16:45 (09:45) Hugh – Delivering 3IFO parts to storage in the LVEA 16:50 (09:50) Jodi – Taking tour through LVEA 16:55 (09:55) Jason & Peter – Finished moving PSL parts 17:00 (10:00) Mitch – Moving (forklift) load from LSB to VPW 17:10 (10:10) Add 175ml water to PSL crystal chiller 17:12 (10:12) Kyle & Joe – Taking 1-Ton and trailer to near End-X to recover leak detector 17:18 (10:18) Christina & Karen – Cleaning in the LVEA 17:30 (10:30) Bubba & John - Going to End-X chiller yard to replace vibration dampers on compressor 17:31 (10:31) Beverage service on site to check the vending machines 17:35 (10:35) Corey & Patrick – Going to sweep End-Y 17:39 (10:39) Gerardo – Delivering batteries to near both end stations 17:46 (10:46) Vinnie & Jordan – Going to both end stations to install PEM equipment 17:47 (10:47) Paradise Water on site 17:47 (10:47) PraxAir truck leaving site (was at Mid-X) 17:52 (10:52) Ken – Going to work on solar panels on Y-Arm 18:05 (11:05) Sudarshan – Taking TFs at End-X 18:12 (11:12) Karen & Christina – Out of the LVEA 18:15 (11:15) Corey & Patrick – Going to sweep End-X 18:34 (11:34) Betsy & Cheryl – Sweeping the LVEA 18:45 (11:45) Gerardo – Going to End-X to check annulus gages 18:45 (11:45) John & Bubba – Finished with chiller work – Checking gauges in End-X 18:48 (11:48) Richard – In LVEA to shut off wireless APs 20:06 (13:06) IFO Locked at NOMINAL_LOW_NOISE 22.5W, 62Mpc 20:32 (13:32) Lockloss – See aLOG 22073 20:41 (13:41) Kyle & Joe – Out to X2A and Mid-X 20:42 (13:42) Daniel – Going into CER 20:47 (13:42) Carpet Contractor on site to meet with Bubba 20:47 (13:47) Daniel – Out of CER 22:11 (15:11) IFO locked at NOMINAL_LOW_NOISE, 22.5W, 75Mpc 22:18 (15:18) Set Intent Bit to Observing 23:00 (16:00) Turn over to Travis Shift Summary: Title: 09/29/2015, Day Shift 16:00 – 23:00 (08:00 – 16:00) All times in UTC (PT) Support: Sheila, Hugh, Betsy Incoming Operator: Travis Shift Summary: - 15:00 IFO locked. Observing Mode set to Maintenance. - 15:24 Lockloss – Maintenance - 16:30 Turnoff dust monitors at both end stations - 17:05 Reset HAM5 L4C Saturation WD -19:00 Corey & Patrick – Sweep of end stations -19:00 Cheryl & Betsy – Sweep of LVEA
The vibration isolation pads on the end station instrument air compressors had deteriorated to the point that the metal portion of the foot of the compressor was in contact with the concrete equipment pad. John and I replaced the old pads on both compressors this morning.
Proposed & Ongoing Maintenance Day Activities
Y--Approved N--Not approved for this week D--Approved but Delayed
D--Test SDF for Beckoff--JHanks--Delayed to 10-6
Y--Move PMC, LASER & Eq from OSB OL to LSB OL--PKing & JOberling--Completed
Y--Replace Vibration Isolators on End Instrument Air Compressors--BGately--Completed
Y--Restart SATAboy--CPerez--Completed
N--Add Botches to HL & HSTS ASC for Bounce/Roll--SDwyer
Y--ETM ChargeMeasurements--BWeaver--Completed
Y--"Fix" HAM5 Rogue Excitation Error--HRadkins--Completed
Y--Swap RF45 Controller--KKawabe--Completed
Y--Add low f Boost (ASC)----Completed
Y--Update GDS Pipeline for 15 usec delay fix--JKissel--Completed
Y--PRAXAIR Deliveries 1 Monday & 2 Tuesday--CP3(MidY)[Monday], CP6(MidX), CP1(CS)--Completed
Y--Shutdown Dust Monitors at End Stations--JBartlett--Completed
Y--PCAL as a Hardware Injector Proof-of-Principle--SKarki--Completed
Y--Forklift DCS Shipment from LSB to VPW--CCarrisco--Completed
Y--Restart NDS 0 & 1--JBatch--Completed
Y--Test Hardware Injection under MONIT--JBatch--Completed
Y--Update Code on DMT for latest Calibration--JZweizig--Completed
Y--Finalize Rack Photo Assay--FClara--Completed
Y--TMSX Raster For Clipping--SDwyer--Waiting on IFO
The inverse actuation filter described in alog 21944 has been installed on F1 and F2 of H1:CAL-PCALX_SWEPT_SINE filter bank.
I installed the inverse actuation filter on Pcal X-end for testing purpose. The filters are installed on F1 and F2 of H1:CAL-PCALX_SWEPT_SINE filter bank. F2 contains a gain factor of average arm-length to convert strain to metres and F1 contains the transfer function that converts metres to counts of excitation at Pcal. The transfer function of the filter that is installed in foton is shown in attachment 1. These filters will remain off during normal IFO configuration and are monitored in the SDF. I took some transfer function measurement between Excitation and TxPD, RxPD and OFSPD. The measurement files are committed to the SVN and can be found at:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/INVACT_PCAL/
To follow: Analysis of the above measurement and a waveform injection at the next opportunity as a test.
Vinny, Jordan
We put power supplies back in place that were removed here. The EY magnetometer in the SEI rack was disconnected now has an old style power supply and seems to be working ok. The EX magnetometer in the SUS rack was disconnected and is now connected with a new style power supply which has 1hz charging glitches.
Add 175ml water to PSL crystal chiller.
ShivarajK, JeffreyK, DarkhanT,
Overview
To reduce phase systematics in the DARM OLGTF model we've adjusted time delays/advances in the actuation and the sensing functions of the DARM loop Matlab model.
With the included 15 us of time-advance into the actuation function, the phase residuals of each of the actuation stage TFs up to 100 Hz measured on Aug. 26 - 29 are under 2 deg at high frequencies (except for L1 stage which is about 5 deg, which is ok because at high frequencies we rely mostly on L3 stage actuation), and the overall actuation function rediduals at high frequencies to mostly under 3 deg (Fig. 1).
To reduce sensing function phase residuals we have added 14 us of time-advance, which is similar to the correction introduced into LLO DARM model for O1 (see LLO alog 20894); with this additional time-advance the sensing function phase residual is mostly under 2 deg (Fig. 2).
DARM OLGTF model for O1 with included actuation and sensing function time delay/advance corrections have phase redisuals that are mostly under 2 deg (Fig. 4).
For GDS pipeline corrections: time delays in the updated H1 DARM model for O1 are:
Details
In the DARMOLGTF model for O1 we had systematic phase residuals, which we planned to account for by adding time delay/advances into the actuation and the sensing functions (see LHO alog 21827). In the H1DARM model for O1 we implemented the time delay/advance correction capability via par.t.unknown_actuation and par.t.unknown_sensing parameters. After that we revisited actuation function stages' redisuals by looking at the plots produced using cmpActCoeffs_viaPcal_O1.m and analyze_pcal_20150928.m (this is a modified version of a script used at LLO, analyze_pcal_20150903.m, see LLO alog 20894), and confirmed that actuation stages with the included 15 us time advance correction show <2 deg residuals (under 5 deg for L1), Fig. 5, 6, 7; we still have ~ 2 % systematic residual in actuation magnitudes that we are leaving unchanged in the Matlab DARM model and the CAL-CS front-end filter modules (Fig. 8, 9, 10).
We modified "H1DARMparams_1125963332.m", "H1DARMparams_1127083151.m" and their kappa corrected versions and re-run CompareDARMOLGTFs_01.m.1 Comparison plots show that:
1we used kappa values at the measurement times from previous calculations (see LHO alog 21827); for the ~30 Hz lines these values shouldn't be too much different from the ones calculated using EP1-9 from the updated O1 model.
H1 DARM model for O1 and comparison script were committed to calibration SVN (r1550)
CalSVN/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMOLGTFmodel_O1.m
CalSVN/Runs/O1/H1/Scripts/DARMOLGTFs/CompareDARMOLGTFs_O1.m
All of the parameter files in the same directory were modified to include time advances noted in this report.
Actuation function analysis scripts were committed to (r1550) (PCAL parameter files, that were copied from ER8 directory have been also committed into the same directory):
CalSVN/Runs/O1/H1/Scripts/PCAL/analyze_pcal_20150928.m
CalSVN/Runs/O1/H1/Scripts/PCAL/cmpActCoeffs_viaPcal_O1.m
Actuation function analysis plots were committed to (r1551)
CalSVN/Runs/O1/H1/Results/PCAL/2015-09-28_cmpActCoeffs_PCAL_*.pdf
Model comparison plots were committed to
CalSVN/Runs/O1/H1/Results/DARMOLGTFs/2015-09-28_H1DARM_ER8O1_cmp_*.pdf
We've updated Epics values for the DARM time dependent parameter estimations with the values from the H1 DARM OLG TF model using H1DARMparams_1125963332.m (r1550) parameter file (WP 5510, was filed on Sep 21). This values can be used for recalibration of the GDS_CALIB_STRAIN between Sep 10 and now.
New EP1-9 values are listed in D20150929_H1_CAL_EPICS_VALUES.m and in a more verbose form in 20150929_H1_CAL_EPICS_verbose.txt (old values are also listed at the end of the verbose output).
We've committed the logs for calculating EP1-9 into calibration SVN (r1553)
CalSVN/Runs/O1/H1/Scripts/CAL_EPICS/20150929_H1_CAL_EPICS_VALUES.txt
CalSVN/Runs/O1/H1/Scripts/CAL_EPICS/20150929_H1_CAL_EPICS_verbose.log
CalSVN/Runs/O1/H1/Scripts/CAL_EPICS/D20150929_H1_CAL_EPICS_VALUES.m
New Epics values were accepted in SDF_OVERVIEW, however some of the values still show difference (values with magnitudes less than 10-17).
Sudarshan, Darkhan,
We've re-generated DARM loop model comparison plots with the kappas calculated using most recent EP# values.
"kappas" for this analysis were calculated from the calibration lines within 2 hours from each of the DARM OLGTF measurements.
For Sep 10 (O1 model) measurement the mean kappas from 30 min time interval starting at GPS 1125970532:
κtst = 1.036441
κpu = 1.025962
κA = 1.029902
κC = 1.005923
fc = 339.272371 [Hz]
for Sep 23 measurement the mean kappas from 30 min time interval starting at GPS 1127081351:
κtst = 1.045246
κpu = 1.022774
κA = 1.031924
κC = 1.007507
fc = 332.429690 [Hz]
I hand edited the h1calcs_OBSERVE.snap to make these diffs go away. OBSERVE.snap copied to h1calcs_safe.snap.
The trend of the time-varying calibration parameters is attached below. These are the values obtained after using the latest epics valuesmentioned in the alog above.
Since LLO had already gone down (we think for maintence) TJ let me start some maintence work that needs the full IFO locked. at about 14:32 UTC Sept 29th we went to commisioning to start running the A2L script as described in WP # 5517.
The script finished right before an EQ knocked us out of lock. Attached are results, we can decide if we are keeping these decouplings durring the maintence window.
The three changes made by the script which I would like to keep are ETMX pit, ETMY yaw, and ITMY pit. These three gains are accepted in SDF. Since we aren't going to do the other work described in the WP, this is now finished.
All the results from the script are:
ETMX pit changed from 1.263 to 1.069 (1st attachment, keep)
ETMX yaw reverted (script changed it from 0.749 to 1.1723 based on the fit shown in the second attachment)
ETMY pit reverted (script changed it from 0.26 to 0.14 based on the 3rd attachement)
ETMY yaw changed from -0.42 to -0.509, based on fit shown in 4th attachment
ITMX no changes were made by the script, 5th +6th attchments
ITMY pit (from 1.37 to 1.13 based on 7th attachment, keep)
ITMY yaw reverted (changed from -2.174 to -1.7, based on the 8th attachment which does not seem like a good fit)
By the way, the script that I ran to find the decoupling gains is in userapps/isc/common/decoup/run_a2l_vII.sh Perhaps next time we use this we should try a higher drive amplitude, to try to get better fits.
I ran Hang's script that uses the A2L gains to determine a spot position (alog 19904), here are the values after running the script today.
vertical (mm) | horizontal(mm) | |
ITMX | -9 | 4.7 |
ITMY | -5.1 | -7.7 |
ETMX | -4.9 | 5.3 |
ETMY | -1.2 | -2.3 |
I also re-ran this script for the old gains,
vertical(mm) |
horizontal (mm) | |
ITMX | -9 | 4.7 |
ITMY | -6.2 | -7.7 |
ETMX | -5.8 | 5.3 |
ETMY | -1.2 | -1.9 |
So the changes amount to +0.4 mm in the horizontal direction on ETMY, -0.9 mm in the vertical direction on ETMX, and -1.1mm in the vertical direction on ITMY.
Please be aware that in my code estimating beam's position, I neglected the L2 angle -> L3 length coupling, which would induce
an error of l_ex / theta_L3,
where l_ex is the length induced by L2a->L3l coupling when we dither L2, and theta_L3 is the angle L3 tilts through L2a->L3a.
Sorry about that...
Parameters for report:
GPS Start Time = 1127423695 # Beginning of time span, in GPS seconds, to search for injections
GPS End Time = 1127510095 # Ending of time span, in GPS seconds, to search for injections
Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
IFO Coinc Time = 0.01 # Time window, in seconds, for coincidence between IFO injection events.
Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
Report Normal = True # Include normal (IFO-coincident, consistent, and scheduled for network injections and consistent and scheduled for IFO injections) injections in report
Report Anomalous = True # Include anomalous (non-IFO-coincident, inconsistent, or unscheduled) injections in report
----
No scheduled injections or non-occurring injections were found.
There was a CAL_INJ reset that occurred only in H1, CALRESET 1127480460.000 (H1). However, it has the anomaly that it appears in ODC HOFT and GDS HOFT frames but not in ODC RAW or ODC RDS frames. This same anomaly was observed with several CBC injections in L1 during the daily period 1127163296 - 1127249696.
The anomalies reported here are likely due to the same bug that caused the anomalies as reported in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=21971.
Now that the multi-processing version of HWInjReport is operational and returning results (multi-processing code is an absolute bear!), this is the first of daily reports of analysis of output from HWInjReport. Currently, HWInjReport still has to be run manually and requires one to checkout the current schedule file from the SVN (currently at https://svn.ligo.caltech.edu/svn/dac/hwinj/Details/tinj/schedule; if this has changed, please let me know so I can modify the run script appropriately). Automatic execution of HWInjReport is soon to come. I've attached copies of the output report file and the schedule file used. NOTE: the report file is very wide due to the number and size of the columns in the network injections tables of the report. To examine the report, you will need to either zoom out or change the font size in your browser/text editor to 10pt or less (I'm looking into compressing the columns in the network injections tables in future updates).
The daily run performed with the following parameters:
GPS Start Time = 1127163296 # Beginning of time span, in GPS seconds, to search for injections
GPS End Time = 1127249696 # Ending of time span, in GPS seconds, to search for injections
Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
IFO Coinc Time = 0.01 # Time window, in seconds, for coincidence between IFO injection events.
Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
Report Normal = True # Include normal (coherent, consistent, and scheduled) injections in report
Report Anomalous = True # Include anomalous (incoherent, inconsistent, or unscheduled) injections in report
NOTE: coherent -> coincident. Missed changing that in the code where it outputs the report.
The schedule file only has injections spanning 1125280499 - 1126450499. This is outside the range of times checked by HWInjReport, so there are no occurring or non-occurring scheduled injections reported.
No normal injections, as defined above for HWInjReport, were reported for the network injections. All injections found were reported as UNSCHEDULED, and all injections occurring were reported as CBC injections.
Two H1-L1 coincident injections were found: CBC 1127175853.757(H1), 1127175853.764(L1) and CBC 1127179822.757(H1), 1127179822.764(L1). Both injections were reported as UNSCHEDULED but, otherwise, had no other reported anomalies.
H1 had only 1 single-IFO injection, CBC 1127173426.757 (the report file shows 3, but only 1 is actually an H1-only injection. There is apparently a bug due to the multi-processing code that is not propagating the association of the other 2 injections with their corresponding L1 injections. It's basically a problem of how memory works for a multi-processing environment.)
L1 had 5 single-IFO injections:
The first three injections have the anomaly that they occur in the ODC hoft and GDS hoft frames but not in the ODC raw or ODC rds frames. The remaining 2, other than being UNSCHEDULED, had no other anomalies reported.
ADDENDUM: I was able to successfully fix the data propagation bug. I've attached a copy of the resulting "fixed" report that correctly shows the single-IFO injections for H1 and L1.
Peter Shawhan and I examined the anomalies more closely and found they are not anomalies. The missing injections in RAW and RDS for L1 do actually occur, but HWInjReport missed them. My current working hypothesis is that the code missed these injections because of how it has to separate the list of files to pass to FrBitmaskTransitions into chunks of no more that 4090 files. This is to prevent the number of arguments passed to FrBitmaskTransitions, one for each file, from exceeding the number of arguments supported by the OS (I actually ran into this issue at one point with the RAW frame files). HWInjReport merges the output from the chunks into a single continguous internal list, however, it currently is not accounting for the occurrence doubled transitions (two "off" or "on" transitions consecutively placed) during the process of merging the transitions internally. This may cause the code to become misaligned when finding the injections, based on the bit transitions, and so it completely misses it.
I am reasonably convinced this is the case because when I performed a run on a time-span around the anomalies, 1127162120 - 1127162970, the anomalies do not occur. But, this is because the list of files is much smaller and only needs one chunk, instead of several, to be passed to FrBitmaskTransitions.
This also brings another point which is that I need to include all the output files, the report generated, the schedule used, and the log file when I upload files with my alog summaries of HWInjReport, because the log file has a lot of information regarding the internal activity to HWInjReport. I built it that way because the code has some unexpectedly complex logic in places, which has made debugging a total bear, and it only got worse with the transition to multi-processing.
I just realized there is another bug in HWInjReport, though this one is somewhat benign. While HWInjReport is specified to cover only a certain time-span, it actually ends up covering a larger time-span due to the fact that FrBitmaskTransitions processes entire frame files and HWInjReport is processing the resultant transitions into injection events. This means that HWInjReport can receive from FrBitmaskTransitions a set of transitions that lie well outside the specified time-span and, consequently, generate injection events that lie outside the time-span. It does not have this issue with the scheduled injections, because it trims those to the specified time-span before doing any further processing. The fix, fortunately, is simple: just trim the transitions from FrBitmaskTransitions to within the specified time-span. However, the bug does have the effect of potentially creating injections just outside the beginning or ending of the specified time-span that are flagged as UNSCHEDULED, because the scheduled injections to which they may correspond were trimmed.
In an effort to create a inverse actuation filter for Hardware injection through Pcal infrastructure, we use the transfer function between RxPD and excitation of which RxPD is calibrated in terms of metres of displacement. . Using this RxPD calibration and the measured transfer fumction we calibrate the excitation [cts] in terms of metres and use it to create the inverse actuation filter. This will be installed in one of the excitation channel, possibly swept sine channel, for testing purpose.
In the above plot, the two left plots are the actual magnitude and phase of the measurement and different fits. The red plot is the inverse of measured transfer function between calibrated RxPD and pcal excitation. In short, it is cts of excitation to metres of test mass displacement. The rest of the plots are fit to that measured TF. In this case, the residual plots on the right side are more informative. The blue plot is the residual between measured TF and the fit that includes two zeros. The residual looks pretty good for this case but we do not have the luxury of only using two zeros. We need equal or greater number of poles to roll off the signal at higher frequency. For this we use a complex pole pair at 7 Khz and an additional real pole at same frequency. This creates some magnitude and significant phase distortion at higher frequencies as seen in the green residual plot but this is a systematic and we can account for this in our analysis later.
The magenta plot is the foton implementation of our two zeros and three pole fit plotted in green. There is a difference between the actual matlab generated filter and the foton version of it at frequencies above KHz. This is a known effect and is described in detail in G1501013.
I have written a litlle more detail technical note and can be found at T1500496.
The script used to generate the plots above is committed to the SVN:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Scripts/INVACT_PCAL/
The measuremnt files are in the following location
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurement/INVACT_PCAL/
I caused a lockloss by moving TMSX too quickly while doing this test.
I also spent some time earlier in the day (durring maintence recovery) to do some excitations on TMS and the End station ISIs to investigate the noise that seems to come from TMSX. An alog with results will be coming soon.