EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  <20022003  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  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: select record versus dbpr() versus SPARC (at least)
From: Marty Kraimer <[email protected]>
To: Benjamin Franksen <[email protected]>
Cc: [email protected]
Date: Mon, 09 Dec 2002 13:03:06 -0600
Benjamin Franksen wrote:
Jim Thomas wrote:

Consider a select record with SELM == "Specified" (SELECTED in the code).
The select record initializes non-constant inputs to 1e+30 .


Does anyone know the rationale behind this (IMHO rather strange)
initialization?

Why this (very large?) number?



It's been a long time since this was done so the following is just a guess.


Looking at the algorithms for SELECT_HIGH, SELECT_LOW, SELECT_MEDIAN the code has to know if a fields was never given a value. For some reason the value 1e+30 was chosen to represent "never given a value". What else could be used? Big problem unless IEEE floating point is assumed. Today perhaps a valid assumption (even today what about VAX and alpha?). 12 years ago this assumption was not considered safe to make.


Why - if deemed necessary or at least useful - is initialization not done in selRecord.dbd, but somewhat hidden inside selRecord.c?


Since the code for the algorithm is hidden in the code why not also hide the initization in the code? At least it all appears in one source module.


Ben



Marty




References:
select record versus dbpr() versus SPARC (at least) Jim Thomas
Re: select record versus dbpr() versus SPARC (at least) Benjamin Franksen

Navigate by Date:
Prev: Re: select record versus dbpr() versus SPARC (at least) Benjamin Franksen
Next: jdct run-time error M.C.Shao
Index: 1994  1995  1996  1997  1998  1999  2000  2001  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: select record versus dbpr() versus SPARC (at least) Benjamin Franksen
Next: jdct run-time error M.C.Shao
Index: 1994  1995  1996  1997  1998  1999  2000  2001  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·