Attached is a plot summarising the behaviour of the front end laser pump diodes. The oscillation in the output power has been observed before and I'm not sure what it is caused by. I had thought that it might be due to an oscillation in the PID loop controlling the pump diode temperature, however it's not visible in the TEC signals (D[1-4]TEC). We still have a reasonable amount of headroom for the pump diodes. At the moment the diode current is ~51.5 A. The maximum is 65 A.
O1 days 83-87. No restarts reported for this time period.
Planning for Tuesday Maintenance:
Activity Log: All Times in UTC (PT) 08:00 (00:00) Take over from Corey 08:46 (00:46) Reset L4C WD saturations on HAM3, ITMX, and the BS 16:00 (08:00) Turn over to TJ End of Shift Summary: Title: 12/14/2015, Owl Shift 08:00 – 16:00 (00:00 – 08:00) All times in UTC (PT) Support: Incoming Operator: TJ Shift Detail Summary: Locked in Observing mode for entire shift. Power at 21.8w, range 79Mpc. Wind is light breeze (4-7mph), seismic and microseism are improving. There is an oscillation showing up in the 20 minute ASAIR_B_RF90_I_NORM, and SUS-PRM_MC3_LOCK signals. There are also oscillations showing up in the Pitch and Yaw ASC Control strip tools.
TITLE: 12/14 Day Shift: 16:00-00:00UTC (08:00-16:00 PDT), all times posted in UTC"
STATE Of H1: Observing at 80Mpc for 12.5hrs
OUTGOING OPERATOR: Jeff b
QUICK SUMMARY: Wind 10mph max, useism 0.6um/s, CW inj running, lights off, PSL 21.8W.
In general a good first half of the shift. In Observing mode for past 8 hours, with a couple of exceptions as noted during the Evening shift. The IFO appears to be functioning normally. Environmental conditions are good or improving except microseism, which remains elevated and shows signs of a decline.
08:46 (00:46) Reset L4C WD saturations on HAM3, ITMX, and the BS.
Are you able to do this while in Observation Mode?
Title: 12/14/2015, Owl Shift 08:00 – 16:00 (00:00 – 08:00) All times in UTC (PT) State of H1: 08:00 (00:00), The IFO is in Observation mode. Power at 21.8W, range 78Mpc Outgoing Operator: Corey Quick Summary: IFO has been in observation mode for the past 5 hours, except as noted by the Evening shift. Wind is a light breeze (4 - 7mph). Seismic and microseism are still a bit elevated, but improving. All appears to be normal.
TITLE: 12/13 EVE Shift: 00:00-08:00UTC (16:00-00:00PDT), all times posted in UTC
STATE of H1: 4+ Hrs of locking (Almost 3hrs in Observing) at around 80Mpc.
Incoming Operator: Jeff B.
Support: Sheila On Phone at beginning of shift
Quick Summary:
Shift Log:
We shook the PSL table and all chambers at the corner station except ITMY individually. By far the greatest up-conversion was at the BS. The figure shows that even a 20% increase in 1-80 Hz GS13 BLRMS produces bumps at higher frequencies. The up-conversion from injected peaks is not broadband like magnet domain changing noise, and is not a harmonic series like from scattering or saturation, but, instead produces peaks that look like intermodulation products.
Robert, Jordan
After the Initial Alignment, it took about 60-90min of attempts with H1 falling out at various points (as noted in newsreel posts earlier). Finally made it on this current attempt. No real issues, other than needing to engage the ISS 2nd ISS Loop by hand (per Kiwamu's alog 22449). So, the latter causes the range to look low (~30Mpc a few minutes) while engaging 2nd Loop. I actually took a little time here to read the alog, and put the output channel on a striptool, so I would have a better idea of when to turn ON the 2nd Loop.
range is has been hovering at a shy 80Mpc. NO SDF diffs
Observatory Mode is now: COMMISSIONING (this is due to Robert beginning chamber-shaking injections; he said on the order of ~1hr.)
Off to make supper.
Making notes from Initial Alignement work, locking and chatting with Sheila:
Initial Alignment:
Locking
DRMI locking: POP18 & 90 looked good with flashes flashing up to 150-200 on dataviewer, BUT the AS camera would have some ugly modes every min or so. Have had a DRMI lock...but only for a about 20sec and then 18 & 90 dropped. Might look at PRMI....oh wait, DRMI LOCKED....Stay tuned!
Comepleted CARM_5PM, dropped while in RESONANCE Guaridan state:
2015-12-14T02:22:27.22172 ISC_LOCK executing state: REFL_TRANS (409)
2015-12-14T02:22:27.22198 ISC_LOCK [REFL_TRANS.enter]
2015-12-14T02:22:27.48413 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-REFLBIAS => ON: FM2
2015-12-14T02:22:27.52074 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-TR_REFLAIR9_TRAMP => 0
2015-12-14T02:22:33.39102 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-TR_REFLAIR9_OFFSET => -0.112938329577
2015-12-14T02:22:33.78661 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-TR_REFLAIR9 => ON: FM1, FM2, FM5, OFFSET
2015-12-14T02:22:33.79052 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-PD_DOF_MTRX_SETTING_9_27 => 3.0
2015-12-14T02:22:33.79147 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-PD_DOF_MTRX_SETTING_9_26 => 0.0
2015-12-14T02:22:33.79198 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-TR_REFLAIR9_TRAMP => 2
2015-12-14T02:22:33.79250 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-PD_DOF_MTRX_TRAMP => 0.2
2015-12-14T02:22:33.79846 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-PD_DOF_MTRX_LOAD_MATRIX => 1
2015-12-14T02:22:33.80202 ISC_LOCK [REFL_TRANS.main] ezca: H1:LSC-ARM_INPUT_MTRX_LOAD_MATRIX => 1
2015-12-14T02:22:33.88079 ISC_LOCK [REFL_TRANS.run] USERMSG: Input matrix not ready.
2015-12-14T02:22:33.88557 ISC_LOCK [REFL_TRANS.run] ezca: H1:LSC-PD_DOF_MTRX_LOAD_MATRIX => 1.0
2015-12-14T02:22:33.89565 ISC_LOCK [REFL_TRANS.run] ezca: H1:LSC-ARM_INPUT_MTRX_LOAD_MATRIX => 1.0
2015-12-14T02:22:35.14264 ISC_LOCK [REFL_TRANS.run] MC not locked
2015-12-14T02:22:35.19776 ISC_LOCK state returned jump target: LOCKLOSS
2015-12-14T02:22:35.19798 ISC_LOCK [REFL_TRANS.exit]
Contacted LLO, and sounds like they are possibly just past the peak of noisy storm activity....and the forecast may lead to them being back online sooner (few hours) rather than later (tomorrow). Robert's determining a game plan for his injections.
I did try an attempt with ETMX with 45mHz on x & ETMy with 45mHz on y for the Blends, but no change. So I went back to having both x & y axis 45mHz blends for both etms.
TITLE: 12/13 EVE Shift: 00:00-08:00UTC (16:00-00:00PDT), all times posted in UTC
STATE of H1: DOWN
Outgoing Operator: TJ
Quick Summary:
After getting hand-off from TJ, will take another look at Input Alignment (will watch x-arm power on DV & also the AS camera to look for obvious misalignment...if needed, will tweak PR2. Will also increase XARM digital gain to see if this helps as well [these were suggestions Sheila gave me over the phone]). If this does not work, I might look at Input Pointing over the last few weeks/months to see what our current state looks like compared to the past.
Conditions look decent (no winds, under 10mph), but useism is still roaring (LVEA is hovering around 1um/s).
Currently, all ISIs have their 45mHz Blend Filters ON. When we are dealing with noisy useism, Jim mentioned we should keep the 90mHz Blends on for the ETM off-axis Blends (i.e. ETMx ISI has 45mHz for X-axis & 90mHz for Y-axis, and similarly for ETMy ISI). But since we are dealing with pretty noisy conditions, Sheila thought we should run with all 45mHz on. She checked the recent locklosses from home to confirm we weren't ringing up the ISIs due to doing this---> and we weren't, so she suggested we continue to stay with all the Blends ON.
OK, onto Initial Alignment!
Really similar to alog24151 from yesterday. Saw the oscillation buid up and had no idea how to stop it.
We've left the ETMX ISI on 45 mHz blends in both X and Y on ST1, so I was worried that these locklosses could be reappearance of the problem described in 23674 . At least this one seems to be a different problem, this is a pitch oscialtion at around 0.4 Hz that shows up in all test mass oplevs, and seems to be in common soft if all the signs on these oplevs are right. It rings up over the last 2 minutes of the lock or so. It doesn't show up in any of the arm ASC control signals. It does show up in SRC1 (AS36I->SRM)
I have edited the ISC_LOCK guardian so that it now turns violin mode damping off before the interferometer reaches nominal low noise. This will hopefully allow us to collect ringdown data on the violin mode fundamentals.
Violin mode damping is still turned on as usual in BOUNCE_VIOLIN_MODE_DAMPING, but it now is turned off in the COIL_DRIVERS state. Thus the modes will still receive a few minutes of damping before DARM is switched to dc readout.
If this behavior needs to be reverted, there is a flag in the main() function of COIL_DRIVERS called self.turnOffViolinDamping which can be set to False.
Violin mode damping in full lock will be re-enabled once sufficient data have been collected.
Are there any observable results from this? For example, does this mean we will now see these on the running power spectrum on nuc3? And is this the reason we now have the red boxes on the violin mode medm on nuc0? I hadn't noticed the latter before, so I was wondering why these were flashing red.
Since turning the damping off, the violin mode fundamentals seem to appear on the DARM FOM at the level of 10−16 m/Hz1/2 or so. Before turning the damping off, they would eventually damp down below 10−18 m/Hz1/2 after a few hours.
I'm guessing this is why the violin mode monitors are red, but I don't know what Nutsinee set the monitor thresholds to.
Also, since writing the above alog I changed the Guardian code for turning off the damping. It is no longer executed inside an if statement; it's just executed directly in the main() function of COIL_DRIVERS.