breaktable checks in dbLexRoutines.c in 3.14.9

[Steven Hartman <hartman@fel.duke.edu>]

I have come across another problem with changes made between 3.14.8.2 and
3.14.9. In base/src/dbStatic/dbLexRoutines.c, sanity checks were added to
breakpoint tables (as are used in ai and ao LINR fields). These checks
appear to have been added in response to a message to tech-talk from May,
2006 (see thread starting with:
http://www.aps.anl.gov/epics/tech-talk/2006/msg00585.php ). However, one
of these checks is too strict and does not accept a number of properly
functioning breakpoint tables which work under previous releases.

In function dbBreakBody() (lines 872-877):
	/* Compute slopes */
	. . .
	if (i == 0) {
		down = (slope < 0);
	} else if (down != (slope < 0)) {
		yyerrorAbort("breaktable: curve slope changes sign");
		return;
	}



A breakpoint table by definition needs a monotonic 'x' parameter
(restricted usually to only increasing values), but there should not be
any restriction for slope or monotonicity for the 'y' parameter. This
check rejects a breakpoint table if either x or y is non-monotonic. This
greatly reduces the usefulness of the breakpoint table.

Properly, the table should be rejected if the raw values are non-monotonic
and the table is to be used with cvtRawToEngBpt(), or if the engineering
values are non-monotonic and the table is to be used with
cvtEngToRawBpt().  However, I don't think such a check can be made at the
point when dbBreakBody() is called and doing it at run time isn't so
useful. I suggest either dropping this check entirely and documenting that
it is the application developer's responsibility to ensure proper
monotonicity, or changing the abort to a warning (which would likely add
confusion during the build process).


We make extensive use of breakpoint tables here at the DFELL (mapping
effective field to current in nonlinear magnets which is monotonic, and
mapping compensation trim magnet fields to main magnet fields which is
extremely non-monotonic). Sorry I missed this when it was discussed on
tech-talk before it was added to base.

Thanks,
-- 
Steve Hartman
hartman@fel.duke.edu || 919-660-2650
Duke Free Electron Laser Laboratory