No new news here--Everyone chugging along. Attached is 40 days of the first pressure sensor on the Pump Station manifold and the control output to the motor.
Remarks: All four CS pumps have a perfect flatlined output (showing only one,) no this is not news. EX's excess noise continues in evidence, notice the ~15 days of quieter readings. At EndY, the daily and weekly glitches continue as before.
No indications of pump output loss.
Attached is a plot of the STS2's Mass Positions. Finally got them all centered (something below 5000cts)
Found that ETMY did not have the Binary I/O cable from the Bin Output to the STS2 Interface so this was not going to re-center remotely anyway. Vincent pulled that cable but we don't quite understand. I can tell you though that the recentering does not work via the medm/cable but the signal select and period select toggling does work... We've left that cable unplugged and did the centering at ETMY via the front panel button.
C. Cahillane I have constructed the uncertainty budget of LHO at GPSTime = 1135136350. The kappa values are given at 11546. Just a reminder on the differences between the calibration versions (according to me and my results): C00 = Sensing, Actuation, and Digital filters given by DARMmodel (I used the DARMparams from GPSTime = 1127083151) C01 = No kappa corrections, but static frequency dependence corrected. C02 = Kappa_tst and kappa_C corrected, as well as static frequency dependence corrected. Kappa_pu and cavity pole f_c NOT corrected. C03 = "Perfect" calibration, i.e. all kappas and static frequency dependence corrected. All comparisons between calibration versions have the C03 "Perfect" calibration in the denominator. C03 represents the best possible knowledge of the detector according to the calibration group. All others have some known systematic errors. For C01, strain magnitude uncertainty is below 7% and strain phase uncertainty is below 3.5 degrees. (See PDF 1 Plot 2) For C01, maximum strain magnitude error over C03 is 0.95 and maximum strain phase error over C03 is below 3 degrees. (See PDF 1 Plot 1)
Here are the trends of the PSL data froim the past 20 days. In reponse to Jeff K's request for more commentary on this data I have conversed with the expert(s) and Jason agreed to provide more analysis.
After reviewing the trends I posted yesterday I determined that the ITMy and SR3 oplevs needed re-centering. This is now complete. The old and new pitch/yaw values for these oplevs are below.
Old (µrad) | New (µrad) | |||
Pitch | Yaw | Pitch | Yaw | |
ITMy | -11.1 | -12.1 | -0.2 | 0.0 |
SR3 | -13.8 | +5.2 | -0.2 | -0.1 |
This completes LHO WP #5676.
I reset the PSL 35W FE watchdog at 17:33 UTC (9:33 PST).
Ops Owl Summary: 08-16UTC
State of H1: down for maintenance
Shift Summary:
10:20 Lockloss due to earthquake in the pacific.
12:30 Back up to observing
14:30 Lockloss from POP decay. Range was ratty, maybe due to bad alignment.
15:00 Start initial alignment. I had to touch TMSY to get the Y-arm back.
15:30 Richard to EX to work on webcam
15:45 JeffB to LVEA
J. Kissel, J. Warner Since the IFO is in such poor shape anyways with POP / alignment woes, I've suggested we just begin with calibration measurements needed for today. Jim has brought the acuiring IFO to DOWN, I'm heading down to the Y-End to begin measuring ETMY coil drivers, and the PCAL team should be in shortly and will go to the X-End to begin their standard calibration of the EX RX and TX PDs. Wish us luck!
Just got back to Observe after an earthquake in the Pacific knocked us down. Slightly more difficult than normal, as I lost lock a couple times at fairly high states (Engage ASC Part 3 and Coil Drivers). I noticed that every time I got to Engage ASC Part 3, the Y arm ALS power would start to drop. It would continue to roll off as I waited for ASC loops to converge. Might be an issue there.
LR behavior has changed over 150 days - trend attached.
Power spectrum of PR2 and SR2 to compare attached also.
I looked into the recent change in H1 behavior, with H1:LSC-POP_A_LF_OUT dropping, and causing lock loss, and see alignment changes that could be contributing to this issue.
The shifting IMs in HAM2 cannot account for alignment changes in the 150 day trend, so there is something else at work here.
Changes in yaw over 150 days:
Changes in pitch, comparing PRM to PR2 (different chambers)
The change in PR2 yaw of +51urad is significantly larger than the changes in the PRM pitch and yaw, and PR2 pitch.
The changes in PR2 yaw may be a response to the cumulative effects of the smaller changes seen in IM1, IM2, and IM3.
Changes in IM pitch:
The change is IM3 yaw of -26urad is significant;y larger than the changes in pitch or yaw in IM1, IM2, and IM3.
H1 out of Observe at 01:16:37UTC:
Lockloss at 01:35:56UTC:
Summary:
Ops Eve Summary: 00-08UTC
State of H1: locked in Observe, range is 74Mpc
Fellow: Keita
Shift Summary:
Executive summary:In regard to narrow lines, the (nearly) full O1 H1 data set is little changed from what was reported for the first week's data: a pervasive 16-Hz comb persists throughout the CW search band (below 2000 Hz), accompanied by a much weaker and more sporadic 8-Hz comb; there remain several distinct 1-Hz and nearly-1-Hz combs below 140 Hz, along with other sporadic combs. The 1459.5 hours of 30-minute FScan SFTs used here span from September 18 to the morning of January 3. The improved statistics make weaker and finer structures more visible than in the 1st week's data. As a result, many new singlet lines have been tagged, and it has become apparent that some previously marked singlets actually belong to newly spotted comb structures. The improved statistics also make it more apparent that the originally spotted combs span a broader bandwidth than marked before Details: Using 1459.5 hours of FScan-generated, Hann-windowed, 30-minute SFTs, I have gone through the first 2000 Hz of the DARM displacement spectrum (CW search band) to identify lines that could contaminate CW searches. This study is very similar to prior studies of ER7 data, ER8 data and the first week of O1 data, but for completeness, I will repeat below some earlier findings. Some sample displacement amplitude spectra are attached directly below, but more extensive sets of spectra are attached in a zipped file. As usual, the spectra look worse than they really are because single-bin lines (0.5 mHz wide) appear disproportionately wide in the graphics A flat-file line list is attached with the same alphabetic coding as in the figures. Findings:
In week 1 Keith identified a comb-on-comb (labeled K, see attached plot), fine spacing 0.08842 Hz, which shows up sporadically at around 77, 154, and 231 Hz. We found it in a large group of channels, centered at the INPUTOPTICS/SUS-BS/SUS-ITM (see full attached list). It remains clearly visible (especially at 77 Hz) in those channels until week 5 of O1, during which it disappears from all of them in all three regions (see attached example). Therefore, it seems likely that its presence in the full O1 data is an artifact from the first four weeks.
I recently re-analyzed this data while testing a comb-finding algorithm, and in the process found a new comb which accounts for several peaks marked as singlets in Keith's original post. This comb has a 2.040388 Hz spacing, with visible harmonics from 9th (18.3635 Hz) to 38th (77.5347 Hz). The code I used, and its docs, can be found on gitlab (requires login).
Activity Log: All Times in UTC (PT) 16:00 (08:00) Take over from Jim 16:59 (08:59) Christina & Karen – Going into the mechanical building to deliver supplies 17:25 (09:25) High temp alarm on CS Zone 1B. Will monitor. 17:55 (09:55) Out of Observing to try to improve power recycling gain 18:52 (10:52) Back into Observing mode 19:32 (11:32) Platt Electrical on site with a delivery for Richard 20:50 (12:50) LockLoss – POP_A_LF has been drifting down all morning despite the tweaking of PR2 21:00 (13:00) Start initial alignment and then on to relocking 22:00 (14:00) Travis – Going into the optics lab 22:02 (14:02) GRB Alert – LHO relocking so ignored alert 22:08 (14:08) IFO locked and back into Observing 22:22 (14:22) Travis – Out of the optics lab 22:44 (14:45) Travis – Going into optics lab 22:58 (14:58) Travis – Out of the optics lab 23:10 (15:10) Travis – Going into optics lab 23:15 (15:15) Travis – Out of the optics lab 00:00 (16:00) Turn over to Cheryl End of Shift Summary: Title: 01/04/2015, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT) Support: Sheila, Jenne, Kiwamu, Incoming Operator: Cheryl Shift Detail Summary: Problems with the POP_A_LF plagued the lock all morning. Went out of Observing for about an hour while Sheila and Jenne tweaked PR2. They were able to improve things a bit but it did not last for long. Finally, the recycling power dropped enough to break lock. Did an initial alignment and relocked the IFO. There were no problems with either alignment or relocking. The initial alignment did make some improvements the too POP_A_LF signal. However, the POP_A_LF signal is still a bit ragged; and has been drifting downward since the lock was reestablished. It is now just below the IMC-MC2_TRANS signal. The IFO is locked in Observing mode. Power is good, range is around 79Mpc. In general, environmental conditions continue to be good.
- 79% duty cycle at 75-80 Mpc, overall data looks quite clean
- a few lost locks due to earthquakes
- microseism stayed under 0.5 um/s
- no Omicron triggers for 2nd half of shift
- on Dec 28, ~20 Hz glitches occurred for most of the day, Hveto found ASC-CSOFT_Y_OUT_DQ to be responsible (possible scattering?)
full shift: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20151228
We have enough data now to convince ourselves that the manually set LLCV setting supplying LN2 is nearly matching the boil-off rate -> Gerardo over filled CP3 yesterday -> next over fill will be tomorrow, Tuesday Jan. 5th
Lost lock at 20:50 (12:50) due to the drop in power in POP_A_LF. Did an initial alignment and was able to relock the IFO on the first try. Back in Observing with 21.7W and 78Mpc. The POP_A_LF signal is still a bit ragged and is just above the IMC-MC2_TRANS signal.
I'm not sure what the significance of this is, or if there is any, but I looked at the pitch and yaw signals for the various optics for today's locklosses, it seems like the ITMY optical lever pitch has behaved similarly to the H1:LSC-POP_A_LF_OUT signal, which is believed to be responsible for our recent locklosses. I've attached two images, one for each lock today. There are many plots shown for the various pitch and yaw signals. The plots in the top right and bottom right are the ones I was interested in.
svn up at .../SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production
All current model features are summarized in a table in G1401132.
The main change in existing features is that the top mass damping now sees both the suspension and the cage, as in real life because we use OSEMs. Consequently, if you input seismic noise to a damped suspension it will enter both mechanically as usual, as well as through the damping loops. See Seismic_Noise_Propagation_2016_01_01.pdf. Page 1 shows longitudinal transfer functions from seismic noise to the test mass with and without the OSEMs seeing the cage. The second page shows the ratio of these transfer functions. Note that the ratio is greater than a factor of 2 at 4.5 Hz. Beyond 10 Hz the maximum is about 20% at about 10.5 Hz.
1. Additional inputs and outputs added to reflect the relative nature of the OSEMs - i.e. they measure relative displacements and actuate between two points
2. Suspension point reaction forces
The discussion above is one consequence of the first new feature. Another is that you can now make transfer functions between seismic noise and the top mass OSEMs, which is dramatically different from the seismic noise to top mass transfer function. See Seismic_to_Top_OSEMs_2016_01_01-2.pdf. These are obtainable in the model with the new 'toposem' field in the 'out' structure given by the generate_QUAD_Model_Production function.
The second new feature is that there are now outputs for the suspension point reaction forces on the ISI. These are obtainable in the model with the new 'suspoint' field in the 'out' structure given by the generate_QUAD_Model_Production function. These reaction forces allow us to dynamically couple the quad model to the ISI model. Thus, if we wanted, we can make one big ISI-SUS model.
This update includes significant under-the-hood modifications to how the pieces of the model are put together. Essentially, Simulink files now define the connections and signal flow, where previously this was all done with append/connect commands in the generate script. The motivation for this change is to make the model more extensible and maintanable by humans. The append/connect commands had become virtually unreadable with the dozens of inputs and outputs now in the model. Now someone can look at a more intuitive graphical representation in a simulink file to read or modify how the model is layed out.
There are 4 simulink files defining the 4 possible layouts of the quad model:
rev 7359: now reads foton files for main chain and reaction damping
rev 7436: Changed hard coded DAMP gains to get the correct values for LHO ETMX specifically.
rev 7508: Restored damping filter choice for P to level 2.1 filters as opposed to Keita's modification. Cleaned up error checking code on foton filter files, and allowed handling of filter archive files and files with the full path.
rev 7639: renaming lho etmy parameter file
rev 7642: Adding custom parameter file for each quad. Each one is a copy of h1etmy at this point, since that one has the most available data.
rev 7646: added ability to read live filters from sites, and ability to load custom parameter files for each suspension
rev 7652: updated to allow damping filters from sites from a specific gps time (in addition to the live reading option)
planned future revision - seismic noise will progate through the damping filters as in real life. i.e the OSEMs are relative sensors and measure the displacement between the cage and the suspension.
rev 7920: big update - added sus point reaction forces, top OSEMs act between cage and sus, replaced append/connect command with simulink files
no recent (at least 4 years) functional changes have been made to this file.
- rev 2731: name of file changed to quadopt_fiber.m, removing the date to avoid confusion with Mark Barton's Mathametica files.
- rev 6374: updated based on H1ETM fit in 10089.
- rev 7392: updated pend.ln to provide as-built CM heights according to T1500046
- rev 7912: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit. Same as h1etmy.m.
- rev 7640: created the H1ETMY parameter file based on the fit discussed in 10089.
- rev 7911: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit. Same as quadopt_fiber.m.
The quad model was tagged on the SVN both before and after this update. The tagged models are at
before this update: /ligo/svncommon/SusSVN/sus/trunk/Common/SusModelTags/Matlab/quadmodelproduction-rev7652_ssmake4pv2eMB5f_fiber-rev3601_fiber-rev7913_released-2016-01-01.mat This version reflects the model after the previous recent update discussed in log 24456, which updated the test mass and PUM inertias with solidworks values. No model features were changed in this update. After this update /ligo/svncommon/SusSVN/sus/trunk/Common/SusModelTags/Matlab/quadmodelproduction-rev7920_ssmake4pv2eMB5f_fiber-rev3601_fiber-rev7913_released-2016-01-01.mat
The tags were created using the following script:
/ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/tagsusdynamicalmodel.m rev 7923
Just as an FYI, I have done this svn update.
MInor updates and fixes:
1) The simulink files were generating warnings in Matlab 2012b because they were saved in 2013a. I resaved them in 2012b, recommited, and the problem has gone away. Matlab versions 2013a and 2015b are fine as well. No promises for versions earlier than 2012b.
2) While fixing the simulink diagrams, I added some extra inputs based on a disucssion with Brian Lantz. These are 'osem like' force inputs acting between the top mass and the cage for the purpose of testing the reaction force outputs on the ISI. These will not impact any prior features of the model.
The conlog process on h1conlog1-master failed soon after the UTC new year. I'm pretty sure it did the same last year but I could not find an alog confirming this. I followed the wiki instructions on restarting the master process. I did initially try to mysqlcheck the databases, but after 40 minutes I abandoned that. I started the conlog process on the master and configured it for the channel list. After a couple of minutes all the channels were connected and the queue size went down to zero. H1 was out of lock at the time due to an earthquake.
For next year's occurance, here is the log file error this time around
root@h1conlog1-master:~# grep conlog: /var/log/syslog
Dec 31 16:00:12 h1conlog1-master conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Duplicate entry 'H1:SUS-SR3_M1_DITHER_P_OFFSET-1451606400000453212-3' for key 'PRIMARY': Error code: 1062: SQLState: 23000: Exiting.
Dec 31 16:00:12 h1conlog1-master conlog: ../conlog.cpp: 331: process_cas: Exception: boost: mutex lock failed in pthread_mutex_lock: Invalid argument Exiting.
This indicates that it tried to write an entry for H1:SUS-SR3_M1_DITHER_P_OFFSET twice with the same Unix time stamp of 1451606400.000453212. This corresponds to Fri, 01 Jan 2016 00:00:00 GMT. I'm guessing there was a leap second applied.
of course there was no actual leap second scheduled for Dec 31 2015, so we need to take a closer look at what happened here.
The previous line before the error reports the application of a leap second. I'm not sure why, since you are right, none were scheduled. Dec 31 15:59:59 h1conlog1-master kernel: [14099669.303998] Clock: inserting leap second 23:59:60 UTC Dec 31 16:00:12 h1conlog1-master conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Duplicate entry 'H1:SUS-SR3_M1_DITHER_P_OFFSET-1451606400000453212-3' for key 'PRIMARY': Error code: 1062: SQLState: 23000: Exiting. Dec 31 16:00:12 h1conlog1-master conlog: ../conlog.cpp: 331: process_cas: Exception: boost: mutex lock failed in pthread_mutex_lock: Invalid argument Exiting.