TITLE: 01/26 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Nutsinee
CURRENT ENVIRONMENT:
Wind: 2mph Gusts, 1mph 5min avg
Primary useism: 0.09 μm/s
Secondary useism: 0.55 μm/s
QUICK SUMMARY:
No issues to report.
TITLE: 01/26 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 69Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Locked and Observe the entire shift. Nothing exciting to report.
LOG:
0:10 Kyle to Mid Y
1:11 Kyle back
~5:15 Patrol on site -- Went to both arms I believe (I definitely saw the car doing down the X arm). He seems to be going slowly enough on the camera to I didn't drop the intent bit.
6:00 Patrol left the site. Called about broken exit gate too.
Summary:
I did jitter subtraction similar to alog 31378 from Nov 09 last year.
It seems like the jitter is eating somewhat smaller than 6% of BNS range. That is a loss of about 4Mpc at the time of measurement. Look at the first attachment (but don't pay attention to absolute number of the BNS range, just make the ratio of the BNS ranges, which is about .944, and the sensemon range at the time of measurement was about 66Mpc, 66/.944=69.9).
Simple spectrum comparison show that the jitter bumps are bigger today than Nov 09 2016.
What was done:
I picked a time window starting 25/01/2017 08:03:00 UTC for 8004 seconds. This is a 66Mpc-ish lock segment without any huge glitch from today (1st attachment left).
Coherence and cross spectrum were measured between CAL-DARM_EXTERNAL_DQ and various witness channels that are believed to have some jitter related information, both angular and doughnut (1st right). These channels are IMC WFS DC A and B PIT and YAW, and ILS HV and PMC HV. As you can see, the coherence is relatively high for f>100Hz.
Next, as a quick and dirty method of noise projection using multiple channels, for each frequency bin I chose the channel with the highest coherence as the best witness for that specific bin to make a combined witness channel:
bestchannel(f) = whatever channel with the largest coh(f).
combinedWitnessASD(f) = ASD(bestchannel(f), f).
combinedCrossSpectrum(f) = crossspectrum(CAL_DELTAL_EXTERNAL, bestchannel(f), f).
noiseProjection(f) = combinedCrossSpectrum(f)/combinedWitnessASD(f).
This way I'm only using whatever is the dominant noise witness without double counting (or without properly calculating the multiple noise sources).
Then I subtracted the projected noise from the original CAL_DELTAL_EXTERNAL.
subtracted= sqrt(CAL_DELTAL_EXTERNAL^2-noiseProjection^2).
I used the dtt calibration file from calibration SVN to convert CAL_DELTAL_EXTERNAL to displacement:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/ControlRoomCalib/caldeltal_calib.txt
I plugged the spectrum to BNS_range.m in the calibration svn to obtain BNS range. This produces different number from sensemon but it should be good for comparison purpose.
If you look at the second attachment, before subtraction the range was 75.9Mpc, after the subtraction it's 80.4, i.e. about 6% increase. If we take the 66Mpc number from sensemon, after subtraction this would become 69.9.
Comparison between now and Nov 09 2016:
Compare the first attachment with the displacement spectrum of this plot, it seems to me that jitter bumps in DARM are larger now than before, though these things change with time.
Krishna
I took a quick look at the data from the PEM STS at EndY, which is mounted on the BRSY platform. The channels are mentioned in 33533.
First plot shows the GND STS (used by SEI) and the PEM STS converted to angle units (by multiplying by w^2/g) in comparison to the BRSY - rX. The wind-speed during this time was less than 2-3 m/s. The GND STS sees less signal than the BRS below ~50 mHz, but the PEM STS sees a lot more. The second plot shows the coherence between some channels and the third plot shows the X-direction signal. The Z channel is not recorded so I can't access it through ligodv-web.
The source of extra noise in the PEM STS could be - a) Insufficient mass centering or b) Extra temperature noise either on the STS case or the table it sits on; more insulation to the table and the STS case might help...
When allowed (Tuesday?) we could go check the centering and center it up as needed--Hugh
On Tuesday went to EndY to Check on and Center the PEM STS Masses
Upon arrival checked the mass measurements right away: U V & W were -3.7 -1.8 & -12V. The X axis is generated from U V & W but the Y signal comes just from V & W. See manual for axis mapping.
While the W mass is clearly out to lunch, U is also high >2volts. However, as W contributes to both X & Y signals (but with different weightings) you'd think both X & Y signals would be noisy. One might even argue that Y(North on STS Manual) would be even worse than X.
This morning, Thursday ~0930pst, with an IFO Lockloss, we went to the VEA again to check and found the U V & W masses exactly where I recorded them almost two days ago after nearly two hours of centering attempts: 9.9 12.9 & -13.5V. After recording the voltages this morning, we hit the centering button and left the VEA.
Now see the attached 60 hours of minute trends. Before the Tuesday mass centering activity, the X & Y time series values suggest fairly zero'd signals; I did zoomed in and they are. During the interum ~2 days before this morning's look, the Y signal was pined to a rail. Noting my U V & W voltages, before Tuesday just W was on it's rail but after Tuesday, essentially all 3 masses were at or near a rail. This further suggests you can not just look at the X Y & Z signals to assess the mass centering.
So, clearly, waiting for the masses to come off their rail did not yield results. In addition, it appears there is a higher frequency noise on the channels showing up on X after Tuesday and now on Y after this morning's centering.. We will go measure the mass voltages when allowed. I did leave some leads hanging off the monitor port for voltage measuring but they are mostly insulated and I don't think they are causing noise. However, we'll remove these next time just in case.
Meanwhile, the positive glitches seen on the time series (average is still under the min trace but the max [black] is way higher than the average) are not continuous. I guess these show up as the 1/f noise starting around 40Hz on the spectra, second attachment. The reference traces are 1200utc 31 Jan (before the Tuesday activities.) Note the higher noise on the X (pink) trace compared to the Y signal (cyan.) I checked the wind, it did not seem to be an issue at that time.
I have to just throw this in and run.
Here is a comparison of the SEI Ground STS and the the PEM unit on the BRS. These have some gain difference I don't understand yet but I made them the same by multiplying by the ratio at the useism. At this BW, the PEM is not happy.
18:00 Delayed entry: Cleaning at both Mid stations since around 17:00UTC: also Betsy is at MY after she went to check on EY upon getting a LOW TEMP Verbal Alert and then a Dust Monitor Alarm; Cheryl went to the warehouse.
18:02 Found that the Locking Filters had been turned off for IM4 which was causing a lit of difficulty doing initial alignment.
18:26 Karen leaving MY
18:30 FOLLOW UP: Sheila called to request remote CDS access and revealed that it was she that had turned the filters for IM4 off. She has since spoken to Jenne and this will be resolved by reloading the ALIGN_IFO Guardian node after the next lockloss and certainly before the next initial alignment.
19:24 Mark and Fil going to MY to check 3IFO inventory.
21:13 Noticed a computer monitor on in the LVEA on the LVEA North Cam that can't really be identified clearly due to the misorienting lack of ambient light. It turned out to be a reflection of the blue LEDs on the ISC rack at HAM6.
22:18 Lockloss (aLogged)
23:45 NLN. Ran a2l script.
00:05 Intention bit Undisturbed. Handing off to Nutsinee.
Around 16:00PST Monday 23 Jan, the corner station weather station outside temp increased by about 13F. It occassionally drops back to the actual temps, but most of the time it has an offset. The wind speeds do not show this problem, so it looks like a possible sensor issue. Jim restarted tbe MSR base station which did not fix the issue.
The attached plot shows 3 days of minimum temps. The black plot is the CS, joined by a line to show the times it corrects itself.
model restarts logged for Tue 24/Jan/2017
2017_01_24 11:46 h1broadcast0
2017_01_24 11:46 h1dc0
2017_01_24 11:46 h1fw0
2017_01_24 11:46 h1fw1
2017_01_24 11:46 h1fw2
2017_01_24 11:46 h1nds0
2017_01_24 11:46 h1nds1
2017_01_24 11:46 h1tw1
2017_01_24 11:47 h1nds0
maintenance day, DAQ restart to support various changes.
model restarts logged for Mon 23/Jan/2017 No restarts reported
| Work Permit | Date | Description | alog/status |
| 6454.html | 2017-01-24 8:16 | Install movable local humidifiers. First locations: EY VEA, CS Ebay. | 33635 |
| 6453.html | 2017-01-23 15:37 | Tues maint 1/24, 1/31. In CER: Measure slow phase noise of the 8, 9.1 80 MHz Osc relative to independent oscillators, as seen on spare fanout channels; non interuptive; with Scope, RF Anal. | |
| 6452.html | 2017-01-23 15:11 | Update GDS software to version branch 2-17.9-1 to fix leap second issue. This version allows users to abort a DTT measurement that is waiting for data, and fixes minor issues of Bugzilla 469 (ezcademod channel list), 1064 (unit names truncated reading from NDS1). | 33634, 33581 |
| 6451.html | 2017-01-23 15:10 | Return CP4 pump level to the daily vacuum texts (was hardcoded out as -1). Mark all CP and Gauge values in these texts with a "!" character if their ERROR signal is in error. | 33634, 33596 |
| 6450.html | 2017-01-23 15:07 | Reconfigure the gds broadcaster to not generate MD5 check sum files. | 33634 |
| 6449.html | 2017-01-23 14:00 | Lubricate all AXIVANE Fans on site. This will require individual shut down of each fan to perform the lubrication. | 33619 |
| 6448.html | 2017-01-23 13:35 | Install improved 4.7 kHz notch filter into DARM2 bank and turn it ON to mitigate ring-up of 10th harmonic violin modes. This will affect computation of calibration group's time-dependent correction factors, so corresponding EPICs records of DARM loop model at calibration line frequencies will need to be updated. This has no affect on CAL-CS and GDS pipelines, because both will read in the updated EPICs records. Once filter change and EPICs records are accepted into SDF, the change is complete. Will be performed during maintenance tomorrow, Jan 24. | 33585, 33546 |
| 6447.html | 2017-01-23 11:24 | Turn off controller to modify its output voltage to 5.6 kV from 7.0 kV and run a system calibration. Power will be removed from the controller for the duration of this activity. After modification power will be restored for the controller. | 33571 |
| 6446.html | 2017-01-23 10:51 | Add a drop (if not already in place) and install a new dust monitor near HAM1/2. This will require a DAQ restart to pick up the new dust monitor channels. | 33634 |
| 6445.html | 2017-01-23 10:36 | Inspect and measure gate valves. This will require moving ladders around and possibly crawling on gate valves and vacuum chambers. | |
| 6444.html | 2017-01-23 9:49 | PMC Maintenance: Tweak beam alignment into the PMC to increase transmitted power. This can be done from the control room and does not require a PSL incursion. Change PMC Transmission limit in the PSL ODC from 60W to 50W and update SDF. Normal operation of the PMC is very close to the current 60W ODC limit, so I'd like to alleviate this potential issue. | 33573 |
| 6443.html | 2017-01-20 13:14 | Create a new TCS guardian node to monitor the health of the ring heaters. The code lives in /opt/rtcds/userapps/release/tcs/common/guardian | 33578 |
| 6442.html | 2017-01-20 11:59 | Have Dave B. make needed changes such that the Vacuum Team be sent a text message for the case when CP4's CDS level indication stays > 0 for longer than 10 seconds. Use a diaphragm pump to apply a vacuum (24/7, unattended) to CP4's clogged "high side" sensing line via a parallel plumbed connection. | |
| 6441.html | 2017-01-19 13:56 | Standardize the OAF range calculation, add notches to DARM BLRMS, unmonitor the OAF range calculation from SDF | |
| 6440.html | 2017-01-18 17:45 | Injections to investigate noise and for vetting. May include shaking of CPs, input arm, BS HEPI, magnetic injections and power mains injections. Will be done while LLO is down. Approved by Keita. | |
| Previous W.P. | |||
| 6286.html | 2016-10-31 10:13 | Remove Pringles from restored DOFs list of HEPI platforms: Edit guardian parameter file for each platform. Test as needed (not really needed.) | 33580 |
Yesterday, Sheila modified the DRMI guardian to turn off the inputs and ramp down the gains of the ISC filter banks for DRMI optics, so that we stop sending signals to the optics as soon as we lose lock.
In the DRMI ASC state, she has the needed ones explicitly turned back on, including IM4.
This morning, Ed was not able to complete the InputAlign state, and he and Keita found that the inputs to the IM4 LOCK filters were off. To alleviate this issue, I have the SetInputAlign state turn on those filter banks, so that the InputAlign state works as it usually does.
22:18UTC
21:59UTC
22:10 Intention bit set back to Undisturbed
21:13 Noticed a computer monitor on in the LVEA on the LVEA North Cam that can't really be identified clearly due to the misorienting lack of ambient light.
It may just be a vaccuum rack computer but it's hard to tell where it is. I don't recall being able to see this on past shifts. Maybe I just got lucky this time?
PSL chiller water levels are good. No water added. The filter are both clean, no debris noted, and no discoloration noted. Closed FAMIS #6507
I installed the 2 new local humidifiers yesterday, one in the electronics bay at EY and one in the electronics bay at the CS. The fans were too noisy to put one in the VEA where I wanted it; I did put them on foam to reduce the vibration coupling to the floor, but I think they are too acoustically noisy to put in the VEAs. I have doubts that these are high enough capacity to help, but I set them to come on at a RH of 30, so we wouldn’t have to refill them all the time. John is going to look again into the building humidifiers.
Also, in related activities, I moved the temporary magnetometer to near the ESD feed-through on the ETMY chamber. It would be good for DetChar to monitor for coincidences with blip glitches. Channels:
H1:PEM-EY_ADC_0_08_OUT_DQ, H1:PEM-EY_ADC_0_12_OUT_DQ, H1:PEM-EY_ADC_0_13_OUT_DQ
late entry for yesterday's maintenance
WP6446 Dust monitor install
Jeff B, Jim B:
A new LVEA Dust monitor was added to the system. A new DAQ INI file was created and installed when the DAQ was restarted
WP6451 Vacuum alarm texts
Dave:
CP4 was added back to the daily status texts. The ERROR status of all signals was added to the texts.
Restart Guardian DIAG_MAIN node:
T.J:
DIAG_MAIN was restarted, memory was recouped
New TCS_RH Guardian node:
TJ, Nutsinee
A new node was created. A new INI file was created which was install on the DAQ restart.
WP6452 Update control room GDS tools for leap second change
Jim:
New version of GDS tools was installed.
WP6450 DAQ GDS-Broadcaster reconfigure
Dave, Jim:
daqdrc for h1broadcast0 was changed to stop writing the MD5 check sum file for each frame file is creates.
Remove controlled power strip from Mechanical Room Vacuum Rack
Dave, Jim:
We removed an obsolete remote power strip from the MR Vac Rack. Richard says this was left over from iLIGO as a means of remotely powering the chamber illuminators.
DAQ Restart
Dave:
DAQ was restarted to support many of the above activities. This was a clean restart, h1broadcast0 was quick to start, but unlike the last time did not need a restart.
I've added the Beckhoff SDF diffs as a matrix in the lower left hand corner of the CDS Overview MEDM.
Guardian will not permit observation mode if any of these diffs are non-zero. Similar to the SDF diff display for the front end models, a non-zero will be displayed with a red circular border around the number.
TITLE: 01/25 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 64Mpc INCOMING OPERATOR: Ed SHIFT SUMMARY: Very quiet night. I restarted video1 to run the updated vacuum overview medm screen. H1IOPASC0 reported a timing error, Ed has reset it. LOG: No events logged.
At some point in the night I noticed that the HAM6 HEPI guardian was reporting SPM diffs. Since I was told at one point that this feature of guardian is not used, I have ignored it.
Thanks for noticing Patrick. This is related to the Guardian Pringle loop changes TJ and I did yesterday. I am surprised the HPI Guardian is complaining as we changed the guardian and used the guardian to reisolate the platform. The SPM diffs should clear safely with an INIT but maybe best to wait until a lock loss to do that. The INIT should not trip the platform but I'd like to understand why there are SPM diffs. Maybe if the platform is reisolated using the SEI Guardian rather than the HPI. I've asked the operator to let me know if there is a lock loss so this can be addressed: when the light is green the trap is clean!
The IFO Broke Lock ~2220utc, HAM6 ISI tripped too on Actuators (Shutter Fire.) Ran Guardian INIT on HPI, again, and then on SEI Guardian but these did not clear the SPM diffs. Untripped the ISI and the SEI Manager brought the ISI back up. SPM diffs remain. Executed INIT again on SEI but this did not clear the SPM diffs. Took SEI down to READY (deisolating ISI and HEPI.) SEI Guardian then brough HPI and ISI back to Isolated and SPM diffs are gone. Good things these aren't in Observing bit.
THis morning I took the weekly ETM charge data set. Unfortunately I did not put 2-and-2 together that Beckhoff EX issues may have caused problems with the SUS ETMX HV power supply while I was running the measurement of ETMX, so its data has a bit of a large error bar. Even so, it mostly looks like things are OK there wrt charge accumulation (or lack thereof!). All looks good at ETMY as well.
What were the Beckhoff EX issues?
ETM X was not a Beckhoff issue. The power supply had a problem. Though still on the display was not displaying properly and thus we were not sure the unit was capable of providing power. Power cycle did not fix this but removal of HV card from back and re-installing it did. ETM-y BRS Beckhoff computer had a problem and needed to be restarted.
Arnaud had sent along some measurements on HAM1, trying to measure the transmissibility from the HAM1 stack to the RM suspensions. I ran these measurments this morning, during the maintenance period. It looks like the LLO and LHO RM damping designs might differ a bit, maybe the LLO damping filter is a bit more aggressive? First image is just the RM1 L plant measurement, it was taken with the RMs both in DAMPED (unaligned) and HEPI isolated (SC was off, but HAM1 uses high UGF, blended (L4C/IPS) loops). The second image is the HEPI X to RM1 L transfer function, which was taken with HEPI in READY and the RMs still DAMPED. Both templates are saved in the SVN in H1/ HAM1/Data/Transfer_Functions/Measurements/Undamped folder.
EDIT: LLO's measurements are the black refs, my measurements are the red. Arnaud reports that the difference is due to an old damp filter design on the RMs, LLO now matches us.
Jim, I attached the results in alog 31179.
