Bernd Schoeneburg wrote:
>
> If readValue () return with ERROR, udf should not be set to FALSE. If the device
> support read routine (called from readValue) returned '2' (don't convert) it should
> have reset udf. So I think moving of this resetting would break (or 'improve')
> existing device support code and is not nessecary. In mbbi-Record it's the same.
>
> Carl Lionberger wrote:
>
> > I agree this sounds OK. I did notice there is a setting udf to false at the end
> > of convert() (after the smoothing). I think it needs to either be deleted (its
> > set false various places in device support) or also moved to process(). Surely a
> > converted value is not considered more defined than a smoothed but not converted
> > one.
Is there some generally agreed upon rule which of record support or
device support should reset UDF? I remember I came onto this myself. My
impression has been that sometimes people put it in the device support
because it's missing in the record support (where IMHO it belongs).
Didn't we fix this for some of the records a while ago?
Ben
- References:
- smoothing for AI Soft Records Brian McAllister
- Re: smoothing for AI Soft Records Bernd Schoeneburg
- Re: smoothing for AI Soft Records Bernd Schoeneburg
- Navigate by Date:
- Prev:
Re: smoothing for AI Soft Records Bernd Schoeneburg
- Next:
Agilent E2050A access from non-EPICS applications Eric Norum
- 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
- Navigate by Thread:
- Prev:
Re: smoothing for AI Soft Records Bernd Schoeneburg
- Next:
Agilent E2050A access from non-EPICS applications Eric Norum
- 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
|