Sheila, Haocun
We had lots of locklosses today, and some were probably caused by the side OSEM driving of the beamsplitter M1, as shown in the figures attached.
(H1:SUS-BS_M1_MASTER_OUT_SD_DQ & H1:SUS-BS_M1_DAMP_T_IN1_DQ)
It seems to have happened again at 22:20:12 UTC June 15th
Tagging SUS and CDS.
Tonight I had a look at several other of these locklosses, and other than the one at 23:57:59 that Hoacun plotted, it seems mostly like the glitch in the side osem comes after the lockloss. Many of these locklosses seem to happen durring the CM board switching.
It does seem like it would be worth investigating this side osem issue, since we know that it causes at least some locklosses.
J. Kissel WP #5932 Today's model modifications come in three parts: (1) Independent Synchronized Oscillators for each isolation stage of the QUAD for calibration lines (2) Updated CAL-CS model with better demodulation scheme that spits out coherence and uncertainty (3) Changed all CAL-DELTAL and CAL-DARM channels to double precision and removed whitening Below are all the details. ------------- Part (1) In order push the PCAL vs. SUS actuation calibration line cancelling scheme for ER9/O2 forward (see T1600218 and T1600215), I've installed independent, longitudinal, synchronized oscillators in each of the UIM/L1, PUM/L2, TST/L3 stages of all of the QUAD models. See first attachment for screenshot of the QUAD OVERVIEW screen that now has the CAL_LINE block beneath every LOCK bank. Sadly, due to the recent split in QUAD library part models, I'd forgotten to add the needed EPICs channel for GPS synchronization to the ITMs. We'll install them tomorrow morning. I've committed the following new models: /opt/rtcds/userapps/release/sus/common/models/ Sending FOUROSEM_DAMPED_STAGE_MASTER_WITH_DAMP_MODE.mdl <-- Used in PUM/L2 stages Sending FOUROSEM_STAGE_MASTER_OPLEV_TIDAL.mdl <-- Used in UIM/L1 stages Sending QUAD_MASTER.mdl <-- Added EPICs record for GPS sync time on TST/L3 stage for ETMs and accordingly modified MEDM screens: M SUS_CUST_QUAD_ITM_OVERVIEW.adl A + SUS_CUST_QUAD_ISTAGE_CAL_LINE.adl D SUS_CUST_QUAD_L3_CAL_LINE.adl M SUS_CUST_QUAD_OVERVIEW.adl ------------- Part (2) In addition, as a continuation of the improvements to using those calibration lines to track changes in the DARM loop parameters, I've followed Joe's instructions (see LHO aLOG 26491) and updated the CAL-CS model to demodulate PCAL and DARM error signals at given frequencies and produce parameter estimates, coherence estimates, and even uncertainty estimates. Darkhan will be working on commissioning the infrastructure with Joe. ------------- Part (3) Finally, I've converted all of the calibrated DARM channels to double precision. *EXCEPT* for DELTAL_EXTERNAL, which is needed to display on the wall in the control room via DTT (which sadly, cannot yet handle double precision; see CDS Bug 1003). As a result, and as per Joe's advice I've turned OFF all dewhitening filters that condition the following (new) channels stored in the frames: H1:CAL-DARM_CTRL_WHITEN_OUT_DBL_DQ H1:CAL-DARM_ERR_WHITEN_OUT_DBL_DQ H1:CAL-DELTAL_CTRL_DBL_DQ H1:CAL-DELTAL_CTRL_PUM_DBL_DQ H1:CAL-DELTAL_CTRL_TST_DBL_DQ H1:CAL-DELTAL_CTRL_UIM_DBL_DQ H1:CAL-DELTAL_RESIDUAL_DBL_DQ We need to investigate if we're now happy with the signal fidelity without whitening or if we just need to re-assess the whitening. Again, I've retained single precision on H1:CAL-DELTAL_EXTERNAL_DQ, so its whitening filter remains ON.
J. Kissel, J. Betzwieser Joe called to let me know that I'd misinterpreted the fixed oscillator part that we chose to use (of the two; see T1600143). Turns out this version of the fixed phase oscillator automatically synchronizes to GPS time 0 (i.e. Jan 4 1980), so there's no need for the extra EPICs record input to the oscillator that specifies the GPS time. So, in opposition to what's said above, the ITM models are fine; we need to take the GPS EPICs record *out* of the ETMs. Will do so tomorrow.
J. Kissel All QUAD Models have been restarted sans EPICs record for synchronization (the ITMs needed a restart to absorb the removal from the L1 and L2 stage common library parts). MEDM screen has been updated as well. I've committed the following to the repo. /opt/rtcds/userapps/release/sus/common/medm/quad/ Sending SUS_CUST_QUAD_ISTAGE_CAL_LINE.adl /opt/rtcds/userapps/trunk/sus/common/models/ Sending FOUROSEM_DAMPED_STAGE_MASTER_WITH_DAMP_MODE.mdl Sending FOUROSEM_STAGE_MASTER_OPLEV_TIDAL.mdl Sending QUAD_MASTER.mdl
The ITMY PI path was measured during maintenance day driving from CDS and measuriung the quadrant outputs to the ESD. WP#5931
Specifically driving H1:SUS-ITMX_PI_OMC_DAMP_MODE2_DAMP_EXC, and measuring P2-P5 of D1600122 directly with an SR785.
Generally behaves well. The LR channel has slight excess noise (about twice the other channels) which is a ~65kHz signal. It goes away when the DAQ input to the box is removed. There was no evidence of the glitchy behaviour of ETMX LR channel.
Other than that it looks just like the ETMX. The electronics TFs slightly over estimating the HF voltages.
Anticipate running this pump for then next week or two.
I've started a test Conlog process on conlog-test-replica connecting to the same channels as the production Conlog process on h1conlog1-master.
Michael, Jim, Krishna
We had 20-40 mph winds for most of the day yesterday. In the evening we tested a couple of different ISI configurations at the Corner Station (ITMX, ITMY) and the End-Stations. We tested the following two configurations:
1. 90 mHz Blends on ST1 and no sensor correction (SC) on all test-mass chambers - The standard configuration used for most of O1 which works well in low microseism.
2. 250 mHz Blend and BRS SC on ST1 at the End-Stations and 90 mHz blends and no SC on ITMX, ITMY - The idea is to use the tilt-subtracted ground seismomter in feedforward more and rely less on the tilt-contaminated ST1 seismometer.
Quick Answer: The effect on some of the Interferometer channels we looked at was a small but uniform improvement of a factor of ~1.5 or so over the 90 mHz blend configuration. Near 0.1 Hz we were limited by ITMY chamber motion.
Details: The first attached pdf shows some of the Interferometer channels in Config 1 (Dashed) versus those in Config 2 (Solid) in units of ADC counts. The red line is equivalent to H1:DARM_CTRL_OUT_WHITEN_DQ which for some reason was not available today. The other three lines are some of the Angular Control Signals, all of which show small improvements. The second page shows the ASD of the wind-speed in both Configs showing that wind-speeds were comparable during the two measurements.
The second pdf shows data from some of the ISI local sensors. The first plot shows the ground motion near each chamber - note that the ITMY seismometer sits in the 'bier garten' which is far away from the walls of the building. Also shown are the tilt-subtracted super-sensor signals (dashed lines). It is worth noting that the secondary microseism becomes visible after tilt-subtraction and is consistent with what the ITMY seismometer measures. The next plot shows the CPS signals which at low frequencies, are representative of the motion of ST1. The combination (ETMY-ITMY)-(ETMX-ITMX) should roughly correlate with DARM_CTRL at low frequencies, since the translational ground motion is small below the microseism. The third plot shows the ST1 seismometer(T240) motion. In all these plots, notice that despite the apparently quieter ground motion, ITMY moves nearly as much as ETMY. This is also seen in the fourth plot - which shows the coherence of the DARM_CTRL with the various CPS sensors. ITMY shows significant coherence between 60 to 200 mHz.
I think this suggests that the ITMY seismometer may not be a good measure of the tilt of the ITMY chamber, which is closer to the walls of the building. Thus our assessment that the Corner tilts significantly less than the End Station may not be valid. But if ITMY seismometer acts as a nearly tilt-free seisometer we can use it for sensor correction just as we do at the End-Stations and gain another small factor of ~1.5-2 in low frequency DARM_CTRL.
(Richard, Gerardo)
Landed cables at rack and at the controller for annulus ion pump 525 (BSC5 AIP), gettind data now.
For future reference at the rack for both X-end and Y-end:
F37 ------- 011(+)
F38 ------- 012(-)
Added 231 channels. Removed 74 channels. (see attached) The following channels are still unmonitored: H1:GRD-TCS_ITMX_LOGLEVEL H1:GRD-TCS_ITMX_MODE H1:GRD-TCS_ITMX_NOMINAL_S H1:GRD-TCS_ITMX_REQUEST H1:GRD-TCS_ITMX_REQUEST_S H1:GRD-TCS_ITMX_STATE_S H1:GRD-TCS_ITMX_STATUS H1:GRD-TCS_ITMX_TARGET_S
Kiwamu, Jeff, Evan
The calibration group has known since O1 that Hanford (but not Livingston) has an anomalous loss of gain in the DARM optical plant at 10 Hz and below. This can be explained by 0.5° of positive (antispring) SRC detuning away from pure RSE.
The first attachment shows a loop-corrected pcal sweep from O1, calibrated into mW/pm. On top of this I have plotted my guess at what theory curve this corresponds to (from Rob Ward's thesis), using 700 W of beamsplitter power, an arm pole of 42 Hz, an SRM transmissivity of 37 %, a homodyne angle of 90°, and a one-way SRC carrier phase of 90.5°. (The theory curve is pretty much insensitive to variations in the homodyne angle at the few-degree level, and we know that the homodyne angle deviates from 90° by less than 3°, since we ran with 20 mA of dc offset light and there is less than 1 mA of contrast defect light.)
To test this, I took a new set of pcal sweeps at 10 W of input power, with several different SRC detunings. The result is shown in the second attachment, again with guesses about the theory curves. All are with 350 W of beamsplitter power, 42 Hz arm pole, 37 % SRM transmission, and 90° homodyne angle. 0 ct of SRCL offset corresponds to the green (90.8°) curve, –200 ct corresponds to the blue (90.1°) curve, and +200 ct corresponds to the red (91.5°) curve. The implied calibration (0.1 ct / pm for the SRCL error point) is consistent with SRCL OLTF budgeting. The fact that 0 ct of SRCL offset produces a nonzero RSE detuning is perhaps not surprising, since we have never had good angular control of the SRM.
With the list of items on our plate and the need to give more time to getting H1 ready for ER9, we did our darnedest to limit Maintenance Day to 4hrs today. Jeff helped from the Detector Engineer side, and Ed was recruited whenever the waves of activities were too much.
With Maintenance starting at ~8:00, we were complete by around 12:39pm. At this point, it was noticed that the Quads were pretty misaligned. I restored their pointing via Oplev trends, and then since there were big changes, I went ahead and performed an Initial Alignment.
Ops Note: Only issue with alignment was when doing the last step (SRC_ALIGN_OFFLOADED). For some reason, the IMC would break lock and Guardian would loop through this step repeatedly. Not really sure what the issue was here. Sheila & Jenne were notified of this.
Alignment took from 12:39pm - 1:44pm & then handed over to Commissioners.
A log of all activities are attached as a pdf (vs posted in this alog......thought of reducing alog real estate with the many lines of each activity during the day---input on preference on how Operators should post logs like this would be nice).
At 18:00 utc I decreased the LLCV valve setting to 18%, previous setting was 20%. Due to LN2 delivery today.
Added 300 mL H2O to the H1 PSL crystal chiller. There were no fault alerts on either chiller. Both canister filters appear clear.
Gerardo, Chandra Adjusted the potentiometers of the following pirani gauges (3-8 turns in CW direction) to calibrate pressure reading to ~5e-4 Torr. PT-100 PT-110 PT-114 PT-134 PT-210
I replaced the razor blade beam dump that was being used to dump the p-pol beam (rejected beam in the MCR path) with two steering mirrors and a Kentek Trap-it.
The p-pol beam will be a minimum of 1.2W at 50W input power, and about 0.8W at 30W input power.
Removed: IO_MCR_BD6 razor blade dump
Added: steering mirrors IO_MCR_M14 and IO_MCR_M15:
Added: IO_MCR_BD6 high-power beam dump
With this upgrade completed, I've modified the IOT2L layout drawing to include the new components, and updated the version to D1300357-v3.
Attached:
15 days trend data for the 3 IFO storage containers attached.
New today is the the SEI_CONF Guardian node that will manage all of the other configuration nodes that we have made the past few weeks. This will hopefully make it much easier to choose a configuration for all of SEI. Sensor Correction for the entire SEI can be turned OFF from here, and then be brought back, of course.
The states and their names are very likely to change in the near future. So keep an eye out for updates, and we will also try to keep documentation up to date.
I also move the GUARD_OVERVIEW.adl around a bit since it was getting crowded in spots.
I changed the Blend_PAGE_MAIN.adl to include all of the config nodes and removed the SC ON/OFF switches. I have also included a guide to help choose states, but take it lightly because I'm sure it will change again soon. The right corner shows if the MATCH bank gains are 1 (green) to allow for sensor correction (Enabled) in that chamber.
Modified the PUM Chassis by connecting pin 2 and pin 18 on the binary input DB37 connector. This was to address the issue of the binary RMS reset not working. See alog 27633. We confirmed this modification was already done at EY. Next Tuesday we will need to verify the ITM units have this modification.
We also confirmed that R111 had the correct value of 100K on all four channels.
David.M, Jenne.D, Jeff.B
This morning we set up 6 L4Cs in the 'beer garden' area of the LVEA. They are positioned close to the STS-2 there, with three on the concrete and three on the linoleum surface (see attached photo). This should enable us to determine the effect of the linoleum coating on the L4C output spectrum.
I've attached a screenshot from Diagnostic Test Tools plotting the power spectrum of all 30 L4C channels. Only the 7th L4C channel (H1:NGN-CS_L4C_Z_7_OUT) shows a seismic response. The other channels only show ADC noise, however there should be 6 sensors connected. Early tomorrow morning I'll perform some checks to try and diagnose where the problem is.
I looked at last night's increase power lockloss, and can see that the lock broke right when the IMC common mode board gain slider moved. (plot attached). For now I've changed the gain adjust function in the IMC guardian to make 2dB steps instead of 1dB.