06:30 Cris into LVEA
08:00 LVEA is LASER HAZARD
08:00 OIB set to "Commissioning"
08:01 restarted Alarm Handlers
08:02 Restarted DTT session on projector 1
08:03 Restarted "hung-up" Operator2 workstation
08:25 port-o-potties on site for exchange
08:30 Corey out to LVEA
08:35 ISS diffracted power adjusted to ~7.6%
08:39 Aaron to EY for PEM work
08:40 HEPI HAM4 L4C watchdog accumulator reset - sat count 380
08:43 Keita and Daniel to EX
09:00 I'm running PSL DBB reports
09:06 Cris to EX
09:19 Travis into LVEA
09:25 Hugh to mazzanine to put HEPI pumpd in manual control. He'll be staying there and adjustin them manually
09:31 Karen into LVEA
09:45 Kyle into LVEA
09:52 Tour group into control room
10:37 Cris back
10:55 Karen to EX
11:04 Dave restarted FSS, ISS and PMC models to accomodate change in acq rate.
11:04 Dave restarted DAQ
11:13 Water delivery
11:34 Sudarshan into LVEA
12:02 Karen leaving EY
12:06 Corey out of LVEA
12:11 Sigg and company back from EX
15:20 Gerardo into H2 LASER enclosure
Hanford hauling indicates that they will not be running trucks on day shift or swing shift on Weds, Thurs or Fri of this week, nor over the weekend.
The button is intermittent because h1lsc is running at RCG2.8.3. The fix for this will be implemented when we upgrade to RCG2.9. In the meantime scripts should check if the button press was accepted, and try again if not.
Sudarsan, Peter, Dave: PSL model changes
The h1psliss, h1pslfss and h1pslpmc models were modified to downsample all 32kHz channels to 16kHz. This resulted in 10 32kHz channels changing to 16kHz with the distribution: ISS=1, FSS=4, PMC=5. The models were restarted and the DAQ was restarted. This resulted in a science frame size reduction of about 20MB per 64 second science frame (2%). The restarted models were burt restored to 9am PST today.
Dave: DMT broadcaster
Following last week's ISS model change, the H1BROADCAST0.ini file was changed to replace the obsolete H1:PSL-ISS_PD[A,B]_OUT_DQ with the calibrated H1:PSL-ISS_PD[A,B]_REL_OUT_DQ. Also the obsolete H1:LSC-OMC_DC_OUT_DQ was removed from the DMT.
Hugh, Dave: HEPI pump controller channels
Following Hugh's software change on the corner station HEPI pump controller EPICS system, a new EDCU INI file was added to the DAQ. Hugh has updated the MEDM screens and is updating the autoBurt.req file.
Dave: Restart of H1SLOW-F1FE EPICS gateway
Following the restart of h1ecatx1 this morning, subsequent restarts of the DAQ EDCU did not establish new connections to this IOC. I restarted the EPICS gateway between the EDCU and the Beckhoff IOCs which prompted the EDCU to re-establish a connection. It took several minutes for the reconnection to complete. Initially the number of disconnected channels went from 1,951 to 81, then took a further minute to reduce to zero.
Dave: DAQ restarts
To support the above work the DAQ was restarted three times this morning. On restart 1 and 3 the data concentrator was very slow on restarting (several minutes) while restart 2 proceded at the usual pace. While waiting for the slow restarts I had time to check for duplicate channels (none) and any errors in log files (none).
Jim, Dave: replace broken thunderbolt monitor at operator station
I collected the repaired Apple thunderbolt monitor from Alpha Computers this morning, Jim installed it at the operator station. We are looking into a tether cable solution for strain relief.
Daniel, Keita, Elli
This morning we worked on the ALS at Ex:
-We added autoalignment PZTs to the green WFS path. Mirrors ALS-M16 and ALS-M19 were taken out and and relaced with PZT mirrors. After adding the PZTs we realigned the green beam back onto the WFS.
-We removed two mirrors blocking the beam path upstream of ALS-M19. The mirrors weren't on the table layout and didn't appear to be doing anything.
-Swapped feedthorugh panels D1100434 on ISCTEX with replacement panels. The original panels had the wrong size screw spacing.
[Stuart A, Arnaud P] Damped TFs had been taken on MC2 back in August (see LHO aLOG entry 13346), but had not been processed until now:- - MC2 M1-M1 undamped TFs (2014-08-11_1091848686_H1SUSMC2_M1_damp_ON_ALL_TFs.pdf) Before the corner vent, MC2 had been exhibiting 1 Hz Pitch and 1.5 Hz Roll modes cross-coupling into the Vertical DOF, which had been exacerbated when the chamber had been pumped down to vacuum (see LHO aLOG entry 11383). This was suspected due to EQ stops being set too close and rubbing, which is captured in an Integration Issue #847. After the most recent July corner station chamber incursion, transfer functions taken at Phase 3a (in-air) for MC2 showed no cross-couplings into the Vertical DOF (see LHO aLOG entry 13036). Having now pumped down, the damped Phase 3b (in-vacuum) MC2 M1-M1 TFs presented above, are clear of cross-couplings into the Vertical DOF. Below is a comparison of undamped Phase 3 MC2 TFs (see allhstss_2014-11-24_Phase3_H1MC2_M1_Doff_ALL_ZOOMED_TFs.pdf), the plot keys are as follows:- Blue Trace = Model (hstsopt_metal) Orange Trace = H1 MC2 M1 (2013−05−25_1053525085), Phase 3b Magenta Trace = H1 MC2 M1 (2014−07−28_1090619695), Phase 3a The original MC2 cross-couplings into Vertical DOF were present in Phase 3a and then exacerbated going to Phase 3b. However, the recent in-air measurements show absolutely no seeds of a cross-coupling. Below is a comparison of damped Phase 3 MC2 TFs (see allhstss_2014-11-24_Phase3_H1MC2_M1_Don_ALL_ZOOMED_TFs.pdf), the plot keys are as follows:- Blue Trace = Model (hstsopt_metal) Orange Trace = H1 MC2 M1 (2013−05−25_1053543407), Phase 3b Magenta Trace = H1 MC2 M1 (2014−08−11_1091848686), Phase 3b Furthermore, back in April, even the damped in-vacuum TFs showed the aforementioned cross-couplings into the Vertical DOF. However, this is again not visible in the recent damped MC2 TFs. Summary: The above measurements indicated that there is no longer any pitch or roll cross-coupling in the vertical DOF of MC2 and therefore, that after the July corner station chamber incursion that the suspension is clear of EQ stops rubbing. This should prove sufficient to close the Integration Issue #847. All data, scripts and plots have been committed to the sus svn as of this entry.
PSL laser weekly trends.
See attached for the time series of the process, all done less than thirty minutes. HEPI isolates first time, ISI & IMC remained locked. Keita says it looks good (enough?.) I tweeked the RZ target ~100nrads to bring the ISI OpLev 'Yaw' (yes, still reversed) back to before reading. I didn't tweek pitch but is within a couple 'units' on the ISI OpLev.
The signs changed on the RX RY & RZ with the matrix correction but all the amplitudes were correct. The output matrix was a mess though and looks much better now--see second attachment for a before & after view of the matrices. The correct matrices are in the right column.
Updated safe.snap and foton txt file commited to svn r9202.
Backup done. Took approximately 19 minutes. Compressed from 13G to 1.6G. Saved in /ligo/lho/data/conlog/h1/backups/h1conlog_dump_25nov2014.sql.tgz.
Searches unavailable for duration.
Work will be starting today on the new DCS area in the VPW as well as outside between the H-2 building and the VPW. Today's activities will include some shallow excavation work outside by George Grant Construction. Inside work will include hanging a temporary curtain in the VPW to isolate the construction area from the C & B area and layout for refrigeration lines by Apollo and George Grant.
model restarts logged for Mon 24/Nov/2014
2014_11_24 06:39 h1fw0
2014_11_24 17:43 h1fw0
both unexpected restarts. Conlog frequently changing channels report attached.
Stefan, Matt, Kiwamu, Evan, Alexa
Attached are a transfer function showing the matched signals, as well as a StripTool plot of the successful sqrt(TRX+TRY) handoff.
Well done! As far as I can tell, the unlock happens at 1100940293. The vertex seems happy, the first thing to go is the Y green.
Aaron and I continued with PEM cabling at EY this morning. We have completed all long cables runs and started installing the permanent power supplies in the DC rack. We disconnected the power supplies powering the microphones in both the VEA and EBAY and placed them in the DC rack. Got a call from commissioners asking us to leave EY, before we could reconnect microphone power with permanent power supplies. Will go back tomorrow morning and power them up.
Microphone power was reconnected at EY this morning.
Matt, Dan
After Alexa gave us a quick alignment tutorial, we started by fiddling with the dither alignment of the X-arm. The PD thresholds for dithering across the baffle PDs were set to very small values, so small that the dither would declare victory before it even started. Matt has been working on the initial alignment, I'll let him say more about it.
We noticed that the green spot on the TMS-Y mirror, visible through ETMY, is very low. There are large offsets in the EY green QPDs that steer the beam to what looks like a bad place on the mirror. Zeroing these offsets (which is where they were for most of the last six months) would have forced us to begin a painful realignment procedure, so we left them as we found them. Historically it looks like people have set these values to maximize the buildup in the arms, but it's hard to believe that the optimal beam position is so far off-center.
With the arms well-aligned for green we aligned the corner optics - IM4, PR2, PRM, BS, SRM. The scripts for this went quickly, about five minutes.
Then we locked the DRMI, with the arms misaligned. Locking tonight was fast and robust; the DRMI would lock within a few minutes (rarely more than 5 minutes), and would remain locked for tens of minutes. There were many unexplained lock losses, so things are not as stable as we'd like, but we didn't see any mode hopping and the sideband buildup was consistently good. Over three hours of DRMI locking we didn't observe a significant drift in the alignment.
We went through the DRMI guardian and commented out lots of gain/switch settings that weren't needed, mostly for the DC centering. The script is now pretty fast, it goes from lock acquisition to ASC loops on in less than 30 seconds. We did not observe any unexpected long pauses. The duration of the script is dominated by ramping the SRM and PRM M2 gains, this takes 9 seconds total (4.5sec each).
We re-enabled the PRM and SRM2 offloading to M2. We found the SRM offloading was a little flaky and sometimes broke the lock. To make this a little gentler, we reduced the initial gain ramp to 1, and ramped the rest of the way (to 4.5) after the WFS turned on.
We measured the LSC OLTFs and found that MICH and PRCL didn't have much phase margin (~25deg each). We reduced the gain for these loops so that they both have >30deg. The MICH gain is now 3 (was 5) and PRCL is 15 (was 22).
Afterwards I mucked around with the OMC, I found a set of good misaligned values for ITMX and ITMY that minimized the RIN at the dark port when the other ITM was aligned (presumably this steers ghost beams away from the OMC). Following Gabriele's instructions I used the picos to center the beam on IMC WFS A and added some offsets to the IMC ASC loops; this reduced the intensity noise measured by the ISS second loops PDs by a factor of three or so. I tried to engage the ISS second loop but failed. The script posted here did not appear to work; I tried to follow these directions but the loop was unstable.
Plots attached are MICH, PRCL, SRCL loops before we reduced the gain to get some phase back in MICH and PRCL.
FWIW the misalignment settings for ITMX/Y that inject the least amount of RIN at the dark port (with a single bounce off the other ITM) are:
ITMX PIT | ITMX YAW | ITMY PIT | ITMY YAW | |
Aligned | 64 | -1.7 | 222 | -140 |
Nominal misaligned | 0 | -62 | 0 | 0 |
Better misaligned | -10 | -380 | 282 | -450 |
I didn't observe any change in the RIN spectrum when moving the PRM, SRM, or ETMs. This doesn't solve the problem - the OMC TRANS spectrum is still a little ratty - but it seems to be dominated by RIN noise that is coming from the input beam, which is a job for the ISS.
The ISS second loop scripts are not 100% fail proof. If they fail once, try a couple of times more. Normally the switch one script works more than 50% of the times.
Well, Gabriele is right -- running the ISS secondloop script with Sudrashan this afternoon was problem-free.
For posterity, I've been using Sheila's DRMI OLTF templates for measuring loop gains: /ligo/home/sheila.dwyer/DRMI/DRMI_MICH_OLG.xml and related.
J. Kissel, J. Warner, E. Merilh, H. Radkins While taking down and bringing up the HAM2, HAM5, BS, and TM ISI + HPIs this morning to upgrade suspension front-end code (see LHO aLOG 14830), we had the following troubles with platforms: (1) The Rogue Excitation Monitor for HAM5 ISI could not be naively reset, and was caught in a trip-loop. - First of all, it's frustrating that there in no MEDM screen indication that the MASTERSWITCH must be ON in order to reset the rogue excitation monitor, so myself / Jim / Ed spent a few minutes clicking all the watchdog reset buttons hoping that there was some special order, until Hugh informed (reminded?) us that the master switch needed to be on - Second, I'm not 100% confident why, but after enacting the "correct order" of reset by turning on MASTERSWITCH, reset Rogue WD, reset all to untrip the DACKILL, the MASTERSWITCH would turn itself OFF again before the three-second counter/delay of the rogue excitation was finished, therefore re-tripping thinking the MASTERSWITCH never was turned ON. I'm 90% confident this happened because the MASTERSWITCH would "turn itself off" because the SEI manager demanded that the MASTERSWITCH be OFF because it was still in the OFFLINE state. Why do we have the SEI Manager controlling the MASTERSWITCH, but the ISI module controlling everything else? (2) There are no monitor signals on the MEDM overview screen to indicate what is currently causing the Rogue Excitation Watchdog to fire. This proved solving the above problem initially difficult -- I had to open the model to find out the logic (especially the hard-coded "100 [ct]" threshold), the three-second delay, open the CDMON channels in dataviewer, find they were low, and then go for figuring out the MASTERSWITCH trick. We should (a) added epics monitors on the three *inputs* rogue excitation monitor, and (b) create a sub-screen for the rogue excitation that reveals the details of this monitor. (3) The BSC-ISI overview screens have the SEI Manager guardians on the overview screen. The BSC-HPI overview has the HPI module guardian. The HAM-ISIs and HAM-HPIs have their individual module guardians on the overview screen. This resulted confusion when trying to quickly bring the platforms back from offline -- I'd gone to the HAM-ISI overview after just finishing the BSCs, and out-of-habit assumed the guardian drop-down menu was the manager and was surprised why it wasn't doing anything for me. Arnaud informs me that this is because the overview screen mods were first made at LLO, where they're not using HEPI and therefore don't need a manager. Since not-using-HEPI is a deviation from aLIGO baseline, I argue that we should fix this by creating the SEI manager for the HAMs, and just temporarily create a managed configuration that doesn't use HEPI -- instead of having the confusing user interface for the HAMs. (4) The SEI manager for ITMY seems to *not* automatically turn on the MASTERSWITCH. Is this automatic operation consistent between chambers? Between HAM managers and BSC managers? (5) HAM3-HPI's L4C saturation counter in watchdog wouldn't reset with a RESET ALL or RESET above the current trigger but, but RESET WD ONLY worked. We can confirm that every other chamber behaves as expected, i.e. any of the three methods reset the counter. What's different about HAM3? Is this reset a python script that is uniquely defined per chamber or something?
(1) "there in no MEDM screen indication that the MASTERSWITCH must be ON in order to reset the rogue excitation monitor," currently, the reset will only work if the signal coming in is not in the alarm state, e.g. if you are still alarming, you can't reset it. 1a) This can be changed to allow to monitor to be reset even though the bad condition persists. probably fine since there is a human there, but it will likely just trip again. 1b) Why was the alarm condition still true? it should not have been. This requires some follow up. most likely the threshold is set to close to zero. - The masterswitch is not for a particular stage - so it does not go into the stage manager. It belongs to the chamber = whole-thing manager. - the ISI manager does not control 'everything else'. There are 2 ISI stage managers, and a HEPI manager, and soon a blend manager. - we need to adjust the chamber manager so it is not too annoying. The 100 cnt limit is set by looking at the levels on the coil drive monitors see: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=2729 and https://alog.ligo-la.caltech.edu/SEI/index.php?callRep=339 Since this is a watchdog thing, it is hardcoded so that folks don't just set it to 1000000000000 and forget it. If 100 is too small, we can certainly make it bigger - we should check how big it was at this time. (2) yes (3, 4) interesting. (5) we need to check this.
Two IR HR removed
There were two IR HR mirrors on the table that were not necessary any more, so I removed them and brought them back to the SQZ area cabinet.
Bug on the ISCTEX
Look what we've found there. I think the moth was attracted by the laser or maybe an LED inside, managed to crawl in from an opening under the white tape that covers a hole on the feedthrough panel, but couldn't find his/her way out and died.
I also found the same kind of moth in a bag of clean wipes. The entire bag went into the trash bin.