Not much to pass along here. Current lock is 5+hrs. The range has been showing a slight trend downward as of late (i.e. from 80.5 down to 77.5Mpc). Not seeing a reason for the drop (LSC POP A looks flat, and useism looks like it's actually dropping).
What a difference a lock makes.
After 54min, H1 dropped out of lock this morning. That lock had the TIdal DIAG_MAIN error messages noted earlier (but Tidal looked fine according to Hugh, whom I had on the phone). The one issue noted was H1:IMC-F_OUT16 diverging.
Since there were no obvious environmental/seismic reasons for the lockloss, I am blaming the IMC drift here. And with that, I am submitting my very first FRS Report (FRS#4199) with 0.8hrs Observation Time Lost.
NOTE: Terramon forecasts a 4.9 EQ from Turkey arriving here in about 20min (18:28UTC/10:28amPST), with motion of a YELLOW 0.15um/s....we'll see how we ride through it.
O1 days 111-114
model restarts logged for Sat 09/Jan/2016
No restarts reported
model restarts logged for Fri 08/Jan/2016
2016_01_08 08:29 h1nds0
Unexpected crash of h1nds0, required a restart
model restarts logged for Thu 07/Jan/2016
2016_01_07 14:40 h1nds0
Unexpected restart of h1nds0
model restarts logged for Wed 06/Jan/2016
No restarts reported
During the last lock segment, we had the Tidal Error messages (X& Y COMM CTRL within 10% of limit). Additionally, noticed on the Striptool on nuc1 that IMC-F_OUT16 was diverging & drifting off-screen (see attached). Ultimately there was a lockloss (could it be related?).
Talked to Hugh while we were locked, and he pointed me to the End Station HEPIs & also to the ISC signals they get. He mentioned they have a limit of 700,000counts. ETMy was moving below -36,000 (this was OK). EX was flatlined at 14,660 (this was ODD). But since both of these were well away from 700,000, we ruled out this being a tidal issue and figured it was something upstream (ISC? PSL?). We'll see how the next lock looks.
The attachment shows how the integrated ALS offsets remain as error point offsets for the IMC-F → UIM offloading.
We should bleed these ALS offsets away once we have transitioned off ALS, and preferrably before increasing the laser power (as this will load CARM by a few microns).
I thought that with EX tidal flatlined, the IMC frequency changes to try and keep H1 locked, but then runs out of range causing lock loss?
Wouldn't that mean the EX flatlined is the issue, IMC_F is just responding?
It seems that during this lock acquisition, there were large offsets remaining on the ALS → UIM offloading filter modules, and correspondingly large offsets on the IMC-F → UIM offloading filter modules (which are used during full lock).
The IMC-F → UIM offloading hit the limit around 15:50:00 Z, causing the tidal offloading to halt. As Cheryl said, this means IMC-F starts accumulating a dc offset to keep the laser on resonance.
TITLE: 01/10 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC STATE Of H1: Observing (at the last minute) SHIFT SUMMARY: Changed end X PCAL freq. Lost lock coincident with jump in earthquake band. Ran an initial alignment after seeing no flashes in DRMI. All the digital cameras froze for ~ 5 min. Had issues with OMC SUS (see previous alog). Engaged ISS second loop by hand. Getting diagnostic messages for X and Y tidal limits (see attached). A trend of the TIDAL_CTRL channels for the last 30 days does not show anything unusual (see attached). INCOMING OPERATOR: Corey ACTIVITY LOG: 14:41 UTC diode room dust monitor invalid 14:43 UTC all digital cameras frozen for ~ 5 min 15:55 UTC back to observing
TITLE: 1/10 DAY Shift: 16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC
STATE of H1: Recently taken to OBSERVING by Patrick
Outgoing Operator: Patrick
Quick Summary:
Foggy morning on the site. Patrick restored H1 to Observing after the EQ (from 5.0 Antartica?). No winds and high useism (LVEA ~0.5um/s.
Have X & Y COMM CTRL within 10% of limit messages on DIAG_MAIN.
I'm stuck at DC readout transition with a message saying the OMC is not ready. I have tried rerequesting the OMC guardian state and changing the starting PZT voltage in omcparams.py. Something strange is going on. The SUS OMC WD is tripping and untripping itself. On the OMC SUS overview screen the IOP DACKILL is oscillating between red and green, but the numbers continue to go to the DAC regardless. LF and RT are stuck railed at -131060. ... Now it has stopped and LF and RT are no longer railed.
After rerequesting it one more time it worked. Moving on.
Coincident with jump in earthquake band (see attached). USGS: 2.8 37km SW of Ferndale, California 2016-01-10 13:05:09 UTC 20.4 km deep
Not sure if this is the correct earthquake. Corey says there may be a larger one in Antarctica scheduled to arrive around this time: 5.0 Pacific-Antarctic Ridge 2016-01-10 12:12:03 UTC 10.0 km deep
Have remained locked. Took out of observing briefly to change the end X PCAL frequency. H1:LSC-POP_A_LF_OUTPUT has been slowly falling and is now around 15,750. There is a slight indication that it may be leveling out (see attached), so I'll give it some more time to see.
Per Rick's request I changed the end X PCAL frequency from 3501.3 to 4501.3. I also changed the sine amplitude from 35,000 to 40,000. I went out of observing from 12:00:23 - 12:11:29 UTC to do this. I accepted the SDF differences from doing this (see attached). Per Rick's schedule this should be left to run for 12 hours.
Ops Eve Summary: 00:00-08:00UTC, 16:00-23:59PT
State of H1: Observe, range around 79Mpc, POP_A_LF at 16000
Incoming Operator: Patrick
Shift Summary: Calibrations continue, and H1 was saved from a lock loss when POP_A_LF dropped to 14800, by adjusting the alignment of TMSY
Shift Details:
H1 in Observe when I took over
02:33:40UTC - H1 out of Observe for adjustments to TMSY alignment, POP_A_LF at 14800, see alog 24818
03:14:46UTC - H1 back to Observe, POP_A_LF at 16100
04:32:32UTC - H1 out of Observe to change the frequency of the PCAL line, see alog 24819
04:33:26UTC - H1 back in Observe
TITLE: 01/10 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC STATE Of H1: Observing @ ~ 79 MPc. OUTGOING OPERATOR: Cheryl QUICK SUMMARY: From the cameras: The lights are off in the LVEA, PSL enclosure and end Y. I can not tell if the lights are on or off at mid X, mid Y or end X. Winds are less than 10 mph. From pinging: CDS WAP is off at the LVEA, end X and end Y. CDS WAP is on at mid X and mid Y. Screenshots of the seismic bands and ISI blends are attached.
PCALX line moved from 3001.3 to 3501.3Hz at 04:32:32UTC (intention bit commissioning).
H1 back in Observe at 04:33:26UTC.
Screenshot of SDF attached.
This cal line frequency, 3501.3Hz, should run for 6 hours.
When this run is complete, the cal line should be changed to 4501.3Hz and then requires 12 hours of data.
See JeefK's alog for details: alog 24802
Summary:
TMSY pitch and yaw alignment tweaked to increase POP_A_LF, saving the lock.
Details:
After JeffK and I saw that POP_A_LF was dropping, I looked at the H1 alignment over the 27 hour lock, and focused of PR3, ETMX, and TMSX.
After looking at the trends, I proposed the idea to JeffK that we might be able to save the lock by aligning TMS, and he suggested TMSY, based on previous work by Kiwamu.
When I compared TMSX and TMSY alignments over the 27 hour lock, I found that TMSY alignment changed by -1urad in pitch and +0.5urad in yaw, when measured from the start of the decrease in POP_A_LF.
To compare, TMSX alignment changed 0.02urad in pitch and 0.05urad in yaw.
I started by raising POP_A_LF with TMSY yaw, and stepped the alignment slider by 0.05 at first and then increased that step size to 0.2, with a ramp time of 20 seconds, and made a step about every 4 minutes, which gave the ASC time to recover.
After some improvement in POP_A_LF, I switched to aligning TMSY pitch.
When I was done, POP_A_LF had increased from 14850 to 16100.
Plots attached:
Time history of this lock:
- Cheryl, JeffK, Kiwamu
ASC during the drop and recovery of POP_A_LF
plot 1 - MICH P and Y and POP_A_LF - MICH noise and a glitch in POP_A_LF, just right of center in the plot, starts the POP dive
plot 2 - PRC is unperterbed by all events
plot 3 - SRC moves away from zero as POP_A_LF drops
PRM, PR3, BS, ITMs, ETMs, and TMSs during the POP drop and recovery
PCALX line moved from 1001.3 to 3001.3Hz at 23:59:53UTC (intention bit commissioning).
H1 back in Observe at 00:02:15UTC.
Screenshot of SDF attached.
This means that the 1001.3 [Hz] line was on from 22:38:27 UTC to 23:59:53 UTC. No appreciable RF45 noise during this data stretch. I attach the usual screenshot demonstrating the amplitude and absense of any other features around the 3001.3 [Hz] line. We'll leave the 3 [kHz] line on for about 4 hours, as per Rick's schedule. Also for future reference, I've checked 3.5 and 4.5 [kHz], and they're also featureless, so no need to worry about injecting their later (see second and third attachment). The next scheduled change (if the IFO is kind enough to stay locked) is at ~8:30 PDT (~4:30 UTC), and I've instructed Cheryl to make the change.
This configuration, cal ine at 3501.3Hz, should run for 6 hours.
After the data at this frquency is collected, the last configuration is the cal line at 4501.3 Hz, which needs to run for 12 hours.
