Iteration 3

From IGSTK

Contents 1 Requirements for Iteration 3 1.1 Time Stamp Class 1.2 Transform Class 1.3 Tracker, Transforms, Spatial Objects, View Interactions

Requirements for Iteration 3

The following sections describe the basic requirements that were identified for this iteration.

The goal of this iteration is to integrate the information sent from the tracker, using events and time stamps to the spatial objects.

Time Stamp Class

1. Should provide an period of time that defines the validity of an object.
2. Should have an atomic operation for setting both start time and expiration time
3. Should allow being queried for whether it is valid or not at a specific time.
4. Should return the inital time of validity in milliseconds
5. Should return the expiration time in milliseconds

Transform Class

1. Should be able to represent single Translations
2. Should be able to represent single Rotations
3. Should be able to represent Rigid Transform (Translations+Rotation)
4. Should have a time stamp associated with the current Translation and Rotation

Tracker, Transforms, Spatial Objects, View Interactions

1. Tracker class will query the hardware tracker at a user-selected rate
2. Tracker class will have per-tool selection of rate for sending events to the Spatial Objects
3. Tracker communication with spatial objects will be done by passing Transforms (with internal TimeStamps)
4. Spatial Objects will compute a new TimeStamp from the intersection of all its internal time stamped objects
5. The Views should send a message to the Scene with an "expected time of rendering"
6. The Scene will propagate that time to the Representation Objects, so each Spatial Object can be rendered according to its validity time.