After relocking there was a SDF difference with the HPI-HAM2_IPS_HP_SETPOINT_NOW. Accepted the difference and went into Observing.
Thanks for the log Jeff. This reminds (smacks in the face) me now that I've removed the HEPI Pringles from the Restore Target DOF list, these will all have to be put into the Not Monitored list. These are the DC positions that the Isolation loops drive to. When the loops first start, we load the current free hanging position into the "SETPOINT_NOW" channel so the loop starts with no DC load. After the loop is on and is stable, we load the "Target Position" to move too. All HEPI loops were driving to Targets but the Pringle loops are AC coupled so loading a DC Target position just was wasted effort that got the loop nowhere in the end. So this Setpoint Now channel will be different every time there is a platform trip and re-isolation.
What I don't understand is why there isn't a VP difference too and why this HP difference is so small.
For the ISIs, all HAMs load all DOF Targets, for the BSCs, none of the Targets are loaded; hence, the Not Monitored Lists.
I probably could do this while Observing but I'm reluctant in case the fussing around sets an SDF flag; I'll get it during commissioning later.
Addendum: Checked the SVN, someone must have saved the OBSERVE.snap earlier in the day, to clear the diffs after the HAM2 HPI trip during maintenance; I remember Jim mentioning the trip in the morning. Then the old e-11 diff popped up; not sure why that happens. Regardless, I'll get these into the Not Monitored list and it will be a thing of the past.
I didn't put the updated script in ISC_LOCK that will switch the SDF reference files since I was worried that I would leave and then something would go wrong. This should hopefully fix this SDF diff in the future. I've tested it a few different ways and it all seems good, but I will do it this shift if I get the opportunity.