EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

<19941995  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 <19941995  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: Re: CALC record
From: [email protected] (Tim Mooney)
Date: Mon, 7 Nov 94 16:48:12 CST
Deb Kerstein writes:
> 
> Ned writes:
> >Such changes to the CALC record routines would impact things other than the
> >CALC records !  The handy routines "postfix" and "calcPerform" have been used
> >by other record types (at least two that I know of). So to say that such changes
> >could be implemented and the known effects minimized by a script that changes
> >CALC expressions in CALC records is quite dangerous.
> 
> Although I agree with Steve's and Tim's comments and requests for change in
> the CALC record, I have to support Ned in this one.  Having been a veteran
> of the GTA project which was done during a time of rapid EPICS development and 
> change, I can vouch for the painful and unexpectedly far-reaching effects
> of a few "simple" changes.  If you really want these changes right now, the
> suggestion of implementing a new "CCALC" record seems like the best bet--maybe
> Tim and Steve could collaborate on this one.  And, of course, be sure and let 
> everyone know when it's available!

There are two kinds of change under discussion; let's not lump them together.

1) Steve and I suggest changes (I'd call them bug fixes, actually) that can,
if properly implemented, have essentially no effect on existing databases.

2) John Winans suggested doing CALC fields the way they probably would end up
being done if the CALC record were first proposed yesterday and we all got to
vote on it.

Change (2) clearly is not going to fly for the CALC record, and is a
good reason for producing a CCALC record, in my opinion.  (I won't be
working on this one :)

Change (1) is quite similar in implementation to changes already made
in the CALC record's calculation engine to support the TRANSFORM
record.  I doubt anyone even noticed those changes.  (For about a year,
I had to have my own private copy of postfix.c and calcPerform.c to
implement the TRANSFORM record.  I didn't stray too far from the
official version to preserve the possibility of a merge.  If a merge
had been out of the question, I would have made LOTS of changes, and
we'd now have at least two incompatible calc engines running around.
I think such a proliferation would be worse for EPICS than any
conceivable effect of the changes Steve and I suggest.)

Tim

Navigate by Date:
Prev: CALC record Deb Kerstiens
Next: VMIC 4514 board. Nick Rees
Index: <19941995  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 
Navigate by Thread:
Prev: CALC record Deb Kerstiens
Next: VMIC 4514 board. Nick Rees
Index: <19941995  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 
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 ·