Ops Day Shift Summary

TITLE: 09/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Tuesday maintenance this morning went fairly smoothly after troubleshooting a failing network switch. Once maintenance activities wrapped up, commissioners continued to work on ALS locking with DIFF on ETMY, which is ongoing. Dust alarms have been going off this afternoon in the optics lab and PSL.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
14:58	FAC	Kim	LVEA	-	Technical cleaning	16:13
15:01	CDS	Richard	CER	-	Checking network switch	15:14
15:14	VAC	Richard	LVEA	-	Checking a turbopump	15:23
15:21	VAC	Jordan	LVEA	-	Prep for craning	16:21
15:22	FAC	Chris	All bldgs	-	FAMIS/safety checks	17:54
16:01	CDS	Erik	Remote	-	h1guardian1 reboot	16:16
16:25	VAC	Jordan, Randy	LVEA	-	Craning over X arm	17:21
16:28	EE	Fil	LVEA	-	Check picomotor cabling at HAM3	18:17
16:31	SUS	Rahul	Remote	-	ETM charge measurements	18:04
16:49	FAC	Kim	EY	-	Technical cleaning	17:39
16:59	EPO	Cory	LVEA	-	Filming	18:23
17:26	FAC	Richard	EX	-	Checking TMDS readiness	18:18
17:39	ISC	Camilla, Miranda	LVEA	-	ISCT1 curtains	18:09
17:39	PSL	Jason	LVEA	-	Looking at electronics	18:03
17:39	FAC	Kim	EX	-	Technical cleaning	19:02
18:03	CAL	Tony, Caroline	PCal Lab	Local	Swap spheres	18:56
18:08	EPO	Ibrahim +1	LVEA	-	Tour	18:33
18:13	VAC	Jordan, Gerardo	LVEA	-	HAM7 RGA checks	19:02
19:40	FAC	Chris	LVEA	-	FAMIS/safety checks	20:40
20:42	CDS	Erik, Dave	CER	-	Pulling switch power cord	21:42
20:46	VAC	Jordan, Gerardo	EX	-	Moving TMDS equipment	22:28
22:36	EPO	Camilla, Cory	Roof	-	Filming	22:53
22:44	SPI	Jennie, Jim	LVEA	-	Plugging oscilloscope into SPI racks	23:13
22:55	TCS	Camilla	Prep Lab	-	Labelling cables	23:29

Documention for HAM3 Flange D3 and D6 Cabling As-Built

WP 13563

Late entry from August 27, 2026

Sheila informed me the HAM3 ISC picomotors were not responding. Verified the picomotor cable was connected to the driver. Verified driver was responsive. The air cabling on HAM3 flange D3 did not match the DCC D1002874 drawing. Recall Keita found the POP QPD connected to the wrong port on flange D3, alog 91409.
We convinced ourselves all the connected cables on the D3 flange (SUS/ISC/SEI/CRS) were connected correctly, all seem to be working. All open ports are spares, ports for the LO1 future installation, or the ISC Picomotors. The picomotor cable was moved from D3-F8 to D3-F7. This means according to Keita’s alog, the QPD cable was originally connected to the picomotors. Sheila verified picomotor were working.

Similar cabling issues were found on the D6 flange, see alog 91226.

The following DCC documentation needs to be updated:
SUS BSC2 HAM3 HAM4 (susb2h34) System Wiring Diagrams D2300383
ISC/SQZ Wiring Diagram for Corner Station D1900511
Flange Layout - H1 Horizontal Access Module 3 (HAM 3) D1002874

As the DCC documentation is out of date, a list of our as-built flange for Flange D3 and D6 is listed below:

Flange - Port	Description	Cable
D6-F1	SUS MC2 M3 OSEMs	SUS_HAM3_20
D6-F2	MC2 M1 T1T2T3LF OSEMs	SUS_HAM3_1
D6-F3	MC2 M2 OSEMs	SUS_HAM3_19
D6-F4	SPARE
D6-F5	SPARE
D6-F6	SPARE
D6-F7	SPARE
D6-F8	SPARE
D6-F9	SPARE
D6-F10	SPI PDs	SPI_HAM3_15
D6-F11	SPI Picomotors	SPI_HAM2_13
D6-F12	SPARE

 

