User Tools

Site Tools


visual3d:documentation:visual3d_signal_types:signal_type_overview

Signal Type Overview

Every signal has a Signal Type, a Signal Folder, and a Signal Name. Every signal is referenced by the Type::Folder::Name. You can see the Signal Types in the data tree (the left hand pane of the Signals and Events tab).

EVENT_LABEL

The list of events and the corresponding time they occur in the trial TARGET

The marker data collected by your motion capture system ANALOG

The analog data collected by your motion capture system FORCE

The force platform data (in lab space) which is calculated from the Analog data and the force platform parameters in the C3D file COFP

The force platform data (in lab space) which is calculated from the Analog data and the force platform parameters in the C3D file FREEMOMENT

The force platform data (in lab space) which is calculated from the Analog data and the force platform parameters in the C3D file LANDMARK

The location of the landmark data (in lab space) LINK_MODEL_BASED

Any signal defined by the Compute Model Based Data command is stored here KINETIC_KINEMATIC

Visual3D automatically calculates this data for any segment in your model (you cannot edit these signals). These should be used for reference and not analysis. You should use the Compute Model Based Data command to create any of these signals you are interested in processing. DERIVED

Most processed signals should be stored here (almost every signal that you create using the pipeline - other than those created with the Compute Model Based Data command, and filtered target/analog data) METRIC

Any discrete variables calculated using the pipeline should be stored here (max/min values, etc.) ROTATION

4×4 rotation matrices. If your motion capture system writes out a C3D file with 4×4 rotation matrices instead of target data, or if you use C-Motion's DSX suite, pose data will be written as a 4×4 rotation matrix. FRAME_NUMBERS

The frame numbers are written by your motion capture system. These signals cannot be modified but can be used for reference.

visual3d/documentation/visual3d_signal_types/signal_type_overview.txt · Last modified: 2024/07/17 15:46 by sgranger