driven sequence

The driven sequence module controls the semi-automatic creation of sequences for the following modules:

• slice

• cut

• plume

• plume shell

Control over these modules is via the purple "Sequence Output" ports on the driven modules and the "Sequence Input" port on driven sequence.

All modules to be grouped in the Sequence must have their red output ports connected to driven sequence instead of the viewer. Consider driven sequence to act like a group objects module.

 

Module Input Ports

• Sequence Input Receives special port from only plume, plume shell, and slice modules
• Input Objects [Field] Accepts any number red object ports from modules changed within the sequence.

Module Output Ports

• Current State Title
• Output Object [Renderable]: Outputs to the viewer.

Other modules not listed above may be included if one of the "driven modules" controls those modules. Examples are titles, isolines, band data, etc.

 

driven sequence has only a Current State slider which allows you to test the sequence or directly access any state. The latter is useful when using this module in EVS or EVS Presentations. Please note that in this case, selecting a state requires that all controlled modules must run. This is much slower than selecting a (saved) state of a .CTWS file.

 

The State Name output port provides a simple way to include a title which specifies the current displayed state in sequences.

 

The Driven Modules have the bulk of the settings which determine what controls and states will be available such as:

• Use Sequencing: This toggle must be on when using driven sequence with a driven module.

• State Control: Choose between

• Slider

• Combo Box

• List Box

• Sequence Type: Choose between

  • By Count (set the number of states between minimum and maximum values)

  • By Step Size (set the increment between each step)

• State Titles are automatically generated for you

Please note: For Log Data, the state values are determined using the same logic (algorithm) which we have traditionally applied to modules such as isolines, band data and legend. This means that for:

• By Count: If the number of Frames results in:

  • 2 steps per decade, then the states will be .1, .3, 1, 3, 10, 30, etc.

  • 3 steps per decade, then the states will be .1, .2, .5, 1, 2, 5, 10, 20, 50, etc.

• By Step Size: If the increment is:

  • 0.5 , then the states will be .1, .3, 1, 3, 10, 30, etc.

  • 0.33333, then the states will be .1, .2, .5, 1, 2, 5, 10, 20, 50, etc.