thomas.shaffer@LIGO.ORG - posted 12:13, Tuesday 11 April 2017 (35468)
LVEA Swept
Unplugged one extension cord, but that is it.
Unplugged one extension cord, but that is it.
The cell phone texter alarm system was reconfigured, all eight LN2 Dewar low level alarms will now start at 15% full instead of the previous 20%.
h1pemcs was modified to return two test ADC channels to the frame, both at 2048Hz.
Jeff made his h1calcs model change. This only added slow channels to the frame (203 chans).
I changed the DAQ master to add the new H1EDCU_SEISMON.ini file.
11:44PDT: DAQ was restarted for the above.
[Kyle, Chandra]
In preparation for anticipated vertex vent, we tested vacuum equipment: QDP80 roughing pump, Kobelco purge air skid, and vertex turbo & scroll pumps. All ran satisfactorily. Purge air measured -43.7degC dew point. A few notes:
[Vaishali, JimW, Jenne]
During maintenance, while no one needed the IMC, we tried out our new L2A decoupling filter for MC2. Recall that Jim found that it would be helpful in alog 35330, and we measured and fit TFs for it in alog 35397.
We found that (a) the pre-existing L2A decoupling was in fact worse than doing nothing at all, and (b) that our new filter works well.
In the attached screenshot, the upper left corner is the Foton Bode plot of our decoupling filter. In the other 3 DTT panels we have the coherence and transfer functions of 3 different MC2 L2A configurations. For these measurements, the IMC was unlocked, but MC2 still aligned. The red traces in all panels are with no L2A decoupling at all. The blue traces are with the old L2A "decoupling" gain. That was a flat gain, and clearly was making things worse than doing nothing at all, over a pretty broad frequency range. The green traces are with our new L2A decoupling filter on, and we win almost 20dB of isolation below a few hundred mHz.
We have accepted the new L2A settings for MC2 in the safe and observe SDF files, so they should always be on now.
I've looked at the coherence between MC2 M1 length drive and the two pitch witnesses (MC2 Trans qpd and MC2 M1 Pit) during locks before and after the install of the new L2P feedforward, and things look better. Attached plot shows the coherence between MC2 M1 L and MC2Trans (top plot, blue is before, red after) and MC2 M1 L and MC2 M1 P (bottom plot, blue is before, red after). Below .1 hz the coherence is much better, which should help for wind and earthquakes, which is what I was looking at originally anyways. Above .1hz the coherence is pretty much unchanged, not sure why, maybe the motion is dominated by the table motion at those frequencies?
Always useful to actually post promised plots...
these models' filter files were static files located in the chans/ directory. I put them into SVN control and made symbolic links from the chans/ directory to there new location under userapps.
[Jeff K, Aaron V] I have produced new GDS filters for LHO that include new paramters (pcal correction factors and EPICS) necessary to compute SRC detuning parameters. It will also be possible to subtract the calibration lines from the strain, producing the additional channel GDS-CALIB_STRAIN_CLEAN, if we desire. The filters can be found in the calibration SVN at this location: ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/GDSFilters/H1GDS_1175954418.npz For information on GDS calculations of SRC detuning parameters, see: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=35041 (note that we now compute Q-inverse instead of Q) https://alog.ligo-la.caltech.edu/EVNT/index.php?callRep=11785 The filters were produced using this Matlab script in SVN revision 4537: ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/TDfilters/H1_run_td_filters_1175954418.m The parameters files used (all in revision 4537) were: ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/2017-01-24/modelparams_H1_2017-01-24.conf ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/2017-01-24/H1_TDparams_1175954418.conf ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/CAL_EPICS/callineParams_20170411.m ASD plots comparing GDS and the front-end CALCS model are attached. These agree with those on the summary pages from the same day (4/10), as expected. Also, time domain vs. frequency domain comparison plots of the filters are attached. Lastly, a time series plot of the kappas from GDS and CALCS is attached, as well as histograms. These show the expected output.
It was discovered that the output of these filters did not agree with the C01 frames. These GDS filters have been regenerated with SVN revision 4781, and the discrepancy has disappeared. For more details on this issue, see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=36863 .
There were number of high frequency calibration lines injected using the automated Guardian scripts. These lines are injected using the Pcal at ENDX (ENDY is used for calibration purpose). The GPS time at which these lines were running are listed below:
| Frequency | Starttime | Endtime |
| 2001.3 | 1174765755 | 1174843009 |
| 2501.3 | 1174843010 | 1175048873 |
| 3001.3 | 1175048874 | 1175185602 |
| 3501.3 | 1175185604 | 1175280996 |
| 4001.3 | 1175280998 | 1175367396 |
| 4501.3 | 1175367398 | 1175532906 |
| 5001.3 | 1175532908 |
Rick, Sudarshan
Th high frequency line was moved to 5501.3 Hz. The guardian script was designed to go upto 5001.3 Hz so Rick moved the frequency to 5501.3 Hz manually during the maintenance period. We will move this line to 6001.3 Hz when we have enough data and the ifo goes out of lock next time.
Updated list of lines with their start and endtime.
| Frequency | Starttime | Endtime |
| 5001.3 | 1175532908 | 1175971199 |
| 5501.3 | 1175971561 | 1176156175 |
| 5751.3 | 1176156177 | 1176255835 |
| 5251.3 | 1176255837 | 1176350524 |
| 4751.3 | 1176350525 |
TITLE: 04/11 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Not much going on. PI Mode 23 rung up. I flipped the phase 180 degree and it seemed to stop ringing up. I later found an alog that operator shouldn't damp this mode. So what's the status now?
LOG:
13:56 Briefly out of Observe (accidentally). See alog35458
~13:56 UTC, I accidentally re-enabled the front end laser watchdog.
The laser output power has slowly been decaying over the past week or so - see attached plot. Most of the power decay is due to the deterioration in the output of diode box 1 (head 1). Pre-modecleaner could probably do with an alignment tweak.
Been locked and Observing since Travis handed off to me. Not much to report.
TITLE: 04/11 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 72Mpc
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY: A pair of locklosses, one unknown and one due to PI. Otherwise, nothing to mention.
LOG: See previous aLogs.
No issues coming back up.
PI mode 28 rang up and I couldn't find the right phase value fast enough.
Ran through a painless IA. Adjusted ISS diffracted power as it was complaining that it was low. Accepted SDF diffs in attached screenshots. ISS refsignal was, of course, me. The other two I am not sure about.
Cause unknown. Lock gave up at 71 hours and 10 minute old.
Wind has calmed down a bit and the range has come up some. We just rolled over to 70 hours locked.
L1 alog #32936 describing an alignment shift of the L1 IM2 in pitch on March 27th, 2017.