| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: NaN and analog records |
| From: | Ralph Lange <[email protected]> |
| To: | EPICS Tech-Talk <[email protected]> |
| Date: | Tue, 04 Nov 2014 13:41:00 +0100 |
Hello Götz, On 04/11/2014 13:32, Goetz Pfeiffer wrote:
another problem is that DRVL and DRVH seem to be ignored for NaN.
The following record;
record(ao,"UE56ID3R:BaseParGapTrs") {
field(ASG,"USERCTL")
field(DRVH,"0.1")
field(DRVL,"0")
field(LINR,"NO CONVERSION")
field(OIF,"Full")
field(PREC,"4")
}
for example can be set to NaN (at least for Epics Base 3.14.8).
Comparisons between numbers and non-numbers (such as NaN) are undefined.What is your suggestion on how to check limits for a non-number without using comparisons?
We also found that you can type "NaN" at any entry field in DM2K which writes NaN directly to the PV.
NaN, -inf and +inf are valid values for a double. Why would you reject entering valid values in entry fields?
Cheers, ~Ralph