1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Why should I care about breakpoint table monotonicity? |
From: | Emmanuel Mayssat <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Thu, 21 Nov 2013 16:29:03 -0800 |
Hello all, I am currently playing with ai and ao records breakpoint tables. Documentation is rather sparse on how to implement them. http://www.aps.anl.gov/epics/EpicsDocumentation/AppDevManuals/RecordRef/Recordref-5.html#MARKER-9-12 I found a couple of interesting emails on the tech-talk mailing list. Including: http://www.aps.anl.gov/epics/tech-talk/2010/msg02152.php (Thank you Stephanie!) and another http://www.aps.anl.gov/epics/tech-talk/2010/msg01896.php "This is a bit of a pain, so I just wrote a blueprint to look at adding the table names to menuConvert automatically in future releases. - Andrew" Has this been implemented in >3.14.11 ? But my real question is this: why should I care about the monotonicity of the data in the breakpoint table? Apparently, I have to set a iocsh variable to 1 "var dbBptNotMonotonic 1" How does this impact monotonic tables? Why not always set it to 1? Why do I need to set it? (I can only imagine that it has to do with RVAL to VAL conversion .... and VAL to RVAL conversion which may return more than one value.) Thanks, -- Emmanuel |