6.2mag quake off the Canadian coast had everything tripped and down
07:00 Cris and Karen into the LVEA
08:05 Hugh out to LVEA to fool with FF seismometer
08:25 Hugh out of LVEA
08:37 Buba to EY to check instrument air pressure transducer.
09:00 Fil to EY to assess AA/AI swap job
09:12 Bubba laeving EY. Inst Air alarm reset
11:28 Travis heading into LVEA to look for parts
11:32 Kiwamu out to help Ellie adjust cameras
11:40 Travis out of the LVEA
~12:00 Patrick restarted Beckhoff Ethercat; Rotation stages/PSL Env. etc
Scott L. Ed P. Chris S. Yesterday the crew cleaned 82 meters ending 12 meters north of HNW-4-012. Today the crew cleaned 61 meters ending 13.7 meters north of HNW-4-015. The crew also serviced the generator today.
As a part of the camera alignment study (alog 18033), I noticed that the ASC loops for green X reacted so slow that it took about several minutes to converge. See the attached screenshot. This is a time series when I turned on the ALS X green ASC loops. I was watching the ALS COMM beatnote strength at the same time as a position-sensitive sensor. I suspected that the camera loop (DOF3) is the one which is so slow, but increasing the gain of this loop told me that the UGF is already close to the 0.5 Hz mechanical resonance (10-sih dB away from instability in gain). Perhaps some kind of cross coupling between the loops exist and may be slowing them down. I am not sure how critical this is in terms of the recycling gain, but if one does not wait for these loops to settle, certainly the alignment will not be repeatable.
Just to be sure:
After the study, I restored the settings (e.g. analog gains, aperture masking and etc) of the ITMX and ITMY green cameras back to what they were yesterday. Also I restored the ALS ASC settings back to what they have been. Theoretically there is no change in the digital cameras and their associated ASC loops.
I've been trying for a while to get feedforward running on HAM's 4&5, but not having much luck. Originally, I just tried copying the filter we are using on the BSC's, only because it was there, and the test was quick and easy. And not the right answer, as (kind of) expected. In order to design a proper filter, I've taken measurements as outlined in Brian Lantz's SEI log 682. Two measurments are needed, 1. a driven tf from the FF path to the ISI GS-13's and 2. a passive tf between the St0 (or HEPI) L4C's and the St1 GS-13's. First attachment is the driven tf for Y on HAM4, second picture is of 2 passive tf's between the ISI GS-13s and St0 L4C's (in blue) and between the ISI GS-13s and the HPI L4C's (in red). The filter should be a fit of the ratio between the passive tf and the driven tf (so green / blue (OR red), depending on the path you choose). Third attachment is plot of these ratios, blue is St0 FF, red is for HPI FF. I've tried a number of filters and so far the best I've gotten is a small improvement between 20 and 25 hz, and at best, no worse any where else. Fourth attachments is of my fits to the St0 feedforward. I've tried closer fits and they didn't work either.
Just to make sure I wasn't totally missing something I tried doing the same for the BSC's and was at least able to get something that worked (fifth plot is the performance, last plot is the design). A work in progress.
There was an error on the phase part of the last plot, I grabbed the wrong data. That's fixed now.
It came up in the seismic call that there may be a sign error in either HEPI or the St0 L4C's. I think that's probably the case. I looked at the transfer function between HEPI and HAM4's St0 L4C's to the HAM5 STS. HAM4's St0 L4C's are 180 degrees out of phase from HEPI's. I checked T1000388, our design document, and it looks like our installed cartesian matrices are "right", but according to my measurements, they ain't right. This probably doesn't explain my difficulties with feedforward(maybe?), but it came up. First 2 images are are the Y direction tf from the HAM4 sensors (HEPI (red) and ISI(blue)) to the STS. X and Z were the same. I will need to repeat this sometime when I can put the ISI into a damped state so I can get the ISI's GS-13's for comparison.
The next 2 images are of the passive measurement from the previous post, but a longer, finer measurement with the phase this time. Same color scheme, red is the GS13/HEPI measurment, blue is GS13/St0 measurement.
I realigned the beam into the ISS array. The QPD signals are close to zero.
For reference, here are the DC values read by the slow signals for 3.3W input power:
| PD1 | IOP-PSL0_MADC1_EPICS_CH24 | 1247 |
| PD2 | IOP-PSL0_MADC1_EPICS_CH25 | 1370 |
| PD3 | IOP-PSL0_MADC1_EPICS_CH26 | 1346 |
| PD4 | IOP-PSL0_MADC1_EPICS_CH27 | 1487 |
| PD5 | IOP-PSL0_MADC1_EPICS_CH28 | 1506 |
| PD6 | IOP-PSL0_MADC1_EPICS_CH29 | 1400 |
| PD7 | IOP-PSL0_MADC1_EPICS_CH30 | 1625 |
| PD8 | IOP-PSL0_MADC1_EPICS_CH31 | 1504 |
I didn't check the jitter to RIN coupling as we did in the past, so the alignment might not be the optimal one yet.
In addition, it seems that PD8 has some problems, since the spectrum is clearly noisier.
J. Kissel The CAL-CS front-end model is where the infrastructure for the calibration (i.e. inverting the DARM actuation function such that a waveform calibrated into strain can be injected into the DARM loop in the correct DARM [ct] units), so I'm looking at what I need in order to fill the one filter bank that we'll use for this inversion. I've used the DARM open loop gain TF model (described in LHO aLOG 17951) to demonstrate (a) what the actuation function model looks like and (b) how simple it *could* be to invert it. In summary, we can get a ~5%, 3 [deg] frequency-dependent fidelity of the full model between 10 - 2000 [Hz] if we simply use a 1.03e-13 [m/ct] * (1 [Hz] / freq)^2 model for the magnitude, and a -1 * 176 [us] delay model for the phase. Huh! Recall that 1.03e-13 [m/ct] has a +/- 26% uncertainty because we're as of yet unable to discern the difference between optical gain fluctuations and ESD strength changes from fluctuations in charge (again, see LHO aLOG 17951 for discussion). I'll discuss with the LLO injection team to see what they'd implemented for ER6, where they've rolled off the *inverse* of this filter, and discuss the path forward, so we can get something installed by the mini-run.
Done around 12:14 to see if it might help resolve rotation stage issues.
Mike, Jeff, Jim, Dave:
Jim has built the h1hwinj1 server. This is a Scientific Linux 6.5 rack-mounted machine in the MSR with software installed as requested by the hardware injection group. Eric Thrane, Ed Daw, Peter Shawhan, Michael Landry and Jeff Kissel are commissioning this machine between now and the 5/1,2 mini run.
Attached are ASD comparing the Old (troublesome) STS2-B and the newly repaired STS2 temporarily in place in the beer garden. The current traces are from ~0130pdt--looks like a quiet time based on the PEM traces.
When I compare these to the plots (calibrations in meters) in 18007 from Wednesday AM, I observe the following:
Strong coherences are moving to lower frequencies in all DOFs.
Unity transfer function for X DOF too is moving down in frequency. The Y & Z TFs look pretty similar.
Maybe this means these signals are getting more stable. However, the Z signal of the Old & New STS2-B still don't look like the A & C units, is this an indication of the vinyl difference?
I have created a new CDS Overview MEDM screen customized more for CDS sysadmin rather than OPS. It is very similar to the CDS overview with the following differences:
The purpose of the screen is that any non-green indicator shows a possible problem which can be resolved by software means (unlike overflows which require system level intervention). The screen is called H1CDS_ENG_STATE_WORD_CUSTOM.adl and is accessible from the CDS block of the SITEMAP (ENG OVERVIEW selection).
Jim, Jeff, Dave
The h1omc model GDS_TP screen was showing a "Modified file" warning for H1OMC.txt filter module file. I checked and found the chans/H1OMC.txt and chans/filter_archive/h1omc/H1OMC_1113901380.txt files are in fact identical. Since the modification time of H1OMC.txt and the time of load were within the same minute, we think perhaps the Load Coefficient button was pressed too quickly after the file change and the front end computer suffered NFS cache lag. To clear up any confusion, Jeff has reloaded the filter file on h1omc.
Want to make sure we are comparing peppers to peppers as we assess the quality of the repaired PEM STS2 and attemp to understand the problems of the original STS2. I also moved it to the exact spot where the oriinal was located. If things still look so-so by Monday, our net step is to place the STS2 on the concrete. STS2-B has always been sitting on the floor vinyl wereas STS2s A & B are on the concrete.
Evan, Sheila
We have been able to lock the IFO at 10 Watts with a recycling gain of 37. We also think that we can probably improve our inital alingment scheme by adding a servo from POP A to PR3 durring the INput align step. We've closed loops around ITMX from the TRX QPDs, these were stable for almost an hour before we dropped the lock for other reasons, and helped keep the X arm build up stable as we increased the power.
Variation on Inital Alingment
At the beginning of the evening, our alignment resulted in a rather low recycling gain (15 or something) which resulted in difficulty locking. This was probably because the ITM camera references would have moved 18033. We have now gone through an initial alignment with some extra steps which brought us back to a decent recycling gain (35 before any manual adjustment or full lock ASC).
| PIT (urad) | Yaw | |
| PD1 | 169.2 | -311.4 |
| PD4 | 134.5 | -278.9 |
| mean | 151.85 | -295.15 |
This resulted in a recycling gain of about 35, so it seems like this was a sucsesful approach at least once. If there is time for some day time commissioning tomorrow, it would probably be helpful to add to the INPUT align state a loop which actuates on PR3 to center the beam on POP A. Commissioning the dither Align script for the BS to ETMY baffle PDs might also be helpful, but this is a lower priority because we aren't sure that step is necessary.
Since we have seen this week that many things (CARM offset reduction, violin and roll mode damping, and ASC error signals, possible radiation pressure instability on the ITMs) change when we go from a bad recycling gain to a good one, it seems like we will want to improve our initial alignment scheme enough to consistently bring us to a high enough recycling gain that we can use consistent settings for lock acquisition.
Avoiding oscillations durring power up
We ran into the oscillation in ITM pitch which we think is due to mis centering and radiation pressure on the ITMs several times tonight. It seems like we are more stable when the recycling gain is high, we have also slowed down the final CARM offset reduction and the power increase.
Closing ITM loops
We were able to close loops around ITMX from the QPD error signals we found last night. Here are settings:
DSOFT P (ITMX P) error signal 1.71 TRX A -1 TRX B FM offset 0.08, FM2,3,4 gain -700,000, top mass offloading on
DSOFT Y (ITMX Y) error signal 1.84 TRX A -1 TRX B FM offset -0.1, FM2,3,4,6 gain 600,000, top mass offloading on
both of these loops respond in a 2-3 seconds.
DARM OLG
Evan made a measurement of the DARM OLG, this was when we still on ETMX, DC readout with low frequency boost, and a recycling gain of 35. 11 Watts input power.
Now a large earthquake has tripped most of the seismic platforms.
While in full RF lock with a good recycling gain, turn off the green QPD servo and align the Y green beam to the arm manually (or using green WFS feeding back to PZT mirrors), then and set the QPD offsets.
Hopefully this will fix the ETMY green beam position, and makes Y arm initial alignment less convoluted.
The BS alignment slider values for PD1 and PD4 are switched in this entry. I redid the BS→EY baffle pointing today and found
| P (µrad) | Y (µrad) | |
| PD1 | 134.3 | −280.0 |
| PD4 | 169.5 | −314.0 |
| Mean | 151.9 | −297.0 |
Also, PD4 has a large dark offset (19.7 µW) compared to PD1 (−0.5 µW). The net power reported by PD4 with the PSL beam pointing onto it is 4.2 µW, and the for PD1 it is 5.2 µW. The settings for both are 0 dB gain, 0.5 A/W responsivity, and 20 kΩ transimpedance.
Evan, Sheila
We have been slowly stepping up the input power tonight, and we see the power drop when we request increased power. Here is an example, from 4-24-15 9:35 UTC. The top left panel shows the power which Evan requested, the bottom left panel shows the actual cmd position, which approriately goes in the same direction consistently when the requested power increases. The right two panels show the problem, that the readback of the actual rotation stage position goes in the wrong direction briefly when a new comand is sent. This is a real decrease in power, the lower right panel shows that the power monitor PD sees these power decreases.
If you zoom in, you can see many things.
1. At the very beginning of the rotation, the cmd position (left bottom) doesn't ramp for about 2 seconds, and suddenly it jumps up (red circle), which coincides with the reversing motion of the rotator. This behavior is repeated in every power step in Sheila's data.
(Updated after reading Daniel's comment: 2 sec delay might be a non-issue, but the jump seems to be an issue.)
2. At the end of the rotation, the cmd position looks good but the rotator jumps up, causing another power jump (blue circle). This also is repeated in every power step in Sheila's data.
3. There's one instance where the rotator reversed direction in the middle of ramping in Sheila's data (green circle).
4. There's one instance where the power increase was requested, nothing happened for 11 seconds, another power was requested, and the rotator started moving (second attachment).
(Updated after reading Daniel's comment: This might be a non-issue.)
After the power request one also needs to press the go button to get it started. So, I guess the 2s delay is just that. For the request without moving, are we sure the button was pressed?
I requested a small power step (from 2W to 2.1W) and immediately back to the original power, and the measured power dropped from 2.25W to 1.9W.
I repeated again, and the power went further down to 1.5W.
All in all, the calculated angle got back to the original number, of course, but the measured angle is down by about 0.4 degrees or so.
Daniel hit the "Go To Power" button without changing the power request, and the driver still did its thing and the power dropped.
After repeating the routine 4 times, the encoder value happened to get back to the number before Daniel started, but the power is still down from 1.5-ish to 1.1-ish W.
Andy, Duncan
When looking for times when the HWS camera was on or off, I found that the minute trends indicated that it was off on Apr 18 6:30 UTC for ~27 minutes. But the second trends indicate that it was turned off 20 minutes later than that (and back on at the same time). The raw data (sampled at 16 Hz) indicates that the camera was never turned off.
This was originally found using data over NDS2, but Duncan has confirmed by using lalframe to read the frames directly. I've attached a plot below. The channels are H1:TCS-ITM{X,Y}_HWS_DALSACAMERASWITCH.
I was able to successfully run it in the Caltech (CIT) cluster using a matlab code i.e., the raw, minute and second trends agree. The matlab code uses ligo_data_find. But if I run the same code at Hanford cluster it produces the results Andy and Duncan saw i.e., the trends disagree. So there seems to difference between the frames at these two locations for the trend ones. I have attached the matlab codes here with incase some one wants to test it.
This is because the trend data from the two CDS framewriters can disagree. This happens if a framewriter restarts during the period covered by the trend file, and the averages from each framewriter are computed using a different number of values. These differences only happens with the trend data. See below for the details.
Note that at LHO, LDAS is using the CDS fw1 framewriter as the primary source of the scratch trends (saved at LHO for the past month) and the CDS fw0 frameswriter as the primary source of the archive trends (copied to CIT and saved permenantly at LHO and CIT).
If a framewriter goes down, it will still write out the trend data based on what data it has since it restarted.
Thus you can get trend frames that contain data averages for only part of the time period covered by the file.
For the time given in this alog, the trend files under /archive (from framewriter-0) and /scratch (from
framewriter-1) differ is size:
$ ls -l /archive/frames/.../H-H1_M-1113372000-3600.gwf
-r--r--r-- 1 ldas ldas 322385896 Apr 18 00:27 /archive/frames/.../H-H1_M-1113372000-3600.gwf
$ ls -l /scratch/frames/.../H-H1_M-1113372000-3600.gwf
-r--r--r-- 1 ldas ldas 310156193 Apr 18 00:46 /scratch/frames/.../H-H1_M-1113372000-3600.gwf
Note that both files pass FrCheck (but have different checksum) and contain valid data according to framecpp_verify (e.g., run with the --verbose --data-valid options).
However, if I dump out the data for one of the channels in question, I get:
$ FrDump -i /archive/frames/.../H-H1_M-1113372000-3600.gwf -t H1:TCS-ITMX_HWS_DALSACAMERASWITCH.mean -d 5 | grep "0:"
0: 1 1 1 1 1
1 1 1 1 1
10: 1 1 1 1 1
1 1 1 1 1
20: 1 1 1 1 1
1 1 1 1 1
30: 1 1 1 1 1
1 1 1 1 1
40: 1 1 1 1 1
1 1 1 1 1
50: 1 1 1 1 1
1 1 1 1 1
$ FrDump -i /scratch/frames/.../H-H1_M-1113372000-3600.gwf -t H1:TCS-ITMX_HWS_DALSACAMERASWITCH.mean -d 5 | grep "0:"
0: 0 0 0 0 0
0 0 0 0 0
10: 0 0 0 0 0
0 0 0 0 0
20: 0 0 0 0 0
0 0 0 1 1
30: 1 1 1 1 1
1 1 1 1 1
40: 1 1 1 1 1
1 1 1 1 1
50: 1 1 1 1 1
1 1 1 1 1
These frames start at,
$ tconvert 1113372000 Apr 18 2015 05:59:44 UTC
and the 0's start about 28 minutes into the /scratch file (copied from framewriter-1), while the /archive version only contains 1's (copied from framewriter-0).
Thus, I predict framewriter-1 restarted at around Apr 18 2015 06:28:00 UTC. It seems that 0's get filled in for times before that.
If I check, H1:TCS-ITMX_HWS_DALSACAMERASWITCH.n, which gives the number of values used to get the averages, this is also 0 when then above numbers are 0, indicating the 0's came from times when framewriter-1 had no data.
Note that this behavior only occurs for second-trend and minute-trend data.
If data is missing in the raw or commissioning data, no file is written out. Thus, we never find a difference between the raw (H1_R) or commissioning (H1_C) frames between valid frames written by both framewriters. Note that the diffH1fb0vsfb1Frames process seen in the first row of green lights here,
http://ldas.ligo-wa.caltech.edu/ldas_outgoing/archiver/monitor/d2dMonitor.html
is continuously checking that the raw frames from the two framewriters is the same. (The same process runs at LLO too.)
If differences are found, it sends out an email alert.
I've never received an alert, expect when the RAID disk-arrays have either filled up (and 0 byte files were written by one framewriter) or
when the RAID disk-array hung in some way that caused corrupt files to be written. In both cases, the files on the problem array never pass FrCheck and are never copied into the LDAS system.
Thus, the above feature, is a feature of the second-trend and minute-frames only. To avoid this issue, code should check the .n channel to make sure the full number of samples were used to obtain the average. Otherwise, some of the trend data gets filled in with zeros.
Greg said:
Thus, I predict framewriter-1 restarted at around Apr 18 2015 06:28:00 UTC. It seems that 0's get filled in for times before that.
the restart log for 17th April says
2015_04_17 23:28 h1fw1
With local PDT time = UTC - 7, Greg gets a gold star.
There should also be a .n channel which tells you how many samples were included in the average.
J. Kissel, K, Izumi I had started the weekend hoping to improve the DARM calibration in the following ways: (1) Including the compensation for the analog and digital anti-aliasing (AA) and anti-imaging (AI) filters. (2) Decreasing the DARM coupled cavity pole by 25% to 290 [Hz]. (3) Establishing an uncertainty estimate of the optical gain (the DC scale factor component of the sensing function). (4) Reducing the delay time in the actuation from four 16 [kHz] clock cycles to one 16 [kHz] clock cycles. After study, and Sunday's improvement to the power recylcing gain, we've decided not to make *any changes to the calibration, yet. However, for the record, I put down what I've studied here, so we can begin to understand our uncertainty budget. %% Details ----------- (1) Including the compensation for the analog and digital anti-aliasing (AA) and anti-imaging (AI) filters LLO has pioneered a method to compensate for the high frequency effects of the analog and digital (or IOP) AA and AI filters, by including the *product* of all four filters in the actuation chain of the front-end CAL-CS model (see the last few pages of G1500221 and LLO aLOG 16421). Further, Joe has analyzed a collection of 281 real, analog AA/AI filters that were tested during CDS acceptance testing to refine the exact frequency response of these filters (see first attachment, aLIGO_AAAI_FilterResponse_T1500165.pdf). In summary, the 3rd order Butterworth's corner frequency is statistically significantly lower; measured to be 8.941 (+0.654 /-0.389 or +7%/-3%) [kHz] instead of the ~10 [kHz] Butterworth model that we have been using (which was inherited from a .mat file the 40m). Though this does not appreciably affect the magnitude error at high-frequency, it does as much as 3 [deg] of phase by 2 [kHz], which can throws off our estimate of the residual unknown time delay by 5 [us] when we try to account for it in our fitting of the open loop gain transfer function. However, after exploring what LLO has implemented, we've discovered a flaw in the implementation of this compensation. In going from the continuous zpk model of the filters to discrete, because we're trying to model these filters which have all of their response near, at, or above the Nyquist frequency, there is significant difference of modeled filter's response between the continuous and discrete models (see second attachment 2015-04-18_AAAI_FilterStudy.pdf). As such, we will *not* begin to compensate for the AA and AI filtering until we arrive at a better method for compensating these filters. (2) Decreasing the DARM coupled cavity pole by 25% to 290 [Hz]. Over the past few weeks, we've established the DARM coupled cavity pole is now at 290 [Hz] instead of the predicted L1 value of 389 [Hz] (see LHo aLOG 17863). We've added one more DARM open loop gain transfer function to the list we're now comparing after the HAM6 vent, Apr 13 2015 04:15:43 UTC % Post HAM6 Vent & UIM/TST Crossover; 10 [W] input power Apr 13 2015 06:49:40 UTC % No loop parameter changes, but input power 15 [W] Apr 15 2015 07:53:56 UTC % Input Power 15 [W] no change in control system from previous measurement with these three measurements, I made a statistical comparison of the model / measurement residual while using 290 [Hz] for the modeled coupled cavity pole frequency, and reducing the unknown time delay from 40 [us] to 30 [us] because I've used Joe's measured mean for the analog AA / AI in the model (see third attachment 2015-04-18_290HzCCP_H1DARMOLGTF.pdf ). As one can see on the 3rd and 4th page, assuming each of the residuals frequency points is a measurement of the the true OLGTF value with a Gaussian distribution, the uncertainty in the frequency dependence of the OLGTF model is now a 1-sigma, 68% confidence interval of +/- 1.5% in magnitude and 1 [deg] between 15 and 700 [Hz] (IF we change the CCP frequency to 290 [Hz], compensate for the AA and AI filters, and include 30 [us] of unknown delay). Note that this assumption of Gaussianity appears to be roughly true for the magnitude, but not at all in phase (I'm still thinking on this). Also note the each one of these frequency points has passed a 0.99 coherence threshold on a 10 [avg] measurement (and most have coherence above 0.995), so the individual uncertainty for each point is sqrt((1-coh)/(2*nAvgs*coh)) = 1 to 2%. Recall the frequency dependence of the model is determined by the following components included in the model: - The 1/f^2 dependence of the [m/N] suspension transfer function (as modeled by the QUAD state space model) - The 2000 [Hz] ESD driver pole - The analog and digital anti-imaging filters - The 130 [us] of actuation delay from 1 16 [kHz] cycle of SUS Computation, 3 65 [kHz] cycles of IOP Error Checking, 1 65 [kHz] cycle of IOP Computation, and 1/2 65 [kHz] cycle for Zero-order Hold Delay - The DARM filters - The single-pole response (at 290 [Hz]) of the optical plant - The analog and digital anti-aliasing filters - The 76 [us] of sensing delay from 1 65 [kHz] cycle of IOP Computation, 1 16 [kHz] cycle of OMC Computation - The 30 [us] of unknown time delay As a cross-check, I recalculated the comparison with the CCP frequency that's currently used in the model, 389 [Hz], and found that at around the high-frequency PCal lines, roughly ~535 [Hz] the model / measurement discrepancy is 25-30%. This is consistent with what the PCAL calibration reports at these frequencies, a DARM / PCAL (which is equivalent to model / measurement) discrepancy of 25-30% -- see LHO aLOG 17582. At the time, the PCAL team reports their internal uncertainty to be in the few-percent range. This had convinced me on Saturday that I had enough information to "officially" change the DARM CCP frequency in the CAL-CS front end, but Gabriele and Evan have since changed the alignment scheme for the corner station to improve the power recycling cavity gain by improving the ITM DC alignment LHO aLOG 17946. This will have an effect on the signal recycling cavity and therefore the DARM CCP frequency, so we'll wait until we get a few more OLGTFs in this new configuration before changing anything. (3) Establishing an uncertainty estimate of the optical gain (the DC scale factor component of the sensing function). After refining the precision of the frequency dependence in magnitude, this allows to quantify the precision to which we can estimate the overall DC scale factor that one needs to scale the model to the measured OLGTF; a factor that we traditionally have attributed only to the change in optical gain between lock stretches. For this study, I've used *all* six DARM OLGTF TFs, see 2015-04-18_AllMeas_FittedCCP_H1DARMOLGTF.pdf. Note that this increases the uncertainty of the frequency dependence to a less Gaussian 2.5%, but as you'll see this is still plenty precise. Recall that before transition to the OMC DCPDs, regardless of input power to the IFO, the OMC_READOUT sensor gain is changed to match the RF readout sensor gains which are already power normalized. That should mean that input power should have no affect on the measured optical gain, and this is a safe comparison. With 6 measurements, the mean scale factor for the OLG TFs is 1.05e6 +/- 26% [ct / ct]. This is consistent by the variation the DARM digital gain by 34% that was used for these 6 measurements. The current optical gain used for the sensing function the CAL-CS front end model is 1.1e6 [ct/m]. This 4% difference from the mean of the these 6 measurements is well within the 26% uncertainty, so we've concluded to *not* change anything there. All this being said, we have used the *same* actuation strength for all of these comparisons, but there is no guarantee that the actuation strength is not changing along with the optical gain. - ETMY is controlled using the Test Mass (L3) and UIM (L1) stages - The cross-over for these two stages in the two groups of measurements is ~1.2 [Hz] and 2.5 [Hz] (see 17713), and by 10 [Hz], the contribution of the UIM is roughly -25 [dB] and -15 [dB]. Therefore the ESD is the dominate actuator in the frequency region which we're we trying to - Static charge affects the actuation strength of the ESD by changing the effective bias voltage of the drive, as well as changing the amount of drive that's in the longitudinal direction (because the charge can migrate to different regions of the reaction mass / test mass gap), see e.g. G1500264, LLO aLOG 16611, or LLO aLOG 14853. - If there is substantial residual charge on the ESD, the charge varies on the the ESD when Ion Pumps are valved into the chamber. - It has been shown many times over that the charge varies on the few hour time scale when there is significant residual charge on the test mass and the ion pumps are valved in (see e.g., G1401033 or as recently as LLO aLOG 17772). Thus, it is reasonable to suspect that the actuation strength is changing between these measurements. LHO has made no-where-near enough measurements (only a one-time comparison between ETMX and ETMY, see LHO aLOG 17528) to quantify how much this is changing, but here is what is possible: - We have a physical model of the actuation strength (or at least more accurate equation for how the bias voltage determines the actuation strength, see above citations). I think we can take what we've seen for the variance (as high as +/- 400 [V] !!) and propagate that through to see how much of an affect it has on the strength - PCAL lines at low-frequency (~30 [Hz]), compared against the DARM calibration lines should show how the optical gain is varying with time, it's just that no one has completed this study as of yet. - Calculation of the gamma coefficient from the DARM lines should also reveal how the open loop gain transfer function is changing with time. In the past, we've assumed that changes in gamma are fluctuations in the optical gain because we've had actuators with non-fluctuating strength. Thus, for now, we'll incorrectly assign all of the uncertainty in the scale factor to optical gain, and call is 26%. Perhaps it will be much better to trust PCAL at this point and time, since it's precision is so much greater than this "scale the OLGTF model" method, but I would need a third measurement technique to confirm the accuracy. I think a power budget propagated to a shot noise estimate compared against the measured ASD (like in LHO aLOG 17082) is the easiest thing to do, since it can be done offline. Or we should resurrect the campaign to use the IMC VCO as a frequency reference, but this has the disadvantage of being an "offline, odd configuration" measurement, just like the free-swinging Michelson. (4)Reducing the delay time in the actuation from four 16 [kHz] clock cycles to three 16 [kHz] clock cycles. As mentioned above, the time delays that are included in this model are - The 130 [us] of actuation delay from 1 16 [kHz] cycle of SUS Computation, 3 65 [kHz] cycles of IOP Error Checking, 1 65 [kHz] cycle of IOP Computation, and 1/2 65 [kHz] cycle for Zero-order Hold Delay - The 76 [us] of sensing delay from 1 65 [kHz] cycle of IOP Computation, 1 16 [kHz] cycle of OMC Computation - 30 [us] of unknown time delay (the equivalent of ~8-9 [deg] of phase at 700 [Hz]) for a total of 206 [us] of delay for which we've accounted, out of the total 236 [us] that's used to produce the above frequency-dependence comparison. So, there's a total of 3.4 or 3.9, 16 [kHz] cycles of known or known+unkuown time delay, respectively. Remember that the "L/c", light-travel time delay (13 [us]) is *less* than the one 16 [kHz] SUS clock cycle (61 [us]) delay that defines when the control signal arrives at the end station over RFM IPC, so we ignore it. Since we only have the infrastructure add the delay in the actuation paths in CAL-CS, then we can only account for the *differential* delay between the two paths. If we assign the unknown delay to the actuation side of things, then the difference in delay between the two paths is (130+30)-76 = 84 [us] = 1.3 16 [kHz] clock cycles, leaving a residual overall delay of 76 [us]. If we assign it to the sensing function, we get 130-(76+39) = 24 [us] = 0.39 16 [kHz] clock cycles, leaving a residual of 130 [us]. Since we can't do less than 1 [kHz] clock cycle, we should chose to assign the unknown delay to the actuation function, apply one 16 [kHz] cycle delay to the actuation function, and suffer the 0.3 / 16384 = 18 [us] phase difference between the sensing and actuation path, and have to account for a 76 [us] delay in offline analysis.
Your list of known delays doesn't seem to include the 13us (L/c) delay from the interferometer response (see e.g. eqn. 16 in T970101).
Daniel's right, details below. As such, the unknown time delay is 16 +/- 5 [us],
For clarity I repeat the new list of time delays:
the time delays that are included in this model are
- The 130 [us] of actuation delay from
- one 16 [kHz] cycle of SUS Computation,
- three 65 [kHz] cycles of IOP Error Checking,
- one 65 [kHz] cycle of IOP Computation, and
- one-half a 65 [kHz] cycle for Zero-order Hold Delay
- The 89.3 [us] of sensing delay from
- one L/c delay sensing the ETM motion in the corner,
- one 65 [kHz] cycle of IOP Computation, and
- one 16 [kHz] cycle of OMC Computation
- 16.7 [us] of unknown time delay (the equivalent of ~3-4 [deg] of phase at 700 [Hz])
for a total of 219.3 [us] of delay for which we've accounted, out of the total 236 [us] that's used in the model.
Details:
--------
More on the L/c time delay, as explained by Daniel:
I have said above,
"Remember that the "L/c", light-travel time delay (13 [us]) is *less* than the one 16 [kHz] SUS clock cycle (61 [us]) delay that defines when the control signal arrives at the end station over RFM IPC, so we ignore it."
Daniel agrees:
The fiber delay is n * L/c or about 20us. It doesn't matter because it is part of
the SUS cycle delay.
However, there is a sensing function delay. When you push the ETM (from the DARM actuation) it takes at least
L/c before you can measure a signal in the corner. This is a pure optical delay. This sensed control signal is indeed what we're measuring when we take an open loop gain transfer function.
For gravitational waves the situation is similar, the photons which travel forth and back in
the arm are, on average, sampling h(t) from half a round trip ago. In reality, this
is only exactly true for perpendicular incidence.
As such, we should subtract 3994.465(+/- 7e-4) [m] / 299792458 [m/s] = 13.3 [us] from the "unknown" time delay, leaving us with a timing uncertainty of 16.7 [us]. Unclear yet what the uncertainty is in this number, since thus far it's merely fit by-eye to make the phase of the OLGTF residual flat. From playing around with the number in the fit, I would suggest a 5 [us] uncertainty on this unknown timing residual.
I'll update
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts/H1DARMmodel_preER7.m
later today to reflect this knowledge.
OMC DCPDs have uncompensated poles at 13.7kHz and 17.8kHz due to their locations above the nyquist freq.
They cause the delay of ~18.5us. The details can be found in LHO ALOG 17647
I've confirmed Koji's statement with a bode plot, though I get a better "fit" with 20 [us] delay. But the point is moot. I'll definitely just include this in the actual frequency response of the sensing function. This brings the unknown time delay to 0 +/- 5 [us] -- wow! Let's hope we don't find out about anything else. ;-) Also -- that means we should include this in the approximation for the super-Nyquist frequency response of the sensing function along with the digital and analog AA filters when we fix that it in the front-end.
I've reprocessed the results after adding the L/c arm delay and the OMC DCPD uncompensated high frequency poles mentioned above. Because we've replaced the equivalent unknown time delay with a known time delay of L/c 13.3 [us] and some very high-frequency poles, the results have actually changed very little and therefore the uncertainty in the frequency response of the OLGTF has changed very little:
Was Is Now
Magnitude Residual StDev: 1.0045 +/- 0.025318 1.0043 +/- 0.025309
Phase Residual StDev: 0.4299 +/- 1.0307 0.23821 +/- 1.0534
However, there're less unknowns in the model, which is exactly what we want.
As such, I stand by my earlier statement:
As one can see on the 3rd and 4th page, assuming each of the residuals frequency points is a measurement of the the true OLGTF value with a Gaussian distribution, the uncertainty in the frequency dependence of the OLGTF model is now a 1-sigma, 68% confidence interval of +/- 2.5% in magnitude and 1 [deg] between 15 and 700 [Hz] (IF we change the CCP frequency to 290 [Hz] -- which is now probably different, and find a good discrete approximation for compensating for the OMC DCPD poles, the AA, and the AI filters). Note that this assumption of Gaussianity appears to be roughly true for the magnitude, but not at all in phase (I'm *still* still thinking on this). Also note the each one of these frequency points has passed a 0.99 coherence threshold on a 10 [avg] measurement (and most have coherence above 0.995), so the individual uncertainty for each point is sqrt((1-coh)/(2*nAvgs*coh)) = 1 to 2%.
Details:
--------
I've added the following parameters to the params files:
par.C.omcdcpdpoles_Hz = [13.7e3 17.8e3]; % LHO aLOGs 18008 and 17647
par.C.armLength.x = 3994.4704; % [m] +/- 0.3e-3; LHO aLOG 9635
par.C.armLength.y = 3994.4692; % [m] +/- 0.7e-3; LHO aLOG 11611
par.C.speedoflight = 299792458; % [m/s]
and added the following lines to the DARM model
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts/H1DARMmodel_preER7.m
par.C.uncompensatedomcdcpd.c = zpk([],-2*pi*par.C.omcdcpdpoles_Hz,prod(-2*pi*par.C.omcdcpdpoles_Hz));
par.C.uncompensatedomcdcpd.f = squeeze(freqresp(par.C.uncompensatedomcdcpd.c,2*pi*freq));
par.t.armDelay = mean([par.C.armLength.x par.C.armLength.x]) ./ par.C.speedoflight;
4:12 - no other activities to report