Add 175ml water to PSL crystal chiller.
When I CTRL-C'ed out of the ESD charge measurement scripts earlier today I reset all of the ESD settings back by hand. I didn't reset the L3 BIO STATE though because I was unfamiliar with these specific settings in the charge scripts (I focused on fixing the L3 BIO screen ESD switches, etc). SO, when the IFO rapidly achieved NOM LOW NOISE after the TUES Maint period, these switches were in the wrong state. Doh!! Shiela tried her magic at transferring the ESD control back to ETMX in order to switch the incorrect ETMY settings, but it broke lock anyways. Praxair is still on site, so we're trying to get back up and into Observe as soon as he's off site. Sorry, that LL was on me!
WP 5495 The daqd processes on h1nds0 and h1nds1 were restarted to force reconfiguration of where old minute trend files exist, since raw minute trend files were copied from SSD RAID to SATAboy RAID. This is normal maintenance.
nm
I have restarted all the dmt processes. This is to fix problems seen at LHO in which disk write delays were interfering with the h(t) and DQ segment generation. The changes made were: 1) remove diagnostic logging from the multicast receiver processes 2) write the DQ xml files to a local disk and then move them to the gds RAID system as a separate process (not time critical). A change of the h(t) calibration filter files was also planned, but this will be done after final calibration group tests.
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
Y--PRAXAIR Deliveries 1 Monday & 2 Tuesday--CP3(MidY)[Monday], CP6(MidX),...
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--OnGoing
Y--Update Code on DMT for latest Calibration--JZweizig--Completed
Y--Finalize Rack Photo Assay--FClara--Completed
Y--TMSX Raster For Clipping--SDwyer--OnWaiting onIFO
This morning, during a short window of pportunity, I ran the charge measurements on ETMX and ETMY. However, the RF45 commissioners were apparently not aware of my hour-long time duration, so the measurements were corrupted at ~45 minutes in. Thankfully the first few measurments ran somewhat successfully. Although, numerous parties visited the end stations while the first few measurements were taken so the coherence is not great. Unfortunately the ETMY measurements from last Fri failed so we do not have any ETMY charge trend between the 8th and today. So, WE NEED ANOTHER HOUR of measurement time in the next day or so. We can use the tail of an earthquake ring down if needed. I'll be trying to pay attention to windows of opportunities for new measruements in the next day or two.
In any case, attached are the trend plots which include todays data - these seem to indicate that it is time to change the bias sign again on at least the ETMY ESD. The ETMX ESD is "flatter in trend".
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.
Summary:
We swapped the 45MHz EOM driver under the PSL table. This box contains the RFAM stabilization board.
Old one: S1500117
New one: S1500118
Related: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=20392
We need some time to assess the impact of this swap.
Phasing:
In the PSL room, we roughly measured the phase of the driver output VS input by inserting a splitter to the input and measure the zero-cross time difference between the input and the output using a scope.
In the old one the output was 6.9ns ahead of the input, but in the new one it was 6.7ns, so there should be 0.2ns or about 3 degrees more delay.
Later we measured the transfer function from the H1:LSC-ASAIR_A_RF45_I_ERR to Q phase while the MICH was free swinging (PRM, SRM and ETMs are all misaligned). The phase between I and Q was basically 0 degrees as it should be.
atan(Q/I) [mean(error)] in degrees | |
Before (according to above mentioned alog) |
76.4(6) |
After, no cable change | 78.7(0.1) |
After, removing one male and one female N barrel | 74.7(0.2) |
After, replace two barrels with one N elbow | 77.3(0.03) |
We decided to go with 77.3deg, which is within 1 degree of the old phasing.
For diagnostics purposes the old unit has been setup in the CER using the 9MHz channels. Instructions how to unhook have been posted there.
The RF glitches are still present and do not depend on the EOM driver. However, they don't seem to show up on the old unit installed in the electronics room.
The h1hwinj1 computer is currently undergoing maintenance and testing. A fresh checkout of the Details directory has been installed, with the old Details directory being moved to Details-old. Testing of psinject and run_tinj will be performed to get these under monit control.
The psinject and run_tinj are now under control of monit. Changes were made to the SOURCEME_LHO.sh script to correct paths to shared libraries, changes checked in. Recompiled run_tinj and tinj using instructions in the source files. Final state, psinject and run_tinj are not running, but under monit control. The output of the H1CALCS_INJ_HARDWARE filter has been turned on, with no injections running.
Detailed here. This process change has been executed. Confirmed the Rogue excitation does not come on and again the GS13s needed to be switched to low gain. Also, even in low gain, the ISI still tripped on the CPS with the GS13 pretty rung up too. I set the ISI guardian to damping only for a few minutes and then it made it to Isolated.
Platform back to nominal with GS13 gain correct in High No whitening.
Title: 09/29/2015, Day Shift 15:00 – 23:00 (08:00 – 16:00) All times in UTC (PT) State of H1: At 15:00 (08:00) Locked at NOMINAL_LOW_NOISE, 22.4W, 48Mpc Outgoing Operator: TJ Quick Summary: IFO locked. In Maintenance mode for start of window.
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/
Elli and Stefan showed in aLOG 20827 that the signals measured by AS 36 WFS for SRM and BS alignment appeared to be strongly dependent on the power circulating in the interferometer. This was apparently not seen to be the case in L1. As a result, I've been looking at the AS 36 sensing with a Finesse model (L1300231), to see if this variability is reproducible in simulation, and also to see what other IFO variables can affect this variability.
In the past when looking for differences between L1 and H1 length sensing (for the SRC in particular), the mode matching of the SRC has come up as a likely candidate. This is mainly because of the relatively large uncertainties in the SR3 mirror RoC combined with the strong dependence of the SRC mode on the SR3 RoC. I thought this would therefore be a good place to start when looking at the alignment sensors at the AS port. I don't expect the SR3 RoC to be very dependent on IFO power, but having a larger SR3 RoC offset (or one in a particular direction) may increase the dependence of the AS WFS signals on the ITM thermal lenses (which are the main IFO variables we typically expect to change with IFO power). This might therefore explain why H1 sees a bigger change in the ASC signals than L1 as the IFOs heat up.
My first step was to observe the change in AS 36 WFS signals as a function of SR3 RoC. The results for the two DOFs shown in aLOG 20827 (MICH = BS, SRC2 = SRM) are shown in the attached plots. I did not spend much time adjusting Gouy phases or demod phases at the WFS in order to match the experiment, but I did make sure that the Gouy phase difference between WFSA and WFSB was 90deg at the nominal SR3 RoC. In the attached plots we can see that the AS 36 WFS signals are definitely changing with SR3 RoC, in some cases even changing sign (e.g. SRM Yaw to ASA36I/Q and SRM Pitch to ASA36I/Q). It's difficult at this stage to compare very closely with the experimental data shown in aLOG 20827, but at least we can say that from model it's not unexpected that these ASC sensing matrix elements are changing with some IFO mode mismatches. The same plots are available for all alignment DOFs, but that's 22 in total so I'm sparing you all the ones which weren't measured during IFO warm up.
The next step will be to look at the dependence of the same ASC matrix elements on common ITM thermal lens values, for a few different SR3 RoC offsets. This is where we might be able to see something that explains the difference between L1 and H1 in this respect. (Of course, there may be other effects which contribute here, such as differential ITM lensing, spot position offsets on the WFS, drifting of uncontrolled DOFs when the IFO heats up... but we have to start somewhere).
Can you add a plot of the amplitude and phase of 36MHz signal that is common to all four quadrants when there's no misalignment?
As requested, here are plots of the 36MHz signal that is common to all quadrants at the ASWFSA and ASWFSB locations in the simulation. I also checked whether the "sidebands on sidebands" from the series modulation at the EOM had any influence on the signal that shows up here: apparently it does not make a difference beyond the ~100ppm level.
At Daniel's suggestion, I adjusted the overall WFS phases so that the 36MHz bias signal shows up only in the I-phase channels. This was done just by adding the phase shown in the plots in the previous comment to both I and Q detectors in the simulation. I've attached the ASWFS sensing matrix elements for MICH (BS) and SRC2 (SRM) again here with the new demod phase basis.
**EDIT** When I reran the code to output the sensitivities to WFS spot position (see below) I also output the MICH (BS) and SRC2 (SRM) DOFs again, as well as all the other ASC DOFs. Motivated by some discussion with Keita about why PIT and YAW looked so different, I checked again how different they were. In the outputs from the re-run, PIT and YAW don't look so different now (see attached files with "phased" suffix, now also including SRC1 (SR2) actuation). The PIT plots are the same as previously, but the YAW plots are different to previous and now agree better with PIT plots.
I suspect that the reason for the earlier difference had something to do with the demod phases not having been adjusted from default for YAW signals, but I wasn't yet able to recreate the error. Another possibility is that I just uploaded old plots with the same names by mistake.
To clarify the point of adjusting the WFS demod phases like this, I also added four new alignment DOFs corresponding to spot position on WFSA and WFSB, in ptich and yaw directions. This was done by dithering a steering mirror in the path just before each WFS, and double demodulating at the 36MHz frequency (in I and Q) and then at the dither frequency. The attached plots show what you would expect to see: In each DOF the sensitivity to spot position is all in the I quadrature (first-order sensitivity to spot position due to the 36MHz bias). Naturally, WFSA spot position doesn't show up at WFSB and vice versa, and yaw position doesn't show up in the WFS pitch signal and vice versa.
For completeness, the yaxis is in units of W/rad tilt of the steering mirror that is being dithered. For WFSA the steering mirror is 0.1m from the WFSA location, and for WFSB the steering mirror is 0.2878m from the WFSB location. We can convert the axes to W/mm spot position or similar from this information, or into W/beam_radius using the fact that the beam spot sizes are at 567µm at WFSA and 146µm at WFSB.
As shown above the 36MHz WFS are sensitive in one quadrature to spot position, due to the constant presence of a 36MHz signal at the WFS. This fact, combined with the possibility of poor spot centering on the WFS due to the effects of "junk" carrier light, is a potential cause of badness in the 36MHz AS WFS loops. Daniel and Keita were interested to know if the spot centering could be improved by using some kind of RF QPD that balances either the 18MHz (or 90MHz) RF signals between quadrants to effectively center the 9MHz (or 45MHz) sideband field, instead of the time averaged sum of all fields (DC centering) that is sensitive to junk carrier light. In Daniel's words, you can think of this as kind of an "RF optical lever".
This brought up the question of which sideband field's spot postion at the WFS changes most when either the BS, SR2 or SRM are actuated.
To answer that question, I:
Some observations from the plots:
I looked again at some of the 2f WFS signals, this time with a linear sweep over alignment offsets rather than a dither transfer function. I attached the results here, with detectors being phased to have the constant signal always in I quadrature. As noted before by Daniel, AS18Q looks like a good signal for MICH sensing, as it is pretty insensitive to beam spot position on the WFS. Since I was looking at larger alignment offsets, I included higher-order modes up to order 6 in the calculation, and all length DOFs were locked. This was for zero SR3 RoC offset, so mode matching is optimal.