J. Kissel, A. Pele, R. DeRosa

(c.f. LHO aLOG 14086)

After having spoken with the LLO team, Ryan informed me that he *did* in fact have to take considerable effort to re-arrange his sensor-correction STS2 readout system after initial install before he could use it. Regrettably, he hasn't written up any aLOGs or documentation on *how* his system is connected.

After a few more hours in the EE room, with new understanding of what was originally intended, and following cables through zipties and cable racks, I now understand that indeed the bulk of the problem is in the front-end models, AND that the HAM45 rack cables were just down-right disconnected at their AA chassis inputs for some reason. I've plugged them back in, and as suggested by Ben, in the order that the HAM16 wiring diagram (D1101584) suggests, such the DuoTone channels remain un-over-written, i.e. now ALL HAM ISIs and HAM HPIs have the following cable arrangment:
ADC_0_24   STS A X
ADC_0_25   STS A Y
ADC_0_26   STS A Z

ADC_1_24   STS B X
ADC_1_25   STS B Y
ADC_1_26   STS B Z

ADC_1_24   STS C X
ADC_1_25   STS C Y
ADC_1_26   STS C Z

As such, I don't think I need any more analog changes to the system, but it's time to dig into the top-levels of the front end models, now that I understand how the analog system is wired up. I attach a system drawing which I intend to follow, which is now a part of ECR E1400386, II 942, all cited in Work Permit 4876. I'll begin work as soon as I'm authorized, and Ben will begin updating the drawings accordingly.

Aleaxa, Kiwamu, Jenne, Sheila

• We turned on the ITMX oplev servo because we saw an oscialltion at 0.55 Hz by 2 urad pp (with sensor correction off)
• We need to install the 45 MHz amplifier to get reasonable signals for 3F.

We worked on DRMI tonight, it is locking at 1Watt within a few minutes. We are using gains of 22 for PRCL, 40 for MICH, and -400 for SRCL.  We are using the PSL-POWER_SCALE_OFFSET, so the gain settings and trigger settings in the gaurdian are now set for 1 Watt input power, but we could scale them to 10 Watts. We have been locking sometimes without the 27 Hz notches in M2 of PRM and SRM, and munually turning them on after it locks (this is needed to prevent the suspensions from ringing up).  We are using the guardian for everything else, including the offloading to M2. 

We started to measure the relative gains between 1F and 3F ( we think we need a gain of 3.2 in the input matrix to swtich PRCL to REFL 27 I) but quickly realized that we don' t have enough signal in REFL 135.  It seems like we need our 45 MHz amplifier installed before we can move on to 3 F. 

Times that DRMI was locked:

3:25 UTC october 1st - 4:21 UTC

5:10 UTC (maybe a few minutes earlier). This is still locked, Kiwamu is now scanning the OMC.

To do list:

• slow offloading to etms to help diff locking
• 3 f with amplifier
• as wfs

I started it back up with the previous channel list. It looks like it must be a problem with one of the channels that Dave tried to add. The error it logged was:

Sep 30 14:23:51 h1conlog2 conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Out of range value for column 'value' at row 1: Error code: 1264: SQLState: 22003: Exiting.

This would seem to imply that the value for one of the process variables was out of the range of the data type in the database. I'll try to narrow it down tomorrow.

See the linearity results attached.

The Range Of Motion results is unable to check (with the current script) H1-, V1+, & V4+ due to current offset on the IPS.  This needs to be reworked.

Maintenance Day Summary of CDS code Status:

Model code with local modifications with respect to SVN repository:

Alexa, Kiwamu, Jim, Dave

h1ecatx1 EPICS channels froze at 11:04PDT. The EPICS IOC was stil running, but all data was frozen and white-invalid. We restarted the computer and Alexa restarted the EPICS IOCs for SYS and PLC[1-3].

The ISS second loop photodiodes are very well coherent with the IMC WFS B yaw signal, as visible in the first plot.

This WFS is used for both DOF1 and DOF2 of the IMC alignment. I added an offset to the DOF1 yaw error signal. This improved significantly the intensity noise at almost all frequencies, see the second plot.

