No leaving the OAF running until you're sure (sure-sure, not kind of sure, not pretty sure, but I've enabled guardians to make sure nothing bad can happen, and I've been sitting here watching it for 24+ hours and it is fine) that it works okay.
OAF (both adaptive and static paths) were left enabled, which was kicking MC2 a lot. Not quite enough that the watchdog tripped, but close. The LSCPOS output for MC2 was in the 10's or 100's of thousands of counts. Not okay.
This brings up the point though, which I hadn't actively thought through before, that we need an OAF watchdog. An OAF ogre? But a benevolent ogre. If the OAF gets out of control, it's output should be shut off. Eventually we can make it more sophisticated, so that it resets the adaptive filter, and lets things start over, or something.
But until we have a reliable OAF ogre, no leaving the adaptive path enabled if you're not sitting in the control room. The static path should be fine, since it can't get out of control on it's own.
Especially no leaving things like this enabled without a "I'm leaving this enabled, I'll be back in a few hours to check on it" elog!