EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Scanning on event number fails with EPICS 3.16
From: Dirk Zimoch <[email protected]>
To: Andrew Johnson <[email protected]>
Cc: EPICS core-talk <[email protected]>
Date: Fri, 9 Feb 2018 08:58:32 +0100
OK.

On 08.02.2018 17:48, Andrew Johnson wrote:
Hi Dirk,

On 02/08/2018 07:23 AM, Dirk Zimoch wrote:
Attached is a patch file for dbScan.c which should fix the problem and
restore backward compatibility.

I have created (and quickly tested) it with EPICS 7 but I guess it
should work with 3.16 as well.

Please work against the 3.15 branch, since that was where we introduced
your named events work. We will merge it up into the later branches from
there.

The hack is to treat "x.000000" and "x" as the same event name if x is
an integer between 0 and 255. ("0" and "0.000000" are no event at all
now just like "").

I don't like the string comparisons since they would silently break if
the number of decimal digits generated by the double → string conversion
gets changed.

Better to parse the string properly into a double — look at the
epicsParseDouble() routine declared in epicsStdlib.h and documented at
https://epics.anl.gov/base/R3-15/5-docs/AppDevGuide/libComOSIlibraries.html#x21-84700020.13
— then either round or truncate the fractional part.

Thanks,

- Andrew


References:
Re: Scanning on event number fails with EPICS 3.16 Andrew Johnson

Navigate by Date:
Prev: Re: Scanning on event number fails with EPICS 3.16 Andrew Johnson
Next: Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Scanning on event number fails with EPICS 3.16 Andrew Johnson
Next: Re: Scanning on event number fails with EPICS 3.16 Dirk Zimoch
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
ANJ, 09 Feb 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·