The thrid plot is a spectogram of the intensity noise as a function of time. The bottom trace shows the IMC DOF1 error signal. It is clear that a mean value of 250 counts gives lower intensity noise. It is also clear that intensity noise is highly non stationary, even with a good IMC offset.

The fourth plot shows the same story, but this time intensity noise is characterized with a trace showing the band-limited RMS between 100 and 200 Hz. Using the best IMC alignment offset reduces the noise in the band by a factor ~10. The last plot is a zoom into the last minuts of the test. It is clear that the residual fluctuations of intensity noise are related to the residual angular motion of the IMC.

In summary, we can improve a lot the intensity noise at the output of the IMC by choosing a better alignment position, and by improving the accuracy of the angular control loops.

NOTE:  Today there is a tour of the Hanford site for LIGO staff from around lunch time - 5pm.

Day's Activities

• Observation Bit was found in Commissioning state over night
• 8:02:  Bubba heading to EX to grab a vacuum
• ---:  Richard investing Beckhoff/slow controls error in the LVEA
• ~9:00:  Chris vacuuming at EX (it had been a while, dust counts will elevate, Commissioners:  is this OK during the day???)
• 8:43:  Danny heading out to work on Quad (Betsy will follow)
• 9:13:  Pulling Cables from HAM3 to Beer Garden (per Aux Power work permit) [Filiberto]
• ~9:45-955:  Drive to EY for ISC EY power cycle of IO Chassis [David Barker]
• 9:20-9:50:  BSC2 inspect HEPI inspection.  May take down the ISI/HEPI [Hugh Radkins]
• 10:00:  Peter K checking cables at HAM2
• 10:15:  Sheila slow controls work
• 10:23:  Unifirst
• 10:38:  Paradise
• CP Overfill Alarms at CP4 (signifying a Praxair delivery)
• Had the Slow Control Computer close at EX (seems to be a recurring thing on Tuesdays so far)

Leaving for Tour at 11:30 (Jim W & Dave will help cover the afternoon)

This morning I reset Counters for following HEPI systems:  HAM2, HAM3, HAM4, BSC3(itmx), & BSC3 (BS).

Note:  BSC3 & HAM3 continue to have saturations though.

WP 4869

The user environment has been changed to set up the awgstream environment properly.

The CERN ROOT package has been replaced with a version that supports python.

The gds software (diaggui, foton, etc) has been updated to gds-2.16.12.2, which has a number of bug fixes and a few enhancements:

* python scripting capability for awg and foton have been added.
* Cut/paste added to the Calibration dialog box in diaggui (and foton).
* Long channel names are no longer ignored in the Calibration dialog box.
* Fix bug preventing diaggui from reliably making continuous measurements.
* Unsigned 32 bit integer data support for diaggui time series.
* Foton legacy write option has been removed.
* Fix foton bugs for file path option, add "-o " option for non-gui file processing.
* Fix foton bug which caused crashes when invoked from diaggui.

Sudarshan, Jim and Dave

We power cycled h1iscey as part of the investigation to fix some dodgy ADC channels, we were not successful.

sequence:

take h1iscey out of dolphin, stop models, power down CPU, power down IOChassis, power down PEM AA chassis.

power up AA, power up IOChassis, power up CPU.

Sudarshan, Gabriele

To try to reduce as much as possible the beam pointing sensitivity of the ISS photodiodes, we wrote a python script that reads the PD signals and demodulate them with the excitation sent to IM3. In this way we could send a 12 Hz, 1000 cts sinusoid in yaw and a 17 Hz, 1000 counts sinusoid in pitch, and look at time domain traces of the demodulated signals, as shown in the first attached plot. We moved a bit the picomotors, and we could improve quite a lot the situation. As shown in the second plot, right now we almost can't see the sinusoids in the PD signals, since they're below the noise background. Here are therefore upper limtis on the dP/P/dx:

The optimal position we found is not exactly with the QPD centered (both x and y are around 0.3). Maybe we could improve this, but for the moment we guess the situation is good enough.

