Josh reported H1:PEM-EY_ACC_BSC10_
Also, I had noticed that H1:PEM-EY_ACC_BSC10_ETMY_X had been unplugged at the electronic racks, so I plugged it back in (looks like its been unplugged since last tuesday).
Josh reported H1:PEM-EY_ACC_BSC10_
Also, I had noticed that H1:PEM-EY_ACC_BSC10_ETMY_X had been unplugged at the electronic racks, so I plugged it back in (looks like its been unplugged since last tuesday).
J. Kissel ECR E1500386 WP 5553 II 1126 I've copied over the PCAL Inverse Actuation filter, as recently updated by Sudarshan (see LHO aLOG 22185). For the record, the foton design string is zpk([0.01;0.01],[1215.5+i*6893.7;1215.5-i*6893.7;7000],3.4514e+12,"n")*gain(3994.47) The filters have been turned ON as shown. I've accepted the filter states in the SDF system. In the process, I've also made sure that the "CHANS NOT MONITORED" list is the same between CAL-CS and CAL-EX. In summary, they're the EPICs "readback" channels that get filled in with TINJ and the EXTERNAL ALERT system, and the ODC string records that tell what each ODC bit means (see attached screenshot).
Over the last few days, we've been trying out the new 45 mHz blend filters for the BSC ISIs, which are designed to help out during times of high microseism.
This aLog is just meant to be a collection of logs relating to the switching, to help Team DetChar know which state things were in at which times, so they can hopefully make a comparison. One of the things that might be most interesting is the effect on the artifacts that Josh pointed out in aLog 22405.
Some of the logs that have talked about the switching back and forth include aLog 22440 and aLog 22459.
Looking at the SWSTAT of the ISI-[chamber]_ST1_BLND_[x or y]_CPS_CUR_SWSTAT channels I can see when the blends were in each state. FM7 is the nominal 90mHz blends (SWSTAT = 40000), and FM9 is the new 45mHz blend (SWSTAT = 40192). Below is a table of the lock stretches in each state.
| 90 mHz blends (nominal) | 45 mHz blends (new) |
| all locks through the one ending 10 Oct, 21:25 UTC | |
| 11 Oct 16:22 UTC - 12 Oct 18:11 UTC | |
| 13 Oct 00:53 UTC - 13 Oct 09:30 UTC | |
| 13 Oct 11:35 UTC - 13 Oct 14:43 UTC |
For some background, 45 mHz blends provide us with isolation at the microseism, which may be partially coherent between the buildings. When we lock with 90 mHz blends, we lock the position of the ISI to stage 0 at the microseism frequencies. With the normal seismic environment at LHO we find this better, because the interial sensors confuse wind induced building tilt with translation at these frequencies and if we try to use them to isolate they move the ISI in response to these spuirious signals.
In the fall, we tend to have less wind and more microseism, meaning that our seismic environment can sometimes be more similar to LLO's normal situation. Using the 45 mHz blends which are more similar to LLO's had allowed us to lock durring a high microseism, low wind time when we were unable to lock on our normal 90 mHz blends. We know that durring winds above about 20 mph we will be imposing spurious tilt signals on the ISI with these 45 mHz blends, which can make locking imposible or difficult.
So can you tell us the impact of these blends on DARM by comparing lock stretches with similar microseism and wind but different blends? It would be good to know this for a few different environmental conditions, (say winds below 15 mph and microseism high, and winds from 15-30 mph and microseism high).
Re WP 5527 & alog 22305, I've returned the cabling to its nominal connections.
nm
I've rearranged the PRMI branch in the DRMI guardian, and added states to the ISC_LOCK guardian to request both these states and the ALIGN_IFO states used for PRMI (finshing unfinished item from WP5533). This is for use when you think that the DRMI alignment is bad (based on the AS camera and the flashes as seen in dataviewer) and will not lock. If DRMI is slow to lock but has been locked recently and looks well aligned on the AS camera, this procedure is probably not your best bet.
We will test this durring maintence recovery today, but the instructions replacing those in 21745 will be:
done!
This has now been tested, and had some bugs but after fixing several typos we made a sucsesfull transition from PRMI to DRMI. If you are trying to lock DRMI and decide to change to PRMI, you would need to take ISC_LOCK to manual, then request LOCK_PRMI, and go back to AUTO.
And remember "Manual" will be on the "ALL" screen for ISC_LOCK (it's the pink button on the upper left). [I forgot where this button was and had to call Sheila!]
J. Kissel The former, old (I think it was installed during the H1 mini-run), redundant Inverse Actuation filter that had been installed in the CAL-INJ_TRANSIENT filter bank in FM1 and FM10 (but never turned ON). To avoid confusion, I've simply deleted these filters. The updated filter file, has been committed to the userapps repo.
J. Kissel, T. Schaffer ECR E1500386 WP 5553 II 1126 I've updated the /opt/rtcds/userapps/release/cal/common/medm/ CAL_INJ_CONTROL.adl CAL_INJ_ODC.adl screens to use macro variables $(FEC), $(fecname), $(FECNAME), and $(INSTANCE), such the common overview screen (CAL_INJ_CONTROL) can be used for both the DARM INJ path and the PCALX excitation path. After doing so, I've modified the /opt/rtcds/userapps/release/cds/h1/medm/SITEMAP.adl All above mentioned screens have been committed to the userapps repo. The INJ and ODC Team should now begin filling out this new infrastructure, and adapting "offline" software to use these channels. I'll be copying over the inverse actuation filter shortly.
As usual, during this morning's maintenance period, I took 5 charge measurements on each ETM. Attached are the trends, back a few months with the added measurement data from today. We plan to swap the sign of the ESD bias this week. To be continued...
As discussed with the detchar group and observatory run coordinators,
1. The H1_C commissioning frames have been permanently archived by ldas (dcs) from
1125097472 == Aug 31 2015 16:04:16 PDT
to
1128783680 == Oct 13 2015 08:01:04 PDT
2. The L1_C commissioning frames have been permanently archived by ldas (dcs) from
1125097472 == Aug 31 2015 18:04:15 CDT
to
1128776448 == Oct 13 2015 08:00:31 CDT
3. Outside of these times ldas (dcs) is keeping only the past ~ month of this data on scratch disk. In particular, the commissioning data before the above times is no longer available, and the commissioning data after the above times get deleted after it is about a month old, to keep our disks from filling up.
I reset the H1 PSL FE Watchdog at 15:48 UTC (08:48 PDT). While garbing down afterwards I noticed the crystal chiller water level was low, so I added 250 mL of water.
J. Kissel, J. Batch ECR E1500386 WP 5553 II 1126 I've run a make and make-install on the h1calex front-end model changes that were described yesterday (see LHO aLOG 22445). Jim has restarted the model and DAQ for me, at roughly 15:00 UTC, about 10 minutes after the lock loss. Will post more details once we get MEDM screens up and running.
Title: 10/13 OWL Shift: 07:00-15:00UTC (00:00-08:00PT), all times posted in UTC
State of H1: IFO unlocked - Maintenance
Incoming Operator: Jim (main), Patrick
Quick Summary: Two lock losses
09:31:23UTC - lock loss
11:39:42UTC - IFO back in Observe, see previous alog for details on relocking
14:43:14UTC - lock loss, Maintenance starts
Attached plot, from the lockloss tool, is zoomed in to the OMC-DCPD_SUM_OUT_DQ channel.
The plots shows that all of the other channels glitched after the OMC DC channel.
The channels were chosen by the lockloss tool, so maybe not a complete story yet.
Lock ended at 9:31UTC, and this plot shows 8.5 hours, which all but the very beginning of the lock.
Plots attached show that POP_A_LF_OUT is oscillating between 16200 and 17000 (800 counts) in the last 10 minutes of the previous lock, and is oscillating between 16200 and 16600 (400 counts) in the current lock (channel 1).
PO_A_LF_RF9_Q_ERR was oscillating between 35000 and 55000 (20000 counts), and is now between 55000 and 65000 (10000 counts, channel 2).
Lock loss at about 9:30UTC, and while nothing is broken, many small issues to relaocking.
Bottom Line - I can see the useism effecting the locks; arms in green, arms in red, PRMI, and DRMI, and that's made relocking twitchy.
Details:
- 3 or more times, I had the the PRMI locked and aligned, and when I brought SRM back in, it didn't just break the PRMI, the SRM watchdog tripped
- at least two times, HAM5 ISI also tripped
- during one of those, the BSC2 ISI tripped
- at least 3 times the DRMI locked but not good enough for WFS, and broke before I could manually fix it
- once DRMI locked and WFS did engage, I let it sit for a while, as I took a much needed break, if you must know, and even then it broke on it's way to Engage ASC
- DRMI just relocked and at 11:21UTC, it looks like the IFO might make it back to Low Noise
- at 11:25UTC, IFO is in Engage ASC and looks OK
BSC chambers switched to Quiet90 ISI Blend Filters, and I accepted changes in SDF in order to return to Observe - screen shots attached.
9:31:32UTC - Lock loss, I haven't investigated
11:39:43UTC - IFO returned to Observe
