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
The mid-X weather station stopped running about 22:36 PDT Saturday Aug. 2. Thunderstorms were reported in the area at the time. Will need to visit MX to determine what the problem is.
LVEA: Viewport and deionizer Gate Valve survey and work on LVEA in preparation to pump down. Gerardo found three Viewports with scratches that will need to be replaced. Kyle is doing a general readiness vacuum survey in LVEA. There will be a chamber close out checklist review in the control room today at 13:00. The Ameristat/C3 covers will need to be removed from around the HEIP piers at the BSC and HAM chambers. HAM6: The north door will be removed for alignment and ISI work. The ISC table to be reinstalled on the north side. OpLevs: Jason working on the X-Arm Viewports. EE: Cabling work at HAM6. End-Y: Work on Rai’s deionizer experiment equipment installation. End-X: Apollo to torque bolts on BSC9 door. Chamber close out review. Need to install gate valve for deionizer.
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
Restart mx_stream on the following front ends: H1sush2b - models h1iopsush2b, h1susim h1susey - models h1iopsusey, h1susetmy, h1sustmsy h1oaf0 - models h1iopoaf0, h1pemcs, h1oaf, h1tcscs, h1odcmaster h1lsc0 - models h1ioplsc0, h1lsc, h1lscaux, h1omc h1pemmy - models h1ioppemy, h1pemmy h1pemmx - models h1ioppemmx, h1pemmx The streams were corrupted by the model restart of h1isietmx on Friday Aug. 1 at 1545 PDT, so data from these models is likely not valid over the weekend.
Due to what Jim states in the above alog, the trend data of the ETMy SUS sensors is lost. Therefore, we are unable to look back at how the temperature excursion that happened at Ey over the weekend affected the position of the ETMy QUAD blades.
FSS out of lock and ISS cycling into and out of lock. Investigated with Sheila’s help, and found reference cavity power output has been dropping for the past month. Lowered the FSS resonance threshold to 0.3 from 0.4. Peter King will look into PSL alignment.
Features found on some of the viewports:
- (OL_HAM3) Optical lever for HAM3 In/Out, viewport type is a 9722012, see photo for missing material, missing material in two different areas.
- (OL_PR3) Optical lever for PR3 output, viewport type is a 9722012, see photo for scratch.
- (Video_MC3) Video for MC3 VP12, viewport type is a ZV-800, see photo for scratch.
- (no photo sorry) There is a viewport installed on G2 positon for BSC1 not on viewport document, currently a camera is installed there.
no restarts reported
John, Gerardo,
Gerardo was at LHO today inspecting viewports and while in the control room noticed temperature alarms at the Y end.
He found the chilled water temperatures to be way out of range (80F instead of 40F) He was able to start the second chilled water pump from the control room but unfortunately this did not start the second chiller as expected.
At the Y end chiller yard he was able to reset the second chiller and successfully start it.
Temperatures are now returning towards normal. The trip occurred Friday afternoon ~5:30. We will investigate next week.
Plot attached shows VEA temperature as well as the chilled water temperature.
model restarts logged for Fri 01/Aug/2014
2014_08_01 15:45 h1isietmx
2014_08_01 15:49 h1broadcast0
2014_08_01 15:49 h1dc0
2014_08_01 15:49 h1fw0
2014_08_01 15:49 h1fw1
2014_08_01 15:49 h1nds0
2014_08_01 15:49 h1nds1
no unexpected restarts. ISI model change and related DAQ restart.
[Arnaud P, Stuart A] Following closing up chambers, I've created new Guardian nodes for the remaining missing output arm suspensions, SUS_SRM and SUS_OMC, which have been verified to be operating correctly under Guardian control. Also, Guardian was paused for all suspensions while the chamber close-out work was being carried-out. Since, this is now complete HAM2, HAM3, HAM4, HAM5, HAM6 and X end suspensions have been transitioned to EXEC mode, and Gurdian will be monitoring for any Watchdog trips (see Guardian Overview Status attached below). n.b. measurements are now underway for ITMX. ITMY, and Beamsplitter over the weekend, so Guardian remains paused for these suspensions for now.
A set of clear Matlab TFs was taken for the top stage of ETMX (QUAD) earlier (see LHO aLOG entry 13134) and lower stage TFs were also taken over the previous evening, which have now been processed as follows:- - ETMX L1-L1 undamped (2014-08-01_1090929911_H1SUSETMX_L1_damp_OFF_ALL_TFs.pdf) - ETMX L2-L2 undamped (2014-08-01_1090938935_H1SUSETMX_L2_damp_OFF_ALL_TFs.pdf) BSC9 ISI Status: ISI damped and ST1 high isolation. ETMX alignment: No offset was applied during this measurement. The above TFs have been compared with equivalent measurements from QUADs at similar phases of testing (allquads_2014-08-01_Phase3a_H1ETMX_L*_Doff_ALL_ZOOMED_TFs.pdf), the plot keys are:- L1-L1 Blue Trace = Model Prediction. Orange Trace = H1 ETMY L1 (2014−04−12_1081392124), Phase 3a (in-air). Magenta Trace = H1 ETMX L1 (2014−08−01_1090929911), Phase 3a (in-air). L2-L2 Blue Trace = Model Prediction. Orange Trace = L1 ETMX L2 (2014−03−26_0900), Phase 3b (in-vacuum). Magenta Trace = L1 ETMY L2 (2014−04−23_0900), Phase 3b (in-vacuum). Cyan Trace = H1 ETMX L2 (2014−08−01_1090938935), Phase 3a (in-air). Summary: L1-L1, ETMX measured peaks reasonably agree with modeled peaks, and are consistent with ETMY, with the largest deviation occurring in the 2nd pitch mode. L2-L2, no measurements have yet been made for ETMY, so comparisons are made to L1 ETMX & L1 ETMY. Again, peaks generally agreement with the model and are consistent with other QUADs. n.b. there is still a factor of ~2 discrepancy in the DC scaling of the above results, as was also reported by Arnaud (see LHO aLOG entry 13128). All data, scripts and plots have been committed to the sus svn as of this entry.
Still getting Stage1 actuator trips on the ISI stage1 followed 6 to 8 seconds later by a HEPI actuator trip.
The HEPI will stay closed loop for as long as I'm patient and I've had the ISI in full isolation for periods of time. Sometimes the trips come shortly after the Stage1 of the ISI gets isolated and others it is when the stage2 is isolated. But the trip is always the same--that is: Stage1 Actuator followed byt the HEPI Actuators. These trips have an 8hz signal on them and the horizontal channels are overwhelmingly stronger than the verticals. I've been following spectra and TFs between HEPI & the ISI but can't find the link, yet. There is of course coherence between the HEPI Actuators and the ISI Stage1 sensors & actuators at the 8 hz peak. The radomness may be the dependance on the wandering ground motion... Still hunting
The Attached plot shows the problem peak in the position sensors which comes up with the HEP loops are closed; this seems independent of the ground noise but may be a problem when it wanders into the area.
J. Kissel As per ECR E1400262, and work permit 4764, I've created a new set of channels for the to-be-installed UWash Beam Rotation Sensor (BRS) in the top level of h1isietmx front-end model. This required re-compiling, re-installing, restarting, and restoring the h1isietmx front end process, and a restart of the data concentrator / frame builder / h1dc0 (restarted at 22:48 UTC). Again, because this is all at the top level, not library parts are affected, and I've committed the updated model to the userapps repo. I've also added two new channels to the frames, H1:ISI-GND_BRS_ETMX_RY_IN1_DQ H1:ISI-GND_BRS_ETMX_RY_OUT_DQ both stored at 256 [Hz], and only the OUT channel (which will be the calibrated channel) in the science frames. More details on the calibration once we get the sensor installed. MEDM screen also to come. I was able to restore the platform to fully isolated, managed by guardian, before handing over to Jim for over-night measurements.
BSC2
After respraying the BS optic with FC yesterday, we successfully pulled the FC sheets from both HR and AR surfaces of the the BS optic. After N2 blowing and some spot cleaning, we estimate particulate concentrations of 5-10 particles per square inch. We then reinstalled the elliptical baffles which had been removed for FC application, unlocked the SUS, and Jim unlocked the ISI. Quick TFs on the SUS were ran and approved, witness plate situated, and we moved to BSC1.
BSC1
The FC sheet removal from the external surfaces of ITMy went without issue. After N2 blowing, we estimate particulate concentrations of 5-10 particles per square inch on the external surfaces of both optics, and a factor of 2-3 higher on the internal surfaces. We unlocked both chains, Jim unlocked the ISI, quick TFs on the SUS ran and approved, witness plate and 1" optic installed, Betsy wiped her way out of chamber, and we handed it over to Apollo for door installation.
Particle count measurements were taken in BSC 1 and 2 numerous times during the ~2 hours of First Contact removal and chamber closeout on Friday. First Contact was pulled on the BS HR and AR surfaces around 12:30pm. FC was pulled on the ITMy HR, CP-AR around 1:45pm. BSC1 door was attached to chamber around 2:30.
Counts were always around:
0.3um ~200
0.5um ~60
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.