As I posted yesterday (LHO alog 24028) HAM2 and HAM3 were consistently tripping when the Guardian switched the GS13s to High Gain after the completion of the Isolation process.  I speculated (like I always do) alot about why this was happening and it was not a problem on the other three HAMs; well actually we aren't switching HAM6 so maybe I need to rethink my space.  Anyway, this morning TJ and I investigated what guardian was doing and I have the following observations.

When the switch GS13 gain was disabled (ISOLATION_CONSTANTS['SWITCH_GS13_GAIN'] = False,) the ISI would isolate just fine.  The gains could then be switched manually, with the old ISI scripts, or the guardian.

I did not try the manual method of just clicking the filters.  Executing the GS13 !HI button on the ISI COMMANDS medm successfully switched the GS13s without tripping the ISI, as it did yesterday.  And now here is the really interesting thing:

I had assumed the switching problem was caused by the timing of the switching, just after completing the isolation and the platform is driving to the Target Locations.  By disabling the Guardian switching I could switch after it was done and not be a problem; this was the case using the COMMAND HI button.

After getting the ISI isolated with the GS13S still in Low Gain, I changed the GS13 Gain Switch to true and when I loaded this, the Guardian switched the blends and the platform tripped.  Looking at the log, it would appear the guardian is not doing anything else other than switching the gain filters.  So, at least for HAMs2 & 3, the way the guardian is switching the gain is the problem and not necessarily the timing of the switching.

Maybe if we could get the GS13 switching to do the same as the COMMAND script we would not be searching for why HAM2 & 3 behave differently than HAMs 4 & 5.