Data Tree: Difference between revisions

From Software Product Documentation
Jump to navigation Jump to search
(Removed lead-in section name, cleaned up links, and corrected typos.)
 
(16 intermediate revisions by one other user not shown)
Line 2: Line 2:
| __TOC__
| __TOC__
|}
|}
The '''Signal and Event Processing''' page is the heart of the data stored in the Visual3D Worksapce. On this page you can examine the data in your workspace in detail, create graphs to visualize signals (time-variant data values), and visualize motion trials as animated graphics.


The Signal and Event Processing page consists of three main display areas:
*'''the data tree'''
*'''the animation display'''
*'''the graphs display'''
[[File:2Dgraphs.png|800px]]
==Overview==
The data tree presents a hierarchical view of your experimental data, similar to the files-and-folders hierarchy seen on most computer operating systems.  
The data tree presents a hierarchical view of your experimental data, similar to the files-and-folders hierarchy seen on most computer operating systems.  


Line 20: Line 10:


The black-outlined square box [[File:BoxEmpty.gif|sub]] next to each data item is a checkbox (click once with the left mouse button and it becomes [[File:BoxChecked.gif|sub]]) which allows you to select that item as input to the pipeline (see below). Note that selecting a folder automatically selects all the individual items in that folder.
The black-outlined square box [[File:BoxEmpty.gif|sub]] next to each data item is a checkbox (click once with the left mouse button and it becomes [[File:BoxChecked.gif|sub]]) which allows you to select that item as input to the pipeline (see below). Note that selecting a folder automatically selects all the individual items in that folder.


At the bottom level of the hierarchy are '''parameters, signals and metrics''':
At the bottom level of the hierarchy are '''parameters, signals and metrics''':
Line 32: Line 21:
::::In contrast, parameters and metrics are discrete data which do not vary as a function of time or any other variable.
::::In contrast, parameters and metrics are discrete data which do not vary as a function of time or any other variable.
:::'''Metrics'''
:::'''Metrics'''
::::Metrics are quantities computed by Visual3D which in some way collapse the time dimension of signals (e.g., average value of a signal over a duration) or the spatial dimension of models (e.g., center of mass of entire ::::model).
::::Metrics are quantities computed by Visual3D which in some way collapse the time dimension of signals (e.g., average value of a signal over a duration) or the spatial dimension of models (e.g., center of mass of entire model).
::::The main distinction between parameters and metrics is that parameters are stored in the c3d file parameter section, whereas metrics are computed by Visual3D.
::::The main distinction between parameters and metrics is that parameters are stored in the c3d file parameter section, whereas metrics are computed by Visual3D.


