*banner
 

Integrating Timing with Data and Space Availability as Firing Rules
Tim Hayles

Citation
Tim Hayles. "Integrating Timing with Data and Space Availability as Firing Rules". Talk or presentation, 9, September, 2008.

Abstract
The structured dataflow of LabVIEW, like C/C++, is untimed. Add-ons do bring control of time to programs but they tend to be somewhat vendor specific and ad-hoc. Furthermore, actors with dataflow dependencies are sequential. The independently free-running yet often precisely timed behavior of I/O actors along with the creation of an experimental asynchronous wire inspired an effort to bring native support to LabVIEW for exchanging both data and timing information between free-running I/O and computational actors. This talk will further outline the motivations for creating this model of computation, the policies for data exchange between actors and how this MOC is likely to be integrated with dataflow. The timing wire abstraction itself will be discussed in some detail along with illustrative descriptions of some typcial I/O architectures and current asynchronous timing and data wire implementations.

Electronic downloads

Citation formats  
  • HTML
    Tim Hayles. <a
    href="http://chess.eecs.berkeley.edu/pubs/485.html"
    ><i>Integrating Timing with Data and Space
    Availability as Firing Rules</i></a>, Talk or
    presentation,  9, September, 2008.
  • Plain text
    Tim Hayles. "Integrating Timing with Data and Space
    Availability as Firing Rules". Talk or presentation, 
    9, September, 2008.
  • BibTeX
    @presentation{Hayles08_IntegratingTimingWithDataSpaceAvailabilityAsFiringRules,
        author = {Tim Hayles},
        title = {Integrating Timing with Data and Space
                  Availability as Firing Rules},
        day = {9},
        month = {September},
        year = {2008},
        abstract = {The structured dataflow of LabVIEW, like C/C++, is
                  untimed. Add-ons do bring control of time to
                  programs but they tend to be somewhat vendor
                  specific and ad-hoc. Furthermore, actors with
                  dataflow dependencies are sequential. The
                  independently free-running yet often precisely
                  timed behavior of I/O actors along with the
                  creation of an experimental asynchronous wire
                  inspired an effort to bring native support to
                  LabVIEW for exchanging both data and timing
                  information between free-running I/O and
                  computational actors. This talk will further
                  outline the motivations for creating this model of
                  computation, the policies for data exchange
                  between actors and how this MOC is likely to be
                  integrated with dataflow. The timing wire
                  abstraction itself will be discussed in some
                  detail along with illustrative descriptions of
                  some typcial I/O architectures and current
                  asynchronous timing and data wire implementations. },
        URL = {http://chess.eecs.berkeley.edu/pubs/485.html}
    }
    

Posted by Hiren Patel on 11 Sep 2008.
Groups: chess
For additional information, see the Publications FAQ or contact webmaster at chess eecs berkeley edu.

Notice: This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright.

You are not logged in 
©2002-2014 Chess