All SEI GS13s are now set in High Analog Gain without Whitening except HAM6 and BS (Stage2.) This standard High Gain configuration is with both FM4 & 5 Off in the GS13 INF module, H1:ISI-HAM5_GS13INF_H1 for example.
For HAM6, because of the shutter hit to the ISI, the GS13s are run with Low Analog Gain without Whitening. This configuration is with FM4 On and FM5 Off.
For BS, because of the hit to the ISI when the MICH acquires, we run the GS13s in the standard low Gain configuration of Analog Low Gain and Whitening. This has both FM4 & 5 On.
These configurations are set in SDF.
Here are the PSL DBB/ISS scans for this week. No significant change from last week.
One of the ISCT6 enclosure handle could not be locked and it was guarded with an yellow caution tape.
Corey brought a new handle, but when we assessed the situation it turns out that the new one and the old one were identical, it was just that the old one was installed at a wrong angle. We removed the old one and re-installed after rotating 90 degrees, and voila, it can be locked when the door is closed and the handle becomes horizontal. Only caveat is that the handle tip points up, not down, when the door is open.
We locked the doors and removed the yellow caution tape.
Here are the past 10 days trends:
The computer that generates web-accessible MEDM screen shots and model simlink captures is not running well since about March 11, 17:59 PDT. It will hopefully be repaired soon.
MEDM screen shots are working now, simlink capture will run at 12:00 PDT.
Today we have spent most of the day trying to lock. We have locked, but only after some diifictulties.
As Sheila mentioned we had problems engaging the ASC in DRMI. In particular, with today's initial alignment, for some reason, both POB_A and AS_C see pointing numbers between 0.2 and 0.46. When we engage the PRC1 loop (which uses POB_A), the control signal very quickly saturates the bottom stage of PRM, leading to a lock loss. The top mass relief loops are not fast enough this engagement. To a lesser extent the same is true for the SRC2 loop. For now I implemented a Guardian section that copies the error signal into the offset (with opposite sign), engages all loops at nominal bandwidth, and starts a 5min slow offset ramp back to the nominal point. We should do several things to mitigate this, probably in this order: - 1) Find an initial alignment procedure that puts us closer to where we want to be, making the WFS turn-on transient less violent. - 2) Commission a much higher bandwidth relief servo to the top mass. - 2) Implement a saturable integrator in the ASC control filter bank - like we have in the tidal servo. This would make engaging the WFS trivial, and guarantee to avoid saturation.
I also added limiters to the PRC1_P, PRC1_Y, SRC2_P and SRC2_Y filter modules: - PRC1: 1e4 cts limit. This corresponds to a drive of - 53168cts to PRM M3 coils - 8741cts to PR2 M3 coils - 24221cts to SRM M3 coils - 3457cts to SR2 M3 coils - 809cts to IM4 coils - SCR2: 1e3cts limit. This corresponds to a drive of - 40368cts to SRM M3 coils - 5762cts to SM2 M3 coils This should under all circumstances leave us enough range for length control on the M3 coils. In addition I added limiters to all involved to top stages angular controls: H1:SUS-BS_M1_LOCK_P_LIMIT = 500 H1:SUS-BS_M1_LOCK_Y_LIMIT = 500 H1:SUS-IM4_M1_LOCK_P_LIMIT = 1000 H1:SUS-IM4_M1_LOCK_Y_LIMIT = 1000 H1:SUS-PR2_M1_LOCK_P_LIMIT = 1000 H1:SUS-PR2_M1_LOCK_Y_LIMIT = 1000 H1:SUS-PR3_M1_LOCK_P_LIMIT = 500 H1:SUS-PR3_M1_LOCK_Y_LIMIT = 500 H1:SUS-PRM_M1_LOCK_P_LIMIT = 1000 H1:SUS-PRM_M1_LOCK_Y_LIMIT = 1000 H1:SUS-SR2_M1_LOCK_P_LIMIT = 1000 H1:SUS-SR2_M1_LOCK_Y_LIMIT = 1000 H1:SUS-SR3_M1_LOCK_P_LIMIT = 500 H1:SUS-SR3_M1_LOCK_Y_LIMIT = 500 H1:SUS-SRM_M1_LOCK_P_LIMIT = 1000 H1:SUS-SRM_M1_LOCK_Y_LIMIT = 1000 They are large enough that we shoul never run into them under normal operations, but small enough to avoid "astronomical" kicks on lock-loss.
Chris, Alexa
The first two attachments show the OLTFs of the various length DOFs. In these plots, the model is the blue trace and the red trace is measured data. The DARM TF agrees pretty well. The PRCL and SRCL loops appear to have a gain missing. The CARM and MICH model loops are not correct.
The fourth attachment depicts the noise budget produced by the model for the 8W lock on March 04, 2015 15:30 UTC. This roughly agrees with the conclusions Evan has made with his NB (LHO#17101). At high frequencies we are dominated by shot noise. At around 300 Hz we suspect intensity noise (or maybe beam jitter), as Gabriele noticed. From 30-100 Hz we are limited by DAC noise. And below 10 Hz we see some angular fluctuations.
The modeled MICH loop gain is looking better now. There were some aggressive BSFM plant inversion filters that weren't being linearized accurately in Simulink. This was fixed by using numerical TFs for them. The shape is still off above 60 Hz, but that's probably due to the filter change from alog 17148.
I put in sign flips as needed to ensure an even number of them are present in each OLTF. There remains some 10 dB of mystery gain to be hunted for in the DRMI loops.
SudarshanK, RickS
Today we had a quick look at our calibration data from Yend, taken after installing a polarizing beamsplitter downstream of the AOM (see aLOG 17145).
We will post a more detailed log after we have fully digested the data, but the preliminary result is that the new calibration of the Tx PD signal is within 6% of the previously reported number (see aLOG 16718).
This is about what we expected from our recent measurements of the signal drifts resulting from depolarization in the AOM.
Added 689 channels. Removed 123 channels.
The X direction at end X and the Y direction at the Y end are blended at 90mHz. Sensor correction is in the normal conifugration (no BRS). This was done at around 22:58 because we have had several lock losses due to large motions in the arms that ALS cannot handle.
This was at about -30 minutes on this screenshot, as you can see the arm control signals are reduced with the higher blends.
There is nothing that look like high ground motion on the seismic FOMs, although the winds are a little elevated (gusty 10-25 mph)
Here's a screen shot of the wind trend. Sheila switched the blends roughly 1 hour in the past on this trend.
Attached is a screenshot of the PEM's seismic FOM. So now we want to look at ISI T240s - 5 hours ago (~18:45 UTC -- after the Earthquake at -6 on the SEI FOM), - 3 hours ago (~20:45 UTC -- when the wind picks up, before the blends were switched) - and now (~22:45 UTC -- when the wind is still up, and when the blends have switched) Take a look at the time series of these few IFO channels: H1:ALS-(X/Y)_REFL_CTRL_OUT(MON or _DQ, whichever) this is what Sheila typically uses to assess badness. (and they're calibrated into [um]'s )
Corner station to X-1-5 double doors of the beam tube has been cleaned. Lights were relocated, support tubes vacuumed and moving north towards mid station from X-1-5 double doors. Looking into purchasing a suitable generator for this operation, the previous one not necessarily designed for this type of duty. We are still able to use site power for this section of cleaning. Beam tube pressures continually monitored by control room operator during cleaning operations.
Times in PST
07:00 Karen and Cris to LVEA
08:49 Richard to EY electronics bay
09:11 Peter King to Mid X
09:17 Richard back, Fil to EX electronics bay
09:30 Peter back
09:37 Fil back
09:39 Peter to Mid X
09:48 Corey to squeezer bay
10:10 Peter and Richard back from MX
10:26 Kyle to LVEA checking pumps
11:56 Corey out
13:38 Corey to squeezer bay for 20 min.
15:33 Dave/Ryan Fisher restarting OCD Master model
I'm posting some plots of the performance of the BSC-ISI's. The attached pdf has 18 plots, the first 12 show the contributions of each control path to the performance of the ISI, shown against aligo requirements, sensor noises and ground motion. The order is St1 X (p. 1), St2 X(p. 2), St1 Y(p. 3),... for x, y, z, rx, ry, rz. The configurations measured were offline, damped ISI, St1 ISI isolated / St2 damped, isolated (both stages), isolated with tilt decoupling, isolated with tilt decoupling and sensor correction, isolated with tilt, sensor correction and feedforward from HEPI. HEPI was off for the offline measurment as well. The blend filters used were the normal blend filters (the rdr compliment of filters with the T750 blend on St1 RZ). Please note that on the rotational plots, I used "paralell" ground direction (Y for RX, X for RY, Z for RZ). No, it doesn't make perfect sense, but X can be injected to RY or vice versa, and the BSC's have a coupling from Z to RZ, that we need to be aware of.
The last 6 plots show the final performance (i.e. our current configuration with damping, isolation, tilt decoupling, sensor correction and feedforward) for each dof for both stages.
Similar plots for the HAM's are next.
The Z and RZ ST2 isolation loops were mistakenly using a high-frequency, 750 [mHz] blend in these performance plots. See LHO aLOG 17222 for further discussion, but we think we can easily do much better in these DOFs between 0.5 and 1 [Hz]. We will remeasure and repost similar, improved "performance progression" plots in the future.
Alexa, Sheila, Evan, Chris, Stefan We implemented Peter's DARM 'SUScomp' from alog 16728. Since we can't lock with that filter directly (see alog 16840), deleted the old 'LLO' filter, but instead loaded a difference filter called 'acqLP' that makes the 'SUScomp' look like the old 'LLO' filter: zpk([80;500-800i;500+800i],[50;70;200],1,"n") Guardian was updated to turn off acqLP' in FM8 instead of turning on a lead. A note on the previous filter is also found in alog 16381.
I have attached a plot comparing our various configurations:
1. Red trace: RF DARM sus compenstation as designed by Peter to obtain more phase margin. The LSC DARM configuration is: FM1(suscomp), FM2(2:0), FM3(resG), FM4(4^2:1^2), FM5(2:0), Gain 800 (LHO#16728, 16840)
2. Blue trace: Our old RF DARM sus compenstation where we used the LLO control filer and a 200Hz lead filter. (LHO#16381)
3. Green trace: ALS DIFF sus compensation. This is the configuration we use to lock ALS DIFF. The LSC DARM configuration is: FM1(suscomp), FM2(2:0), FM3(resG), FM7(SB60), FM8(acqLP),FM10(RLP33), Gain 400. As Stefan mentioned, FM1+FM8 returns our old LLO control filter.
I have also attached the RF DARM OLTF model with the new (red) and old (blue) configuration as described above, along with the respective measured data. The RF DARM UGF is now 55 Hz with a phase margin of ~45deg.
Measurement of new DARM loop on dc readout is attached.
I've saved Evan's .xml to the calibration repository here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs/2015-03-09_DARM_OLGTF_LHOaLOG17153.xml and exported text files of the transfer function and coherence, /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs/ 2015-03-09_H1_DARM_OLGTF_LHOaLOG17153_coh.txt 2015-03-09_H1_DARM_OLGTF_LHOaLOG17153_tf.txt Transfer function contains the following columns (i.e. I exported IN1 / IN2 "as is"): Frequency [Hz] Real Part [ ] Imaginary Part [ ] We'll use later for calibration / noisebudget model verification!
Also including the CARM OLTF that we took at 9 W.
I checked the measured DARM open loop transfer function posted by Evan against my DARM open loop model. Even though I did not do a fitting or any fancy analysis yet, it seems that the optical gain was consistent -- the measurement matched the model with an optical gain of 1.1x106 cnts/m or 9.09x10-7 m/cnts which we have been using since Feb. 21st (alog 16843) for the CAL-CS front end model.
Here is a plot showing the model and measured one:
The matlab script to generate this plot is archived in calSVN:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts/DARM_OLTFGTF_LHOaLOG17153.m
Note for myself:
optical gain in the model = 1.1e6
ESD strength in the model = 2.8e-10 [N/V^2] (see alog 16843)
LSC_DARM_GAIN = 800 (instead of 400)
Only ETMX was actuated
In response to Evan's alog (alog 17065), I took a look at the DARM spectra. Here are conclusions at the moment:
(Noise spectra)
The data sets that I used are from:
Here is a comparison of all three curves with the GWINC theoretical curves above 400 Hz up to 7600 Hz.
As Evan reported, indeed the measured curves from last night are lower than the GWINC curve in 1 - 4 kHz band while the one from Feb-26 looks fine.
(Discrepancies between the curves)
Now, I want to answer how much the Mar-4 data differed from the one from Feb-26th by taking the ratio between them. I divided the Feb-26th by Mar-4th spectra in 400-7600 Hz band. Then I convert it into a histogram to see how they differ on average. Since there were many peaks whose amplitude varied as a function to time, I excluded them by limiting the histogram range from 0 to 2. The ratio is shown as red bars in the below plot.
Note that I could have done a fancy Gaussian fit for it, but for now I picked the highest bar in the histogram in order to coarsely estimate the ratio. As shown in the plot, the Feb-26 data had a higher noise level by a factor of 1.09 on average.
Then I did the same ratio analysis for the 2.8 W and 8 W data of Mar-4th. It is shown as blue bars in the same histogram plot. Picking the highest bar, I measured the ratio to be 0.58 which agrees with what we expected i.e. sqrt( 2.8W / 8W) = 0.59. So the power scaling from 2.8 W to 8 W seems to have been done correctly last night.
(Unexplainable dip at around 2.8 kHz in the 8 W data)
However, it is not the end of the story yet. The noise curve of the Mar-4 at 8 W had a funny feature at around 2.8 kHz where the noise go down below the GWINC curve even if i apply the 9 % correction.
The below plot shows "normalized" spectra of all the three data sets. In order to line up all the spectra at the same level, I "normalized" the Mar-4th-2.8W data by multiplying a factor of 1.09. In a similar manner, I "normalized" the Mar-4th-8W data by a factor of 1.09/0.59. In this way I checked the shape of all the spectra.
The Mar-4th-8W data was lower by the rest of the two curves by 10-ish %. I did not do a serious histogram analysis.
Finally , if I apply only the 1.09 correction factor to the data from last night, they look like this:
Apparently the Mar-4-8W data is lower at around 2.8 kHz than the GWINC curve.
At least part (maybe all) of the issue here is actually due to the GWINC curves that we're using right now. In particular, I had put in a value for the arm losses that was too high.
By putting in 50 ppm per optic (i.e., 100 ppm per arm, which is closer to reality than the 180 ppm I was using before), I get a GWINC curve that is below the measured calibrated strain curve. This is shown for the recent 8 W lock in the attached noise budget.
Out of curiosity, I've also shown a rough estimate for how much DAC-induced ESD noise we can expect if the proposed low-pass filtering is installed (pole at 1.6 Hz, zero at 53 Hz). Obviously this is subject to the same uncertainty as the current noise trace with regard to the magnitude of the actuation coefficient.
Notes: