The attached plot shows the tidal feedback signals during the 3.1 hour lock with the common correction on. There was about 150µm of motion in the y arm and about 100µm in the x arm, while the IMC stayed within a 100 KHz of nominal with no visible drift. The L1 drives of of both ETMs stay within 2µm of zero.

I have measured the violin mode using the most recent lock data (February 10th ~5pm). Due to the lack of precisions in the existing information and the mismatch in values I was not able to identify any of the peak except for the ITMX BR (Back Right) at 499.9 Hz. The violin mode found in the recent lock data are as follow:

499.9, 505.58, 505.71, 505.80, 505.85, 505.92, 506.92, 507.16, 507.20, 507.36, 508.01, 508.15, 508.20, 508.85 Hz 

The (fundamental harmonic) violin mode is expected to be somewhere between 500Hz and 520 Hz. Not every line is present - possibly due to high noise floor.

The violin mode has been previously identified as follow:

Positions of the wire:

BL = Back Left

BR = Back Right

FL = Front Left

FR = Front Right

Where's left and where's right you ask? I'm trying to find the answer myself!

I have started a SenseMon instance running on the dewhitened H1:OAF-CAL_DARM_DQ channel. The lock detection uses the guardian ISI lock channel as recommended by Jamie. I have set up a dmtviewer configuration to plot both the L1 and H1 ranges. The dmtviewer file is in 

   /opt/rtcds/userapps/release/isc/h1/scripts

and is called HL-Range.xml. I also added a script to set the DMTWEBSERVER environment variable so that it can find the web servers at both observatories. This is in the same directory and can be run from bash with 

   cd /opt/rtcds/userapps/release/isc/h1/scripts
  source dmtvsetup 

Then run dmtviewer with e.g.

  dmtviewer HL-Range.xml &

Note that this requires kerberos authentication so you must kinit and supply a key tab or username/password.

 

Lisa, Peter, Alexa, Evan

We have closed WFS loops to stabilize the angular motion of the BS during full lock.

We looked at ASA36Q and ASB36Q while giving small steps to the BS angle. We found that ASB36Q responds with the wrong sign (i.e., if the BS step gives an improvement to POPAIR18 and ASAIR90, the ASB36Q signals move away from zero), so we aren't using it. ASA36Q has the right response, so that's what we're using.

In the ASC-MICH filter banks, we are using FM1 (-20 dB), FM2+FM3 (1/f shape everywhere), and FM10 (inverse BS angular plant). The gains for both pitch and yaw are 0.3 ct/ct. The time constants of the loops are about 1 s.

On the BS suspension, we are feeding back only to M2. M1 is off. We are leaving the BS oplev damping on.

TCS slow channels

Alastair, Aidan, Dave. WP5043

The two laser setpoint channels which were temporarily added to script0's IOC last friday were removed and replaced by these plus more chanels in the h1tcscs front end model. The full list of new channels added to tcs/common/model/TCS_MASTER.mdl are

• H1:TCS-ITMX_CO2_LASERPOWER_SETPOINT
• H1:TCS-ITMX_CO2_LSRPWR_SETPOINT
• H1:TCS-ITMX_CO2_LASER_INTERLOCK
• H1:TCS-ITMX_CO2_CHILLER_TSTEP
• H1:TCS-ITMX_CO2_PZT_VOLTAGE_LCKPT
• H1:TCS-ITMY_CO2_LASERPOWER_SETPOINT
• H1:TCS-ITMY_CO2_LSRPWR_SETPOINT
• H1:TCS-ITMY_CO2_LASER_INTERLOCK
• H1:TCS-ITMY_CO2_CHILLER_TSTEP
• H1:TCS-ITMY_CO2_PZT_VOLTAGE_LCKPT

TCS_MASTER.mdl submitted to SVN r9793. This closes WP5043

PEM DAQ channels

Peter F, Robert S, Dave. WP5042

The PEM models h1pemcs, h1pemex, h1pemey, h1pemmx and h1pemmy were modified to conform with Peter and Roberts PEM data rates to frame document T1400768. There remains an inconsistency in the number of magnetometers and accelerometers, so this WP will remain open. Code was committed to SVN r9794

PCAL addition of working standard channel

Rick, Sudarshan, Dave. WP5045

An additional ADC channel was added to the PCAL model to read out the Working Standard signal. The model files pem/h1/models/h1pem[ex,ey] and cal/common/models/PCAL_MASTER.mdl were modifed. The new code went in at the same time as the above PEM restarts because CAL and PEM were merged. The PCAL_MASTER.mdl was committed to SVN r9763. This closes WP5045.

DMT Broadcaster and DAQ configuration

John Z, Dave

The following channels were added to H1BROADCAST.0.ini

• [H1:GRD-ISC_LOCK_ERROR]
• [H1:GRD-ISC_LOCK_MODE]
• [H1:GRD-ISC_LOCK_OK]
• [H1:GRD-ISC_LOCK_STATE_N]
• [H1:OAF-CAL_DARM_DQ]

The ALS testpoint par file was added to the DAQ (was accidentally left out during the ISC split last week)

DAQ Restart

Jim B, Dave

To support all the above, the DAQ was restarted. Jim delayed the startup of h1fw1 and h11nds1 to reconfigure their NFS mounts to support minute trend offloading on h1fw1.

Cleanup

Dave

I pressed all the DIAG_RESET buttons to clear accumulated ADC,IPC,etc. errors.

The following models had modified filter file warnings, I did a full filter file load on them: h1susmc2, h1iscex, h1iscey.

h1susmc2 did not seem to actually have a modified file (filter_archive files were identical).

isc end stations were a residual of the ISC split last week, so of the filters left in the isc models no actual filter changes were applied.
 

== Daily Ops Summary ==

06:50 Jeff to LVEA/PSL
07:30 Karen to LVEA
08:00-10:00 Jeff runs a test on HEPI pump servo
08:02 Peter King to H2 enclosure
08:04 Rick worked on PSL. IMC state DOWN, input to frequency servo disabled
08:11 Corey to EX (30 mins)
08:16 Andreas and Aiden to TCS area around HAM4
08:30 Jamie runs Guardian upgrade testing on ITMX seismic system
      Fil and Richard to HAM4, 5 ISI and STS2
      NDS servo shutdown
09:00 Joathan and a visitor went to LVEA
08:45 Sudarshan and Thomas to End Y (PCal)     
09:00 Cyrus to LVEA
      Karen to Mid Y
09:17 Cyrus back
09:04 Corey back from EX -> heading to VLEA
09:06 Ali to EX, EY
09:24 Doug to LVEA H1 PSL Area
      Matt to H2 enclosure
09:26 Hugh to LVEA
09:40 Karen left Mid Y
      Jeff restarted pump servo (EX)
      Travis taking TFs (ETMX SUS)
9:50 Corey back
     Jonathan and the visitor back
     Jeff - HEPI Pump servo mag. sys. identificaion 
10:00 Jim restarting PEM model for Corner, Mid, and End stations
      Jim restarting TCS (Corner Station)
      Doug back from the LVEA
10:31 Aiden and Alestair to X manfold lab
10:46 Jeff done with pressure servo test
11:05 TJ and Mitch - forklift from mech. room to VRW
11:09 Travis done measuring TFs (ETMX)
11:15 Jeff brought down ETMX chamber
11:19 Jeff brought ETMX to safe
11:25 Thomas and Sudarshan back
11:09 Travis done measuring TFs
11:15 Jeff brought down ETMX Chamber
11:19 Brought ETMX Chamber to SAFE
11:25 Sudarshan and Thomas back 
11:30 Rick et al back, IMC locked
11:37 Jim restarted DAQ
12:58 Jim restarted OAF
15:52 Peter K. back

Happy Maintenance Day

Attached is spectra from WHAM6 looking at the GS-13 INF IN1s--before the digital filters.

The Red traces where taken at 1417utc (~6am local) with the FM4 & FM5 ON, my understanding and based on the plots here, this is analog low gain and whitening.

The Blue traces are from 1550utc with FM4 ON and FM5 OFF--analog low gain but not whitened.

Green traces are from 1650utc with both FM4 & 5 OFF--analog high gain and not whitened; The brown traces start at 1722utc with FM4 OFF and FM5 ON, that is, analog whitening and high gain.

Again, based on the plots, the switches appear to be doing what I thought and expect.

Do we have saturations when in whitened high gain?  No, based on the H1:FEC-51_ACCUM_OVERFLOW, no saturations accumulated during any of the measurements.

What about being ADC limited in low gain without whitening.  Included on the traces are the ADC noise from the svn.  It certainly looks like in low gain without analog whitening, we approach the ADC limit at 100Hz and very likely about a few 100Hz.

Conclusion--Leave FM5 ON all the time--we are not saturating in high gain and we are near the ADC noise in low gain without whitening...but wait:

But what about those ugly lumps between 200 and 400Hz?  They do not show up on the unwhitened hi gain signal but are evident on the other three configurations.  The ringing is exactly 1Hz and the beating is about 45Hz.  Maybe this suggests a problem with the whitening filter?  Maybe we should not whiten the signal when in high gain.

I added a zoom in of the high frequency beat  stuff.

From JeffK's 16425, while I'm a bit confused as to Jeff's language I think i understand:

These two states are compensated for digitally in FMs 4 and 5 of the GS13INF banks, by the difference between the two states (the overall gain of 2 is folded into the calibration filter). FM4 is the switchable gain compensation, FM5 is the switchable compensating de-whitening filter. The front-end code for the HAMs and BSCs is set up that these digital banks control the analog switching. 
- When FM4 is ON, the gain switch is HI (or a binary output of 1), so the analog gain is 2, and FM4 compensates the gain of 10 difference. 
- When FM4 is OFF, the gain switch is LO (or a binary output of 0), so the analog gain is 20.
- When FM5 is ON, the analog whitening is LO (or a binary output of 0), so there is no whitening, and FM5 compensates the z:p = 50:10 difference. 
- When FM5 is OFF, the analog whitening is HI (or a binary output of 1), so the whitening is engaged.

and I think the FM5 states are backwards as to the above verbeage.  The digital DWH filter certainly looks like a De-Whitening and the above traces bare out the FM5 enables the analog whitening.

dtt template is in /ligo/svncommon/SeiSVN/seismic/HAM-ISI/H1/HAM6/HAM6_GS13_GAIN_DWH.xml

J. Kissel

I've performed the same step response system identification (SysID) for the two end station HPI pump systems, as I'd done for the corner station HPI pump system (see LHO aLOG 16447), now that both ends are using the differential, supply - return, pressure signal that close to the chamber (EY switched in Nov 2014 LHO aLOG 14888; EX switched this morning LHO aLOG 16595).

Results: The low frequency response is well-characterized by
EX: a single pole at 12 +/- 1 [mHz] and a DC gain of 0.163 [PSI/ct]
EY: a single pole at 17 +/- 1 [mHz] and a DC gain of 0.141 [PSI/ct]
and for quick reference,
L0: a single pole at 24 +/- 1 [mHz] and a DC gain of 0.0546 [PSI/ct]
I quote an uncertainty on the pole frequency because the fitting method -- matching the step response against data by-eye -- is crude (though sufficiently accurate for my needs). I don't quote an error bar on the DC gain because the fitting method for that is quantitatively robust and the uncertainty is negligible.

The three attachments are the raw data and fitting for EX and EY, and a plot showing the (low) frequency response of all three models together.

