SudarshanK, RickS
We have reduced the amplitude of the higher frequency Pcal lines by about a factor of five as follows:
Xend 534.7 Hz: 28570 cts. -> 6000 cts.
Yend 540.7 Hz: 23500 cts. -> 5000 cts.
Sheila, Dave:
Sheila made a h1oaf model change [WP5232], this required a DAQ restart which was done at 17:35PDT
The system which runs on cdslogin and sends emails and cell phone text messages if certain vacuum or fmcs EPICS signals go out of nominal was reconfigured and restarted. The changes are:
07:15 Rick to EY for PCal
08:00 Ops phone apparently not ringing
08:16 Sudarshan to EX end assuming Rick went there. Rick reported no one answered at ops. (ringer)
08:20 re-booted FOM video4
08:42 Kingsoft on site
09:10 Rick and Sudarshan to both end stations to do calibrations on Pcal. Will not be moving mirrors.
09:12 P King into LDR
09:15 Peter out of LDR
09:20 Jodi at MidX
09:25 Jodi out of MidX
09:31 Kingsoft off site
09:32 Bubba to begin strip installation on X arm just the other side of the berm
09:50 Richard to EX to check out phones
10:17 Richard back from EX
10:21 Jodi back from MidY.
10:53 Pcal team out of the Ends
11:00 Rick Nutsi and Sudarsh back from End stations
11:02 Pcal team back out to EY
11:05 2 tour groups in succession into the control room
12:30 Rick et al finished at EY
12:35 Begin initial alignment
12:42 Dark Mich locked
12:55 initiated ISC_LOCK
13:16 DC readout. will stay here and asses before proceeding to LSC_FF
14:30 Sigg went to MidY
14:45 Sigg back from MidY
Sometime earlier in the week one of the storms knocked the phones out at End x. I have traced it down to the switch at the corner station. I have reprogrammed a different port to connect to the end station and the phone should now work
Jeff, Evan
The current CW hardware injections into DARM control are too loud to allow transitioning from ETMX to ETMY. So we turned them off around 21:00:00 by turning off the input to CAL-INJ_HARDWARE.
On ETMX, the loudest line (at 1395 Hz) has an rms of about 2 counts. For ETMY (with the low-pass filter on the low-noise driver), one must actuate 50×(50/2.2)2 ≈ 26000 times harder at high frequencies. That means the ESD will have to push 50000+ counts rms. The attached plot shows the DARM drive at a few points along the actuation chain (only ETMX was used as an actuator). The hardware injection does not show up in DARM_OUT, or in the version of DARM_OUT that it sent to the CAL model. It does show up in the ETM drives. The attached screenshot helps us remind ourselves of the relevant model topology.
Also note that this is happening at frequencies above the Nyquist of the quad drive DQ channels, which is currently 1 kHz. That means it would have been much harder to catch this if we had been trying to do a lockloss analysis after the fact. The same goes for instances where the drive is being saturated by higher-order violin harmonics, as has happened in the past.
The line amplitudes were bumped up by a factor of 10 for last night's test. Can we remove that factor of 10 to see if you still see problems? We can go down still further for the higher-frequency lines.
Yes, factor of 10 lower is probably fine. I turned injections back on with a gain of 1 instead of 10.
Here is a recent DARM spectrum, taken with 24.6 Watts of power into the IMC, with the new low noise ESD driver with the low pass on.
The peaks around 300 Hz which are worse than in the reference are coherent with the PSL periscope, we might be able to adjust IMC WFS offsets to improve this. There is also coherence with SRCL, there was no feedforward of MICH or SRCL durring this time.
This lock stretch did not appear on the summary page, this must have to do with the change on the sumary page from H1:DMT-SNSW_EFFECTIVE_RANGE to H1:DMT-SNSH_EFFECTIVE_RANGE. I'm not sure when the SNSH is calculated, but we should note that some good lock stretches are now missing from the summary pages.
I have restarted h1broadcast0 with the latest DMT channel list from John Z. Number of channels was reduced from 1080 to 928 (removed 284, added 132)
https://redoubt.ligo-wa.caltech.edu/websvn/filedetails.php?repname=cds_user_apps&path=%2Ftrunk%2Fcds%2Fh1%2Fdaqfiles%2Fini%2FH1BROADCAST0.ini
Something is not healthy on SR2 suspension.
Recently we noticed that some DAC on SR2 suspension saturated intermittently at a rate of roughlu once per 10 minutes or so. At the begginig we thought this was due to some ISC feedback saturating some DACs when we lock the interferometer. However, it turned out that it saturates even when no ISC feedback is sent.
The attached is a one-hour trend of all the saturation motniors of the SR2 top stage actuators from the period when SR2 was aligned and damped without any ISC feedback signals yesterday. As seen in the plot, the RT and LF DACs saturated mutiple times. The LF saturated more frequently than the RF actuator. Looking at the suspension screen, Betsy and I found that the longitudinal dampig showed higher signal level at its output than every one else. It is on the order of 100 counts at the output. Betsy is currently checking the longitudinal damping loop by running a transfer function measurement.
I ran a damped L (longitudinal) loop TF which looks "healthy" when compared to previous TFs - so nothing agregious there. However, we note that we do not have a lot of damping in any of the H1 HSTS L loops as observed from looking at the other HSTS L TFs. Also the L loop output seems to be doing more work (higher numbers rolling through) than other L loops. We started looking at filter diffs in the L loops and see that in some HSTSes we have the FM10 Ellip50 engaged. We engaged this filter and see that the L loop output became much quieter (closer to zero). Kiwamu wants to see if this will improve the saturations of SR2 and imprve locking. Attached is a quick damped TF of SR2 M1 DAMP L with the FM10 engaged, as well as a screen snapshot.
For some reason, the elliptic filter that we installed at FM10 of the longitudinal damping loop was taken out on 2015-June-2 18:00. SR2 seems to be saturating again. Sad.
I wrote this earlier and then got distracted and too smart (logged out of machine), apolgies for the delay.
Untripped watchdogs around 0800+ pdt. No issues with untripping. HAM5 ISI did have rogue exc alarm as well. BS was only HEPI tripped--is this because of the large vertical drive? Could be.
Here are the X1 and X2 module pressures while the tube washing has been progressing. The features present are those resulting from ION pump voltage changes, gate valve cycles, and a repair of a leaky metal valve at XEND.
Rick Savage and the Pcal Team request NO IFO LIGHT IN THE ARMS while they are at the end stations doing calibration work. This activity will take approx 2 hrs or until they report to the operator. (whichever comes first). That is all.
Calibration run ends today at 12:01PM
Annealing begins today at 12:01PM
SUS - no report
SEI - no report
Pcal - Rick and co. finishing calibration efforets at both end stations. Mirrors will remain in nominal states w/ no shaking. Only alognment of pcal will take place.
FAC - Issues with RO water ongoing. Installation of aluminum strips wil begin today
Jim batch announced an upcomin computer upgrade for FOM monitors. MAC mini will be replaced with Intel nook. (possibly video4)
Vern mentioned re-implementation of Betsy's LockLoss Pie chart to track destructive ground motion around the site.
Chris B, Jeff, Eric Starting at GPS = 1116915517, we turned on the HWINJ with gain=10 to run in the background indefinitely. The idea is to make the CW signal loud enough that CW can recover some of these signals with just a few days of data, but weak enough so that they don't disturb the strain spectrum significantly. If these jobs are found to cause a problem with anything, simply disable the injections with the off switch in the cal model. NOTE: the overall injection gain is now set to 10, so any tinj injections should be scaled DOWN by 10x. Here are the CW signals that are currently active (frequency and amplitude shown below not including gain=10 factor): -bash-4.1$ grep Freq *cfg Pulsar0_StrainAmp.cfg:Freq = 265.5771052 ## GW frequency at tRef Pulsar1_StrainAmp.cfg:Freq = 849.0832962 ## GW frequency at tRef Pulsar2_StrainAmp.cfg:Freq = 575.163573 ## GW frequency at tRef Pulsar3_StrainAmp.cfg:Freq = 108.8571594 ## GW frequency at tRef Pulsar4_StrainAmp.cfg:Freq = 1403.163331 ## GW frequency at tRef Pulsar5_StrainAmp.cfg:Freq = 52.80832436 ## GW frequency at tRef Pulsar6_StrainAmp.cfg:Freq = 148.7190257 ## GW frequency at tRef Pulsar7_StrainAmp.cfg:Freq = 1220.979581 ## GW frequency at tRef Pulsar8_StrainAmp.cfg:Freq = 194.3083185 ## GW frequency at tRef Pulsar9_StrainAmp.cfg:Freq = 763.8473165 ## GW frequency at tRef Pulsar10_StrainAmp.cfg:Freq = 26.3589129 ## GW frequency at tRef Pulsar11_StrainAmp.cfg:Freq = 31.4248598 ## GW frequency at tRef Pulsar12_StrainAmp.cfg:Freq = 39.7276097 ## GW frequency at tRef -bash-4.1$ grep aPlus *cfg Pulsar0_StrainAmp.cfg:aPlus = 2.0125e-25 ## plus-polarization signal amplitude Pulsar1_StrainAmp.cfg:aPlus = 6.4405e-25 ## plus-polarization signal amplitude Pulsar2_StrainAmp.cfg:aPlus = 3.74175e-24 ## plus-polarization signal amplitude Pulsar3_StrainAmp.cfg:aPlus = 8.1915e-24 ## plus-polarization signal amplitude Pulsar4_StrainAmp.cfg:aPlus = 2.45645e-23 ## plus-polarization signal amplitude Pulsar5_StrainAmp.cfg:aPlus = 2.94475e-24 ## plus-polarization signal amplitude Pulsar6_StrainAmp.cfg:aPlus = 3.54275e-25 ## plus-polarization signal amplitude Pulsar7_StrainAmp.cfg:aPlus = 1.728625e-24 ## plus-polarization signal amplitude Pulsar8_StrainAmp.cfg:aPlus = 7.9815e-24 ## plus-polarization signal amplitude Pulsar9_StrainAmp.cfg:aPlus = 5.6235e-25 ## plus-polarization signal amplitude Pulsar10_StrainAmp.cfg:aPlus = 2.343323e-024 ## plus-polarization signal amplitude Pulsar11_StrainAmp.cfg:aPlus = 9.958896e-024 ## plus-polarization signal amplitude Pulsar12_StrainAmp.cfg:aPlus = 1.331275e-025 ## plus-polarization signal amplitude
One thing to watch out for is that for the sake of continuity with initial LIGO HW injections (cf. Emerson, consistency, hobgoblins), we use reference times going back to the start of S3, and some of the stars are spinning down pretty hard. The parameters for this set of injections, including the ER7 start and stop frequencies in the source rest frames can be found here. (Those frequencies can be further modulated by Doppler effects from the Earth's rotation and orbital motion, but for the duration of the ER7 run, those effects are no greater than 1/100,000.) In particular, the start-of-ER7 source-frame frequencies for the 13 pulsars are the following, where especially large spin-downs are noted: 0 - 265.575587774 Hz 1 - 848.973602759 Hz 2 - 575.163522907 Hz 3 - 108.857159395 Hz 4 - 1393.875953 Hz (vs 1403.163331 Hz in S3) 5 - 52.8083243585 Hz 6 - 146.258236176 Hz (vs 148.7190257 Hz in S3) 7 - 1220.57005882 Hz (vs 1220.979581 Hz in S3) 8 - 191.145490954 Hz (vs 194.3083185 Hz in S3) 9 - 763.847316495 Hz 10 - 26.3430397679 Hz 11 - 31.4247651214 Hz 12 - 38.5604676312 Hz (vs 39.7276097 in S3) I checked the 15 minutes or so of data from last night, preceding the Alaskan earthquake, where all pulsars were turned on. Not all of them were immediately visible, but attached are spectrograms for some that were obviously there (the NDS2 server is giving me trouble at the moment; I'll look for more signals later).
NDS2 is cooperating again. Here are spectrograms for additional visible CW injections in last night's pre-quake lock.
After a measurement of charge on each ETM yesterday, I took a few more on each today. Attached show the results trended with the measurements taken in April and Jan of this year. There appears to be more charge on the ETMs than in previous measurements, although there is quite a spread in the measurements. The ion pumps at the end stations are valved in.
Note, the measurement was saturating on ETMy so Kiwamu pointed me to switch the ETMy HI/LOW Voltage mode and BIO state. This made the measurement run with saturation. Attached is a snapshot of the settings I used for the ETMy charge measurement.
1. I think that the results of charge measurements of ETMY on May, 28 are probably mistaken. I haven't see any correlation in dependence of pitch and yaw from the DC bias. 2. It seems like there was very small response at ETMX LL quadrant at this charge measurements. Other ETMX quadrants are ok. It correlates with results of June, 10 https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=19049
Dan, Evan, Sheila
Tonight we started to look at the angle to length couplings of our test masses. We injected lines into pitch and yaw on the PUMs, and adjusted the A2L gains to minimize them. Using the math in the 40 meter alog and Jax's alog, we can estimate the miscentering from these measurements
| Gain P2L | vertical miscentering (mm) | Gain Y2L | horizontal miscentering (mm) | |
| ETMX | 1.6 | 21 | 1.1 | 14.4 |
| ETMY | 0.69 | 9 | -0.3 | -3.9 |
| ITMX | 2.4 | 31.5 | 1.15 | 15 |
| ITMY | 1.5 | 19.7 | N/A (-1.7 to -2) |
After we had adjusted these, we saw an improvement in the spectrum below 20 Hz. The line in the attached screen shot at 16.6 Hz with sidebands at half a hertz are the excitation. Keep in mind that this is on the new ESD driver and we haven't redone the calibration yet, but clearly this improved the noise below 20 Hz.
Earlier in the evening we were having difficuulty powering up because of a pitch instability at the main suspension resonant frequency that showed up in all the test masses. We moved the QPD offsets for pitch back to what they were may 15th, (they had been changed last tuesday). We then remeasured the miscentering for pitch only, things were a little bit better. Once we increased the power to 17 Watts, the IFO was stable and we repeated some of the measurements. We were able to power up to 23 Watts without seeing the instability twice, but lost the lock quickly for other reasons.
| Gain P2L | vertical miscentering (mm) | 17 Watts P2L | ||
| ETMX | 0.7 | 9.18 | 0.8 | |
| ETMY | -0.57 | -7.5 | -0.49 | |
| ITMX | 2.1 | 27.6 | 2.4 | |
| ITMY | 1.2 | 15.7 | NA |
DARM OLTF file attached. This template has reduced drive strength so that the ESD does not saturate in the LVLN state.
At last I was able to switch the DARM actuation over to ETMY at 25 W with the LPF engaged on the LVLN driver. We had discovered that the L1 LOCK filters on the ETMs were charging up because of small amounts of ringing in the lower stage filters. Therefore, the L1 filter for ETMX is zeroed after actuation is moved to ETMY, and the lock filters for ETMY are cleared after lockloss. Also, the INCREASE_POWER state now automatically increases the power to 25 W once again.
I tried the LOWNOISE_ESD_ETMY state at 25 W once, and it seemed to work. I then turned on some pieces of the LSC_FF state (namely the SRCL gain reduction, the SRCL cutoff, and the MICH FF). I am leaving the IFO locked with the intent bit undisturbed.
One last note: the power was 3 Watts in the spectrum attached, and to repeat, the calibration is not updated since the actuator change. They're working on it
The displacements in mm are wrong here, we were measureing from the PUM.
Another DARM OLTF, this time with the ETMY LPF off.
There are two DARM Open Loop Gain TFs attached as comments to this entry that represent the first two DARM OLGTFs taken with the new low noise ESD driver and the new L1L2L3 hierarchical control scheme. I've downloaded them and submitted them to the CalSVN for use later: - From LHO aLOG 18662, DcDarmLVLN.xml, measured starting 2015-05-28 13:17:00 UTC, has been copied to /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs/2015-05-28_H1_DARM_OLGTF_LHOaLOG18662_ETMYL3LPON.xml - From LHO aLOG 18709, DcDarmLVLN.xml, measured starting 2015-05-30 03:07:00 UTC, has been copied to /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs/2015-05-30_H1_DARM_OLGTF_LHOaLOG18709_ETMYL3LPOFF.xml. I attach conlogs of all relevant DARM filter banks and BIO switches, where the date in the file name corresponds to each measurement.