Per the weekly Tues Maintenance task, the chiller was topped off to the MAX level mark (needed ~250ml to do this).  The stopper for the Chiller isn't ideal (seems a bit big and sheds a bit to make it seat in the inlet).  Last time the chiller was filled was on 9/15/14.

Now with added "damped" plots.  Note, the damping loops on the electronics test stand are hodge podge and so damping was poor for some regions of many loops.  As well, like I mentioned in earlier logs, the coherence of this in-air QUAD is poor at lower frequencies.  I spent some time trying to work out better excitation filtering/boosting but to no avail.  Damping works on both M0 and R0 chains of Q6.

QUAD 06 (Q6) Phase 1B transfer function plots are attached.   We had a hard time obtaining good coherence in the Transverse TF, so it is a bit hashy.  Will try again.  

Most notably is that, like Q8, the second pitch mode frequency is unexpectedly pushed upward on the main chain.  Recall, we never found the mechanism to fix it on Q8.  Interestingly, both the Q8 and Q6 assemblies are of the same batch of wires and are fresh builds, but by 2 different assembly teams, and on 2 different solid stack/test stand units.  Q8 is an ETM type of QUAD while Q6 is an ITM QUAD, but both main chains have the same pendulum parameters - both are detailed in the 'wireloop' model.

The Q6 data is plotted as QUADTST.

J. Kissel

I was warned that -- though all the GND STS channels are mapped from the instrument to the frames correctly now (see LHO aLOG 14072) -- what actually gets fed into the sensor correction filter banks is a total mess in the corner station. I've scoured the front-end simulink models, toggled some switches at the racks in the EE bay, and stomped on the ground near the STSs themselves trying to map it out, and all I can say is WOW do I agree. I'll work with the SEI and CDS groups to clean up.

Here're the facts, as they stand now, in order of my discovery:
(1) In reality, we want the following seismometer-location-to-channel map for all 17 digital instances of the signals in the corner (6 HAM HPIs, 5 HAM ISIs, 3 BSC HPIs, 3 BSC HPIs):
       Just +X of HAM2    => STS A
       In the Beer Garden => STS B
       Just +Y of HAM5    => STS C
as determined by D1002704, revised due to Integration Issue 45, and DCN E1400111.
(2) I've confirmed that the above mapping is correct for ITMY (the "master" front-end model responsible for storing these STSs and "GND" channels in the frames) by performing my finest hill-billy hoe-down near the respective STS, and watching the ISI-GND channels on a CDS laptop. 
(3) Because of the STS-2 analog distribution chassis, and that the SEI BSC wiring diagram (D0901301), and SEI HAM wiring diagrams (D1101584, D1101576, and D1000298) were written before the ABC convention was established and not addressed in E1400111, there're 17-choose-3 = 680 possible combinations, and I'm pretty sure we used all of them.

Front end models:
(4) ALL HAM-ISIs use the library part, ${userapps}/release/isi/common/models/isihammaster.mdl. There is another library, isiham236master.mdl, that looks deceiving in the same directory, but it's unused according to the tar balls of source code for what's actually running on the IFO. This should be removed from the repo.
(5a) The HAM-ISIs  are reasonably consistent, in that, 
       ADC_0 or ADC_2 Channels 24-26 => STS A XYZ
       ADC_0 or ADC_2 Channels 28-30 => STS B XYZ
       ADC_1 or ADC_3 Channels 24-26 => STS C XYZ
where it's ADC_0/1 on the "first" HAM-ISI in the I/O chassis, and ADC_2/3 on the "second" HAM-ISI (HAM2, HAM4, and HAM6 are the "firsts," HAM3 and HAM5 are the "seconds."). 
(5b) EXCEPT HAM2, who has ADC_0 channels 24-26 mapped into BOTH STS A and STS B. 
(6) Because of an RCG "feature" even though different ADC *card* numbers are used between the seconds and firsts, the block name is always ADC 0 or ADC 1. 
(7) The HAM-HPIs all use the same library part, ${userapps}/release/hpi/common/models.
(8a) HPIs HAM2-5 have GND STSs hooked up, also, reasonably consistent in that they all use
       ADC_0 or ADC_2 Channels 24-26 => STS A XYZ
