EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: synchronizing data to an event
From: Till Straumann <[email protected]>
To: [email protected]
Cc: [email protected]
Date: Wed, 07 Nov 2007 08:03:59 -0800
Here at SLAC, the lcls and spear3 projects
abuse a number of bits in the nanosecond part
of the EPICS timestamps to carry a 'pulse ID' number
which is obtained from the timing system.
Data from all over the machine can then be aligned
using this pulse ID.
A hack - but it has proven to be quite useful
w/o the need for changing the CA protocol.

-- Till

Ron Rechenmacher wrote:
Hi,

I did a search of tech-talk for: timing event synchronization
The results along with my experience to date leads to the conclusion
that synchronization by 8 byte time stamp is the only synchronization that
CA currently provides. (please correct if wrong)

The question:

  I was wondering if there has ever been any (perhaps behind the scenes)
  discussion of adding additional synchronization information to the
  Channel Access protocol?


Perhaps, in addition to the timestamp, a "synchronizing event" structure, which would be NULL if not used, but would otherwise have an event type and event count.


At some linear accelerator facilities, there has been a move toward counting RF pulses and associating data collection triggered by the RF pulse with that pulse count. Of course there would be a pulse count to time correlation also,
but many people seem to embrace the main data association (in archived data) being with an event count.


I've heard that there has been work on "beam flavors" at SLAC. (sorry if this is bogus information). But if in addition to a timestamp, data also has "flavor" information, then this could be considered a start to additional synchronization information? Has there been work on this? and if so, has any progress reports been published?

Thanks,
Ron





References:
synchronizing data to an event Ron Rechenmacher

Navigate by Date:
Prev: RE: Stream device Szalata, Zenon M.
Next: Re: Stream device Dirk Zimoch
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: synchronizing data to an event Jeff Hill
Next: Tech-talk post delays Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·