RE: Breakpoint tables: Raw value must be integer?!?

[Emmanuel Mayssat <emayssat@outlook.com>]

Breakpoint tables should be considered a basic feature of any control system, including EPICS.
I would like to make a petition to have the breakpoint table implementation reviewed.
My suggestions:
1/ RVAL in should be double (at least for ai/ao and maybe for all records)
2/ no check on monotonicity in X and Y.
    * Just properly document side effects in manual.  (Happy to take care of that!)
    * Whoever create the table and associated records should know what she/he is doing

Comments?

PS: Bob, I wouldn't mind contributing to the documentation.
Except most of the documentation is formatted as PDF documents or read-only html pages.

--
Emmanuel

> From: steiner@nscl.msu.edu
> To: saa@slac.stanford.edu; emayssat@outlook.com; tech-talk@aps.anl.gov
> Subject: RE: Breakpoint tables: Raw value must be integer?!?
> Date: Mon, 25 Nov 2013 14:15:49 +0000
>
> I've taken the cheap way out -- instead of using Ampere for my current-to-field records, I use milliAmp integer values.
>
> So instead of a 'sub' or 'aSub', I have to deal with one 'ai' and one trivial 'calc' record.
> It's marginally simpler this way.
>
> Cheers -Mathias
>
> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Allison, Stephanie
> Sent: Friday, November 22, 2013 8:08 PM
> To: 'Emmanuel Mayssat'; tech-talk@aps.anl.gov
> Subject: RE: Breakpoint tables: Raw value must be integer?!?
>
> Hi Emmanuel,
>
> > Is RVAL supposed to be an integer?
>
> Yes.
>
> > How can fix my current example?
>
> I'm sure other people have a better solution but I use a subroutine record. The logic looks something like this (I snipped code that you don't care about so maybe it doesn't compile):
> ...
>