J. Kissel, D. Barker

Following the instructions in SEI aLOG 491, I've svn up'd the following common isi corners of the userapps repo,
${userapps}/release/isi/common/models/
${userapps}/release/isi/common/src/
${userapps}/release/isi/common/medm/
to receive software updates from ECR E1400239, and integration issue 901.

I've then recompiled, reinstalled, restarted, and restored the following models (in chronological order):
h1isietmx
h1isietmy
h1isiitmy
h1isibs
h1isiitmx
h1isiham2
h1isiham3
h1isiham4
h1isiham5
h1isiham6

Only the ETM chambers are still fully functional, but for each chamber (because most corner station guardians were still requesting fully isolated), I requested the guardian to go to OFFLINE before the four R's. Once 4R'd, for the BSCs,
- Confirmed that the T240MON responds as expected, showing red if T240 values are above the HI THRESHOLD, and not returning green until spending DELAY number of seconds below LOW THRESHOLD
- Confirmed that the T240MON values were restored to HI 20000, LOW 5000, DELAY 120, if necessary. Apparently these new-ish channel's values were never captured in the ETM chamber's safe.snaps. 
- For ETMs only, to confirm software changes were successful, I
    - used guardian to being chambers back up to FULLY_ISOLATED, to confirm the safe.snap didn't lose anything else vital. This was successful.
    - used guardian to transition to DAMPED, such that isolation loops were turned OFF. Set stage 1 (ST1) watchdog (WD) T240 threshold to a value that would normally trigger the WD; I chose 0. This DID NOT trip the watchdog as expected with the new software changes. In addition, the saturation counter that appears in the "FIRSTTRIG" column above the label for T240 limit begins counting up. This was successful.
    - with the T240 threshold still low, used the guardian to request FULLY_ISOLATED. After a short period of time (the time it takes guardian to set things up for turning the isolation loops), the watchdog tripped, as soon as the isolation loops began to be turned on, as expected. This was successful.
    - RESET the ST1 T240 WD threshold to its nominal value of 32760, RESET the WD, and guardian happily marched all the way back up to FULLY_ISOLATED, resetting the T240 saturation counter along the way. This was successful.

All other changes appear successful -- the T240 matrices have expanded, a Z to RZ filter bank now exists. and a new isolation filter gain comparison exists whose output presumably feeds to the ODC vector.

The following still needs doing:
(1) Update safe.snaps to include the correct threshold values for the T240MON
(2) Update safe.snaps to include the correct ISO gain comparison values
(3) Test Z-RZ path for functionality / usefulness
(4) Add matrix elements for new T2402CART matrix elements
(5) Update safe.snaps to include the new T2402CART matrix elements

Rich will work on (3) and (4). But I don't know in what state the ISIs need to be to capture a new safe.snap, so I'll leave (1), (2), and (5) to those who pay closer attention to the ISIs.

The corner station BSC-ISIs and all HAM-ISIs remain OFF in some way or another (user watchdog, masterswitch, or IOP DACKILL) for the vent, with their Guardians set to OFFLINE and paused.

The restarted the "DAQ"/data concentrator/h1dc0/frame builder to account for the new epics channels and filter models at 23:07 UTC.
I also accidentally compiled, installed, and restarted the h1susbs because my fingers have too much muscle memory and I mistyped h1isibs. No good reason otherwise!