Different types of data are represented by distinctive icons in the data tree. Points and vector-valued signals whose values are point coordinates are represented by a red sphere icon [[File:RedSphere.gif|sub]]; scalar-valued signals (e.g., analog signals recorded during motion trials) are represented by a graph icon [[File:GraphIcon.gif|sub]]; parameters are represented by three green lines reminiscent of printed text [[File:TextIcon.gif|sub]]; and so on. Note also that every item in the data tree has a name, also referred to as its '''label.'''
Different types of data are represented by distinctive icons in the data tree. Points and vector-valued signals whose values are point coordinates are represented by a red sphere icon [[File:RedSphere.gif|sub]]; scalar-valued signals (e.g., analog signals recorded during motion trials) are represented by a graph icon [[File:GraphIcon.gif|sub]]; parameters are represented by three green lines reminiscent of printed text [[File:TextIcon.gif|sub]]; and so on. Note also that every item in the data tree has a name, also referred to as its '''label.'''
Line 40: Line 28:
==Data Folders==
==Data Folders==
In the Visual3D Data Tree, the highest level folders represent the signal or data type (example TARGET, ANALOG, or FORCE). Here we will describe each data type and what the data represents.
In the Visual3D Data Tree, the highest level folders represent the signal or data type (example TARGET, ANALOG, or FORCE). Here we will describe each data type and what the data represents.
===Signals===
::'''TARGET'''
:::The TARGET data folder contains the POINT signals (MoCap markers) stored in the c3d file. Specifications on c3d data type and format can be found [[C3D_Format#C3D_POINT_Parameters|here]].


::'''ANALOG'''
===TARGET===
:::The ORIGINAL folder for ANALOG data include the raw signals stored in the c3d file. These can include force, moments, or EMG signals. Specifications on analog data type and format can be found [[ANALOG_Data_Type|here]].
::The TARGET data folder contains the POINT signals (MoCap markers) stored in the c3d file. Specifications on c3d data type and format can be found [[C3D_Format#C3D_POINT_Parameters|here]].
 
===ANALOG===
::The ORIGINAL folder for ANALOG data include the raw signals stored in the c3d file. These can include force, moments, or EMG signals. Specifications on analog data type and format can be found [[ANALOG_Data_Type|here]].


::'''FORCE, COFP, FREEMOMENT'''
===FORCE, COFP, FREEMOMENT===
:::The force, center of pressure, and free moment signals (Force Platform Signals) are computed from the ANALOG signals and the FORCE_PLATFORM parameters in the c3d file.
::The force, centre of pressure, and free moment signals (Force Platform Signals) are computed from the ANALOG signals and the FORCE_PLATFORM parameters in the c3d file.
:::These signals can be modified by changing the C3D Force Platform parameters, or by processing the ANALOG signals. Specifications on data type and format can be found here: [[FORCE_Data_Type|force]], [[COFP_Data_Type|cofp]] & [[FREEMOMENT_Data_Type|freemoment]]
::These signals can be modified by changing the C3D Force Platform parameters, or by processing the ANALOG signals. Specifications on data type and format can be found here: [[FORCE_Data_Type|Force]], [[COFP_Data_Type|Centre of Pressure]] & [[FREEMOMENT_Data_Type|Free Moment]]


::'''KINEMATIC_KINETIC'''
===KINEMATIC_KINETIC===
:::The KINEMATIC_KINETIC folder contains a sub-folder of each segment created in the model that contains the kinetic and kinematic data resolved in the Laboratory Coordinate System. These signals exist for reference; they cannot be processed or included in a Report Graph. The LINKMODEL based items use this data to create the LINK_MODEL_BASED signals. Specifications on kinematic_Kinetic data type and format can be found [[KINETIC_KINEMATIC|here]].
::The KINEMATIC_KINETIC folder contains a sub-folder of each segment created in the model that contains the kinetic and kinematic data resolved in the Laboratory Coordinate System. These signals exist for reference; they cannot be processed or included in a Report Graph. The LINKMODEL based items use this data to create the LINK_MODEL_BASED signals. Specifications on kinematic_Kinetic data type and format can be found [[KINETIC_KINEMATIC|here]].


::'''MODEL_LINK_BASED'''
===LINK_MODEL_BASED===
:::The MODEL_LINK_BASED data is populated with LINKMODEL based items/signals specified by the user from the command Commute_Model_Based_Data. Specifications on link_model_based data type and format can be found [[Model_Based_Items|here]].
::The LINK_MODEL_BASED data is populated with signals produced by the [[Model_Based_Items|model-based]] items defined by the user through the graphical interface or from the [[Compute_Model_Based_Data]] pipeline command.


===DERIVED===
===DERIVED===
The DERIVED folder contain signals that can not be directly associated with the data that was originally captured. It contains the result of processing one or more signals, for example, taking the average of two signals. [[DERIVED_Data_Type|DERIVED]]
::The DERIVED folder contain signals that can not be directly associated with the data that was originally captured. It contains the result of processing one or more signals, for example, taking the average of two signals. Specifications on derived data type and format can be found [[DERIVED_Data_Type|here]].


===EVENT LABELS===
===EVENT LABELS===
The ORIGINAL folder contains all of the Event labels stored in the C3D file, or any Event Labels that the user has created or modified.[[Event_Labels|EVENT_LABELS]]
::The EVENT LABELS folder contains all of the defined events stored in the C3D file, or any Event Labels that the user has created or modified. More details on events and creating them can be found [[Event_Labels|here]].


===METRIC===
===METRIC===
The ORIGINAL folder contains the signal as it was computed originally.[[Metrics|METRIC]]
::The METRIC folder contains metric values, which are discrete quantitative values computed through pipeline commands that do not have a time-base like other signals. More details about metrics can be found [[Metrics|here]].


===PARAMETERS===
===PARAMETERS===
[[C3D_Format#C3D_Parameter_Format|PARAMETERS]]
::The PARAMETERS data folder contains data that defines the data collection process (e.g., the number of analog channels, the sampling rate, scaling factors). This folder also specifies the location of the data (and type of data) within the file, and sometimes contains isolated annotations. More information on parameters in c3d data structures is found [[C3D_Format#C3D_Parameter_Format|here]].


===HEADER INFORMATION===
===HEADER INFORMATION===
[[C3D_Format#C3D_Header_Format|HEADER_INFORMATION]]
::The HEADER INFORMATION folder contains a summary of the data storage, including pointers to the start of the Parameter and Data blocks. More information on header information data types and formatting in c3d files can be found [[C3D_Format#C3D_Header_Format|here]].


==ORIGINAL and PROCESSED Data==
==ORIGINAL and PROCESSED Data==
Line 147: Line 135:


----
----
====To Open and Use Data View====
#In the data tree on the left, the folder with the original signals should already be open but if it isn't do the following:
##Click the + sign next to <b>TARGET</b> folder to open the inner folders.
##Click the + sign next to <b>ORIGINAL</b> subfolder. This reveals the contents of the original c3d data file. The red dots are the original signals as labeled by the capture system.
#Click on the marker labeled <i>LFT2.</i> with the Left Mouse Button  The <i>Data View</i> dialog box will open to the <b>Data Values</b> tab. Here you can see raw data or to export to an ASCII file<br>[[File:Tutorial2_10.png|441x756px|caption]] [[File:tutorial2_10(2).png|441x756px|caption]]<br>
#On the <b>Data Values</b> tab scroll down to the 24th frame.  This is where the data capture system began to collect data for this segment. No data was recorded for this segment in the previous 23 frames.  This is not abnormal but it is good to be aware that some markers will not have data for every frame.  The reasons for this vary but in this particular case the left foot was not in view of the cameras until the 24 frame.  If you see blank frame in the middle of a data set it may be an indication of an erroneous result.
#Open the <b>Data Graph</b> tab to view analog graphs. A Quickview can help you to locate obviously incorrect or noisy data.
#Open the <b>Signal Processing History</b> tab.  Although this tab is currently empty, you can view the processing history of signals here.  Visual3D has a command pipeline which allows the user to prepare scripts for processing data.  Typically these commands create new data that is derived or interpolated from their original data.  Determining the distance between 2 points would be an example of such deriving data.  The <b>Signal Processing History</b> tab will tell you what events if any took place on the data.
#Close the graph by clicking on the <b>X</b> in the top right-hand corner of the <i>Data View</i> dialog box.
NOTE:
The Data View can only be used for one Active file at a time. If you select ALL_FILES or a TAG, the Left Mouse Button click will not do anything.
An exception to this rule is that Metric signals will be displayed for more than one active file.
===Displaying a Signal Graph===
There is another way to view signal graphs which is different from signal data graphs in the Data View window.  These are "interactive" and offer different viewing options of the data which we will explore later. When activated, signal graphs appear on the right-side of the screen and can be used to visualize or add event labels.
====To activate an interactive signal graph====
#In the data tree on the left, if it's not open already open the <b>TARGET</b> folder.
#In the <b>ORIGINAL</b> subfolder, right-click the target <i>LFT2.</i>
#Open <b>Graph X, Y and Z, and Residual</b> and select <b>New Graph.</b>  A set of graphs will open on the right side of the screen.<br>[[File:tutorial2_11.png|665x504px|caption]]<br>
#Place the mouse on any point of one of the graph lines and wait. <br><b>Note:</b>  The technique used here is called a mouse over.  When you hold the mouse still long enough a yellow tool tip window will appear which displays information about that point on the graph.  This corresponds to one frame of data in the motion capture.<br>[[File:tutorial2_11a.jpg|caption]]<br>
===Formatting and Animating a Signal Graph===
#From the <b>View menu</b>, click on <b>View Graph Animation Frame Line.</b> This will create a line on the graph to correspond to a point in an animation. Then click PLAY in the VCR control panel to activate the animation. The vertical line on the signal graph will move along with the 3D figure.<br>'''Note:''' This may already be up by default.
#To format the signal graph, right-click anywhere on the graph to open an options menu. Select <b>Format Graph.</b><br><b>Note:</b>  You can also select multiple graphs first using the CTRL key on your keyboard.  Any changes you make will apply to each graph you select.<br>[[File:tutorial2_12.png|caption]]<br>
#Enter your desired changes and click <b>Apply.</b> Not all of the options apply to the <b>Signal and Events Processing</b> tab.  Below are some of the options that do apply.  Other options will be covered later in the <b>Reporting</b> tab.
*<b>Show Grids:</b>  Adds the number of X and or Y grid lines you specify.
*<b>Tics:</b>  Add or subtract tic marks to the axes.
*<b>Proportional Units:</b>  Makes width units equal to length units.
*<b>Show Points:</b>  Shows a small box for each frame on the graph.
*<b>Show BaseLine:</b>  Shows a line at zero.
*<b>Apply to All Selected:</b>  Applies the changes to multiple graphs if you have more than one selected.
*<b>Apply to Primary Selection Only:</b>  Applies the changes to only the first graph you selected if you have multiple graphs selected.
===Modify the Properties of the Animated Markers===
You can modify the size of the targets, landmarks, and joints in three ways.
====Marker Size====
First, by defining the default size of all markers
:[[File:DefaultMarkerSize.jpg]]
:[[File:SetMarkerSize.jpg]]
Second, by scaling the size in the Data Tree. Select a signal in the data tree using the right mouse button, then select the item "Draw Target Size"
:[[File:DrawTargetSize.jpg]]
Third, by scaling the size by selecting "Draw Target Properties"
:[[File:DrawTargetProperties.jpg]]
:[[File:SetAnimationDrawSize.jpg]]
Fourth, use a pipeline command.
Note that this uses the same dialog as above.
:[[Set_Animation_Draw_Properties]]
:/SIGNAL_TYPES=
:! /SIGNAL_FOLDER=ORIGINAL
:! /SIGNAL_NAMES=
:! /TARGET_SIZE=NORMAL
:! /OVERRIDE_TARGET_COLOR=TRUE
:/TARGET_COLOR=#80FF80
:/DRAW_TRAIL=TRUE
:! /OVERRIDE_TRAIL_COLOR=TRUE
:/TRAIL_COLOR=#FFFF80
:/TRAIL_ALL_FRAMES=TRUE
:! /TRAIL_BEHIND=
:! /TRAIL_AHEAD=
:''';'''

Latest revision as of 15:08, 24 April 2024

The data tree presents a hierarchical view of your experimental data, similar to the files-and-folders hierarchy seen on most computer operating systems.

Wherever you see a file-folder icon you can click once with the left mouse button on the small box containing a plus sign (+) to its left to expand it and see what the folder contains, e.g.

        becomes

The black-outlined square box next to each data item is a checkbox (click once with the left mouse button and it becomes ) which allows you to select that item as input to the pipeline (see below). Note that selecting a folder automatically selects all the individual items in that folder.

At the bottom level of the hierarchy are parameters, signals and metrics:

Signals
Signals are data items recorded over time by your motion-capture or data-acquisition system.
Mathematically, signals are discretely sampled functions whose independent variable is time. Signals may be scalar-valued (e.g., a single voltage output by a strain gauge) or vector-valued (e.g., (x,y,z)
coordinates of a target marker).
Parameters
Parameters are individual metadata items from a C3D file, which may be as simple as a single number or as complex as a list of names.
In contrast, parameters and metrics are discrete data which do not vary as a function of time or any other variable.
Metrics
Metrics are quantities computed by Visual3D which in some way collapse the time dimension of signals (e.g., average value of a signal over a duration) or the spatial dimension of models (e.g., center of mass of entire model).
The main distinction between parameters and metrics is that parameters are stored in the c3d file parameter section, whereas metrics are computed by Visual3D.

Different types of data are represented by distinctive icons in the data tree. Points and vector-valued signals whose values are point coordinates are represented by a red sphere icon ; scalar-valued signals (e.g., analog signals recorded during motion trials) are represented by a graph icon ; parameters are represented by three green lines reminiscent of printed text ; and so on. Note also that every item in the data tree has a name, also referred to as its label.

Data Folders

In the Visual3D Data Tree, the highest level folders represent the signal or data type (example TARGET, ANALOG, or FORCE). Here we will describe each data type and what the data represents.

TARGET

The TARGET data folder contains the POINT signals (MoCap markers) stored in the c3d file. Specifications on c3d data type and format can be found here.

ANALOG

The ORIGINAL folder for ANALOG data include the raw signals stored in the c3d file. These can include force, moments, or EMG signals. Specifications on analog data type and format can be found here.

FORCE, COFP, FREEMOMENT

The force, centre of pressure, and free moment signals (Force Platform Signals) are computed from the ANALOG signals and the FORCE_PLATFORM parameters in the c3d file.
These signals can be modified by changing the C3D Force Platform parameters, or by processing the ANALOG signals. Specifications on data type and format can be found here: Force, Centre of Pressure & Free Moment

KINEMATIC_KINETIC

The KINEMATIC_KINETIC folder contains a sub-folder of each segment created in the model that contains the kinetic and kinematic data resolved in the Laboratory Coordinate System. These signals exist for reference; they cannot be processed or included in a Report Graph. The LINKMODEL based items use this data to create the LINK_MODEL_BASED signals. Specifications on kinematic_Kinetic data type and format can be found here.

LINK_MODEL_BASED

The LINK_MODEL_BASED data is populated with signals produced by the model-based items defined by the user through the graphical interface or from the Compute_Model_Based_Data pipeline command.

DERIVED

The DERIVED folder contain signals that can not be directly associated with the data that was originally captured. It contains the result of processing one or more signals, for example, taking the average of two signals. Specifications on derived data type and format can be found here.

EVENT LABELS

The EVENT LABELS folder contains all of the defined events stored in the C3D file, or any Event Labels that the user has created or modified. More details on events and creating them can be found here.

METRIC

The METRIC folder contains metric values, which are discrete quantitative values computed through pipeline commands that do not have a time-base like other signals. More details about metrics can be found here.

PARAMETERS

The PARAMETERS data folder contains data that defines the data collection process (e.g., the number of analog channels, the sampling rate, scaling factors). This folder also specifies the location of the data (and type of data) within the file, and sometimes contains isolated annotations. More information on parameters in c3d data structures is found here.

HEADER INFORMATION

The HEADER INFORMATION folder contains a summary of the data storage, including pointers to the start of the Parameter and Data blocks. More information on header information data types and formatting in c3d files can be found here.

ORIGINAL and PROCESSED Data

In the Visual3D Data Tree, the highest level folders represent the signal or data type (example TARGET, ANALOG, or FORCE). Within these, there are ORIGINAL and PROCESSED folders. These folder names are occupied by Visual3D, and replicas cannot be created by the user.

ORIGINAL folders typically contain data read from the c3d file. Visual3D can also compute new signals from existing signals; smoothing to filter out noise is a typical example. New signals always go into a new folder, initially named PROCESSED, which is a sibling of the folder containing the signal from which the new one was derived (i.e., the new folder sits at the same level in the data hierarchy). By default when a signal is processed in Visual3D, the resulting signal is stored in the PROCESSED folder. Note that by default this will over-write and existing signals of the same name in the PROCESSED folder.

Many pipeline commands, however, will allow you to select the output folder for the PROCESSED signals.

Example: Link Model Based

If the LINKMODEL_BASED_SIGNAL is processed, the result is placed in the PROCESSED folder. Visual3D remembers how to build the ORIGINAL LINKMODEL_BASED_SIGNALS but has not kept complete track of the processing of the LINKMODEL based signals, so the PROCESSED LINKMODEL_BASED_SIGNALS must be reprocessed every time the LINKMODEL is changed. This is a subtle control from C-MOTION because we don't believe that the LINKMODEL_BASED_SIGNALS should be processed, just to make the signals look good.

If the user has elected to use PROCESSED data to create the LINKMODEL based items or if the user has elected not to use PROCESSED data to create the LINKMODEL based items the resulting signal is in the ORIGINAL folder.LINK_MODEL_BASED

Data Management

Context Menus

Clicking the right mouse button in the data tree will bring up a different context menu depending on the type of data selected. The following context menus are available from the data tree:

EVENT_LABEL - Brings up a context menu to:
Highlight a label on the 2D graphs
Rename a label
Delete a label
TARGET, GRFORCE, COFP, FREEMOMENT - Brings up a context menu to:
Graph the X component of a signal
Graph the Y component of a signal
Graph the Z component of a signal
Graph X, Y and Z components of a signal
Remove all graphs
View signal processing history
ANALOG - Brings up a context menu to:
Graph the signal
Remove all graphs
View signal processing history
Viewing Data

Checkboxes

The checkboxes next to each signal is used for signal and event processing. The processes specified in the "Process Signals" or "Process Events" dialog will be performed on the checked signals in the data tree.

Quick Processing

For example, if you want to interpolate and lowpass filter all TARGETs in all files, you would: Bring up the "Process Signals" dialog
Add an Interpolate, and a Lowpass Filter process to the "Signal Processing" list.
Set the files pulldown to "All Files"
Check the ORIGINAL checkbox under TARGET (All signals are selected).
Click the "Process" button in the "Process Signals" Dialog
Now all the TARGETs should be interpolated and filtered.
This creates a "PROCESSED" hierarchy under TARGET for the newly processed target data.

Creating a QuickView of Data

Visual3D has several tools to help you view your data. Data View is one of them.

Clicking the left mouse button on a signal will bring up a quickview window for quickly viewing the signals. Clicking the left mouse button on a parameter will bring up a dialog box to view the parameter data.

You can use the Data View to:

Display the raw data for a signal.
Display the graphs for a signals.
View the processing history of a signal.
Export a single signal file to an ASCII file.

Renaming a Signal

A Right Mouse Click on a signal name in the data tree pops up a menu.

One of the options is to rename the signal.

Deleting a Signal

A Right Mouse Click on a signal name in the data tree pops up a menu.

One of the options is to rename the signal.


Retrieved from ""