Since LLO had already gone down (we think for maintence) TJ let me start some maintence work that needs the full IFO locked. at about 14:32 UTC Sept 29th we went to commisioning to start running the A2L script as described in WP # 5517.
This is a reminder that this lock has been out of the nominal calibrated configuration since the RF45 SET is at 22.2dB instead of the nominal 23.2dB. See alog22045 for times and reason for change.
Locked for my whole shift, not even a saturation. Nothing to report.
Title: 9/29 OWL Shift: 7:00-15:00UTC (00:00-8:00PDT), all times posted in UTC
State of H1: Observation Mode at ~72Mpc for the last 1hrs
Outgoing Operator: Travis S.
Quick Summary: He had a normal first 6 hours of his shift, then lost lock but brought it right back for me.
Title: 9/28 Eve Shift 23:00-7:00 UTC (16:00-24:00 PST). All times in UTC.
State of H1: Observing
Shift Summary: One lockloss due to ITMx saturation. After an initial alignment due to poor ALS alignment, locked up without issue.
Incoming operator: TJ
Activity log:
5:06 Lockloss. ITMx saturation.
5:20 Begin initial alignment.
6:02 Briefly went to Observing before seeing RF45 needed some tweaking.
6:07 Locked in Observing Mode.
Back to Observing Mode @ 6:07 UTC after an initial alignment. I briefly went to Observing @ 6:02 UTC, but noticed that the RF45 was running away again. Went out of Observing and adjusted RF45 back to 22.2dB (from 23.2dB that was reset sometime during lockloss and alignment).
Full report can be found here. Some highlights:
(sorry I forgot to post to alog earlier)
Lockloss @ 5:06 UTC. No obvious cause as seismic and wind are calm. Coincided with ITMx saturation.
Nothing of note here. H1 is in Observing and running smooth and steady for 7 hours now. 4 ETMy saturation alarms since the start of the shift. RF45 is looking good.
In case it is ever of use, I asked Christina and Terry G. to try and log the arrival and departure times of delivery vehicles for two weeks. UPS and FedEx do daily deliveries: various other vendors deliver occasionally. If necessary, we can make inquiries as to Gross Vehicle Weight etc.
Attached is a snapshot illustrating which observe mode segment had the ASC DHARD Yaw FM2 filter engaged. Recall that the filter was engaged a few times over the last week in an attempt to ride out a species of ground motion. In all but one of the cases when this FM2 filter was engaged, the IFO Observation Intent bit was NOT set. The following is the one segment when the filter was engaged:
H1 Single IFO Segment #30 from https://ldas-jobs.ligo.caltech.edu/~detchar/summary/O1/
(Segment lists are shown via the blue pop-open banners across the bottom of the page - see specifically H1:DMT-ANALYSIS_READY:1)
30 1127313107 1127329701 16594
Laura Nuttall, Marissa
I've repeated what Laura did in alog 21820 for this time, to compare the glitch rate between times that did and did not have the DHARD Y boost and determine whether this should have much of an impact on the transient searches' backgrounds. Unfortunately, this lock segment had some really bad RF45 noise so it's not ideal for evaluating glitch rates (since a lot of this time will be cut out from the search backgrounds), but it's what we have...
I've attached the omicron glitchgrams and trigger rates for the time that the filter was turned on, and for the same amount of time just after it was turned off. The overall rate of low SNR triggers is about the same during both segments, with some times of increased rate of higher SNR triggers while the filter was engaged, most likely due to the RF45 noise. Similarly, the glitchgrams' structures do not appear significantly different between the two segments, besides the awful RF45 times.
From this comparison, I would agree with Laura's earlier conclusion that this filter does not appear to have a significant effect on the background.
TITLE: 09/28 [DAY Shift]: 15:00-23:00 UTC (08:00-16:00 PDT), all times posted in UTC
STATE Of H1: Observing at ~70 Mpc.
SUPPORT: Peter, Mike, Laura
QUICK SUMMARY: Reducing RF45 modulation index definitely helps with the glitch rate. Lockloss twice within the shift due to an earthquake and PSL tripped. Had no problem relocking. Wind speed ~10mph tilts the ground and increase the seismic activity in the earthquake band (0.03-0.1Hz) to 0.05 um/s.
INCOMING OPERATOR: Travis
ACTIVITY LOG:
Morning Meeting:
- We have had good weekend locking, but not a good running. Driver swap tomorrow.
15:51 Lockloss due to an earthquake. Adjusted PR3 to maximize COMM beatnote. Touched BS to get DRMI locked at the right mode.
16:27 Back to Observing.
17:37 RF45 was acting up. Dropped the intent bit to reduce RF45 mod index. Kept the configuration as Laura suggested and continued to Observe.
18:12 Lockloss due to PSL tripped. Peter turning the laser back on.
Praxxair on site. Going to Mid Y. Intent bit dropped.
18:20 Peter back
18:46 Locked again at NOMINAL_LOW_NOISE but not Observing. Waiting for Praxxair to leave site.
19:49 Praxxair hasn't moved for a really long time. I switched the bit to Observing.
19:51 Out of Observing. Praxxair leaving site.
19:56 Back to Observing.
Parameters for report:
GPS Start Time = 1127423695 # Beginning of time span, in GPS seconds, to search for injections
GPS End Time = 1127510095 # Ending of time span, in GPS seconds, to search for injections
Check Hanford IFO = True # Check for injections in the Hanford IFO frame files.
Check Livingston IFO = True # Check for injections in the Livingston IFO frame files.
IFO Coinc Time = 0.01 # Time window, in seconds, for coincidence between IFO injection events.
Check ODC_HOFT = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in HOFT frames.
Check ODC_RAW = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RAW frames.
Check ODC_RDS = True # Check ODC-MASTER_CHANNEL_OUT_DQ channel in RDS frames.
Check GDS_HOFT = True # Check GDS-CALIB_STATE_VECTOR channel in HOFT frames.
Report Normal = True # Include normal (IFO-coincident, consistent, and scheduled for network injections and consistent and scheduled for IFO injections) injections in report
Report Anomalous = True # Include anomalous (non-IFO-coincident, inconsistent, or unscheduled) injections in report
----
No scheduled injections or non-occurring injections were found.
There was a CAL_INJ reset that occurred only in H1, CALRESET 1127480460.000 (H1). However, it has the anomaly that it appears in ODC HOFT and GDS HOFT frames but not in ODC RAW or ODC RDS frames. This same anomaly was observed with several CBC injections in L1 during the daily period 1127163296 - 1127249696.
The anomalies reported here are likely due to the same bug that caused the anomalies as reported in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=21971.
B. Weaver, J. Oberling
After this morning's PSL trip there was a 0.5W increase in IMC-PWR_IN, observed ~15 minutes after reaching NOMINAL_LOW_NOISE. We started digging in the Guardian code and rediscoverd that the ISS diffracted power gets adjusted by a software PID loop located in the IMC_LOCK guardian; this adjustment is done via changing the ISS 2nd loop reference signal. At the start of a lock stretch this PID loop is necessary to keep the ISS diffracted power around the predetermined nominal value of 8%. However today we witnessed that when the diffracted power trended towards the upper threshold (set in the IMC_LOCK guardian code) of 10%, the IMC_LOCK turned on the PID loop, thus increasing the measured IMC-PWR_IN by ~0.5W.
Looking back 16 days we discovered 2 more cases of the IMC_LOCK guardian turning on the ISS PID loop during a NOMINAL_LOW_NOISE (and observing) lock stretch. Attached is the 16 day trend and the 2 examples. The 2nd example was 30 hours into last week's 46 hour lock stretch. Also note, in the 16 day trend, the continued power discrepancy from lock to lock.
Looking at the 16 day trend, by eye it seems the ISS diffracted power is hugging the upper threshold of 10% more often then not, hovering around 9%. This might be normal acceptable behavior, however we were surprised to see that a PID loop was increasing power in the middle of an observing lock. Will follow up with commissioners.
What do the in- and out-of-loop signals for the outer loop look like during these events? (I.e., SUM14 and SUM58.)
B. Weaver, J. Kissel, Not sure what Evan wants with the "SUM14" and "SUM58" channels, so I found what channels are stored in the frames for the ISS, and used my vague knowledge of how the ISS SECOND LOOP works, and chose H1:PSL-ISS_SECONDLOOP_SUM14_REL_OUT_DQ H1:PSL-ISS_SECONDLOOP_SUM58_REL_OUT_DQ and reproduced Betsy's plots with trends of those channels in addition to the original channels. I'll leave it to Evan to interpret the results, 'cause we don't know how. Let us know if you need anything different, Evan (or on a different scale, or whatever).
Fil came to let me know that the alarm at Hanford site is going off. They called earlier that there will be an alert system testing between 12:30-13:30.
I switched to Observing a bit at 19:49 after Praxxair hadn't moved for a really long time. I went back to comissioning then the truck took off from Mid Y at 19:51. And back to Observing when it went back to Rt. 10.
The PSL AOM diffracted power was dropping but now stable within desired range (8%). Peter went to turn on the laser Watchdog.
The script finished right before an EQ knocked us out of lock. Attached are results, we can decide if we are keeping these decouplings durring the maintence window.
The three changes made by the script which I would like to keep are ETMX pit, ETMY yaw, and ITMY pit. These three gains are accepted in SDF. Since we aren't going to do the other work described in the WP, this is now finished.
All the results from the script are:
ETMX pit changed from 1.263 to 1.069 (1st attachment, keep)
ETMX yaw reverted (script changed it from 0.749 to 1.1723 based on the fit shown in the second attachment)
ETMY pit reverted (script changed it from 0.26 to 0.14 based on the 3rd attachement)
ETMY yaw changed from -0.42 to -0.509, based on fit shown in 4th attachment
ITMX no changes were made by the script, 5th +6th attchments
ITMY pit (from 1.37 to 1.13 based on 7th attachment, keep)
ITMY yaw reverted (changed from -2.174 to -1.7, based on the 8th attachment which does not seem like a good fit)
By the way, the script that I ran to find the decoupling gains is in userapps/isc/common/decoup/run_a2l_vII.sh Perhaps next time we use this we should try a higher drive amplitude, to try to get better fits.
I ran Hang's script that uses the A2L gains to determine a spot position (alog 19904), here are the values after running the script today.
I also re-ran this script for the old gains,
vertical(mm)
So the changes amount to +0.4 mm in the horizontal direction on ETMY, -0.9 mm in the vertical direction on ETMX, and -1.1mm in the vertical direction on ITMY.
Please be aware that in my code estimating beam's position, I neglected the L2 angle -> L3 length coupling, which would induce
an error of l_ex / theta_L3,
where l_ex is the length induced by L2a->L3l coupling when we dither L2, and theta_L3 is the angle L3 tilts through L2a->L3a.
Sorry about that...