Something probably not covered in the other logs, the seismic platforms were not in their proper state when I came in this morning. ITMY_ST2_SC node was complaining and the ISI_CONFIG screen showed that HAM1 sensor correction was off. I think this happened because all of the seismic models were restarted, but the guardian machine did not get restarted. This meant that the SEI_CONF guardian and the ops overview showed that the seismic was in the nominal state, but because the way those guardians are implemented is kind of flexible, it did not force the right configuration. I fixed this by requesting the RECOVER_SC state on the SEI_CONF guardian, then going back to WINDY.

In the future, probably any seismic model restart should be followed by taking SEI_CONF to the SC_OFF state, then selecting whatever the appropriate environmental state is.