david.barker@LIGO.ORG - posted 08:51, Friday 04 September 2015 (21208)
CDS model and DAQ restart report, Thursday 3rd September 2015
ER8 Day 18, no restarts reported.
ER8 Day 18, no restarts reported.
Per request by Robert Schofield, I am lowering the air flows in the LVEA to allow him to preform his injections. These will be going down from ~15000 CFM to ~11000 CFM. Since the weather is cooling down, I will leave these flows at this rate until something or someone convinces me otherwise.
12:45 UTC Christina here 12:51 UTC Karen here More SUS ETMY saturation alarms. Most if not all were coincident with glitches in the spectrum. List of all from verbal alarms script: SUS E_T_M_Y saturating (Fri Sep 4 8:13:12 UTC) SUS E_T_M_Y saturating (Fri Sep 4 8:28:3 UTC) SUS E_T_M_Y saturating (Fri Sep 4 8:28:5 UTC) SUS E_T_M_Y saturating (Fri Sep 4 10:40:16 UTC) SUS E_T_M_Y saturating (Fri Sep 4 10:51:18 UTC) SUS E_T_M_Y saturating (Fri Sep 4 11:15:5 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:10:24 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:10:26 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:10:28 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:10:30 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:47:13 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:47:26 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:47:29 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:48:39 UTC) SUS E_T_M_Y saturating (Fri Sep 4 13:24:44 UTC) SUS E_T_M_Y saturating (Fri Sep 4 13:24:46 UTC) SUS E_T_M_Y saturating (Fri Sep 4 14:44:33 UTC) Nice quiet shift otherwise. H1 remains in observing mode around 70 Mpc. Handing off to Corey.
A scheduled burst hardware injection was done early this morning, at GPS 1125390500 = Sep 04 2015 01:28:03 PDT, that was extremely loud. It was detected by Coherent WaveBurst (see https://gracedb.ligo.org//events/view/G181472) and also produced several MBTA triggers that were inserted into GraceDB, with (inferred) coalescence end times up to 37 seconds later. I have removed all future burst injections from the tinj schedule file so that no more will be done until we sort this out and make sure that future injections will have reasonable amplitudes.
Received H1 locked and in observing mode from Cheryl. Cleaned up control room. If you are missing something check the cardboard box on the floor behind the computers to the left as you come in. Checked IP9 as requested by Gerardo. High Voltage is around 7 kV for both A and B. Moved cameras looking in PSL enclosure to see that they were not frozen. Lights are off in PSL enclosure. Moved cameras in LVEA to point to doors. Lights are on in LVEA. Lights appear to be off at all mid and end stations, but I don't entirely trust those cameras. I don't seem to be able to move end X. mid Y is constantly flickering green horizontal lines. Darkhan and Sudarshan were the only people left in the control room after Cheryl left. 08:07 UTC Darkhan and Sudarshan leaving. I'm all alone. 08:13 UTC I shut down all of the workstation computers in the control room except the ops station. 08:38 - 08:44 UTC I stepped out to use the restroom. SUS ETMY voice saturation alarms at: 08:13:12, 08:28:03, 08:28:05, 10:40:16, 10:51:18 UTC. Have caused glitches. H1 remains locked slightly below 70 Mpc.
- Quiet night in terms of locking.
- Most of the night dedicated to PEM injections.
- One lock loss due to injections (PEM).
- Relocking went pretty well, with the biggest thing being that I had to reset the EX ALS VCO (on the VCO screen).
- Transient injections are again enabled.
- Only ~9 hours of lock time during the 3 days
- Low glitch rate during lock time
- 60 Hz magnetic glitches showed up again at EY
- 2 interesting glitch types seen in evening of Sept 2:
- 90Hz lines in ASD-AS_A_RF45_Q_YAW_OUT_DQ (found by Hveto)
- some loud triggers in CBC BBH that looked like lots of vertical lines at around 100Hz.
- Full DQ page: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20150831
Eric, Cheryl Following advice from D Shoemaker et al., we have disabled the LIMIT on the HWINJ filter bank. The change was made at approximately GPS = 1125361473. The LLO LIMIT was turned off earlier today: https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=20249
J. Kissel More UIM driver spelunking uncovers a false alarm, but a definite bug in the QUAD front-end code. I found that the H1 SUS ETMY COILOUTF Bank (the bank that compensates for the analog coil driver electronics frequency response) for UIM / L1 stage has its last set of filters which compensated for the last stage of z:p = 10.5:1 [Hz] low pass were errantly OFF. Thinking that this might be the source of the frequency dependent descrepancy I've been whinning about for the past week in the measured UIM actuation strength (identified in LHO aLOGs 21015 and 21049), I made sure to conlog back to the state of the BIO request and filter banks during those measurements. Yup -- these compensation filters were OFF then too. BUT -- IT DOESN'T MATTER. (1) If there were a low-pass ON without an appropriate compensation filter, then we would see a *reduction* from 1/f^6 drive strength in the measurement starting at 1 [Hz]. We see an *increase* measured drive strength from 1/f^6 starting at ~50 [Hz]. (2) *If* there was a low-pass ON we would see a reduction in actuation strength. However, in State 1, there are NO low-pass filters ON (see T1100507 -- note that this document has NOT been updated to reflect the chage in zero frequency of the output impedance network). Further, because of the simLP3 / antiLP3 perfect compensation, which is what *would* be on if there were no bug, then there is no difference betweeen having both ON and both OFF. That means as long as the antiAcq filter was ON, and it was, then the driver response is compensated for correctly. We're in full lock so I can't further confirm this bug, but we should. Why hasn't the SDF caught this? Because the user requested H1:SUS-ETMY_BIO_*_STATEREQ is supposed to control these filter banks, so we've chosen to not monitor them in the SDF system. Perhaps we should change that decision. Or perhaps we should just fix the bug.
I have checked all front end code (model source, filter modules, safe.snap and guardian) which had local mods into svn. h1susitmy had a partial filter load; after verifying the filter changes had all been individually loaded, I performed a full load when the IFO was in commissioning.
To study the variation over time of the jitter peaks in the sensitivity, I computed the band-limited RMS of CAL-DELTAL_EXTERNAL between 300 and 400 Hz, for all the reasonably long lock stretches of the last three weeks. The attached plot shows the result: blue dots are the values over one second periods, while the orange traces are smoothed version over 10 minutes.
I was hoping to see some variation or trend during each lock, but apparently the amplitude of the peaks are quite constant, and it doesn't change much over each single lock. There are few exceptions: a couple of locks show very low values, but looking at them in more detail it looks like the entire sentivity was scled down, so I'm not sure if they are meaningful. Moreover, there are a couple of cases where the amplitude of the peaks suddendly decrease or increase, for example around GPS 1124092417 (Aug 20 2015 07:50 UTC) and 1124863017 (Aug 29 2015 05:55 UTC).
9/3 DAY Shift: 15:00-23:00UTC (08:00-16:00PDT), all times posted in UTC
Locked @Nominal_Low_Noise for ~12hrs with a range ~65Mpc. Kept H1 in Observation Mode as much as possible (there were a few errant drops & then we stayed down for PEM Injections starting at around noon (PST). I went through the Operator Checklist & completed most of it. I am supposed to check the Visitor Checklist, and it looks fine. I hesitated to check the HEPI watchdog saturation counter, for fear it might add diffs to the SDF (might try it tomorrow).
Remember:
End of shift Control Room Activities:
Log of Activities:
DCS restarted the diff of the H1 science frames written by the two framewriters: Sep 03 2015 15:29:47 PDT
J. Kissel I got sick of trying to debug the high-frequency affects UIM driver (LHO aLOG 21142), so I've moved on to the more important ESD Driver for H1 SUS ETMY. Instead of fitting the results of the remote measurements of the driver with the monitor circuit (LHO aLOG 20846), I've gone back to the measurements originally taken just after the LVLN driver was installed (LHO aLOG 18579), and fit them more precisely than Evan used to inform the current compensation filter (LHO aLOG 18596). Below are the details. The messages: - Each of the quadrants are *differently* frequency dependent at the ~5% level ~ 5 [deg] level; since we desire higher precision than this, they cannot be modeled with the same set of poles and zeros for each quadrant. - In order to model this correctly, will have to - break out the quadrants in the actuation chain model, - de-compensate for the installed compensation filter, - use the fit poles and zeros from each quadrant, and - then sum the quadrants together (and divide by four as necessary) -------------- The answer: Here're the precise poles and zeros for each quadrant: Diff Receiver Summing Node LP1 LP2 Overall DC Gain Summary (one pole, [Hz]) (z:p) [Hz] (z:p) [Hz] (z:p) [Hz] [V/V] z [Hz]: p [Hz]: k [V/V] UL 24e3 3200:165 48.8:2.160 48.8:2.160 1.8868 (48.8 48.8 3200) : (2.16 2.16 165 24e3) : 1.8868 LL 23e3 3050:160 47.8:2.105 47.8:2.105 1.8868 (47.8 47.8 3050) : (2.105 2.105 160 23e3) : 1.8868 UR 24e3 3050:157 48.8:2.160 48.8:2.160 1.8868 (48.8 48.8 3050) : (2.16 2.16 157 24e3) : 1.8868 LR 24e3 3125:160 47.8:2.130 47.8:2.130 1.8868 (47.8 47.8 3125) : (2.13 2.13 160 23e3) : 1.8868 These poles and zeros result in a frequency dependent residal, which represents a systematic error in the fit. This systematic error is smaller that 1% and 1 [deg] over the entire frequency band for all quadrants (save for where we know the measurement is incoherent noise at ~30 and ~100 [Hz]). Rather than bothering to carry around the precise systematic error and figuring out how to propagate it correctly through the uncertainty analysis, we shall just represent this as this a statistical, 1-sigma, uncertainty of 1% and 1 [deg]. We used to call this being "conservative," but really it's a "perfect is the enemy of good enough" decision. Open the attachment for plots demonstrating the goodness of fit (pg 1) and comparison of each quadrant against the fit and other models (pg 2-5), and a comparison of the models when the LP filter is OFF (pg 6). The fitting process: There are four models that I show: "Spice", "Simple Circuit", "(Compensation Filter)^-1", and PZ fit. "Spice:" Rich had graciously provided us with a spice model of the entire driver with both the low-pass off and engaged: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts/Spice/ LVLN_Driver_v8_PZ_Off.txt LVLN_Driver_v8_PZ_On.txt "Simple Circuit:" For my edification, to determine what parts of the box were determining which parts of the frequency response, I also did some simple analytical analysis of the driver accounting for all of the parts of the driver that contribute to the frequency response. "(Compensation Filter)^-1" These are the poles and zeroes currently used in the ESDOUTF bank, under the "antiAcq" and "antiLP" filters, a "good enough" compensation developed by Evan back when the driver was first installed. I had started off hoping, like we always hope, that one can compensate each quadrant of the ESD driver with the same set of poles and zeros, based on those pole and zero frequency derived from some simple RC analysis of circuit. Turns out this is not the case. The frequency-depednent residual between the Spice, Simple Circuit, and (Compensation Filter)^-1 models and each quadrants' measurement for the following models is upwards of 10% and 5 [deg], different for each quadrant. A such, I created the PZfit model, where each quadrant's residual is tuned to as small as possible using the same number of poles and zeros as in the simple circuit model. That results in the poles and zeros quoted above. --------- Analysis script lives here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Scripts/Electronics/model_LVLN_driver_20150902.m
(Peter Shawhan, Eric Thrane, Corey Gray) Using waveforms created by Chris Pankow, we have set up a schedule of burst hardware injections to occur once every 10000 seconds (~2.7 hours). The schedule runs from now through the end of ER8, but we intend to turn them off once we've obtained 10 coherent (successful at both sites) burst injections. This series is primarily intended to check the infrastructure, the low-latency analysis, and the EM follow-up alert generation machinery; we're not yet attempting to verify the calibration. The injections are all scheduled for GPS times 1000*n+500, i.e. the first one should happen at GPS 1125350500, the next one at 1125360500, etc. However, an injection will be automatically skipped if ANY of the following conditions is true: * The detector is not locked (L1:GRD-ISC_LOCK_OK==0) * We are not in Observing mode (L1:ODC-MASTER_CHANNEL_LATCH bit 0 is off) * There has been a GRB or SNEWS alert within the past hour (L1:CAL-INJ_EXTTRIG_ALERT_TIME is a GPS time less than an hour before the current time) * Injections are currently disabled by the operator (the Disable button on the TINJ / Transient Injection Control medm screen has been clicked, which sets L1:CAL-INJ_TINJ_ENABLE = 0) * Injections have been temporarily paused by the operator using the Pause button on the TINJ / Transient Injection Control medm screen (which sets L1:CAL-INJ_TINJ_PAUSE to a future GPS time when the pausing should end) So, it's anybody's guess how long it will take to obtain 10 coherent burst injections. To get this started at LHO, we needed to start the 'run_tinj' process on h1hwinj1, which hasn't been running since August 25. I talked with Corey, who asked that we not do any hardware (strain) injections right now because the PEM injection folks were about to start doing tests. However, we worked out that the injections can be disabled for now using the Disable button on the TINJ Control medm screen. LHO had an old version of the screen, but Dave updated it to the latest version which has the Disable button (along with Enable and Pause). Corey clicked Disable, and I double-checked that it's disabled by doing 'ezcaread H1:CAL-INJ_TINJ_ENABLE'. I then did "nohup run_tinj &" at about 12:44 PDT. So tinj is running now, but injections will be skipped until an operator clicks the Enable button on the TINJ Control medm screen. Please do that when the PEM injection folks have finished their work - thanks! There was one side effect that I didn't expect: when Corey clicked the Disable button, it took the detector out of observation mode. Corey said that looks like it was done by sdf, i.e. this status (injections disabled) is being considered nonstandard. I'm not sure if that is due to checking the value of L1:CAL-INJ_TINJ_ENABLE, or to some read-back bitmask value. We should follow up with Jamie to find out, and take the injection enable/disable out of the configuration check if possible. However, this isn't a problem right now because the PEM injection folks wanted to be out of observation mode anyway.
Vern told me that if it's sdf, I should contact Dave B and either he or Betsy should be able to look into it. So I emailed Dave.
I have modified h1calcs SDF to not monitor the operator hwinj enable/disable PV H1:CAL-INJ_TINJ_ENABLE. safe.snap checked into SVN r11560.
J. Kissel, D. Barker I had to look didn't I. Anamaria asked me what channel represents the IMC VCO frequency. The answer is H1:IMC-VCO_FREQUENCY, which is a Beckhoff-renamed version of the signal from the timing comparator, H1:SYS-TIMING_C_FO_A_PORT_11_SLAVE_CFC_FREQUENCY_5. However, to find this infomration out, I knew that the VCO frequencies are generated from the corner station timing comparator, so I opened up the timing screen. I found two things: (1) The Timing MASTER's status light was red. Dave informs me that this is because of the recent tests of the 9 and 45 MHz oscillators in the EE shop. They had stolen a sync signal from port 7 of the MASTER via fiber into the EE shop. This has since been disconnected, which made the monitor of the status channel H1:SYS-TIMING_C_MA_A_PORT_7_ERROR_FLAG go red. We've hit the monitor button, H1:SYS-TIMING_C_MA_A_PORT_7_ACTIVE and the status light has gone green. (2) In the corner A fanout, even though it's unrelated to the IMC VCO frequency, we noticed that whatever 5 MHz frequency is being measured on port 11, H1:SYS-TIMING_C_FO_A_PORT_11_SLAVE_ISIRIGB is blinking in and out. The last attechment shows the past hour, showing that this has been intermittently blinking in and out for long time. Screenshots of the timing screens also explain what we saw. ------------- For the record, all of this was done in "observation mode." Granted, all I did was turn on and off monitors, but I don't think we should go into observation mode if the timing master status light is red... I assume this is because Beckhoff as a whole has not been folded into the settings monitoring.
We don't really read back a 5 MHz signal. Unfortunately, unconnected frequency inputs sometimes flicker when their neighboring channels are beeing used. There should be 3 VCO frequencies as well as the main modulation frequency. There is no 40.6MHz channel neither. All RF sources have their own internal readback.
|
Injection |
Time of first injection, UTC |
Injection spacing |
Total number of injections |
Good channels for environmental signal |
|
|
Sept. 2 |
|
|
|
|
Truck braking by EY station parking area |
22:56:00 |
5s |
6 |
EY seismometers |
|
|
Sept. 3 |
|
|
|
|
OSB shipping roll up door actuation |
2:46:00 2:47:00 |
5s 5s |
6 6 |
vertex seismometer and/or output optics mic |
|
Loud Bach in control room (2s bursts of music) |
2:52:00 |
5s |
12 |
input optics mic |
|
Loud Underworld in control room (bass heavy) |
2:55:00 |
5s |
12 |
input optics mic |
|
Single bounces on exercise/seating ball in control room |
2:57:00 |
5s |
12 |
HAM2 seismometer, vertex seismometer |
|
Dropping large super ball from about 5 feet onto control room floor |
2:59:00 |
5s |
12 |
H1:PEM-CS_ACC_LVEAFLOOR_HAM1_Z
|
|
5 people jumping in synch in control room |
3:01:00 |
5s |
12 |
HAM2 seismometer, vertex seismometer |
I've attached the result.
Quick conclusion: Dropping large super ball and people jumping in control room coupled into DARM.
In case people wonder what's the super ball looks like, I've attached a photo as well.
No more super ball during observing run =(
Dan, Daniel, Evan
The addition of a 9.1 MHz bandpass on the OCXO output has removed the broadband excess noise between DCPD sum and null. The dashed lines in the figure show the sum and the null as they were three days ago (2015-08-31 7:00:00 Z), while the solid lines show the sum and the null after the filter was inserted.
Since at least June (probably longer), we've had a broadband excess noise between the sum and null DCPD streams. Stefan et al. identified this as 45.5 MHz oscillator noise a few weeks ago (20182).
In parallel, we switched the 9 MHz generation from an IFR to the OCXO (19648), and we installed Daniel's RFAM driver / active suppression circuit (20392), but the excess noise remained (20403). For a while we suspected that this was 45.5 MHz phase noise (and hence not supressed by the RFAM stabilization), but the shape and magnitude of the oscillator phase noise coupling (20783) were not enough to explain the observed noise in the DCPDs, under the assumption that the OCXO phase noise is flat at high frequencies (20582). For that matter, the shape and magnitude of the oscillator amplitude noise coupling were also not enough to explain the observed noise in the DCPDs, assuming a linear coupling from the RFAM (as sensed by the EOM driver's OOL detector) (20559).
Daniel et al. looked at the 45.5 MHz spectrum directly out of the harmonic generator in CER, and found that most of the noise is actually offset from the 45.5 MHz carrier by 1 MHz or so (20930), which is above the bandwidth of the RFAM suppression circuit. This suggested that the noise we were seeing in the DCPDs could be downconvered from several megahertz into the audio band.
Yesterday there was a flurry of work by Keita, Fil, Rich, et al. to find the source of this excess noise on the 45.5 MHz (21094 et seq.). Eventually we found circumstantial evidence that this excess noise was caused by baseband noise out of the 9.1 MHz OCXO.
Tonight we installed a 9.1 MHz bandpass filter on the OCXO output. This has removed the huge 1 MHz sidebands on the 45.5 MHz signal, and it also seems to have greatly lowered the coherence between DCPD A and DCPD B above a few hundred hertz.
The chain from OCXO to filter to distribution amplifier currently involves some BNC, since we could not find the right combination of threaded connectors to connect the filter to the amplifier. This should be rectified.
Also, it appears that our sum is lower than our null in a few places (400 Hz in particular), which deserves some investigation.
"NULL>SUM" problem is just DARM loop. You're talking about 10%-ish difference, and DARM OLTF gain is still 0.1-0.2 at 400Hz.
See attached.
I don't know how to obtain official DARM OLTF model, so I just took 2015-08-29_H1_DARM_OLGTF_7to1200Hz_tf.txt in
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/DARMOLGTFs/
The coherence for this OLTF measurement was much larger than 0.95 for the entire frequency range shown on the plot.
On the bottom is |1+OLTF|. I interpolated this to the frequency spacing of SUM and NULL spectra, and plotted SUM*|1+OLTF|, SUM, and NULL at the top.
Note that DARM OLTF template measures -1*OLTF.
Nice work. After O1 we can figure things out now you have narrowed it down.
Nice work!
Great job! Following up on the discussion during the commissioning meeting today, at LLO Evan's equivalent plot of the coherence between the two OMC PDs is already below 10^-3 (below 3 kHz).
Fil and I replaced the BNC cable with an SMA/N cable.
J. Kissel, K. Izumi We've completed another round of the suite of actuation coefficient coefficient measurements today, very similar to what was done on Wednesday (see LHO aLOG 20940) with the same templates. There were some differences between the two days worth of measurements -- we don't expect these to have made a difference, but we've been living 1% accuracy and precision land for a week with no sleep, so we write them down anyways. They are: - We managed to get all of the full IFO transfer function measurements within the same lock stretch, unlike Wednesday. - We did Full IFO config measurements, ALS DIFF measurements, then Free-Swinging MICH (FSM) measurements, as opposed to Wednesday when we did DIFF, then Full, then FSM. - Because we got distracted with full-frequency range DARM OLG and PCAL to DARM TFs, and there were some problems with DIFF saturating, there were about ~4 hours between when the ETMX TF was taken in full lock and when it was taken in ALS DIFF. - On Wednesday, we ran ALS DIFF with ALS COMM OFF. Today we ran ALS DIFF with ALS COMM ON. - We missed a MICH OLG TF for the FSM. We may try to get away with checking if the power and PD normalization levels are the same -- if they are we may just use Wednesday's data. Otherwise it means we have to scrap all of today's FSM data. A "When will you have a number?" update: we are heavy into analyzing both of the data sets (ALS DIFF is done with the help of LHO aLOG 21001, tomorrow will be PCAL and FSM). A goal is to have a comparison between methods by Sunday. For a sneak peak on the analysis scripts for ALS DIFF (in case LLO wants to use them), check out /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Scripts/ALSDiff analyze_alsdiff_data_20150826.m analyze_alsdiff_data_20150828.m #NoSleepTilO1 The DTT files live here: (2) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FullIFOActuatorTFs/2015-08-28/ 2015-08-28_H1SUSETMY_PCALYtoDARM_FullLock.xml (5) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/ALSDIFF/2015-08-28/ 2015-08-28_ALSDiff_ETMX_L3_HVHN.xml (6) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-28/ 2015-08-26_H1MICH_freeswingingdata.xml (7) Does not Exist (8) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-28/ 2015-08-28_H1SUSITMX_L2_State2_MICH.xml (9) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-28/ 2015-08-28_H1SUSITMX_L2_State2_XARM.xml (10) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-28/ 2015-08-28_H1SUSETMX_L3_HVHN_XARM.xml (X) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FullIFOActuatorTFs/2015-08-28/ 2015-08-28_H1SUSETMY_L3toDARM_LVLN_LPON_FullLock.xml (Y) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FullIFOActuatorTFs/2015-08-28/ 2015-08-28_H1SUSETMY_L1toDARM_FullLock.xml 2015-08-28_H1SUSETMY_L2toDARM_FullLock.xml (Z) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FullIFOActuatorTFs/2015-08-28/ 2015-08-28_H1SUSETMX_toDARM_FullLock.xml Wish us luck on tomorrow's measurement suite; hopefully it'll be the last time for while!
Just for booking purpose.
In addition to the measurements that Jeff posted, I have done a Pcal Y sweep and DARM open loop measurements in a frequency band of [7 800] Hz using Darkhan's template. The data can be found at:
aligocalibration/trunk/Runs/ER8/H1/Measurements/PCAL/2015-08-28_PCALY2DARMTF_7to800Hz.xml
aligocalibration/trunk/Runs/ER8/H1/Measurements/DARMOLGTFs/2015-08-28_H1_DARM_OLGTF_7to800Hz.xml
The attached pdf contains current Stage-1 and Stage-2 NB model performance of ITMY chamber for X,Y,Z and RZ dof. Fig 1- ST1 ITMY X Low frequency near microseism model performance is limited by the ground blend filter (HEPI L4C+IPS) 1-5Hz frequency band is limited by GND-STS passing through the sensor correction path 5Hz and above (upto 10Hz say) is limited by Stage-2 back reaction Below microseism model does not match with actual performance. (May be because of some tilt coupling?? But it looks like actual measurement is limited by the sensor noises (T240/CPS) via isolation filter. - Not sure about it) Fig 2- ST2 ITMY X Instead of T240 BLND OUT, I have used T240 BLND IN as the input (stage-1 displacement) to the ST-2 model. Though the model and measured GS13 are in agreement above blend frequency (250mHz), the shape between 1-3Hz are not same. The model output looks more like the input signal T240 BLND IN. May be a better input noise model will work better. Since the stage-2 model performance above ~1Hz is highly dependent on stage-1 displacement, we can san say that the Stage-2 back reaction on stage-1 can have effect on the final performance of the model. Fig 3 - ST1 ITMY Y Most of the features and model performance are same as X dof. Fig 4 - ST2 ITMY Y Though this one is same as ST2 ITMY X only thing I have noticed here is the actual IFO ST1 performance is better than ST2 between ~ 300-500 mHz. Fig 5- ST1 ITMY Z ST-1 model performance matches the actual measurement at almost all the frequency range of interest. The conclusions derived for ground model and Stage-2 back reaction hold here too. Fig 6- ST2 ITMY Z Unlike X and Y dof, the model performance between 60 to 250 mHz is quite good (I am still trying to figure out why this sort of discrepancy exists between these dofs ???) At the same time the mismatch between model and actual performance above 5Hz is noticeable. Model is over estimating the actual performance here (though the model has already included stage-2 back reaction in Stage-1) Fig 7- ST1 ITMY RZ Apart from the limitations of the model due to ground noise at low frequencies, the performance of this stage is mostly limited by CPS sensor noise via BLEND+ISO path. Fig 8- ST1 ITMY RZ Please DO NOT go through this figure. Still need to sort out the problems. Same sort of features can be seen in almost all the BSC chambers except BS where the stage-2 controllers are not in use.
T240 and GS13 sensor noise floors are added to the seismic noise budget plots.
[TJ, Jenne]
TJ pointed out to me that the Cal Hardware Injection ODC bit is red, and I tracked down where it's coming from. The ODC is upset that the CAL-INJ_HARDWARE limiter was turned off. I don't think that this has been preventing us from going to Observing mode, since the limiter was turned off on Thursday, but if it does (particularly if some updates have been made during maintenence day that tie this bit into our "OK" status) I will turn the limiter back on until the ODC can be updated to know that the limit switch should be off.
I have sent EricT an email asking for him to help figure out the ODC part of this.
Just to be clear, there should be NO ODC CHECKS INVOLVED in the IFO READY bit. ODC is only used as transport of the bits, and none of the checks being done by ODC affect IFO READY. The only thing that should be going in to IFO READY now is the GRD IFO top node. In other words, this ODC issue should not have been preventing you from going to Observing mode.
Note, when the EXC bit in the CALCS CDS overview is in alarm, we tend to open the screen CAL_INJ_CONTROL to attempt to diagnose - This shows a big red light for some ODC Channel OK Latch, leading us to misdiagnose what is actually in alarm. We have 2 operational problems:
1) If generically, there is a red light on the CDS screen - where do you go? Normally, we follow the logical medm and are able to get to the bottom of the red status via logical nested reds. This is not the case for the CALCS screen - the CDS H1:FEC-117_STATE_WORD bit is RED on the H1CALCS line of the overview screen, yet this bit is nowhere on the CALCS screen.
So, where does the info come from for specifically the EXC bit of the H1CALCS state word, such that we can do something about it?
2) Someone should rework the CAL_INJ_CONTROL.adl so that it doesn't cause us to misdiagnose actual reds. Currently, the HARDWARE INJECTIONS are out of configuration (outstanding issue to still be sorted) and yet, there is NO INDICATION of that on the CAL_INJ_CONTROL screen... Also, the CW injection appears to be off, but there is no "red alarm" on the screen.
BTW, the HARDWARE INJ appear to be off. They dropped around 7pm local time last night (20 hours ago).