Ops Eve Summary: 00-08:00UTC, 16:00-23:59PT
State of H1: Observe, range 79Mpc, POP_A_LF stable
Fellow: Darkhan
Shfit Summary:
Calibration measurements until about an hour into my shift
Locking went well, and made it past DRMI
Calibrations needed H1 in not-DRMI, so I broke the lock
Calibrations continued, then back to locking
Even after having been out of lock most of the day, H1 locked and went back to Low Noise
Relocking Issues:
Changes:
I restored the gaudian to requestion 23W instead of 10W. JeffK had suggested it, and I emailed Sheila, and she said to go ahead.
TITLE: 01/08 [OWL Shift]: 08:00-16:00 UTC (00:00-08:00 PDT), all times posted in UTC STATE Of H1: Observing @ ~ 78 MPc. OUTGOING OPERATOR: Cheryl QUICK SUMMARY: From the cameras: The lights are off in the LVEA. The lights are off in the PSL enclosure. The lights are off at end Y. I can not tell if the lights are on or off at mid X, mid Y or end X. The winds are less than 10 mph. From pinging: CDS WAP is off at the LVEA, end X and end Y. CDS WAP is on at mid X and mid Y. nds0 is down and the EDCU is red. Screenshots of the seismic bands and ISI blends are attached.
J. Kissel, K. Izumi We're too exhausted to write the aLOG this deserves, so we'll just say "we did it!" and leave plots and conclusions until tomorrow. The message: from what prelimiary analysis plots we have made, we can say that these new results are consistent with those taken during ER8, modulo the well-tracked change in kappa_{TST} (the EY L3 ESD actuation strength). Stay tuned! We can also say that using ALS DIFF instead of a single arm locked on red has drastically improved the statistical uncertainty of the Free Swinging Michelson method -- thanks LLO!
Manually filled CP3 -> Opened exhaust check valve bypass -> Opened LLCV bypass valve 1/2 turn ccw -> LN2 evident at exhaust after 29 minutes 30 seconds -> Closed LLCV bypass -> Closed exhaust bypass valve after several minutes -> Confirmed with Gerardo that we are performing this exercise following the same prodedure -> I cannot explain the discrepancy between the fill times between today vs. the previous fill unless the LLCV bypass valve's stop-to-stop is very course and our "1/2 turns" differ significantly. Next manual over fill of CP3 is scheduled for Saturday before 4:00 pm
Several minutes prior to filling CP3, I had used an SS wire brush to remove the Q putty that had been applied during our leak hunting of the GNB spool a few months ago (in the VEA) to see if, by doing so, it changed the pressure in the Y-mid -> no change -> I then applied Vacseal to the previously repaired leak site on the GNB spool -> no change -> Finally, I applied Vacseal to the area around the repaired leak site -> no change This effort was an attempt to explain the ongoing slow pressure rise observed in the Y-mid station which began shortly after the problems with CP3 which required manual filling of CP3
Activity Log: All Times in UTC (PT) 20:00 (12:00) Take over from Corey 21:22 (13:22) Office supply delivery for Bubba 21:54 (13:54) Office supply truck off site 22:21 (14:21) GRB – Ignored due to calibration work 22:26 (14:26) Acknowledged HWJ stopped message 22:45 (14:45) Kyle – Going to Mid-Y to top off CP3 23:45 (15:45) Calibration work finished for the day. Starting to relock 00:00 (16:00) Turn over to Cheryl End of Shift Summary: Title: 01/07/2015, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT) Support: Jeff K., Kiwamu, Gary, Incoming Operator: Cheryl Shift Detail Summary: Supporting calibration work. 23:45 (15:45) – Tried relocking the IFO without running initial alignment.
Posted are the December data files from the temperature and relative humidity data loggers for the 3IFO desiccant cabinet and the Dry storage boxes. All appears to be normal.
Calibration work continues.
TITLE: 1/7 DAY Shift: 16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC
(Corey from 16-20UTC & Bartlett from 20 - 00UTC)
STATE of H1:
Incoming Operator: Cheryl
Support:
Quick Summary:
Calibration work continues.
Shift Activities:
Performed a run spanning the time period from 1132963217 (Dec 01 2015 00:00:00 UTC) to 1136155727 (Jan 06 2016 22:48:30 UTC)
The following parameters were used for this run:
During this time period, 12 scheduled injections were found to have occurred
Only 1 injection was found to not occur:
Of the occurring scheduled injections, only two occurred as single-IFO injections:
All other scheduled injections occurred as H1-L1 coincident injections. The only UNSCHEDULED injections were 5 CALRESETs at L1 and 1 CALRESET at H1.
The CALRESET injections have the same pattern of occurring with only certain paired combinations of the frame flags indicated by HWInjReport, as seen previously. However, all of the occurring scheduled injections have the anomaly of not occurring in the CAL-INJ channel and not having the TRANSIENT bit set to “off” to indicate the presence of a transient injection. They do occur, consistently, in the ODC-MASTER channel for HOFT, RAW, and RDS frames and the GDS-CALIB channel for HOFT frames.
Minor correction made to report. There were, in fact, 2 single-IFO injections that occurred, both in L1. I missed the second one due to an eyeball error.
As reported by Chris B. in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=24282, the two single-IFO injections were the result of H1 losing lock.
The absence of occurrence of the injections in the CAL-INJ channel turns out to not be an anomaly but the result of a deliberate change to using the new CAL-PINJX_ODC_CHANNEL_OUT_DQ channel to record the information that was originally in CAL-INJ_ODC_CHANNEL_OUT_DQ. Currently, HWInjReport does not check the CAL-PINJX channel, however, it should not be difficult to add checking on this channel.
Per Operator Shift Checksheet activity for Thursday Task, I topped off the Crystal Chiller by adding 175mL of water.
TITLE: 1/7 DAY Shift: 16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC
STATE of H1: OBSERVING (but taken out at 8am for calib)
Outgoing Operator: Jim
Quick Summary:
As I walked in, H1 was in Observing, but Jeff was staging for his first Calibration measurements, which promptly started at 16:00UTC. Also heard from Joe B. at LLO and how they are also starting as well.
At the moment both interferometers are up and running for calibration work. In the LVEA the useism continues to be high at about 0.75um/s; virtually no winds.
1/7 Owl Shift 08:00-16:00UTC
State of H1: Observing 80Mpc
Shift Summary: Quiet shift. Locked at 9:00UTC, not much else to report
Quiet shift so far. Locked about 9:00 UTC, been in Observe since. Wind is low, microseism is high, range is ~80MPC. POP bleed off seems to have been resolved after the work earlier today.
[Jenne, Kiwamu, Sheila, JeffK]
Today, the interferometer decided that it didn't want to go from ASC_PART2 to ASC_PART3 without some hand-tuning each lock. However, after some investigation, it's still not entirely clear what the right thing to do is :(
The things we were playing with were the offsets in the CSOFT and DSOFT pitch filter banks (can only be tweaked *after* the loops are on, since there's an integrator always on in each of those filter banks) and the transmon qpds' ASC-[x,y]_TR_[a,b]_[pit,yaw]_OFFSETs. These things are kind of the same, but you need to adjust the transmon offsets if you want to do some adjusting before the loops are closed, and you need to adjust the CSOFT and DSOFT offsets if you want to do some adjusting after the loops are closed.
We've had locks where we didn't survive if we didn't re-zero the qpd offsets before going to part3, and we've had locks where we didn't survive part3 if we didn't adjust the CSOFT and DSOFT offsets. But, we've also had locks where the opposite was true.
Anyhow, at this point, I think our advice is to try going through the guardian like normal (no by-hand offsetting), and if that fails one or more times, call a commissioner (it's me for now, so please call). For example, the last lock, I re-set the qpd offsets during asc part 2, but forgot to engage the CSOFT and DSOFT offsets, and we seemed to be just fine. So, it's not totally clear yet what the final prescription should be.
Tonight we had one OK lock with the offsets as Jenne aloged above, which we lost because of an EQ (see Cheryl's shift summary). On relocking without changing the offsets or doing anything special, we lost lock due to the CSOFT pitch instability that has plauged us when we have changed the TMS QPD offsets in the past. (There was a small EQ that arrived on site shortly after this lockloss, but clearly we lost lock because of the pit instability before it arrived). After this, Cheryl and I let the IFO lock and engage ASC with the offsets that Jenne had found this afternoon, then once the soft loops were closed very slowly reverted to the old offsets (see Cheryl's alog) at 2 Watts. Our recycling gain was around 41 when we started, and although it dropped as we reverted the offsets it returned to 41-42 once they were all reverted. We powered up slowly and the recycling gain stayed above 40. After about 20 minutes I thought that things seemed better than they have in several days, so I suggested we offload the full lock ASC. Sadly this broke the lock.
Since this situation is very similar to what happened Dec 3rd -4th, I re-ran the script I used then to look at build ups (23959), for the past 10 days. The results are very similar, the drop off in the POP DC trace is very similar to the drop off in the arm transmissions (ratio of arm transmissions to POP DC is shown in the middle panel, and is changing by at worst 1% while the powers drop by nearly 15%. )
One explanation we considered in December was that the OMC was becoming misaligned, causing the DARM offset to change. The second attachment shows the OMC ASC control signals and the QPDs, which are out of loop. You can see that they move around even in locks where the recycling gain is stable and don't seem to be any worse in the last few days, so it seems like this is not our problem.
Jim has just relocked with a recycling gain of 41, which has been stable for nearly 20 minutes, so this is looking more promising. One thing that we did is edit lscparams so that the guardian will go to 10 Watts in the increase power state instead of the normal set point of 23 W.
Until this is reverted the steps to follow for power up are:
1) request INCREASE_POWER (it is important to change the PSL power only in this state, this state automatically takes care of gain scalings for you).
wait until the power reaches approximately 10 watts, and the recycling gain seems stable. We have been waiting a few minutes here to make sure it stays stable, that should not normally be necessary.
2) open the PSL rotation stage medm screen (from site map under IOO on the top right hand side, Rotation Stage).
3) type 23 in the requested power dialog box and hit go to power
4) only once the rotation stage has finished moving is it safe to leave the INCREASE_POWER state.
For the record, I give you another similar example that Nutsinee and I had experienced back in October (alog 22575 and comments). At that time, we conluded that it was due to subopitimal alignment in TMSY.
Opened FRS ticket
Fault Report 4186 - Trouble advancing past Guardian state ENGAGE_ASC_PART2
(This was done as "for-real" practice with R. Oram)
J. Kissel In efforts to finally nail down the mysterious "zero" around 50 [Hz] in the UIM (see LHO aLOG 24296), I've measured the TOP, UIM, and PUM driver using three different measurement configurations. The hope is that, with this "matrix" of differences, we can find out what's going on with the UIM to see if its something specific to the driver, or specific to the OSEM chain upstream of the driver. From what I've seen watching the measurements go by on the SR785, both the TOP and PUM stage show similar zero-like behavior as the UIM, though the TOP mass has a pole-like behavior above the zero and eventually rolls off. Both the PUM and the UIM look as though they are rolling up to "infinity" by 10 [kHz], without even a phase shift indicating their might be a pole "soon" in frequency. More detailed analysis and plots to come. The data has been committed to the repo here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/Electronics/ EYPUMDriver/2016-01-05/TFSR785*.txt EYTOPDriver/2016-01-05/TFSR785*.txt EYUIMDriver/2016-01-05/TFSR785*.txt where the key to each driver's measurement set is in the log files, /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/Electronics/ EYPUMDriver/2016-01-05/2016-01-05_EYTOP_Measurement_log.txt EYTOPDriver/2016-01-05/2016-01-05_EYUIM_Measurement_log.txt EYUIMDriver/2016-01-05/2016-01-05_EYPUM_Measurement_log.txt I also attach a white board sketch that indicates each of the measurement configurations. (0) [Not shown] The "reference" measurement is identical to the reference setup shown in page 2 of the 2nd attachment in 18518, which is divided out of every transfer function to get rid of the response of the differential driver. (1) This is measuring the response of the coil driver as it is typically measured on the bench by CDS. It uses a differential to single-ended receiver and the 40 [ohm] internal load (as I only found out later, the documentation on this box, D1000931 leaves something to be desired), so the response differs from configuration (2) only by a scale factor of 2. (2) This is measuring the response of the coil driver as is typically done in the field when the OSEM and/or satellite amplifier is not available. The box (D1100278) is, as far as the coil chain is concerned, only a two 20 [ohm] (for a total of 40 [Ohm]) resistor load. (3) This is the "real life" scenario, where we measure the response of the driver with the full SatAmp and OSEM included as a load on the output of the driver. It is in this configuration is where the magic happens, apparently.
Since the IFO has decided to give up on Calibration Week, I've put together some .graffle diagrams of what I show in the whiteboard picture above such that a future user and/or LLO can more clearly replicate my results, if need be (or they don't trust what Evan G's is about to post). Also note for future me, the source code for these diagrams lives in /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PostO1/H1/Measurements/Electronics/EYTOPDriver/2016-01-05/ CoilDriverChassisSetup_BenchTestSetup.graffle CoilDriverChassisSetup_DummyOsemChain.graffle CoilDriverChassisSetup_RealOsemChain.graffle
Summary:
I plotted the results of Jeff's measurements for the H1 End Y driver electronics for the top, UIM, and PUM masses. All show odd behavior at high frequencies that we cannot model as an ideal inductor.
Details:
For each measurement of a given mass' driver electronics (TOP, UIM, or PUM), I divided the measured BOSEM (for TOP/UIM) or AOSEM (for PUM) transfer functions (normalized) by the corresponding transfer function for when there is a dummy 40 ohm resistor terminating the output of the drive electronics (also normalized). In addition to plotting the results of the measurements, I also investigated the high frequency behavior. Nominally, we expect to observe the inductance of the BOSEMs or AOSEMs as a simple zero--the high frequency dependence goes as f. Instead, we observe different dependences for the BOSEMs of the top and UIM masses and the AOSEMs of the UIM (state 1 and 3). We attempted to fit by hand some zero-pole models to these Bode plots but were unsuccessful to replicate the high frequency dependence.
Attached are 7-day pitch, yaw, and sum trends for all active H1 optical levers.
Centering:
Glitching (via DetChar summary pages):
Update on the BS oplev. Appears the cessation of glitching was only temporary, as the last couple of days have seen the laser go wild. Will attempt a power adjustment during the next maintenance period (as discussed here). If that is unsuccessful then I will swap back in the now re-stabilized laser SN 130-1 (that I just recently removed from this oplev and found to be functioning normally, just in need a slight tweak to it's TEC setpoint).