Tried clearing MC1, MC2 and MC3 PIT/YAW WFS history. Not sure if this is still an earthquake problem. 0.03 - 0.1 Hz seismic band is still above .1 um/s.
Wind is low and microseism is high.
TITLE: "11/06 [EVE Shift]: 23:00-07:00UTC (16:00-00:00 PST), all times posted in UTC"
STATE Of H1: Lock Acquisition
SUPPORT:
SHIFT SUMMARY: The ifo is down due to earthquake(s).
INCOMING OPERATOR: Patrick
ACTIVITY LOG:
00:38 LLO called saying they will be "sweeping" for another 10 minutes. Robert has already gone to make injection in LVEA. Both sites out of Observing.
00:48 LLO done
00:57 Robert done. Back to Observing.
07:28 Lockloss. See alog23172
TITLE: 11/07 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC STATE Of H1: Lock acquisition. Recovering from earthquakes. OUTGOING OPERATOR: Nutsinee QUICK SUMMARY: From the cameras the lights are off in the LVEA, PSL enclosure, end X, end Y and mid X. I can not tell if they are off at mid Y. Earthquake seismic band is above 1 um/s. Microseism has been increasing over last 10 hours and has recent jumps above 1 um/s. Winds are ~ 0 - 5 mph. ISI blends are on Quite_90.
We just had several big earthquakes. The one that dropped us (and Livingston) out of lock was probably the 5.6M in Venezuela (the R-wave arrival time reported in Terramon matched our lockloss time). Shortly after we had another 5.8M in Chile, 4.8 in Venezuela, and another 6.8 in Chile. The seismic activity in the EQ band has already reached 1um/s and continues to increase. Relocking probably won't happen for at least another half an hour.
Livingston reported that they were locked for about 69 hours and 20 minutes before the earthquake(s) took them down. We have a new record to beat!
NOTE: This entry is related to 22847 and 22959
This entry is a summary of the 3rd and 4th harmonic frequencies of the QUAD suspensions violin modes. The frequency identification was done through 2 stages;
1) First looking at a 1mHz resolution spectrum of channel H1:OMC-DCPD_SUM_OUT_DQ on 10800 seconds from 2015-10-28 12:00:00 (before the test mass injections described in 22959), total of 20 averages and 50% overlap. See plots attached. This gave a first approximate value of the frequencies.
3rd harmonics (32 modes identified): Attached file: '3rd_Harmonics_from_Spectrum.txt'
4th harmonics (30 modes identified): Attached file: '4th_Harmonics_from_Spectrum.txt'
2) Second, feed the above frequencies to a line tracker (iWave) for a more accurate identification and over different data. In particular 21 hours of data with detector in Observing mode and with damping filters turned off, from 2015-10-21 21:30:00
3rd harmonics (22 modes identified, notice that the reason for the smaller number of modes being identified is the automation applied to the line tracker in order to be able to process the big number of modes being tracked over a long data stream. For this reason the line tracker sometimes locked to the wrong mode of higher amplitude and or was not able to separate modes of high amplitude and proximity. The number of modes identified may improve by more targetted application of the tracker): Attached file: '3rd_Harmonics_from_LineTracker.txt'
4th harmonics (25 modes identified): Attached file: '4th_Harmonics_from_LineTracker.txt'
For reference, here are the compilations of tentative 3rd/4th quad harmonic frequencies from 104.5 hours of early O1 data, using 0.5-mHz binning: Q 1456.1793 1.109279e-18 ******* Q 1456.8448 4.093626e-19 ***** Q 1461.4125 3.152596e-19 ***** Q 1461.7318 1.663059e-17 ********** Q 1461.8627 2.275449e-19 ***** Q 1462.0311 9.120542e-17 ************ Q 1462.3129 1.442451e-16 ************* Q 1462.5991 1.951920e-18 ******* Q 1463.0994 1.613099e-17 ********** Q 1467.4759 9.898746e-18 ********* Q 1467.9648 1.940260e-16 ************* Q 1470.3809 7.576511e-17 ************ Q 1470.8263 1.099916e-16 ************* Q 1471.9279 1.821525e-16 ************* Q 1472.4505 9.761998e-17 ************ Q 1472.5268 7.321176e-18 ********* Q 1474.0800 1.401120e-16 ************* Q 1475.0976 3.710737e-17 *********** Q 1475.2510 2.168896e-16 ************** Q 1476.3779 4.452248e-18 ******** Q 1478.1701 2.011867e-16 ************* Q 1478.6459 2.489583e-18 ******** Q 1482.5840 6.298267e-16 *************** Q 1484.0765 3.847696e-16 ************** Q 1484.4293 7.193998e-18 ********* Q 1484.5241 2.194240e-16 ************** Q 1484.5731 1.033684e-17 ********** Q 1484.6685 2.331379e-16 ************** Q 1922.9259 4.402502e-18 ******** Q 1923.6124 2.213001e-17 *********** Q 1923.8550 3.272046e-18 ******** Q 1923.8610 1.089465e-17 ********** Q 1924.6739 2.196115e-17 *********** Q 1924.9150 1.129535e-17 ********** Q 1926.2402 9.830786e-17 ************ Q 1927.4652 5.627035e-18 ********* Q 1927.4662 5.627035e-18 ********* Q 1928.4620 1.166487e-17 ********** Q 1929.3128 2.991775e-18 ******** Q 1931.5738 2.536072e-18 ******** Q 1932.1391 1.111758e-17 ********** Q 1932.3359 3.306404e-17 *********** Q 1932.6117 3.029987e-17 *********** Q 1940.3232 3.044162e-18 ******** Q 1940.6643 2.881532e-17 *********** Q 1941.3501 9.968986e-17 ************ Q 1942.1270 1.072596e-18 ******* Q 1942.1751 6.163310e-17 ************ Q 1942.3900 6.222474e-17 ************ Q 1943.7780 1.641306e-17 ********** Q 1944.1332 3.131086e-18 ******** Q 1946.7318 4.684879e-17 ************ Q 1947.7089 1.957731e-18 ******* Q 1954.4574 1.942626e-17 ********** Q 1955.9208 2.102610e-17 ********** Q 1957.3347 3.023210e-17 *********** Q 1959.0215 4.312900e-17 *********** where the 2nd number is the inverse-noise-weighted average displacement ASD, and the asterisks are a crude log-scale depiction of the ASD value. This table is a subset of this earlier alog attachment: https://alog.ligo-wa.caltech.edu/aLOG/uploads/21982_20150926195339_Lines_H1-CAL-DELTAL-EXT_O1-week1.txt Although the frequencies are given to 0.1 mHz precision, I have seen them vary in the past by as much as a few mHz over months time scales.
Thank you Keith. I was aware of this frequency list however I noticed that several modes were missing. In principle if mode frequencies do not overlap then we should expect 32 modes per harmonic. In my manual check of the 3rd harmonic frequencies I identified 32 frequency candidates with a few others of small amplitude. In comparison with your list I can confirm that your list misses several 3rd harmonic modes:
There are two very close modes at 1463.097 and 1463.101 Hz, your list only identifies one mode from this pair at 1463.0994Hz. Also your list misses the mode at 1472.217Hz.
In relation to the 4th harmonic: Your list shows a repeat peak at 1927.465Hz, although it assigns a 1 mHz difference between the 2 peaks the amplitude is identical so it looks as if it is actually a single peak.
Notice that the main reason of my analysis is not just to identify the violin mode frequencies but to actually measure their Q (through exponential decay) which I will report in another aLog which I am writting at the moment.
UPDATE ON ORIGINAL ENTRY:
Some of the peaks I originally identified as 3rd and 4th harmonics from the 1mHz resolution spectrum plots are not violin modes, as verified after careful analysis of their exponential decay with a line tracker (iWave).
3rd harmonic identified modes: 30 with Spectrum of 1mHz resolution, the line tracker locked properly to only 25.
4th harmonic identified modes: 26 with Spectrum of 1mHz resolution, the line tracker locked properly to only 25.
For completion I provide next the frequencies of the identified modes, on a table of 3 columns, the first column are the frequencies given by Keith, the second column are the frequencies as per the 1mHz spectrums shown in this entry and the third column are the median frequency tracked by a line tracker on 21 hours of data. The zeros are missing information from each list:
Keith_table 1mHz_res_spectrum Line_tracker_21hours_data
1.0e+03 *
1.456179300000000 1.456180344722471 1.456177151198640
1.456844800000000 1.456847712651581 1.456842618595428
1.461412500000000 1.461413707108750 1.461409317387718
1.461731800000000 1.461733620917401 1.461732469282266
1.461862700000000 1.461861606048793 1.461859532596437
1.462031100000000 1.462032270322383 1.462031865574721
1.462312900000000 1.462313909933999 1.462313301797892
1.462599100000000 1.462599872305624 1.462596623730558
1.463099400000000 1.463097080131224 1.463096689345246
0 1.463100546759006 1.463100039151534
1.467475900000000 1.467476228900213 1.467475846153371
1.467964800000000 1.467965366395409 1.467964868969873
1.470380900000000 1.470381699013083 1.470380789546349
1.470826300000000 1.470827285183412 1.470826225123052
1.471927900000000 1.471929276656110 1.471928631371064
0 1.472217057788634 1.472216372878212
1.472450500000000 1.472451085888389 1.472450299085779
1.472526800000000 1.472528816242792 0
1.474080000000000 1.474080396944674 1.474079862541953
1.475097600000000 1.475099020030272 1.475097416001178
1.475251000000000 1.475252651191380 1.475251394384721
1.476377900000000 1.476379150480257 0
1.478170100000000 1.478170077745102 1.478169573722027
1.478645900000000 1.478646456410533 0
1.482584000000000 1.482587879011576 1.482585385731902
1.484076500000000 1.484082047455499 1.484077440343936
1.484429300000000 1.484431224630876 0
1.484524100000000 1.484525638863272 1.484525699339724
1.484573100000000 1.484573390876472 0
1.484668500000000 1.484669984871669 1.484668763161195
1.922925900000000 1.922927022647360 1.922925588791648
1.923612400000000 1.923613112500675 1.923612097950808
1.923855000000000 1.923855111277119 1.923854588725318
1.923861000000000 1.923862018275805 1.923861256988942
1.924673900000000 1.924674100071188 1.924673358918374
1.924915000000000 1.924915873423103 1.924914735873632
1.926240200000000 1.926241192663720 1.926240582396548
1.927465200000000 1.927466117175330 1.927465533945791
1.927466200000000 0 0
1.928462000000000 1.928465010303079 1.928461858686449
1.929312800000000 1.929315906067996 1.929312798521826
1.931573800000000 1.931575488954602 1.931573475268973
1.932139100000000 1.932140403468284 1.932139817442099
1.932335900000000 1.932335886291686 1.932335653144635
1.932611700000000 1.932611738162179 1.932612502374920
1.940323200000000 1.940327437428355 1.940322842326236
1.940664300000000 1.940668395302165 1.940663844123977
1.941350100000000 1.941355862583405 1.941349656248626
1.942127000000000 0 0
1.942175100000000 1.942176424197661 1.942174876991754
1.942390000000000 1.942391628419225 1.942390477296026
1.943778000000000 1.943779225301499 1.943777686818187
1.944133200000000 1.944135400000000 0
1.946731800000000 1.946734993919390 1.946732788506648
1.947708900000000 0 0
1.954457400000000 1.954461746453794 1.954459288744910
1.955920800000000 1.955924562578534 1.955921817650888
1.957334700000000 1.957335449254732 1.957335075248596
1.959021500000000 1.959024110148374 1.959023577426715
Quiet evening so far. Tidal oscillates frequently -- likely due to the increasing microseism.
During the down hour, I made shaker injections at HAM1 and IOT2, and made the following site activity injections:
Injection |
Time of first injection, UTC |
Injection spacing |
Total number of cycles |
Good channels for environmental signal |
|
Nov. 7 |
|
|
|
RFID on/off main LVEA entrance; first is off |
00:04:00 |
15s |
7 |
H1:PEM-CS_MAG_LVEA_INPUTOPTICS H1:PEM-CS_MAG_EBAY_LSCRACK |
Optics lab -X cleanroom on/off, first is on, other clean rooms on |
00:11:00 |
10s |
9 |
H1:PEM-CS_MAG_LVEA_INPUTOPTICS H1:PEM-CS_ACC_PSL_PERISCOPE |
Optics lab -X cleanroom on/off, first is on, other clean rooms off |
00:16:00 |
10s |
9 |
H1:PEM-CS_MAG_LVEA_INPUTOPTICS H1:PEM-CS_ACC_PSL_PERISCOPE |
Electric cart driving on ramp at OSB shipping |
00:22:00 |
5s |
6 |
H1:ISI-HAM6_BLND_GS13 |
RFID on/off, Hi-Bay entrance, first is on |
00:30:30 |
15s |
6 |
H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS |
Good news. None of these injections showed up in DARM. Most didn't even show up on the PEM channels (only the electric cart seems to make some noise in HAM6 GS13). The card reader is expected to make a line at ~10Hz, the cleanroom fan is expected to show up any where between 15-30 Hz, and the electric cart on ramp (and bumbs) is expected to show up in the seismometer between 0-100Hz. Attachment #1 - #5 shows DARM spectrogram during the time of different injections. Attachment #6 - #14 shows PEM and HAM6 GS13 (for electric cart on ramp) channels. Every spectrogram is plotted +/-10s before and after the time of the injections. The spectrum of PEM (and GS13) channels at higher frequency can be found here. The Omega scan at the time of each injection can be found here. Look for the scans that were generated on Nov7.
When both sites went out of Observing I was going to take the opportunity to do some violin mode damping. However, we were ready to go on Observing before I get to damp anything (I didn't even finish making the filter). The modified filter bank is ETMY L2 DAMP MODE4 FM7 and FM8 (BP and -60deg). This frequency however was already damped by MODE10 filter bank but hasn't been included in the violin mode table. I will edit the table accordingly.
TITLE: "11/06 [EVE Shift]: 23:00-07:00UTC (16:00-00:00 PST), all times posted in UTC"
STATE Of H1: Observing at ~ 80Mpc
OUTGOING OPERATOR: Ed
QUICK SUMMARY: LLO was down for some commissioning. Robert took the opportunity to do some injection on HAM1. Wind ~5mph. EQ band seismic activity slowly increase and now cruising between e-2 and e-1 um/s. Microseism is crossing over the 50th percentile line.
While looking at our PRC gains as a function of time, I noticed that yesterday we had a very abnormal lock. The lock between approx 01:30-10:00 UTC on 5 Nov 2015 sees a slow drift where we slowly lose power buildup over time, and lose lock when we have lost about 10% of the power buildup. The IM4 Trans PD doesn't see the power drift, so it's not anything to do with the IMC or anything upstream of that.
All 3 power recycling optics see some drift (as seen by their M3 witness sensors), as do the ETMs (as seen by their oplevs). This is the same lock that SR3 had its problem where I hand-offloaded pitch from M2 to M1 (aLog 23128), but it doesn't look like that drift lines up with the power drift very well. Anyhow, I'm not sure what started drifting and why, but it looks like all of these optics' ASC controls are pushing them around to try to fix the drift, perhaps?
Our locks since this one have been fine, and look totally normal, so I'm not sure that there's a persistent problem that we need to fix, but this seemed worth noting.
The first plot shows the power drift in POP and a Transmission PD, as well as the optic alignments of most of the optics, and the second plot has another few alignment traces, as well as the SR3 cage servo output.
TITLE: Nov 6 DAY Shift 16:00-00:00UTC (08:00-04:00 PDT), all times posted in UTC
STATE Of H1: Observing
SUPPORT: N/A
LOCK DURATION: ≈5 hrs
INCOMING OPERATOR: Nutsinee
END-OF-SHIFT SUMMARY: There was a mysterious lockloss ≈7 hrs ago and I had some trouble re-locking (see activity log). After that, smooth sailing. Handing off to Nutsinee.
ACTIVITY LOG:
17:02 Robert into LVEA to install shaker
16:57 LockLoss
17:30 went 20 minutes trying to get PRMI locked. Ditched and went to initial alignment
17:56 Chris called to tell me he was leaving in a few to go doen X-Arm to do beam tube work. Joe will accompany.
18:15 First attempt at relocking failed. Problems with Y-arm and diff vco. Re-visited Y arm alignment. H1:SUS-ETMY_M0_LOCK_Y_OUT16 took a rather long time to decide where it wanted to settle down.
19:00 OMC locked on wrong mode: After playing with OMC guardian and LOCK_00, then tripping the OMC watchdog and having to request align a few times, I got OMC back locked on the proper mode. 19:18 NOTE TO SELF: make sure that after manually locking OMC to advance the OMC Guardian node to “READY_FOR_HANDOFF” before manually pushing DC_READOUT. D’OH!
19:58 Re-locked at NLN
20:01 set intent bit to Undisturbed
00:00 Set intent bit to Commissioning for Robert to do some injections. This is being done in cooperation with Livingston.
NOTE: We tested 2-way radio (walkie/talkies) between 1420 - 1430 hrs. local
This week we were able to install and caulk metal strips on the upper portion of 120 meters of enclosure.
Total of 36.55 hours of OTL dues to faults during month of October 2015.
ID▼ | Product | Comp | Observation Time Lost (Hours) | Status | Resolution | Summary | Assignee | Opened | Changed |
---|---|---|---|---|---|---|---|---|---|
3928 | LLO Detector Enginee | general | 2.50 | NEW | --- | Alignment script issues, ITMY misalignment and REFL WFS trigservo loop not running | adam.mullavey@LIGO.ORG | Wed 06:39 | Wed 12:37 |
3926 | LLO Operators | general | 1.00 | CLOSED | PROCEDURAL | Lock loss due to a CHARD excitation | gary.traylor@LIGO.ORG | Tue 19:28 | 13:39:07 |
3925 | LLO Operators | general | 1.00 | NEW | --- | Lock Loss due to aborting a measurement of (swept sine excitation) using DTT . | gary.traylor@LIGO.ORG | Tue 16:15 | Tue 16:21 |
3922 | LLO Detector Enginee | general | 0.25 | WORKINPROGRESS | --- | Restarting the Guardian machine causes both ETM ISIs to trip. | arnaud.pele@LIGO.ORG | Tue 13:21 | 10:57:44 |
3916 | LLO Detector Enginee | general | 0.10 | WORKINPROGRESS | --- | Suspensions tripping | arnaud.pele@LIGO.ORG | Mon 15:39 | Wed 09:28 |
3895 | LLO Facilities | general | 2.50 | CLOSED | UNAVOIDABLE | Power glitch - around 8:35PM local time | timothy.nelson@LIGO.ORG | 2015-10-28 | 02:35:34 |
3863 | LLO Detector Enginee | general | 2.20 | CLOSED | UNRESOLVED | Difficulties Locking Input Mode Cleaner (IMC) due to l1sush2a front-end DACKILL issue | janeen.romie@LIGO.ORG | 2015-10-23 | Wed 15:30 |
3860 | LLO Detector Enginee | general | 0.50 | CLOSED | DUPLICATE | l1ecatc1 Beckhoff lost communication again | janeen.romie@LIGO.ORG | 2015-10-23 | 2015-10-24 |
3846 | LLO Detector Enginee | general | 9.00 | CLOSED | UNRESOLVED | TR CARM to TR REFL9 transition | janeen.romie@LIGO.ORG | 2015-10-22 | 2015-10-23 |
3830 | LLO Detector Enginee | general | 0.10 | CLOSED | RESOLVED | Tidal Servos | janeen.romie@LIGO.ORG | 2015-10-21 | 2015-10-26 |
3828 | LLO Detector Enginee | general | 0.50 | CLOSED | UNRESOLVED | ETMY ESD LVLN binary control mismatch | janeen.romie@LIGO.ORG | 2015-10-20 | 2015-10-22 |
3825 | LLO Detector Enginee | general | 1.50 | CLOSED | PROCEDURAL | ALS Laser head crystal frequency | adam.mullavey@LIGO.ORG | 2015-10-20 | 2015-10-23 |
3823 | LLO Detector Enginee | general | 3.00 | CLOSED | RESOLVED | Frontend laser tripped over the weekend | matthew.heintze@LIGO.ORG | 2015-10-20 | 2015-10-23 |
3808 | LLO Detector Enginee | general | 3.00 | CLOSED | RESOLVED | ALS-Y pitch oscillating | adam.mullavey@LIGO.ORG | 2015-10-17 | 2015-10-23 |
3796 | LLO Detector Enginee | general | 0.25 | PENDING | --- | Intent bit state change | stuart.aston@LIGO.ORG | 2015-10-15 | 2015-10-22 |
3793 | LLO Detector Enginee | general | 2.00 | CLOSED | RESOLVED | BS OpLev Sum below Guardian threshold | stuart.aston@LIGO.ORG | 2015-10-14 | 2015-10-16 |
3747 | LLO Detector Enginee | general | 2.50 | CLOSED | RESOLVED | Marginal CARM gain | adam.mullavey@LIGO.ORG | 2015-10-06 | 2015-10-16 |
3744 | LLO Detector Enginee | general | 11.00 | CLOSED | RESOLVED | ALS Y PZT-QPD servo instability | adam.mullavey@LIGO.ORG | 2015-10-05 | 2015-10-20 |
3928 is marked as new. ITMY did not misalign as requested by the script. PR2 and IM4 alignment REFL WFS not running. This is still being investigated.
3926 is marked as closed procedural. This fault was due to a human error. The actuation amplitude was too strong in the template and will be reduced to avoid this in the future.
3925 is marked as new. The interferometer broke lock when aborting a measurement of the CHARD P open loop (swept sine excitation) using DTT. This is still being investigated.
3922 is marked as work in progress. To avoid Guardian nodes from hanging, it is now standard operating procedure to reboot the Guardian machine following a DAQ process restart, which is scheduled weekly at the end of the Tuesday maintenance period. However, there is a concern that there is a potential that this could re-occur should we need to restart these vulnerable Guardian nodes while the IFO is locked, resulting in a lock loss and more significant down-time. This is still being investigated.
3916 is marked as work in progress. Suspensions WD can trip during an alignment and be set to bad positions. Audible alarms should be set to avoid missing a suspension or SEI that tripped. These are not yet set up.
3895 is marked as closed unavoidable. Effect of glitch was limited i.e PSL tripped but Front Ends did not. Recovery from power glitch was very smoothly done by LLO staff
3863 is marked as closed unresolved. Alarms handlers have been set for operators to be informed should this issue arise again. We may wish to consider options for implementing something in Guardian.
3860 is marked as closed duplicate of Fault Report 3141 - MASTER: Beckhoff communication issue. We will monitor for a reoccurence
3846 is marked as closed unresolved. For some reason performing this transition only worked at a smaller CARM offset . It's not clear what necessitated this change. We will monitor for a repeat occurence.
3830 is marked as closed resolved. The settings were not saved correctly under the safe snap file which was restored during the model restarts -cf https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=21832-. The safe snap file has been corrected to prevent a repeat occurence.
3828 is marked as closed unresolved. Don't know what the root cause is yet. A note on a work around procedure has been added to the Operator Wiki. We will monitor for a repeat occurrence
3825 is marked as closed procedural. This was an OOPS. Detector engineers miscommunicated interaction between PSL work and affect on ALS. Awareness has been shared which should prevent a reoccurrence
3823 is marked as closed resolved. This resulted in two action items one to look into widening control limits on the front end watchdog which is programmed so that it trips at 15% loss of power from when it was activated and the other to close training gap on single operator on PSl restart procedure.
3808 is marked as closed resolved. Required spare PZT controller to be installed. Root cause of the failure of the controller is still under investigation and being monitored for a repeat occurrence.
3796 is marked as pending. This is not likely to be addressed until a future RCG update, and so it was recommended that we turn off monitoring of DACKILL channels in IOP models until the fix is available.
3793 is marked as closed resolved. The BS OpLev Guardian settings were widened which should prevent a reoccurrence
3747 is marked as closed resolved. The ISC_Lock Guardian has been modified which should prevent a reoccurrence
3744 is marked as closed resolved. We will monitor for a reoccurence
RF45 has been quiet since I and Evan made an investigation last time (alog 23125).
One thing we didn't do in the PSL room was to wiggle/tap the EOM inductor box and its connectors. Next time it acts up, we should try that. FYI, inductor box is the top part of EOM assembly that accepts the cable from EOM driver, and is connected to the lower part where the crystal sits by now infamous DB15.
Lost lock about 2 hours ago, not sure why. Trying to relock now, but DRMI is not cooperating. Otherwise, things are quiet. Winds down, useism is down. RF45 has not been awful.
Not sure what the cause of the power drift / alignment drift was, but it looks like we may have lost lock when the power recycling gain dropped below 33.5-ish. See aLog 23164 for some plots and details.
J. Kissel, K. Izumi, N. Kijbunchoo We've gathered new DARMOGLTF measurements to continue our long-term investigating on the slow evolution of the calbriation parameters. Based on what I see in DTT alone, the uncorrected loop gain and pcal to CAL-CS transfer function remains within 5% and 5 [deg] of the reference model. Very good! I attach screen shots of the raw measurements and a conlog of the relevant settings, but more detailed analysis to come. The new DTT results live here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs/2015-10-28_H1_DARM_OLGTF_7to1200Hz.xml /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/PCAL/2015-10-28_PCALY2DARMTF_7to1200Hz.xml and have been exported to the following: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs 1 / (1 + G) = 2015-10-28_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_coh.txt 2015-10-28_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_tf.txt -G = 2015-10-28_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_coh.txt 2015-10-28_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_tf.txt /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/PCAL/ C / (1 + G) = 2015-10-28_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_coh.txt 2015-10-28_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_tf.txt
Sudarshan, Darkhan, RickS
Using data from the SLM tool for 67 minutes just before the measurement of the Pcal2Darm TF, we calculated the TF for the 1 kHz and 3 kHz Pcal lines.
The plots attached below show:
1) The "kappas"
2) The measured TF, with coherence and the fractional uncertainty
3) The data for the 1 kHz line and comparison with TF values interpolated from the measured TF data
4) The data for the 3 kHz line
At 1 kHz, the transfer coefficient calculated from the SLM data differes from the interpolated coefficient from the meassured transfer function by 1.01% in amplutude and 0.15 deg. in phase.
The script and plots will be submitted to the SVN tomorrow and I will add a comment giving their location when they are.