When you say, "have the TSE be accurate", do you mean "have the time (obtained from the event system and corresponding to the most recent arrival of the event whose number is in the record TSE field) be accurate"?
The TSE field doesn't hold a time value -- it merely specifies the source from which a time value is to be obtained.
On May 30, 2012, at 10:23 AM, Mark Rivers wrote:
> I'm not sure I understand this. I am supposing that the areaDetector acquisition can keep up, but that there is a pipeline delay. If the image frames are tagged at the moment they are acquired the TSE should be valid, even though by the time the records process it may not be the same pulse. Wouldn't it be useful to have the TSE be accurate for such PVs even if they don't finish processing until 1 or more events later?
>
> Mark
>
--
Eric Norum
[email protected]
- References:
- Proposed change in asyn - request for comments Mark Rivers
- Re: Proposed change in asyn - request for comments Ernest L. Williams Jr.
- Re: Proposed change in asyn - request for comments Eric Norum
- RE: Proposed change in asyn - request for comments Mark Rivers
- RE: Proposed change in asyn - request for comments Allison, Stephanie
- RE: Proposed change in asyn - request for comments Mark Rivers
- Navigate by Date:
- Prev:
RE: ether_ip problem reading DINT arrays Dudley, David
- Next:
Re: calc VAL field not updating from bi VAL field 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: Proposed change in asyn - request for comments Mark Rivers
- Next:
RE: Proposed change in asyn - request for comments Allison, Stephanie
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·