I'll speak more on this in a later entry and/or DCC document, but note that this estimation of the plant via step response does *NOT* measure several other parameters that determine the high-frequency (above ~1 [Hz]) response that I've discovered to be relevant to the PID loop design  (in particular, the phase), including
- The second-order, 16 [Hz], Sallen-Key, anti-aliasing filter before the input to the ADC on all pressure sensor channels (see D0901559, pg 2)
- The [clock cycle / sampling rate] time delay
- Any epics smoothing parameters that have been installed on any pressure sensor channels
Including all of these features, I think I'm finally able to predict what we see in the closed-loop amplitude spectral densities (see, e.g. 16474, or 16426). Stay tuned.

Log files of the excitation, including GPS times of step impulses:
/ligo/svncommon/SeiSVN/seismic/HEPI/H1/Common/
2015-02-10_HPIPumpServo_EX_OpenLoopSteps.txt
2015-02-10_HPIPumpServo_EY_OpenLoopSteps_SMOO_ON.txt

Scripts to load and process the data (needs on-site nds access, but could be modified to gather data remotely):
/ligo/svncommon/SeiSVN/seismic/HEPI/H1/Common/
H1HPI_PumpServo_EX_StepResponse_20150210.m
H1HPI_PumpServo_EY_StepResponse_20150210.m

Rick S., Jason O., Matt H., Ed M., and Jeff B.

Went into the PSL today and performed a few maintenance tasks (work permit #5039).

1) Measured PSL power at several points in the beam path:

• 33w - between M1 & M2 (just outside of the front end)
• 26w - reflected from PMC
• 27.2w - incident light on PMC
• 24.4w - downstream of the EOM (in the IO section of the PSL table)
• 24.9w - PMC transmitted

• 67.5mW – upstream of the FSS AOM
• 54.5 mW - Single pass power, upstream of M25 (81%)
• 36.3mW - Double pass power, upstream of FSS EOM (66%, 54%)
• 33.7mW – At top of periscope mirror, incident on RefCav

3) Measured voltage of RefCav REFL PD (H1:PSL-FSS_RFPD_DC_OUTPUT):

• 299mV – With FSS RefCav unlocked
• 165mW – With FSS RefCav locked
  • This is too high, giving a RefCav visibility of only 45%!

Once again the RefCav Trans PD (TPD) has begun to drift down.  Was set to ~1.6V on 1/5/2015 (see alog 15871) and today is reading ~0.9V.  Therefore we adjusted the RefCav alignment by adjusting the vertical and horizontal of the top periscope mirror.  Measured voltages at the RefCav REFL PD.

• Vertical adjustment dropped RefCav to 83mV
• Horizontal adjustment dropped RefCav to 65mV

After adjustment (and locking of adjustment screws):

• RefCav REFL PD - 300mV (with FSS RefCav unlocked)
• RefCav REFL PD - 60mV (with FSS RefCav locked)
  • This gives a FSS RefCav visibility of 80%, which is better.  Per Rick S. this should closer to 98%, so some more work to do here, but is good enough for now and we were running out time in our maintenance window.
• RefCav TPD - 1.63V (H1:PSL-FSS_TPD_DC_OUTPUT)
• RefCav transmitted power - 19.1mW

Will keep an eye on this as the RefCav transmitted power seems to drift down suddenly.  We’re not sure what’s causing this apparent alignment drift.  All the measured powers leading up to the RefCav were close to those measured during the 1/5/2015 adjustment, but the RefCav TPD was still reading ~44% less.

4) We also measured the UGF of the FSS:

• UGF: 200kHz, phase margin 35 deg
  • According to Rick S. this should be closer to 600kHz, so we have some work to do here.
• At 500kHz: -6dB, phase margin 58 deg 

5) For Daniel, we adjusted power at IO PD (IO-AB-PD3-DC) to 3.3V by turning up the PD gain by 3 clicks and adding a ND filter to the PD (see Daniel's earlier alog).

6) We are now storing the 2 3IFO PMCs in the NW corner of the PSL LAE on a cart, with their lids off.

Summary:

