jeffrey.bartlett@LIGO.ORG - posted 11:21, Friday 20 February 2015 (16830)
Adjust ISS Power
Adjusted ISS diffracted power from ~ 5% to ~ 8%.
Adjusted ISS diffracted power from ~ 5% to ~ 8%.
Estimates are at least 10 working days needed to complete the 3IFO tasks before the end of March. To reach this goal, Tuesday’s and Thursday’s will be open access to LVEA and VEAs and noisy work (craning, forklifts, etc.) will be permitted between 08:00 and 16:00. During this time, the LVEA and VEAs can be transitioned to Laser Safe as needed. Always check in with the operator before starting a task.
The 08:00 to 10:00 noise windows are suspended while the extended Tuesday and Thursday noise hours are in effect.
Summary: No commissioning and noisy work on Tuesday and Thursday between 08:00 and 16:00. Commissioning during all other hours. These times can be altered due to special requirements, with agreement of the commissioners.
Fred brought up the need to review and refine the alarms, alarm handlers, and system monitoring. Fred asked that that the staff think about how these systems can be improved. This will be the subject of the next Science Team meeting.
Tuesday 02/24 - GV5 and GV7 will be closed to support the pump down of HAM1.
Kyle – will be installing the remaining bolts on the HAM1 doors.
Filiberto – Will be shutting down the Test Stand in the West Bay area to prep for rack removal.
Jim – running TFs on HAM4
model restarts logged for Thu 19/Feb/2015
2015_02_19 07:56 h1fw0
2015_02_19 16:34 h1nds1
Two unexpected restarts, nds1 most probably due to request overload. Conlog frequently changing channels report attached.
Dan, Sheila, Evan, Jeff, Alexa
Tonight locked many times (on RF) but didn't stay locked verry long. We found two new lockloss causes that were relatively easy to solve:
During one of our short locks early in he evening , we made an attempt to align the green to the arm cavities after the DHARD WFS had come on. For the X arm the only thing we needed to do to get a good build up was move the TMS, we saw the spot move on the ITMX green camera and updated the spot positions for the green WFS (248.3 for PITCH, and 354.8 for YAW). For the Y arm we saw that moving TMS was not good enough, we needed to also adjust QPD offsets. We lost the lock in the middle of this process. Note: the recycling gain tonight was low, around 25, but we think that having the green co-alinged even for this low build up would be better than our original situation.
During the earth quake we have spent some time on the new COMM IR search state that evan wrote. We modified it, it is now 100% successful, but it can take a couple of minutes (generally under 5). This is still faster on average than having a human do it, and we can think about something else while this is working now.
Here are the plots that tell the tidal story. The offset to the {X,Y}_COMM_ERR filter banks is supposed to be updated by the TIDAL_HACK Guardian; this provides the error signal which is controlled through the SUS and ultimately offloaded to HEPI. This offset was turned off for the X-end on Tuesday, which is why the X_COMM_ERR output is zero. At the same time the HACK Guardian, which takes the DC component of IMC_F and writes this to the COMM_ERR offsets, was turned off, which is why the output of Y_COMM_ERR is a nonzero constant. The Y_COMM_CTRL filter bank was happily integrating this constant off to infinity whenever the arms were locked. HEPI was still getting some input from the SUS drives but it was, as you might expect, not helpful.
First plot is today, we lost lock because IMC_F (lower left corner) was railing at the limit of the VCO, something like >2000 counts (calibrated to kHz, so that's the 2MHz VCO range).
Second plot is the 2-hour lock from last week, when the IMC_F output was small and steady. The low-frequency signal was being offloaded to HEPI, the COMM_ERR outputs were nonzero.
It looks like the TIDAL_HACK guardian module does not define an initial request, meaning that it will come up with REQUEST = NONE, and the system won't leave the INIT state. This is why the TIDAL_HACK node wasn't doing anything after the recent guardian restarts.
I suggest setting:
request = 'COPY_AND_PASTE'
in that module, so that when the node restarts it always goes back into the appropriate state.
J. Kissel, S. Dwyer During the earthquake we captured new safe.snaps for the ETMs. Note that in doing so, I brought the SUSs to "safe" by hand, then requested the guardian to go to "SAFE", and vice versa brought the sus to "ALIGNED" via guardian, then restored everything that the guardian didn't touch -- all because I finally wanted to compare what my impression of what the guardian should be doing is different from what the guardian currently does after months of neglect from me, and commissioning by others. Most notably, it DOES NOT touch any part of the locking filters, and it DID turn on BOTH degrees of freedom of optical lever damping. For the record, the safe I gathered, I turned OFF ALL euler basis output switches: LOCK, DITHER, DAMP, OL DAMP, DARM DAMP, etc. Further, I've turned OFF the large offsets installed by Keita reference in LHo aLOG 16591. Those offsets, and all the expected LOCK filter banks and optical lever Pitch damping has been turned back ON. I've committed the new safe.snap the the userapps repo. Currently, we want optical lever damping to be either under human control or ISC guardian control, so we have commented out the lines in the INIT and ENGAGE_DAMPING states with call the function susobj.olDampOutputSwitchWrite to turn the levers ON. I've commited SUS.py to the userapps repo.
J. Kissel, B. Weaver The above log is a unclear regarding Keita's offsets. I had turned the offsets in M0 DRIVEALIGN L2L, L2P, and L2Y, as well as the R0 TEST L OFF while capturing the safe.snap and have LEFT them OFF since. Repeat: the M0 DRIVEALIGN L2L, L2P, and L2Y, as well as the R0 TEST L are now OFF and should remain OFF because they have proven to be ineffective (Betsy's posting an aLOG with the proof shortly).
J. Kissel, S. Dwyer, D. Hoak We were cruising along trying to align green beams to a red lock when an earthquake in Japan killed the lock. Interesting notes: - There have been two EQs in the past 16 hours, 2015-02-19 13:18 UTC in Vanuatu, 6.4 M 2015-02-20 04:25 UTC in Japan, 6.3 M - Attached is a band-limited RMS velocity of the 0.03 to 0.1 [Hz] band over the past 24 hours. This shows that, on site, the Japanese earthquake hit harder, almost 2/3rds more amplitude than the slightly stronger (at epicenter) Vanuatu quake. - The SEI systems, HEPI and ISIs rode out the EQs without a problem. In fact, looking at the BLRMS colored performance matrices of all the ISIs, the only non-green blocks are the very lowest band, (0.03 - 0.1 [Hz]) that have gone orange (indicating the displacement is between a factor of 100-1000 larger than requirement in this frequency band). @DetChar -- it would be great to get ASDs and time series of lots of sensors during these two quakes and compare them against each other and "quiet" time. Note this would note just be a pull of the summary pages, 'cause I want a few averages, just around the EQ time. (1) Check the arm length stabilization control signals: H1:ALS-[X/Y]_REFL_CTRL_OUT_DQ, roughly pre-calibrated [um] (the calibration may be off by a factor of two, and there's a minus sign between the two arms). Note that they also saturate near the limit of their range (2) Check the GND STSs' (a) time series to *see* if they saturate, and (b) their ASDs (in displacement, preferably) to see how loud all frequency bands get. H1:ISI-GND_[ETMX,ETMY,ITMY,HAM2,HAM5]_[X,Y,Z]_DQ -- should be calibrated into 1 [nm/s] (only above ~10 [mHz], so be careful when looking at 30 [mHz] data) (3) Check the Beam rotation sensor: H1:ISI-GND_BRS_ETMX_RY_OUT_DQ -- should be calibrated into [rad]. Good also down to ~10 [mHz] (4) BSC ISI T240s (5) HAM ISI GS13s
LVEA: Laser Hazard Observation Bit: Commissioning 07:15 Cris – Cleaning in the LVEA 08:00 - Cannot login to CR terminals – CDSFS0 had crashed. Ryan rebooted computer 08:00 Jamie – Restarting Guardian to pick up new patches 08:15 Corey – 3IFO work in H2 Squeezer Bay 08:18 Elli & Dave – Working around HAM6 08:20 Filiberto – Working on PR3 OpLev 08:30 Betsy – Running TFs on SRM and SR2 08:40 Andres – In LVEA looking for tooling 08:45 Andres – Out of the LVEA 09:00 Kyle – Looking for the bolts for the HAM1 door – Prep for pump down 09:45* Kyle – Out of the LVEA 09:55 Jodi – Working at Mid-Y on 3IFO stuff 10:00* Dave & Elli – Out of the LVEA 10:00* Filiberto – Out of the LVEA 10:30* Corey out of the LVEA 12:13 Vending provider on site to stock machines 13:48 Apollo – On site to work on CDS AC units 15:35 Kyle – Going to End-X to recover tools for the HAM1 vacuum work
I had noticed on the Detchar pages that ITMY had been doing a lot better between 1 and 10 hz than the other BSCs, so I started poking around in filters to see what was wrong. The FF filters were all the same and isolation loops all looked roughly similar. On Hugo's suggestion I looked at the L4C blend in on HEPI and the FF in on the ISI. The signals should have been exactly the same, but the ISI showed less signal at 1hz by a factor of ~2 (first image, HEPI is red, ISI FF is blue). The only filters applied on both platforms a that point are a calibration filter and a symmetrization filter. On HEPI (second image), the calibration is just a gain (red trace), the symmetrization is a notch filter that smooths the L4C response(blue). On the ISI (third image), the calibration filter is a notch filter (red again), and the symmetrization filter is mostly flat filter that tunes the calibration filter slightly (blue trace). Either approach is fine, as the product of the cal and sym filters stays the same, (green taces on both pictures). Unfortunately, the ISI HEPI FF L4C cal and sym filters were not loaded in a consistent manner on most chambers (ITMY was done correctly, so FF worked there!). Basically the other chambers were using the blue trace on the first plot with the red filter on the second plot. This effectively cut the FF L4C signal in the region we needed it most. I've now loaded right, consistent set of filters from HEPI on the ISI FF path, so we should see a good improvement on most of the chambers in the 1-10hz region. One dof for ETMX is shown in my fourth image, blue before, red is after, I'll try to get a more complete comparison tomorrow morning. I haven't finished the doing gain matching on these chambers yet for the FF path, whcih should improve this a little more.
I reset the dust monitor counts alarm levels to reflect the US Fed 209E cleanroom standards, as defined in T1400024.
For Clean-1000 (General room monitoring of LVEA and VEAs)
0.3 minor 2000, major 3000
0.5 minor 750, major 1000
For Clean-100 (Open chambers, cleanrooms with Class-A, etc.)
0.3 minor 250, major 300
0.5 minor 75, major 100
The dust monitor alarm have been set to these levels. I will monitor over the next couple of weeks to see if these levels need to be adjusted.
In general, the 3rd ifo work can go ahead all day Tuesday and Thursday; all other days should be off completely.
Today: Concentrating on initial alignment
Friday: Schnupp length measurement (morning); Locking and alignment (afternoon)
Saturday: Schnupp length measurement
Monday: Locking and alignment
Tuesday: LSC/OMC model split; 3rd ifo work (all day)
Wednesday: Locking and alignment
Thursday: SRC length measurement; Locking and alignment; 3rd ifo work (all day)
Friday: Locking and robustness
This morning at ~0025utc 19 Feb, the End Station HEPI Pump Servos were restarted with the Scan Rate reduced from 0.1 second to 1 second. Also, the database has JeffK's 10mHz PID parameters--see 16782. Also, EndY had the SMOO parameter but that has never been in the database, so any restart requires those to be replaced manually. The smoothing has NOT been reloaded.
See the attached as I going to say that while things are better at both stations, EndY remains noisier than EndX and this is evident in amplitude of the Pressure data and the control signal going to the VFD. The 24 hour plot attached clearly shows the time things were switched 23 hours ago. But whereas Ex Pressure got quieter, EndY's got noisier, likely from the Smoothing going away. Because the pressure signal is noisier at EndY, the drive to the VFD is larger than it is at EndX. I predict that if there is measurable coherence with platform sensors, it will be larger at EndY.
The Pcal calibration line for the LHO END Y is set at 36.7 Hz (40 cts excitation amplitude) and 540.7 Hz (23500 cts excitation amplitude) both producing an SNR of about 20. These frequencies are in line with the agreed upon frequencies as reported in LLO alog #15870.
This morning, Jamie enabled the Guardian SPM on all suspensions. There will be a new yellow bar across the bottom of the GRD screens which may point to settings that have been switched and are discrepant from what the current guardian state says they should be. The system is a work in progress so for now you can ignore this indicator while we learn what comes up in the monitor. To disable the monitoring, set ca_monitor = FALSE in the GRD of choice. Note, while we were working on this the ETMy guardian node completely froze and Jamie had to completely restart it.
While taking acceptance review TFs over the last 2 days, I noticed that the SR2 Pitch TF does not look healthy when the IFO alignment bias is enabled. (Note, acceptance TFs are usually taken with all bias offsets disabled.) Likely the large pitch bias plus the TF excitation is causing an earthquake stop to brush the suspension somewhere. The first attachment is the Pitch TF taken with the full IFO requested bias enabled (P=2789, Y=759), the second attachment is with a lower Pitch bias but the same Yaw bias (P=2589, Y=759). This could be be headache for commissioners. I mapped out that for reduced Pitch bias between ~1500 and ~2600 the TF looks healthy. I did not map out exactly where between ~2600-2789 it goes bad. Indeed, the TF at the aligned state looks to have both Pitch and Yaw motion when viewed on the AS Air camera. The bad TF seems to happen when the beam is somewhere off the top of the camera view. Probably too close for comfort.
On the plus side, I checked the the SRM Pitch TF which is healthy at it's nominal IFO alignment setting. The PR2 has a pretty high Yaw bias enabled (Y = 4311) so should probably be checked. The rest (MCs, PR3, PRM, and SR3) have smaller bias offsets under 2000 so I wouldn't suspect a problem with them.
Kiwamu and I checked that there is no DAQ saturation happening during the SR2 TF. Darn.
model restarts logged for Wed 18/Feb/2015
2015_02_18 14:27 h1fw1
2015_02_18 16:17 h1broadcast0
2015_02_18 20:22 h1fw1
two unexpected restarts. DAQ broadcaster restart to add channels for DMT. Conlog frequently changing channels report attached.
PR3 oplev died at about Feb 17 2015 20:00:00 UTC, that's about noon local time.
The commissioners had to stop using PR3 oplev for some ASC purpose yesterday evening.
I thought I had powered-on all Op Lever Whitening Chassis after my work on Tuesday. I went out this morning and powered unit back on.
