The h1asc, h1ascimc and h1sqzwfs models were updated to the most recent DAQ channel assignment. Some non-functional extra stuff has been removed from h1ascimc. Where necessary cables were moved on the ADC chassis.
Yesterday, Ed and I removed all of the temporary IO hardware from HAM2 and HAM3.
This included:
Notes:
New Iris Markers:
This morning:
Having discovered a dog clamp bolt for my iris marker in front of PRM was not as tight as I thought it would be, I tested a few other select IO dog clamp bolts (on baffles and beam dumps) and found that some could be tightened. I tested SUS dog clamps on IM2 and IM1, and none that I tested were loose.
When closing out HAM2 in 2013 I torqued all of the dog clamp bolts, of which there are many, and then I asked Scotty to check all of the ones he could reach with the torque wrench, and he found only a couple that needed to be tightened.
With that information, the dog clamp bolts I tried yesterday were all easily accessed, so I'm confident that both I and Scotty tested them in 2013, and yet I found some that had some room to rotate.
Not sure if this might be something that is contributing to Jeff's B&K results for of components in HAM2, not sure about the effect of checking/tightening all of the dog clamp bolts in HAM2 now, but since that was something that was done in the original IO install, I wanted to alog what I found yesterday.
WP7161: Dan, Dave:
h1fw1 is running again, writing frame files to its new E18. First file was written at 16:18 PDT this afternoon.
The two SATABOYS (originally used as a pair by h1ldasgw1) have been split, one per ldas-gateway machine.
Because both NDS servers are serving h1ldasgw0's framed data (data acquired since 10/18), Dan is building h1ldasgw0's SATABOY first and will populate its raw minute trend area with the latest backup (May-Oct 2017) first. He estimates this file copy will take about 8 hours, so will be available to nds in the morning.
The SATABOYs store two types of files: archived raw minute trend files and MD5 check sum files for GWF framed files (both full and trend) written by the frame writer.
The sataboy will be exported by the ldasgw as /sataboy-0 and /sataboy-1 for the two systems. The directory structure under this mount point is:
/sataboy-n/fchksums/full* (contains directories with 5digit-GPS name, same as /frames/full)
/sataboy-n/fchksums/trend/second (contains directories with 5digit-GPS name, same as /frames/trend/second)
/sataboy-n/fchksums/trend/minute (contains directories with 5digit-GPS name, same as /frames/trend/minute)
/sataboy-n/minute_raw (contains one directory per archived data block, with names minute_raw_10-digit-GPS)
Note: for now we are not creating the /frames/science directory, this was removed when the commissioning/science frame distinction was abandoned.
correction, the path the the archived raw minute trend data is:
/sataboy-0/frames/trend/minute_raw/minute_raw_1192382538
Dan has recovered all the files in this area, I'll add this to h1nds1's configuration.
But first....
we noticed that the archived minute trends were actually too big to fit on the SATABOY uncompressed. We have two options:
1. Keep the SATABOY all QFS and i) manually compress the trends, meaning ii) changing the DAQ code to uncompress files when needed.
2. Dan suggests splitting the SATABOY into two partitions, one small QFS for MD5 files, the second a large ZFS file system with firmware compression built-in.
We mulled this around and decided on Dan's suggestion. He has done some further investigation to determine the best compression algorithm for our application. He also found that only 2TB is needed to store all the archived min trend data taken so far in compressed files, leaving plenty of room left in the 11TB file system for future data.
Day Shift: 15:00- 23:00UTC (8am-4pm PDT)
Today's Activities:
J. Kissel, T. Sadecki, B. Weaver Same story for ITMY as was ITMX. Transfer functions look fabulous, with no evidence of mechanical flaws. Let's push things forward! Excellent work, team QUAD!
Noticed this swing in PSL table North temperatures.
Also seen in AOM power, and slightly in IMC power in (though IMC power in is low, at 60mW).
Rotation stage has not been moved, and PMC Trans drop is reason we are at 60mW into HAM1.
Depending on what beam quality is needed for work on the SRC that's coming up, temperatures may need to be stabilized in the PSL, to stabilize power.
This looks somewhat similar to what we saw this last March with the AC causing swings in the PSL temp even though it was off (alogs 34497, 34586, 34642, 34673, and 34686. Final resolution was to turn the ACs off at the breaker box.). To my knowledge, the PSL AC units at LHO are only used to keep the HEPA fans from spiking the temperature when they are turned on when a PSL incursion is required and to keep the enclosure comfortable for those working inside, not to keep the interior enclosure temperature tightly controlled. Remember, the HEPA fans and AC units are turned completelly OFF, with the make-up air set to 20%, when the LHO PSL enclosure is in Science Mode (like during an observing run). In addition, the environmental controls have been ON since we swapped the aging NPRO at the beginning of the vent, so that could be contributing to the observed temperature swings.
In light of this, I have transitioned the PSL enclosure back to Science Mode (and turned the ACs off at the breaker box, which has been standard LHO procedure since the above linked March incident). I will let things stabilize over the weekend and re-evaluate the temperature on Monday.
I will also take a look at tweaking the beam alignment into the PMC on Monday, once temperatures have stabilized. This will require turning the picomotor driver in the HAM2 area ON; this driver was turned OFF for safety reasons while the corner station was being vented to atmosphere.
J. Kissel, T. Sadecki, B. Weaver Betsy and Travis have finished up and are happy with new ITMX after BRD / NMBD installation yesterday (see 39239), so I grabbed a full suite of transfer functions to make sure the suspension is as expected in detail. Attached are the results. The message: both chains of the suspension look virtually identical to the prior build; they look spectacular. If anything, I'm a little sad about the first Vertical mode (at 0.55 Hz) showing up in Transverse / Roll on the Reaction Chain (R0), where it has not before, but I'm confident this is simply exceptionally large vertical motion from the SUS being in air polluting the sensors' response. The coherence at those resonance points is minimal at best. There's otherwise no evidence of anything mechanically awry. We should definitely proceed with replacing the QUAD's stiffening sleeve and go forward with IFO alignment.
Today, Travis swapped out the problematic AOSEM (FRS Ticket 5058)
| OLD (S/N 232) WAS | NEW (S/N 594) IS | |
| OLV | 24,100 | 26,600 |
| OFFSET | 12,056 | 13,300 |
| GAIN | 1.244 | 1.128 |
A quick check of suspension freedom, we did a top stage V and L TF which showed reasonably placed peaks. A full suite is likely up next, as well as a check of actuation (maybe falls out with TFs).
WP7161: Dan, Dave:
Today we are upgrading the second frame writer system (h1fw1/h1ldasgw1) from SATABOY-RAID to E18-RAID.
Remember that we had upgraded the fw0 system back on 18th October, that system has been accumulating full and second trend data since that time. The default NDS is h1nds1, so this change was transparent to the control room.
Today's change will be more intrusive to the control room. In preparation for the upgrade, I have reconfigured h1nds1 (default NDS) to mount h1ldasgw0:/frames-0 file system. The nds was down for about 10 minutes while this was done.
We will now power down h1fw1 and h1ldasgw1, disconnect the two SATA-BOYS, connect the E-18. Build a file system on the E-18. Connect one of the SATA-BOYS and build a file system on it customized to its function as a raw-minute-trend archive server.
h1nds0 (guardian's NDS) is unaffected by today's work.
Attached are screenshot for BSC & HAM CPS spectra. Nothing notable for high frequencies.
Fairly quiet so far. (although the useism has taken a step up in last 18hrs & we continue to have sizable EQs over last few hours).
LVEA Zone Temperature StripTool looks fairly normal/flat around 20.1degC for last 43hrs.
Went through most of the Ops Checksheet with nothing to note.
On the CDS Overview, the edcu is red (this is due to BRS work).
DOE Ground Water Services was on site yesterday morning to perform annual testing of our well. I had to manually run the well for ~ an hour which is longer than I expected and as a result, I overfilled the well tank. There is a high level alarm sounding in the maintenance building but it is nothing to be concerned with, the annoying alarm will silence when the level drops.
IO alignment is complete, until final check, and until after a fix for IM2 and IM4:
Other IO changes to the HAM2 payload:
I've updated the BSC-ISI model in the repo and it is ready for installation. - HAM-ISI model is still pending (should be very soon).
Following requests from Jim, Sheila, et al, this change will update the BSC-ISI watchdog to make the ISI more robust during earthquakes. We have changed the model to increase the hold-the-damping-on-even-if-stuff-is-saturating time from 3 to 60 seconds.
The updated model is in the userapps repo at SVN revision 16398
Installation instructions and more technical details are in technical note T1700481.
The approved ECR is E1700367
and the FRS is 9309
I've not pulled work permits.
-Brian
[Spelling Ed from DAY Ops Shift duties so he can join IO Team for HAM2 activities.]
Day's Activities:
Hugh, Jim, Krishna
This is regarding the idea of placing a seismometer on the BRS-Y platform in order to improve coherence and hence tilt-subtraction. The brief summary is that we found excess low-frequency noise in the seismometer when it was placed on the table on BRS-Y. Hugh had attempted to reduce the noise by adding thermal insulation to the table and the instrument. The last alog on this is 35426.
In the recent data I looked at, this excess noise looks non stationary - it seems to get worse with elevated wind. This suggests it is likely not thermal. The seismometer data shows that the table has much higher motion in the 10-100 Hz as compared to the ground. Since the seismometer isn't held securely on the table, it is possible this excess high-frequency motion is causing it to move ever so slightly, which could look like excess low-frequency noise (step changes). We are attempting to mount the seismometer securely to the table using M10X1.0mm threaded rods and holes to be machined into the table. Results and plots will be posted in a few days.
How is the table secured to the ground?
The table on which the BRS sits, is sitting on three legs, not sure if these are hard point or rubber mount... Good question, Krishna?