Looking at ITMx HWS data from full interferometer locks on 7 Feb and 9 Feb, here are some estimates of ITMx coating absorption:   500(150) parts per billion measured on Feb 7,  9 Feb: 430(130) ppb measured on Feb 9.  For reference, Livingston measured 140-200 ppb coating absorption on the ITMs, see log 14634.

Method:

-HWS measures spherical power.  The raw data was multiplied but a factor of 0.00326 in dataviewer to account for magnification of the image, which gives Spherical power in diopters.   The change in the spherical power before and after the interferometer drops lock was ~5*1(0.02) microdiopters both days.  The measurements were averaged over a few minutes.

-The shperical power is related to absorbed power by 1.06(0.3) mW/microdiopter (log 14634) which means ~5mW power was absorbed.

-On 7 Feb 10.4 kW was in the x-arm, on 9 Feb 11.5 kW was on x-arm (calculated as per alog 16579).  I've assumed 10% uncertainty on this power, but perhapse that is too small.

[absorption in ppb]=[absorbed power]/[locked arm power] *1e9

Datasets and code are saved in /ligo/home/eleanor.king/HWSreadouts.

Jeff restarted ETMX SUS, but this didn't solve the decimation problem reported in alog 16511.

All models on h1oaf0 stopped running just before 1:00 PM PST with ADC timeout errors.  Had to kill the user models and restart the IOP model to recover timing, then the user models were restarted.

Richard, Filiberto

Late last week I noticed the current meter for the Ham4 and Ham5 +-24V ISI DC supplies that feed the coil drivers were oscillating at about 1Hz and 0.5amps.  Today we connected a meter to the output lines of the supply and systematically shut down the ISI system starting with the Ham4 moving to Ham5.  First step was using guardian to take the system to READY state.  We then shut off the outputs using the watchdogs.  The oscillation remained until we shut off the 2nd Ham5 coil driver.  The system was brought back up and the oscillation was gone.  Re-engaged the software had guardian take it back to isolation.  Still no oscillation present.  I will check the power on this system during the week to see if it goes back into oscillation.    There was no obvious problem with the HAM isolation during this time.  If the oscillation returns we will power the HAM 5 electronics down first to see if this corrects the problem.

The h1nds1 NDS server has been reconfigured to serve past data from the same disk systems as h1nds0.  The /trend/minute_raw data has been renamed, and is being copied to /frames/trend/minute_raw because the /trend file system is nearly full.  The h1fw1 is still writing minute_raw files, so there will still be a redundant source for the files.

Added 26 channels. Removed 105 channels.

On Nov 7 I added smoothing to the terribly noisy channels generating the differential pressure.  I revert these back to no smoothing.

The first attachment is a time series of the HAM6 Watchdog, the Fastshutter State, and a GS-13 trace on HAM6.  The switch to low Gain is clear on this last trace.  This is a 5 day trend and the ~20 minutes needed to get the below .005Hz BW data is comfortably unmolested by the ISI or the fastshutter--the start times of the Spectra calculations begin at the vertical black lines.  As for ISI trips and shutter fires--there were none.

The High Gain Spectra period begins at 0800utc on 29 Jan, the Low Gain Spectra begins at 0800utc 1 Feb.

The second attached graph has Horizontal GS13s on HAM6 in High and Low Gain on the upper plot.  The Verticals are in the lower plot. High Gain Spectra is Dashed, Low Gain traces are Solid.  Also shown is our ADC noise in counts.

One caveat is that the ground motion is different at the two times.  The third attachment shows the Cartesian DOFs for the HAM6 GS-13s in the upper two plots and the ground noise in the bottom plot.  We've had a ground motion decrease in the microseism frequencies and below during the low gain period.  You can see the Low Gain Spectra are at the ADC level below 50mHz.  And the 10x signal reduction expected is more like 5x below these frequencies.  If this conclusion passes mustard, we'll have to revisit the GS13 triggering delays/levels.

DTT template is /ligo/svncommon/SeiSVN/seismic/Common/MatlabTools/HAM6_GS13_GainNoiseTest.xml