Inspect3D Advanced Query Section: Difference between revisions

From Software Product Documentation
Jump to navigation Jump to search
Line 87: Line 87:
Refinement allows you to say if this trial contains "Signal X", check if that signal meets the specified criteria.
Refinement allows you to say if this trial contains "Signal X", check if that signal meets the specified criteria.
* <b>Refinement Name:</b> Each refinement in a sub-group requires a unique name
* <b>Refinement Name:</b> Each refinement in a sub-group requires a unique name
* <b>Signal Definition:</b> Specify the signal you want to work with as it is referenced in the Visual3D Data Tree
* <b>Signal Definition:</b> Specify the signal you want to work with as it is referenced in the [[Data_Tree_Summary|Visual3D Data Tree]]
** <b>Type:</b>
** <b>Type:</b>
** <b>Folder:</b>
** <b>Folder:</b>

Revision as of 18:32, 2 May 2022

Language:  English  • français • italiano • português • español 


Introduction

The group definition dialog is used to define which signals you want to query from the CMZ library and allows you to group data together (ex. right and left side, intact/affected).

Sections

Group Definition File

You can save group definitions (.q3d) so they can be loaded again (for use on the same or a different CMZ library). You can save one group definition at a time to a file, or all files.

Groups and Sub Groups

You can define Groups and Sub-Groups.

  • A Group would be "AnkleMoment_X"
  • A Sub-Group would be "LAnkleMoment_X" and "RAnkleMoment_X"
  • A group can have as many Sub-Groups as necessary (1-N)

Note: Groups and Sub-Groups can use spaces and special characters - if you plan to update the CMZ files with exclusions, be cautious using special characters. Sub-Group names can be repeated in different groups (but not within the same group).

Sub-Group Definition

The Sub-Group Definition lets you define the signals you want to query. These signals are defined using the following information:

Signals

Name of the signal as it is referenced in the Visual3D Data tree:

  • Type
  • Folder
  • Name
  • Component
  • Negate Results

Events

Events you want to use to normalize the data to:

  • Event Sequence: Events to normalize data to
    • Typically Kinematic Signals are normalized from R/LHS to R/LHS
    • Typically Kinetic Signals are normalized from R/LON to R/LHS
  • Exclude Events:
    • Event sequences that data should not be included
  • Number of Points: Typically a gait cycle is normalized to 101 data points
  • Spline Type: Cubic or Linear - you should use a cubic spline to normalize the data

Refinement

Refinement:

  • Refine using tag: Any tags that exist in the workspace can be selected
  • Use AND Logic: If two tags are selected:
    • Checking AND will only include trials that contain both tags
    • Unchecking AND will include any trials that contain either tag
  • Refine using signal: Allows you to add further requirements to query a signal



Refinement allows you to say if this trial contains "Signal X", check if that signal meets the specified criteria.

  • Refinement Name: Each refinement in a sub-group requires a unique name
  • Signal Definition: Specify the signal you want to work with as it is referenced in the Visual3D Data Tree
    • Type:
    • Folder:
    • Name:
    • Component:
  • Value Must Be: Options are:
    • Less Than: Specify a threshold the signal must be less than
    • Greater Than: Specify a threshold the signal must be greater than
    • Equal To: Specify a threshold the signal must be equal to
    • Not Equal To: Specify a threshold the signal must not be equal to
    • Between: Specify two values the signal must be between
    • Manual: Specify a Visual3D Expression the signal must satisfy

Retrieved from ""