After switching to the down to check things and then going back to the OBSERVE, e-16 differences pop up that reflect the precision difference of the file and front end.  This will really hobble the commissioners/operators and jeopordize the configuration and IFO lock.  I know this is not a new problem.

The safe (for the lock) solution is to Accept the values in the FE to the file; but, this is temporary: the FE thinks the value in the file is the same even though it can not write that precision.  Next time the FE reads the file, the problem returns.  A more permanent fix is to revert the FE to the file but this requires the FE to change its value and potentially (maybe pretty small) break a lock.  Some argue we just not monitor these channels but I say that is risky for the configuration as we stop seeing actual problem channel changes.

The real solution is to have the FE code (RCG?) actually write the file at the precision of the FE so all these problems go away.