Flange - Port	Description	Cable
D3-F1	MC2/PR2 RTSD/T1T2 OSEMs	SUS_HAM3_2
D3-F2	PR2 MM1 T3LFRTSD OSEMs	SUS_HAM3_3
D3-F3	PR2 M2 OSEMs	SUS_HAM3_25
D3-F4	PR2 M3 OSEMs	SUS_HAM3_26
D3-F5	LO1 M1 F1F2F3LF	Future Install
D3-F6	POP QPD	IO_245
D3-F7	IO/ISC PICOMOTORS	ISC_230
D3-F8	LO1 M1 RTSDxxxx	Future Install
D3-F9	SPARE
D3-F10	ISI GS13 H3V3	SEI_GS13_3
D3-F11	CRS PD READOUT & CONTROL	CRS_HAM3_006
D3-F12	CRS PD READOUT & CONTROL

 

CDS Maintenance Summary: Tuesday 1st September 2026

WP13560 CAL CS remove channels

Joe, Erik, Jonathan, Dave:

We installed a new h1calcs model which removes channels from the DAQ. We verfified none of these channels were being sent by the DAQ broadcaster.

The rev-update showed a surprising number of modified mdl files used in the build, details are:

Changed dependency revisions in new version:
cal/common/models/CAL_CS_MASTER.mdl : r28532 --> r35947
cal/common/models/CAL_LINE_MONITOR_MASTER.mdl : r28567 --> r35947
cal/h1/models/h1calcs.mdl : r27506 --> r35949
sus/common/models/ESD_LINEARIZATION_WITH_CHARGE_MASTER.mdl : r16336 --> r30316

Removed dependencies in new version:
cds/common/src/ATAN2.c
 

The INI file just changed by the removal of the channels:

--: slow channel H1:CAL-CS_DARM_ARM_LENGTH_AVG removed from the DAQ 
--: slow channel H1:CAL-CS_DARM_ARM_LENGTH_X removed from the DAQ 
--: slow channel H1:CAL-CS_DARM_ARM_LENGTH_Y removed from the DAQ 
--: slow channel H1:CAL-STRAIN_SLOW removed from the DAQ 
--: fast channel H1:CAL-STRAIN_DBL_DQ removed from the DAQ 
 

sw-lvea-aux crash, reboot, build replacement

Richard, Fil, Erik, Jonathan, Dave:

As noted in other alogs, a lot of today's time was taken investigating and recovering the CER main POE switch which drives the majority of the gige-cameras. Erik is building a spare Cisco Catalyst 3560 switch as a swap-out replacement.

WP13569 Guardian reboot

TJ, Ryan S, Erik:

h1guardian1 was rebooted for PM and to clear its CFC flags. No problems with this reboot.

WP13578 Add Guardian nodes to DAQ

TJ, Dave:

H1EPICS_GRD.ini was modified to add the two new guardian nodes CRS_HAM3 and SPIH23_STAT (+46 chans). EDC+DAQ restart was required.

DAQ Restart

Erik, Jonathan, Dave:

The DAQ was restarted for the new h1calcs model and EDC additional grd channels.

This did not go well.

( A Reminder: in the new DAQ, the framewriters continue to run throughout, switching to the new configuration automatically. Only the DC, NDS and TW restart)

At 11:13 I restarted the 0-leg. This caused both FW0 and FW2 to crash. We then restarted the EDC, but the framewriters did not come back.

Erik restarted the FW daqd services, noting these now have new names (rts-daqd_rs.service)

Jonathan looked at the 0-leg logs, we determined there was nothing we could do to prevent FW1 from failing, we would just recover it afterwards.

At 11:41 we restarted the 1-leg, and FW1 did not restart. It behaved normally, picking up the new run number and configuration.

Jonathan is investigating what happened to FW0/2 and why FW1 did not crash.

sw-lvea-aux failed again 11:09:57

After getting the switch going again at 08:46 it only lasted about 2.5 hours before going down again at 11:16. We immediately did the "pull the cords" power cycle which got it running again at 11:16.

At time of writing (15:34) it has been running for 4.25 hours.

SPI dark noise measurement

Jennie W, Sina K,

Summary: Yesterday Sina and I did the dark noise measurement for the SPI interferometer and the two SPI optical levers and added in calibration filters based on Jim's measurement of the optical lever to ISI sensor TFs. We also founbd that the dark noise for QPDA has an unexpected shape and so need to do some noise hunting to track this down.

