TITLE: 08/02 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 54Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: locked in Observe all shift
LOG:
Around 7:00UTC the dust levels at EY started to climb, and then started to alarm 10:00UTC. The level of dust at EY was similar to the dust levels from Maintenance. At some point last night smoke rolled in, and not sure how the EY VEA would get smoke inside, but this might be an explanation for the high dust levels. Plot attached.
Elevated counts and alarms are to be expected during these hazy high particulate laden days. Not much we can do about it until the air clears. Operators - Please keep an eye on the alarms. Let me know of any unusually high counts or persistent alarms. These may indicate a leak to the outside air.
TITLE: 08/02 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 54Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 6mph Gusts, 5mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 is locked and humming along in Observe
TITLE: 08/02 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Quiet shift
LOG:
0:08 UTC SUS_ITMX again threw us out of observing for 3 seconds. No idea what (probably some guardian, somewhere) is doing this, but it's only happening once per day(ish), so it's a little hard to catch. Sounds like Dave is working on it.
We started the Pcal lines at 331.9 Hz and 1083.3 Hz at ENDX after moving the Pcal beamspot today. We have now stopped those two lines after collecting about an hour and half worth of data and started the high frequency guardian script to collect high frequency calibration data from 4501.3 Hz to 2001.3 at 500 Hz interval.
SudarshaK, ChristianP
We had left the Pcal camera Viewport cover off on Keita's request to take pictures of the ETM with light resonating for Christian Pluchar SURF project. He is done with it and we drove down to EndX and put the cover back on.
After relocking, accepted the following SDF differences.
SudarshanK, RichardS,
Summary:
We moved the Pcal beams on ENDX ETM about 14 mm away from the their optimal position of +/- 111.6 mm in y direction. They were moved away from the center of the optic. We had moved the beam about 7 mm from their optimal position towards the center of the optic last Tuesday.
Details:
We moved the top (inner) beam by moving the mirror mount in pitch in anticlockwise direction. We had to move the adjustment screw little more than quarter turn to achieve the beam movement of about 22 mm. (from -8 mm to +13 mm). For the bottom(outer beam) we moved the mirror mount in yaw in anticlockwise direction about quarter turn to achieve similar movement as the top beam.
The position of the Pcal beam spot from their optimal locations before and after are as follows:
| Before 07/25/2017 | 07/25/2017 | 08/01/2017 | |
| Upper Beam | [1.9, 0.3] | [2.5, -8.4] | [1.1, 14.5] |
| Lower Beam | [-1.0, 0.3] | [-1.3, 8.6] | [-0.5, -14.1] |
Andy, Beverly There was an interesting event pointed out by Corey in alog 37882. Beverly identified it as a 1.9 earthquake at 60 km from the site. At that distance, the higher frequencies (a few Hz) had a big effect, and caused a lot of noise in DARM very similar to the blue mountains noise. It seems like this motion rang up a baffle with a very long damping time, so maybe it'll give us some new information about how ground motion couples to the baffles. The first plot shows the earthquake in the HAM2 seismometer. It lasts about 60 seconds. The second plot shows how IMC_F is affected - it has a lot of scattering during the quake, but that only lasts during the earthquake. The effect in DARM (third plot) lasts much longer. It seems like the ground motion ends around 75 seconds into the plot, after which it takes more than 60 seconds for the scattering to die down by a factor of 2. The fourth plot shows that the IMC has fairly regular scattering arches coming from a motion with a frequency around 2.5 Hz. We should be able to confirm that one of the resonances of the MC mirrors is rung up. The last two plots are a comparison of the start of the motion in IMC and DARM. IMC seems to respond immediately, while it seems that the baffle takes some time to build up enough motion to make scatter that shows up in DARM. The observed damping time doesn't seem to match the Swiss cheese baffle either before or after the damping, though this needs further checking. Is this something else getting rung up?
How many arches per second in DARM? If it is 2.1 arches per second, as found in this log: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=34420 it may be the Output Faraday Isolator. If it is the OFI, we are planning on putting sensor/actuators on them. But the decay time seems longer than for the OFI ...
It looks more like 2.7 arches per second. It's hard to get clean arches, because it's not that strong in DARM and they're pretty fast. But spectrograms and Omega each seem to give me between 11 and 12 arches in four seconds. So I think a resonance in the 1.3 to 1.5 Hz region is more likely. It might be possible to do better by whitening the data, removing everything outside the band of interest, and then take a spectrogram with 0.1 or 0.2 Hz FFTs.
THe LVEA was swept in accordance with LIGO-T1500386v7. There was the usual whirring of fans in the vacuum rack, from a bench-type power supply on the floor at TCSX table and rather noticeably through the wall from the CER/High Bay area. I noticed some condensation dripping from CP1 and forming a little puddle on the floor.
The power cart/transformer next to HAM4 was powered down around 11:50 am. Panel VEAC-02 circuits 13,15, and 17 were turned off. The only extension cord connected to the power cart was connected to the Hartmann Table (TCSHT4R) for fans and lights, which are currently not being used.
J. Kissel Took more standard top-to-top transfer functions today in order to rule out any rubbing from the July 6th EQ. I've closed out the doubles and triples by getting high-res data of the TMTS and IMC HSTS (I got the OMCS last Tuesday). Below are the listed data files. More detailed plots and analysis to come. This leaves only the single suspensions (IMs, RMs, OMs), and these should be pretty quick since there are only 3 DOFs per SUS instead of 6. The data lives and is committed here: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/ MC1/SAGM1/Data/2017-08-01_1645_H1SUSMC1_M1_WhiteNoise_L_0p01to50Hz.xml MC1/SAGM1/Data/2017-08-01_1645_H1SUSMC1_M1_WhiteNoise_P_0p01to50Hz.xml MC1/SAGM1/Data/2017-08-01_1645_H1SUSMC1_M1_WhiteNoise_R_0p01to50Hz.xml MC1/SAGM1/Data/2017-08-01_1645_H1SUSMC1_M1_WhiteNoise_T_0p01to50Hz.xml MC1/SAGM1/Data/2017-08-01_1645_H1SUSMC1_M1_WhiteNoise_V_0p01to50Hz.xml MC1/SAGM1/Data/2017-08-01_1645_H1SUSMC1_M1_WhiteNoise_Y_0p01to50Hz.xml MC2/SAGM1/Data/2017-08-01_1733_H1SUSMC2_M1_WhiteNoise_L_0p01to50Hz.xml MC2/SAGM1/Data/2017-08-01_1733_H1SUSMC2_M1_WhiteNoise_P_0p01to50Hz.xml MC2/SAGM1/Data/2017-08-01_1733_H1SUSMC2_M1_WhiteNoise_R_0p01to50Hz.xml MC2/SAGM1/Data/2017-08-01_1733_H1SUSMC2_M1_WhiteNoise_T_0p01to50Hz.xml MC2/SAGM1/Data/2017-08-01_1733_H1SUSMC2_M1_WhiteNoise_V_0p01to50Hz.xml MC2/SAGM1/Data/2017-08-01_1733_H1SUSMC2_M1_WhiteNoise_Y_0p01to50Hz.xml MC3/SAGM1/Data/2017-08-01_1703_H1SUSMC3_M1_WhiteNoise_L_0p01to50Hz.xml MC3/SAGM1/Data/2017-08-01_1703_H1SUSMC3_M1_WhiteNoise_P_0p01to50Hz.xml MC3/SAGM1/Data/2017-08-01_1703_H1SUSMC3_M1_WhiteNoise_R_0p01to50Hz.xml MC3/SAGM1/Data/2017-08-01_1703_H1SUSMC3_M1_WhiteNoise_T_0p01to50Hz.xml MC3/SAGM1/Data/2017-08-01_1703_H1SUSMC3_M1_WhiteNoise_V_0p01to50Hz.xml MC3/SAGM1/Data/2017-08-01_1703_H1SUSMC3_M1_WhiteNoise_Y_0p01to50Hz.xml /ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/ TMSX/SAGM1/Data/2017-08-01_1503_H1SUSTMSX_M1_WhiteNoise_L_0p01to50Hz.xml TMSX/SAGM1/Data/2017-08-01_1503_H1SUSTMSX_M1_WhiteNoise_P_0p01to50Hz.xml TMSX/SAGM1/Data/2017-08-01_1503_H1SUSTMSX_M1_WhiteNoise_R_0p01to50Hz.xml TMSX/SAGM1/Data/2017-08-01_1503_H1SUSTMSX_M1_WhiteNoise_T_0p01to50Hz.xml TMSX/SAGM1/Data/2017-08-01_1503_H1SUSTMSX_M1_WhiteNoise_V_0p01to50Hz.xml TMSX/SAGM1/Data/2017-08-01_1503_H1SUSTMSX_M1_WhiteNoise_Y_0p01to50Hz.xml TMSY/SAGM1/Data/2017-08-01_1504_H1SUSTMSY_M1_WhiteNoise_L_0p01to50Hz.xml TMSY/SAGM1/Data/2017-08-01_1504_H1SUSTMSY_M1_WhiteNoise_P_0p01to50Hz.xml TMSY/SAGM1/Data/2017-08-01_1504_H1SUSTMSY_M1_WhiteNoise_R_0p01to50Hz.xml TMSY/SAGM1/Data/2017-08-01_1504_H1SUSTMSY_M1_WhiteNoise_T_0p01to50Hz.xml TMSY/SAGM1/Data/2017-08-01_1504_H1SUSTMSY_M1_WhiteNoise_V_0p01to50Hz.xml TMSY/SAGM1/Data/2017-08-01_1504_H1SUSTMSY_M1_WhiteNoise_Y_0p01to50Hz.xml
MC1, MC2, and MC3 are all definitely clear of rubbing. They look like each other, past measurements, and the model.
TMSX and TMSY look clear of rubbing as well. The TMTS are tougher to clear of rubbing, because they're each their own unique snowflake: we've never had good agreement with measurement and model, and we know they don't look like each other since they're really two different suspension types (the first article and the production version, plus left and right handed)... BUT both suspension measurements look to have resonances as they always have. I'm not sure what's going on the with the DC scale factor changing over the years, but its an indication of electronics / measurement calibration wonkiness, not anything mechanical / rubbing. Some might be explained away by OSEMs LED failing, because we gave these guys the bottom of the barrel OSEMs.
TITLE: 08/01 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 53Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Mostly quiet
LOG:
0:10 NLN, with violin mode damping left off, per Sheila's log
0:50 IFO went to commissioning for no reason I could find. IFO guardian only showed some spm diffs on SEI ETMX(that had been there all along), but there were no SDF diffs. No one had touched anything.
Guardian DIAG_SDF suggests a difference showed up momentarily on SUSITMX
From DIAG_SDF log file:
2017-08-01T00:50:00.82615 DIAG_SDF [RUN_TESTS.run] USERMSG 0: DIFFS: susitmx: 1
Dataviewer second trend show the difference was only in effect for 3 seconds (00:50:02 - 00:50:04). Conlog did not report any settings changes at this time.
susitmx just threw us out of observe again at 0:08 UTC . DIAG_SDF logs one sdf diff, but I didn't catch it. susitmx guardian log shows nothing.
I'm running a python script on zotws6 which will print the name of the first channel in the difference list if the number of SUSITMX SDF diffs becomes non-zero.
