Difference between revisions of "NaviTrack Tutorial:Creating module:Module introduction"

From NAMIC Wiki
Jump to: navigation, search
Line 2: Line 2:
  
 
===Sink nodes (XxxxSink.h, [XxxxSink.cxx])===
 
===Sink nodes (XxxxSink.h, [XxxxSink.cxx])===
Leaves in the graph and receive their data values from external sources, such as Polaris optraciking system, and send put the data into NaviTrack data flow graph.
+
Leaves in the graph and receive their data values from external sources, such as Polaris optraciking system, and put the data into NaviTrack data flow graph.
  
 
===Source nodes (XxxxSource.h, [XxxxSource.cxx])===
 
===Source nodes (XxxxSource.h, [XxxxSource.cxx])===

Revision as of 17:39, 18 May 2007

Home < NaviTrack Tutorial:Creating module:Module introduction

Three types of nodes

Sink nodes (XxxxSink.h, [XxxxSink.cxx])

Leaves in the graph and receive their data values from external sources, such as Polaris optraciking system, and put the data into NaviTrack data flow graph.

Source nodes (XxxxSource.h, [XxxxSource.cxx])

Leaves to propagate their data values received from other nodes to external outputs.

Filter nodes (we don't use this in the tutorial)

Intermediate nodes and modify the values received from other nodes.


Two types of Modules

Normal module

Each node of modules has event handling functions to put, pull and process data, and these are called whenever corresponding events occure. Therefore, the timing of processing is detemined only by NaviTrack events.

Thread module

In some application, a module has to call certain procedures with its own timing, e.g. monitoring hardware, acquiring data from a device. For this purpose, NaviTrack allows us to create a module with threading capability. The structure of thread module will be described later.


Go back to Creating module.