Before doing this we edited the SPI-H23_DIFFDISP matrix to include the factor of 2 that comes from the fact the IFO measures the light round trip between the two platforms and we want it to measure the displacement between them, ie. we divided the first line of coefficients by 2.

Jeff has implemented a new filter bank set for the optical levers called OPLEV CAL FILTERS on the main SPI overview. See image. The output of this filter bank is the optical lever in the qpd basis. The measured calibration will go in 'OPLEV OUT FILTERS' and the output of this filter bank will therefore be in the ISI basis.

We then followed the procedure in T2600019.

• With the laser unshuttered measure the average and amplitude of the photodiode signals on the ADCs. Then measure the average signal in the QPD quadrants. Here is the diaggui template where I measured the signals with the laser unshuttered.
• Shutter the light and use awg to create fake signals into the SPI-H23_SIG filter banks for each PD. This should be at 4096 Hz with a 180 degrees phase offset between the A and B PD signals. We used a script to calculate the average and peak to peak values for each interferometer based on what the real data gives us.
• For the QPDs use static offsets in the QPD input filter banks to give the correct average power (picture taken today so offsets turned off).
• We did a measurement to check that the values we chose gave what we expected. Note the input filters banks for the QPDs convert the signal to V so these plots are in V while the IFO plot in the top left is in counts. The average values for all the signals match our measurement with the laser unshuttered and the amplitude for the interferometer signals matches what we measured from real data.
• The amplitude spectral density of PD and QPD signals is shown here. Top left is the displacement of the interferometer with no light. It is calibrated into nm/sqrt(Hz) using the equation disp = lambda/(2pi*phase) which is implemented in the H23 IFO DISP filter bank. Bottom left is the QPD A channels in normalised units (ie. the pitch and yaw readings normalised by the total sum of the signal from each quadrant) in pink and light blue. The other four traces are taken downstream after the theoretical calibration is applied in the CAL filter bank and at the output of the OPLEV OUT filter bank. Top right plot shows the same channels for QPDB and HAM2, again showing the value for pitch and yaw of QPDA in pink and light blue and then showing the output of the CAL and OUTPUT filter blocks for QPDA and ISI J.
• After comparing the theory calibrations with the measured ones Jim obtained in alog # 91754, Sina realised (SWG log #12414) that the QPDB theory calibration is wrong by a factor of 2 due to the fact that its beam is a back reflection from a mirror in HAM2 and so measures twice the angle that the ISI rotates by.
• I updated the calibration in the QPDB CAL filter banks (pitch and yaw) and also added a measured calibration factor in the OPLEV OUT filter banks. This correction factor is (measured calibration in nradians/normalised QPD units) / (theory calibration in nradians/normalised QPD units. QPDB Pitch to HAM2 Pitch, QPDB Yaw to HAM2 Yaw, QPDA Pitch to HAM3 Pitch, QPDA Yaw to HAM3 Yaw.
• I took another measurement with the meaasured calibrations for the optical levers turned on. Top left is again the interferometer displacement in nm/sqrt(Hz), top right now has the rotation of HAM2 in QPD A basis with theory calibration included and in ISI basis with measured calibration included. Bottom right now has the rotation of HAM3 in QPD B basis with theory calibration included and in ISI basis with measured calibration included.
• The comparison between the dark noise of the two QPDs in normalised units (ie before calibration is applied) is shown in the bottom left. We understand the shaping of QPDB as being mainly due to the whitening filter which has a pole at 0.39Hz and a zero at 39.8 Hz, implying the dark nosie is dominated by ADC noise. The shape of QPDA does not match this whitening filter and so there must be some other electronic noise dominating. This requires further investigation.

 

Framewriter 1 crashed during restart

h1daqfw0 crashed during the daq restart while trying to load metadata.  Log output for the service showed a panic on an out of range request.

Sep 01 11:13:10 h1daqfw0 daqd_rs[10370]:  - going to request channel list update
Sep 01 11:13:10 h1daqfw0 daqd_rs[10370]: attempting to load metadata from /opt/rtcds/lho/h1/daq0/running/master
Sep 01 11:13:11 h1daqfw0 daqd_rs[10370]: loaded metadata from /opt/rtcds/lho/h1/daq0/running/master, it took 1.0284032s
Sep 01 11:13:11 h1daqfw0 daqd_rs[10370]:  - going to request channel list update
Sep 01 11:13:11 h1daqfw0 daqd_rs[10370]: attempting to load metadata from /opt/rtcds/lho/h1/daq0/running/master
Sep 01 11:13:12 h1daqfw0 daqd_rs[10370]: thread 'dq_input' (10428) panicked at ifo_stream/src/data_store.rs:527:13:
Sep 01 11:13:12 h1daqfw0 daqd_rs[10370]: available range is [0..245944), requesting [245944..245948) IFOChannel { name: "H1:DAQ-DAQSTAT_FW_SECOND_FRAME_GPS_STATUS", dcu_id: 52, ifo_id: 0, data_type: Float32, seq_num: 237380, ch_num: 0, data_rate: 16, bytes_per_cycle: 4, offset: 245944, test_point_dcu: None, acquire: 1, signal_gain: 1.0, signal_slope: 6.1028e-5, signal_offset: 0.0, units: "V" }
Sep 01 11:13:12 h1daqfw0 daqd_rs[10370]: note: run with 'RUST_BACKTRACE=1' environment variable to display a backtrace

A restart of the rts-daqd_rs service restored the server to normal operation.

Re-opened H1SPIH23 shutter; turned OFF OL Offsets

J. Kissel

Jennie and Sina's work were measuring DARK noise of the SPI PDs yesterday (aLOG pending) and neglected to unshutter the light going into the SPI system. I un-shuttered the light by hitting the H1:SYS-MOTION_C_SHUTTER_N_OPEN button linked from the top-middle of the overview screen. The SPI was dark from 2026-08-31 21:13 UTC to 2026-09-01 16:58 UTC.

Also, I reset the phase unwrapping in the SPI L IFO PD signal processing.

I also turned OFF the H1:SPI-H23_OL_QPD_{A,B}_SEG{1,2,3,4}_OFFSET offsets that were used to replicate the SUM on the QPD when there's no light present, but accepted the values in SDF.

MEDM Infrastructure for QPD Calibration

J. Kissel

Finishing the job started in LHO:91705, in which we added filter banks to calibrate the H1SPIH23 optical lever's QPDs from units of normalized spot position ([V/V]) into angular displacement of the respective ISI ([rad], or the preferred order of magnitude [nrad]) -- I 
   - created a new 4x filter bank cluster screen for the 
       H1:SPI-H23_OL_QPD_A_PIT_CAL (measuring HAM3 rotation)
       H1:SPI-H23_OL_QPD_B_PIT_CAL (measuring HAM2 rotation)
       H1:SPI-H23_OL_QPD_A_YAW_CAL
       H1:SPI-H23_OL_QPD_B_YAW_CAL
     channels; 
         /opt/rtcds/userapps/release/spi/common/medm/
             SPI_CUST_OL_CAL.adl    rev 35979
   - added a block with link to these banks to the SPI OVERVIEW screen,
         /opt/rtcds/userapps/release/spi/common/medm/
             SPI_CUST_OVERVIEW.adl    rev 35979
     and along the way also modded the overview with a few other things that have popped up as requests for user interface:
        . top-level views of the QPD XY scatter plots so we have an "at-a-glance" view of whether they're centered, 
        . Another column to the PICOMOTOR section that helps the reader understand which actuator aligns which beam
   - Filled in the CAL filterbanks with the calibration from LHO:91754.
        /opt/rtcds/userapps/release/spi/h1/filterfiles/
            H1SPIH23.txt    rev 35985.
   - Made sure to *initialize* the above bank's channels in the SDF system, and accepted the values.
        /opt/rtcds/userapps/release/spi/h1/burtfiles/
            h1spih23_safe.snap   rev 35986.

Thus, 
       H1:SPI-H23_OL_QPD_A_PIT_CAL_OUT_DQ (measuring HAM3 rotation)
       H1:SPI-H23_OL_QPD_B_PIT_CAL_OUT_DQ  (measuring HAM2 rotation)
       H1:SPI-H23_OL_QPD_A_YAW_CAL_OUT_DQ 
       H1:SPI-H23_OL_QPD_B_YAW_CAL_OUT_DQ 
are now calibrated into [nrad] of ISI rotation, based on the *measured* values of the calibration from LHO:91754.
     
        
     

Network switch sw-lvea-aux in CER stopped working at 23:47:15 Mon 31 Aug 2026, caused loss of PSL diode room and camera connectivity

Richard found that the actual problem was the loss of the CER Cisco network switch sw-lvea-aux. Its power supplies are both showing fault lights, there are leds lit on the rear but the front of the switch is not showing activity lights except SYST is flashing.

Fil is power cycling the unit with a "cords out" power down.

The backup POE Cisco sw-lvea-aux1 may have to be pressed into service if we cannot get aux working.

I looked at the CS mains power monitor, nothing suspicious was happening at this time.

Ops Day Shift Start

TITLE: 09/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 4mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY: PSL Beckhoff is down, but apparently the laser is still running? Possibly just a readback issue (PSL overview attached). All CDS cameras appear to be down (blue screen), including PSL enclosure cameras. Will talk to Dave/Patrick about this.

Several Tuesday maintenance activities planned for today, including a Guardian machine reboot, DAQ restart, and some craning in the LVEA.

PSL diode room Beckhoff controller offline, 23:47:15 Mon 31 August 2026 PDT

EDC lost connection to all the PSLNEOLASE channels late Monday at 23:47:15. CDS hardware monitor IOC reported no connection with h1pslctrl0 at this time.

Workstations updated

workstations were updated and rebooted.  This is an OS packages update.  Conda packages were not updated.

trying to locking ALS DIFF on ETMY

Louis, Sheila, TJ, Camilla, Oli

We have been working on changes to lock ALS DIFF on ETMY.  

• We put the negative sign in the LSC output matrix to account for the DARM sign flip from switching arms, we will try to use the same bias and filter signs elsewhere because that seems easiest to keep track of. 
• On Friday we added a flag to lscparams:  no_ETMX_actuation to be set to true when we don't want any actuation on ETMX (basically only for this week when we have a rubbing issue), which also sets a flag that determines which ETM to use for locking ALS DIFF,     ALS_ESD = 'Y'.  We will need to clean this up a bit, but there are two slightly different purposes for the two flags, because we may want to run ALS on ETMY even once the ETMX suspension is fixed and can run slow feedback and WFS. 
• Filiberto got the ESD high voltage driver working: 91750
• Oli and TJ re-ran the baffle align scripts to reset the alignment of the TMSs and ITMs, since we may have wandered off with the X arm alignment with some ETMX shifts that happened on Friday:  91747
• the ETMY LR electrode does not work: 43053.  We changed the EUL2ESD matrix to only drive LL and UR to reduce the cross coupling to pitch from our length drive. (screenshot attached).  
• ALS COMM locked without any issue. This stayed locked while we locked and unlocked ALS diff many times, this is a nice feature compared to locking DIFF by actuating on ETMX.
• ALS DIFF we were able to keep locked by manually setting ALS Y to NO_SLOW_GR_WFS, and setting the DARM gain to 4.  It should be set to 400. 
  • Ramping the gain up to 8 rings up a 1Hz instability after ~10 seconds. 
  • ramping gain to 40 or 400 instantly breaks the lock, probably saturating the ESD.  
  • We tried copying the L1 L2P from ETMX, and turned off the L1 L2Y (was a scalar -0.002) neither of these things seemed to change the outcomes. 
  • We can leave the DARM1 gain at 4 and increase the L3 drivealign gain to 2.  This may be because our UGF is so low that L3 doesn't come above unity gain. 
  • We got a few points of OLG measurement with the gain at 4, attached. 

SPI QPDA & QPDB pitch and yaw calibration measurements

It took a couple tries last week, but I have taken HAM2&3 calibration transfer functions for SPI QPA and QPDB for pitch and yaw. I did this by using the  excitation in awggui that we have used for the CRS calibration using amplitudes similar to what Huyen used recently, located at /ligo/svncommon/SeiSVN/seismic/HAM-ISI/H1/HAM3/CRS/Templates/dtt/ryexc2.txt. For RY I used an amplitude of 7e3, for RZ I used an amplitude of 10e3. Isolation loops were engaged on both ISI's and they were running nominal blends (no crs on HAM3), but sensor correction and cps diff were both off.  For each measurement I've saved the excitation and relevant sensors timeseries into mat files that I am adding to SeiSVN/seismic/Common/SPI/DATA, as well as scripts for each excitation to get the data, save the timeseries structure and plot the tfs.

The four attach plots are the tfs for each excitation in the order HAM2 RY, HAM2 RZ, HAM3 RY, HAM3 RZ. For each tf, the SPI and CPS seem to agree very well over a few mhz to ~.2hz, the gs13s go a bit higher in frequency, but aren't good witnesses much below .1hz. On each plot I've indicated amplitude  of the spi to cps tf at one frequency point, I think the calibration should be the inverse of these values. I don't remember the units of the QPD channels, it's not cts. 

From those numbers I get:

HAM2 pitch calibration for QPDB is 19829 nrad/?

HAM2 yaw calibration for QPDB is 20400 nrad/?

HAM3 pitch calibration for QPDA is 231430 nrad/?

HAM3 yaw calibration for QPDA is 237700 nrad?

I think the HAM3 pit calibration is roughly inline with the one Arnaud calculated.

Excitations were all ~40minutes long. The timestamps for each injection are:

HAM2 RY: aug 28 2026 0:29:55 utc

HAM2 RZ: aug 28 2026 1:07:29 utc

HAM3 RY: aug 28 2026 2:00:00 utc

HAM3 RZ: aug 28 2026 2:49:14 utc

The question keeps coming up whether the QPDs were centered during these calibration runs, and whether the amplitude of the excitation was too large, pushing the spots outside of "centered" during the calibration excitation run.

Here, I attach a trend of the SPI optical levers' QPDA and QPDB during Jim's excitation. For a little more detail, the excitation points used were at the input to the isolation filter banks;
    H1:ISI-HAM2_ISO_RY_EXC_DQ >> PIT excitation
    H1:ISI-HAM3_ISO_RY_EXC_DQ
    H1:ISI-HAM2_ISO_RZ_EXC_DQ >> YAW excitation 
    H1:ISI-HAM3_ISO_RZ_EXC_DQ
and thus the units of the amplitude of the excitation he quotes are in nanoradians.

The response channels that Jim used are 
    H1:SPI-H23_OL_QPD_A_PIT_OUT_DQ
    H1:SPI-H23_OL_QPD_B_PIT_OUT_DQ
    H1:SPI-H23_OL_QPD_A_PIT_OUT_DQ
    H1:SPI-H23_OL_QPD_B_PIT_OUT_DQ
As discussed in, e.g. LHO:91210, these channels are records of the normalized spot displacement at the face of the QPD. Thus, the units of these channels are [V/V] ***, because we've chose to calibrate each QPD segment into ADC input voltage (in [V]). These are the units in the denominator of the transfer function Jim quotes "?" above.

The QPDs were relatively centered during these measurements (mean each less than +/- 0.02 [V/V]), and during the excitation, the response amplitude did not exceed +/- 0.15 [V/V].
As such, we can safely use the linearized version of the error function -- erf(z) -- to interpret the calibration of the optical lever QPD as linear (again, as discussed in, e.g. LHO:91210; erf(z) ~ 2 z / sqrt(pi) for  z less than ~0.5 ).

*** Because it's the ratio of identical units, the normalized signal will sometimes be labeled with "dimensionless" units, or "[radians]" I've even seen "[abs]," which may be a version (or typo) of "[arb.]" for "arbitrary units" which is a misnomer for "this signal is the ratio of two identical dimension-full signals, so *technically* you can label it with any ratio of identical units; [V/V], [m/m], or [elephants/elephants]. Don't be fooled. This signal is the ratio of dimension-full signals which started out as having units, and while arbitrary, we *chose* those units to be ADC input [V].

Also, Jim committed the raw calibration data and processing scripts to the SeiSVN -- see 
    /ligo/svncommon/SeiSVN/seismic/Common/SPI/Data/
        ham2_ry_injection_spi_data.mat
        ham2_rz_injection_spi_data.mat
        ham3_ry_injection_spi_data.mat
        ham3_rz_injection_spi_data.mat
and 
    /ligo/svncommon/SeiSVN/seismic/Common/SPI/Data/
        ham2_ry_spi_calibration.m
        ham2_rz_spi_calibration.m
        ham3_ry_spi_calibration.m
        ham3_rz_spi_calibration.m