The h1seiey computer crashed with a kernel panic at 08:41 PDT today. Attempts to remove it from the dolphin network were unsuccessful, so on restart, h1susey was glitched and needed to be restarted as well. Inspection of the computer and I/O chassis showed no obvious reason for the crash.
J. Kissel, K. Venkateswara, E. Shaw Krishna and Eric arrived yesterday, and we've begun installation of the Beam Rotation Sensor at H1 EX. Pictures attached! Some quick notes -- the center of the platform is roughly 41" WEST (+Y), and 9" SOUTH (-X) of the GND T240, and aligned with the IFO's X-axis, parallel to the line formed by the GND T240 and PEM Guralp. I also attach a screen shot of the custom overview screen I created.
BSC1 and 3 gatevalve work in progress The extra viewport on BSC2 will be left in place IOT2 table to be moved to west side of HAM2 The north door will be pulled on HAM6 for ISI rebalancing wipe down and particle assessment beforehand Pumping vertex by noon HAM6: placing of fast shutter component today, remainder of work requires beam Peter K. is checking alignment on PSL table TCS: Started bonding polarizer Start work on X arm table after lunch, request for laser hazard in the afternoon ITMX optical lever work in the morning EE work in racks by HAM6 Hugh will be removing the ameristat at HAM4 Rai W. here to work on mirror charging experiment at end Y end Y will be transitioned to laser safe tiltmeter experiment underway at end X Kiwamu updating and restarting the ASC realtime model Praxair delivery to mid Y upgrade of conlog
model restarts logged for Mon 04/Aug/2014
2014_08_04 12:39 h1lsc
2014_08_04 12:42 h1lsc
2014_08_04 12:45 h1broadcast0
2014_08_04 12:45 h1dc0
2014_08_04 12:45 h1fw0
2014_08_04 12:45 h1fw1
2014_08_04 12:45 h1nds0
2014_08_04 12:45 h1nds1
no unexpected restarts. LSC ipc work plus related DAQ restart.
Sorry, got the dates wrong and skipped Sunday:
Sunday 3rd August: no restarts reported
Monday is actually the 4th of August.
[Jeff Arnaud]
Tonight we balanced the coils of the lower stages of MC2 SRM and SR2. The MC2 notes attached are explaining the procedure in detail. Below is summarized the ASD ratio after/before the exercise for each suspension and each level.
For some reason M3 stage of SR2 was harder to balance than the other ones, so we gave up on it for now and will come back to it later.
| SUS | STAGE | ASD RATIO before/after balancing | |
| PITCH | YAW | ||
| MC2 | M2 | 19.71 | 2.63 |
| M3 | 21.27 | 13.52 | |
| SRM | M2 | 9.95 | 38.53 |
| M3 | 6.96 | 3.8 | |
| SR2 | M2 | ||
| M3 | 107.7 | 5.12 | |
And the gains which were found optimum for each coils
| SUS | STAGE | OSEM | GAIN |
| MC2 | M2 | UL | 0.988 |
| LL | -0.992 | ||
| UR | -1.007 | ||
| LR | 1.012 | ||
| M3 | UL | 1.082 | |
| LL | -0.948 | ||
| UR | -1.051 | ||
| LR | 0.922 | ||
| SRM | M2 | UL | 0.935 |
| LL | -1.024 | ||
| UR | -0.971 | ||
| LR | 1.063 | ||
| M3 | UL | 0.972 | |
| LL | -1.014 | ||
| UR | -0.972 | ||
| LR | 0.964 | ||
| SR2 | M2 | UL | |
| LL | |||
| UR | |||
| LR | |||
| M3 | UL | 1.003 | |
| LL | -1.050 | ||
| UR | -0.951 | ||
| LR | 0.996 |
Measurements will be running overnight to measure the cross couplings transfer functions for SR2 SRM and MC2
There is a discrepancy in the text. While it says that SR2 M3 was not balanced however in the results table it is SR2 M2 the one blank. I can confirm that SR2 M2 is the one not yet balanced.
After BS and ITMY results, attached are itmx tfs ran over the week end, after doors closeout. During the measurement ISI was damped. Results look good. Lower stages show factor of two-ish discrepancy with model as Jeff pointed out.
1. Undamped H1 ITMX M0-M0 tfs compared with fiber model
2. Undamped H1 ITMX R0-R0 tfs compared with thincp model
3. M0 undamp R0 damp H1 ITMX L1-L1 tfs compared with fiber model
4. M0 undamp R0 damp H1 ITMX L2-L2 tfs compared with fiber model
4. H1 ITMX M0-M0 tfs compared with other ITMs
5. H1 ITMX L1-L1 tfs compared with Livingston's ITMX
6. H1 ITMX L2-L2 tfs compared with Livingston's ITMX
Data and scripts were commited to the svn
Today I have been working on porting the ESD Charging measurement automation scripts that Bryan Barr et. al. created at LLO. This has now been completed. I am adding some modifications to make the code more general. I have run the code over all the ESD quadrants on the only mass in vacuum (ETMY) and for several offset values with excitation signal at 4Hz and amplitude of 60000 and 120000 counts. The obtained analysis results did not make any sense so I looked the data more in detail and noticed that the oplev did not seem to be affected by the ESD driving signal. To be sure that I was not making any mistake I used awggui to excite the ESD in pitch and yaw such that they would excite the respective pendulum modes (at 0.56 and 0.6 Hz) identified here: https://awiki.ligo-wa.caltech.edu/aLIGO/Resonances/LHO. Nothing was observed on 'oplev'. Tomorrow I will have to verify that the ESD is actually physically connected.
LVEA laser safe 09:00 – FSS out of lock. Lowered the FSS resonance threshold to 0.3 from 0.4. Peter King will look into PSL alignment. 09:15 Nathan – Working in the optics lab 09:58 Greg – At BSC1 area working on laser barriers for CO2 laser alignment 10:01 Travis – Working on mobility experiment at HAM3 10:06 Betsy – General post chamber close cleanup in the LVEA 10:13 Gerardo – Working on viewport survey at BSC1/BSC2 area 10:55 Jim – Recycle mid-X weather station software 11:12 Peter – Going into H1-PSL enclosure to tweak ISS alignment/power loss 12:00 Power cycle restart of the camera monitor computer in the control room. 12:42 Kiwamu & Dave – Kiwamu update and restart LSC model. Dave restart DAQ 13:00 Bubba – End-Y working on deionizer installation 13:27 Bubba – Drilling bolt holes in floor at End-Y 13:47 Gerardo – Viewport survey in LVEA 13:52 Allister – At TCS-X to examine optics 14:10 Karen – Reported the emergency lights are on in the End-Y VEA 14:37 Doug & Jason – Working at the ITM-X manifold 14:52 Jeff & crew – At End-X 14:55 Alarm on corner station chiller pump #3. Pump tripped off. Informed John W. 15:25 Summer students – PEM work at End-X
Strange - another chilled water pump trip - this time in the corner. CWP3 VFD unit tripped. I reset the 480volt circuit (pushed the reset button, did NOT cycle the breaker).
The pump started up with no issues. Currently I have left the system with two CWPs and their associated chillers running. Both CWP1 and CWP3 are running. I happened to be in the control room when Jeff reported an alarm The LVEA is recovering from a ~0.5 F temperature excursion.
PSL Status: SysStat: Green Output power: 35.9w Frontend Watch: Good HPO Watch: Red PMC: Locked: 0 days, 0 hours, 28 minutes Reflected power: 4.9w Power Transmitted: 19.9w Total Power: 24.7w FSS: Locked: 0 days, 0 hours, 28 minutes Trans PD: 0.003v ISS: Diffracted power: 12.831% Last saturation event: 28 minutes
Rolf, Jim and Dave. We have created RCG tag 2.8.5 from branch 2.8. This version has the bug fix to disable the 18bit DAC Anti-aliasing chassis when the new timed DACKILL part is activated.
2.8.5 also has two dataviewer changes, these have already been installed at LHO by Jim prior to this release.
I have set the rcgcore and lho/h1 release pointers to use 2.8.5. All model builds from now on will use this release.
JimW JeffK HughR
We looked at HEPI TFs from March and this morning and see almost no differences. Comparing TFs beween EndY & EndX also sees almost no differences either.
However, see the attached comparing the Isolation filters at the endy (Blue) and endx (Red). Mag & phase both are quite different at our 8hz problem area.
Cleaning crew reports the emergency lights are on in the LVA at End-Y. Have informed John W. Will check if there is an open circuit breaker left over from Fridays power glitch.
Kiwamu and Dave. Installed new LSC model, then restarted the DAQ. We had an NFS caching issue, even giving a period of at least 15 seconds between the make-install and the restart, the model had cached the old INI file and we did not get the expected DAQ status of 0x2000. After verifying that the INI had indeed changed, we restarted the model once more and the new INI file was picked up by the model.
I have edited both /h1/models/h1lsc.mdl and /common/models/lsc.mdl. The motivation of this update is for us to keep up with Livingston's model.
Background:
Currently, the Livingston LSC model is completely disconnected from the common libraries and therefore it can be regarded as a prototype at this point. On the other hand, our Hanford model is more like a production model and therefore we use and maintain the common LSC libraries on the basis of the LLO prototype.
The modifications:
Discrepancies between the sites (as far as I know):
Also, I checked the connection of the new RFM recievers by sending some values from the end station over to the LSC model. And I confirmd that they are working fine. Both H1 and Common models are now checked in SVN.
J. Kissel, A. Pele Ran transfer functions over the weekend, to assess if the SUS is free after first contact removal and closing doors. While the top stages look great, this is the first time I've been exposed to a factor of two missing between model and measurement for the lower stages. While we don't expect the model to account for the dynamics of the reaction chain (which is why we see a whole bunch of "extra" features in the main-chain dynamics), we don't expect an overall gain mismatch. Arnaud informs me that this is true of every QUAD except one stage of one (including L1 SUS ITMY). No reason to pull doors off, but we should figure out where this discrepancy lies. And also , we should develop a model of the lower stage dynamics which include both chains.
The reaction chain will displace about the same amount as the main chain for the lower stage measurements. Could this explain the factor of two gain relative to the model, since the OSEMs measure the difference between chains?
HA !
Plausible. Let's model it to find out!
I added a feature to .../SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/generate_QUAD_Model_Production.m to compile a quad model with both main and reaction dynamics to predict what the L1 (UIM) and L2 (PUM) OSEMs will measure. See the results in the attached pdf. The overall gain is still not 100%, but is definitely closer. Pitch has some obvious mismatch due to known extra stiffness on the reaction chain (from OSEM cables I think). The update to generate_QUAD_Model_Production.m has instructions commented into the header for using the new combined main/reaction model. I copy those instructions here. " You can compile multiple chains simultaneously, to predict what the UIM (L1) and PUM (L2) OSEMs will measure. To use this feature, sandwich the string '_with_' between the two build types you want to use, main chain 1st, reaction chain 2nd. For example, for a monolithic ITM use buildType = 'fiber_with_thincp' The combined model will only combine the outputs for the UIM (L1) and PUM (L2) L, P, and Y DOFs, to reflect the OSEM measurements. The inputs however will be shared for all the seismic inputs as well as the UIM and PUM L, P, and Y DOFs. The indices for inputs and outputs are unchanged. Caution: there is no error or warning for non-physical combinations. For example, 'fiber_with_fiber' will compile OK, but the results will be inconsistent with reality. "
For future reference, attached are osems spectra from before the swap comparing top mass damping on / off
J. Kissel, J. Batch, Jim informed me this morning that other front-end models, seemingly unconnected to my h1isietmx model restart, had their framebuilder data corrupted immediately following my restart. Hence all frame data from these computers has been hosed since 2014-07-31 22:45 UTC. See Jim's complementary log here. The corruption is a result of an mxstream glitch sent out by h1isietmx upon restart, that was sent across the ethernet connection to other computers on the same ethernet network (i.e. h1sush2b, h1oaf, h1pemmy, h1pemmx, h1susey and h1lsc). This is a known problem at least by Jim (who will subsequently write a bugzilla report). To identify the problem: - Open CDS_OVERVIEW screen - Look for models / computers that have *both* the DAQ (Data AQuisition system) and the DDC (Daq Data Concentrator) showing red status in their CDS STATE WORD, (e.g H1:FEC-103_STATE_WORD). To solve the problem: - Log into corrupted front-end - run /etc/start_streamers.sh This reboots the mxstream process, occasionally glitches the framewriting PSL front end (?!), presumably fixes the problem, and restores the STATE WORD to green.
The old /etc/start_streamers.sh command may not be the best way. Instead use "sudo/etc/init.d/mx_stream stop", "sudo/etc/init.d/mx_stream start" so it starts the mx_stream on the correct 'mx' slot for the data concentrators's Myricom card - Of course, LHO may have been cleverer than I and re-wrote /etc/start_streamers.sh to do this
This plot is interesting. It seems the only moderately pronounced peak in the horizontal ground spectrum wanders, seen from 8 to 11hz changing quite rapidly.
The attached plot's current traces are with HEPI loops closed and the ISI Damped. While the middle graph shows all four local IPSs have the strong 8hz peak (the dashed REFs are with the HEPI loops open), the peak only shows in the X & Y and not the RZ cartesian traces (top graph). Also, note the bottom graph where the ground sensor pretty much has nothing at 8hz but does have a minor peak just above 9hz that is also peaking up in the local sensors.
The second plot shows just the ground Seismometer with X & Y traces from last night (Dashed) and the others from this morning. The peaks in that area come and go and wander around so it may or may not be a problem or just a red herring (are those edible?)
I am attaching the spectrograms for the X, Y, and Z directions of the STS Seismometer in ETMY. I used 19 continuing hours, starting 2014-07-22 01:00:00 UTC. There is a feature that is present all the 19 hours: Around 10.5 Hz in X direction. Around 9 Hz in Y direction. Around 10.5 Hz in Z direction. More features can be seen wandering along the 19 hours around 3-5 Hz and 8-10 Hz, for X, Y, and Z directions. In the spectrograms, each count is 1 nm/s /sqrt(Hz).
Continuing with the investigation on the 8 Hz, I am attaching the spectrograms for the X, Y, and Z directions of the GND STS in EY. Comments on the spectrograms: - Feature wanders between 7.5 to 12.5 Hz. - Depends on the time of the day. - It is present every 15 to 30 minutes. - Displacement amplitude higher than 2 nm. 6 hrs were used for each spectrogram, starting: - August 01, 2014 00:00:00 UTC (Figure 1) - August 01, 2014 06:00:00 UTC (Figure 2)
The 8 hz motion seen here is most likely related to the "pier resonance" Laura Nutall has a nice set of plots in the DCC https://dcc.ligo.org//LIGO-G1400820 which show this motion. Likely you are seeing the floor component of this motion. Rich M. has data showing that (at MIT) the slab bending is an important component of this motion
I investigated the GND SDS and PEM MIC channels using the coherence tool at 100mHz bandwidth and found several peaks between 5 and 9 Hz. I've attached some slides with zoomed-in plots.
