Gerardo and I worked out a nice little dish setup such that the primary and secondary prisms on one side of the optic barrel could soak in acetone for a while today.  We used an SST dish lid and organic cotton rounds to sit the optic in a bath of acetone submerging both prisms.  With an all glass pipette, we will add acetone as needed over the next few mornings.  The evaporation rate in the setup is on the order of 10s of minutes, so needs far less babysitting than the setup needed when only removing one prism.

J. Kissel, H. Paris

Hugo and I updated the operational H1 SEI and SUS systems as described in T1200478. Unlike with H2, we were not plagued by RFM IPC issues, so the update when extremely smoothly (done within half-a-day). Since they're the only one's running, we updated
HAM2-ISI, HAM3-ISI,
MC1, MC2, MC3, PRM, PR2, PR3, SR2
successfully. 

Notes of interest to others: 
- With the updates, we're now running 62 PCIe IPC channels over the dolphin network; "dangerously" close to the 64 channel limit (there's no danger at all actually, we just won't be able to have more than 64 until RCG 2.6).
- I've edited the h1susim.mdl top-level model to include new sender IPC parts to broadcast the PR3 optical lever signals (which come in on the susham2b front-ends). Consequently, I've added receivers in the h1suspr3 model, which -- with these upgrades -- now accepts its optical lever as the QUADs have (i.e. using the QPD.mdl library part). 

As with the H2 SUS, there's a similarly long list of "OK, now actually *use* this new infrastructure," to-do items:
- Installing values into the new infrastructure
     - 4k to 16k AI filter for ISIWIT path
     - Calibration filter for ISIWIT path
     - CART2EUL matrix elements for ISIWIT path
     - OPTICALIGN offset calibration gains
     - EUL2CART matrix elements for OFFLOAD path (MC2 and PRM only)
     - 16k to 4k AA filter for OFFLOAD path (MC2 and PRM only)
     - 2k to 16k AI filter for ISCINF ASC P and Y signals (MC2 and PRM only)
     - Install whitening compensation filters into PR3 OPLEVINF bank
     - Install OL2EUL matrix
     - Fill out all matrix elements in PR3, PRM, and SR2 
     - update/create safe.snaps
- Start using calibrated sensor path, as has been done with L1 HSTSs
     - turn on "to_nm" or "to_um" filters in OSEMINF bank
     - compensate for calibration in DAMP bank

J. Kissel, V. Lhullier, D. Barker, J. Batch

Though we were not as successful as hoped due to (re)discovering that RFM IPC receiving is computationally expensive (see LHO aLOGs 4499, 4511, and 4521), Vincent and I did manage to complete all other H2 BSC-ISI and SUS models and MEDM screens described in T1200478. Really. it's ONLY ETMY and TMSY that cannot communicate with BSC6-ISI, all other changes were successfully and relatively smoothly installed. I updated the TMSY infrastructure as well, as it used several library parts common to the QUADs and BSFMs. All corresponding changes to SUS- ETMY, ITMY, FMY, and TMSY common screens, top-level models, and bug fixes to common model parts have been committed to the userapps repo as of this entry. The BSC6 SUSs have been left with TOP stage damping loops ON (ITMY for FMY [H1BS] are not plugged in).

Though the infrastructure is now in place, there's still plenty of work to do on the SUS side of things:
- Pending Dave and Jim getting an independent dolphin network set up at the end station, we'll get the TMSY and ETMY ISI witness paths turned on
- Installing values into the new infrastructure
     - 4k to 16k AI filter for ISIWIT path
     - Calibration filter for ISIWIT path
     - CART2EUL matrix elements for ISIWIT path
     - OPTICALIGN offset calibration gains
     - EUL2CART matrix elements for OFFLOAD path (ETMY only)
     - 16k to 4k AA filter for OFFLOAD path (ETMY only)
     - 2k to 16k AI filter for ISCINF ASC P and Y signals (ETMY only)
- Start using calibrated sensor path, as has been done with L1 HSTSs
     - turn on "to_nm" or "to_um" filters in OSEMINF bank
     - compensate for calibration in DAMP bank

Stay tuned for the exciting conclusion!

As a fix to the problems encountered yesterday when adding more IPC channels at EY, namely the SUS model running too long with direct RFM access and the IOP model running too long with DMA access, we decided today to install a Dolphin network on the EY systems.

We installed a Dolphin switch in the EY rack, and installed Dolphin pcie cards in h2pemey, h2susb6 and h2seib6.

We are reconfiguring the Dolphin master on h2boot, but recent IPC file changes caused recovery problems and we have ran out of time today, we will continue working on this tomorrow.

For now we retested the dolphin network in the LVEA and it all looks good, so we'll leave it like that overnight.

I installed the following filters for HAM3-ISI:

- Symmetrization
- Damping (G)
- 900mHz Blend (G)
- 500mHz Blend (G)
- 250mHz Blend (G)
- Isolation Level 1 (G)
- Isolation Level 2 (G)

(G)= Generic filter

I will keep testing them tomorrow.

Note: Jeff Kissel and I got the offlead running for both HAM2 and HAM3

[Stuart A, Jeff B]

