The Problem: The SEI configuration nodes have been in error since Friday at 2:58 local due to a bug in the WD decorators, and a bit of oversight by the one who coded that part (me). The regular SEI guardian nodes were tripped and then someone requested the config nodes to change, but these config nodes were not designed to be changed when everything was tripped. The decorator that caused the isse is just copied code and so it tried to jump to a state that didn't exist. Glad this was found before O2.

The Fix: removed all of the decorators that check on WD's, isolation, and damping of the regular nodes. Jim W and I talked and decided that it wasn't really necessary for the config nodes to even have to watch that, so lets lose them. Changing the config states while it is tripped or isolating was thought to maybe be an issue before, but doesnt seem to pose a problem anymore.