all piped into STS A, with STS B and STSC terminated. Again, the "firsts" use ADC0, and the "seconds" use ADC 2. 
(8b) EXCEPT HAMs 1 & 6 have all STS inputs terminated.
(9) The BSC ISIs and the BSC-HEPIs are consistent, but consistently bonkers.
       BSC1 ITMY ADC_3   23-25 => STS A
                         26-28 => STS B
                         29-31 => STS C
       BSC2 BS   ADC_3   29-31 => STS A
                         23-25 => STS B
                         26-28 => STS C
       BSC3 ITMX ADC_3   26-28 => STS A
                         29-31 => STS B
                         23-25 => STS C
That's right -- the channels have been cyclically rotated between BSC chambers.

Electronics Chain:
To test out which STS chassis maps to which GNDSTSINF (for ISIs) or STSINF (for HPIs), just in case the STS distribution chassis had been used to rectify the front-end badness, I toggled the period switch on the front of each of the three chassis, in consecutive order, and followed which channels showed the characteristic flip to (more) AC coupled signal (1 [sec] period) and then drove off into tilt land after switching back to the low-frequency mode (120 [sec] period). Since I didn't want to disconnect any cables, and couldn't simultaneously look at all the channels needed with the tiny laptop while zydeco dancing, all I could determine which which *rack* affected which GNDSTSINf or STSINF channel.
(10) BSC 1 (ITMY) ISI and HPI on-board sensors are read out in rack SEI-C4, BSC2 (BS) ISI and HPI are read out in rack SEI-C5, and BSC3 (ITMX) ISI and HPI are read out by rack SEI-C6. As such, I'll refer to the STS chassis that I switch as C4, C5, and C6, after the rack in which they're mounted, since I was unable to determine which was HAM2 (STS A), Beer Garden (STS B), or HAM5 (STS C).
(11) For the BSC-ISIs, the matrix of channels affected by the switching is as follows:
          ITMY     BS      ITMX
     C4     A       A       A
     C5     B       B       B
     C6 (bonkers)   C       C
This indicates that, even though the ADC to model mapping is some crazy, cyclic thing, the cables from the STS distribution chassis have been arranged such that what goes into the ADC is "normal." The ITMY STS C channel doesn't make any sense to me. It didn't respond to any of the period-switch toggles, but still showed live tilt-full signals. Need to debug that one.
(12) For the BSC-HPIs, it's different:
          ITMY     BS      ITMX  
     C4    A        B       C
     C5    B        C       A
     C6    C        A       B
This indicates, that the cabling matches the crazy-bonkers front-end mapping.
(13) For the HAM-ISIs, it's different:
           HAM2     HAM3     HAM4     HAM5     HAM6
     C4    A&B       A      (dead)   (dead)      A
     C5 (no change)  B      (dead)   (dead)      B
     C6     C        C      (dead)   (dead) (no change)
HAM2 is weird, but is consistent with the model layout described in (5b). HAMs 4 and 5 are receiving only ADC noise -- maybe this means the channels aren't hooked up? I didn't check.
(14) And finally, the HAM-HEPIs, they're the worst off:
           HAM1     HAM2     HAM3      HAM4      HAM5     HAM6
     C4   (n/c)      A        B       (dead)    (dead)    (n/c)
     C5   (n/c)     (n/c)    (n/c)    (n/c)      (n/c)    (n/c)
     C6   (n/c)     (n/c)    (n/c)    (n/c)      (n/c)    (n/c)
where "n/c" is not connected in the front-end model as described in (7a). Still no help as to why HAM4 and HAM5 are reading out ADC noise.
And that's the anti-climactic end of the list. We've got some work to do!

Step-one will be to update the SEI wiring diagrams to clearly define how each STS gets into each front-end via an ADC channel list. Next, change the top-level front end models to match the convention in the drawings. Third, change the cabling at the racks around so we get the expected behavior. At the moment, although it's don't in an icky way, the BSC-ISIs are our best case.