Jeff was experiencing problems with tripping watchdogs on SR3. I logged-on remotely and noted that damping loops would not close, thus indicating a sign related issue. This was due to the incorrect sign being present in the COIL OUTPUT FILTERS, given that HLTS suspensions have their SD BOSEM mounted on the opposite side of the structure when compared to a HSTS. The SD BOSEM sign was switched from -1 to +1.     

I noted that the OSEM2EUL & EUL2OSEM matrices contained elements pertaining to a HSTS rather than a HSTS, so I corrected them.

I also noted that DAMP FILTER gains were configured for a HSTS rather than a HLTS, so I updated them to be consistent with the LLO PR3 suspension.

Following the changes noted above, damping loops could successfully be closed on SR3.

Jeff is now making a new BURT snapshot of this configuration and intends to run damped and undamped Matlab TFs overnight.

Foundry switch at end Y was accidentally unplugged. This disconnected the vacuum system, weather station and dust monitors. They are back up.

Dave, Jim adding dolphin network at end Y.

Installing BS on BSC2 ISI on Test Stand in LVEA.

In prep for installing MC1 in HAM2 (a deviation from the install plan due to the MC3 issues, which had much banter today), I've clamped MC1, installed the face shileds, and stowed it's cables in prep for a trip into the chamber this week.

Attached shows the poor pitch of the suspended IMCF06 optic (MC3).  Today, we confirmed again that one of the prisms is mis-placed by ~2mm in the pitch-centric direction.  So, I've removed it from the suspension and will remove the errant prism (and it's errant secondary metal prism) here at LHO.

Hugo & Hugh
Attached is an image with an installed TMD on the underside of the ISI Blade Spring.  We did not have the install jig that has been used previously.  Using images in E0900119, I placed the TMD by eye and feel.  I attempted to position the countermass inline with the rib outboard from the Spring.
Serial Numbers:Corner1--010, Corner2--012, Corner3--011

Shoot, I guess I didn't upload this...when did this happen?  Yesterday...Tuesday?

Last Friday, I finished the test of the third BSC-ISI (E1100296-v1). It looks good.

Jeff, Jim, Dave and Alex.

We worked today on adding more IPC channels using the GeFanuc Reflective Memory network which runs between the H2 EY systems h2susb6, h2seib6, h2pemey and the LVEA h2susb478. Senders and Receivers were added to several models as part of the code upgrade.

It was found that RCG2.5.1 does not allow DMA data transfer to the RFM card no matter what the no_rfm_dma setting is. With the non-DMA default of RCG2.5.1, it was found that the h2susetmy model was running too long, over its 60uS limit. Working with Alex, we overrode the "no dma" setting on 2.5.1 by editing the feCodeGen.pl handling of the no_rfm_dma CDS block setting. It was found that DMAing the IOP caused it to slow down to a point that the software watchdog on the ISI front end would not allow DAC activation. So we tried a hybridized system of non-DMA for IOP, and DMA for user model. All was looking good with CPU usage, except for the fact that the IPC did not in fact work. No data got through, and the IPC receive error rate was at the max value.

Alex did some digging and found that the RFM DMA can only work if both the IOP and the user model are set to use DMA. We tried this and indeed the model-to-model IPC did work with no errors and no CPU overruns, but the IOP again was running too long, causing Watchdog IPC errors of a rate of about 200 per second (out of 65536) which meant that the SEI front end DACs were disabled. We seem to have reached an impasse.

So for now we are reversing today's DMA changes. All DMA is turned off, in fact the RCG is reverted back to the 2.5.1 version of feCodeGen.pl which does not allow DMA at all. Jeff has backed off on the number of new IPCs in the SUS models to keep the CPU usage well below 60uS.

Hugh, Hugo,

We wanted to make sure that the rubbing detected yesterday would not occur again. We opened the doors of the horizontal actuators and clamped the actuator/CPS cables to the spring posts. Only corner 3 had its cables already clamped.

We installed the TMDs on the blades. Hugh had to go in the chamber.

We released HEPI. No fluid running yet.

Transfer function measurements are running overnight.

Mark B.

I started Matlab TFs on MC1 at 16:18 PDT.

In my earlier alog, I reported that the MC3 optic hangs with a large pitch.  And, I had also reported that the suspension had minimal pitch error during the metal hang last week, so the pitch error was either from the prism placement on the optic or the new wire loop.  Today, Andres provided us with another fresh wire loop which we installed - and we still see the large pitch error.  With a fine scaled metric ruler we see that the right front prism notch is sitting 32.0mm (+/-0.25mm) away from the HR surface of the IMCF06, while the left front notch is at 34.25mm from the HR surface.  These numbers should be the same.  We're bantering with Mark and Kissel now  - we'll likely moke for more measurements and try a few adjustments tomorrow, but...  ugh.

The remaining dust monitors have been moved over to the code tested at end Y as under work permits 3471, 3512.

The main goal of the code change is to allow each dust monitor to be stopped and started from the medm. This should allow changes on the front panel to be done without turning the dust monitor on and off and then quickly changing the settings before the code puts it into remote mode. That is, to change the front panel settings, stop the dust monitor with the medm, make the changes, and then start the dust monitor with the medm. Whether stopping the dust monitor and setting it to local mode with the code allows the front panel changes to be done still has to be tested.

This now requires that each dust monitor be started under its associated 'expert' medm screen when it or its IOC is restarted.

I will let the code run for a while before I submit it into svn.