User Tools

Site Tools


other:inspect3d:documentation:dialogs:auto_populate_groups

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
other:inspect3d:documentation:dialogs:auto_populate_groups [2024/12/17 19:07] wikisysopother:inspect3d:documentation:dialogs:auto_populate_groups [2024/12/17 20:07] (current) – [Get Signals from] wikisysop
Line 1: Line 1:
 ====== Auto Populate Groups ====== ====== Auto Populate Groups ======
 The Auto Populate Queries is meant to simplify the tedious task of defining Queries and query Conditions. There are five main sections to this menu: The Auto Populate Queries is meant to simplify the tedious task of defining Queries and query Conditions. There are five main sections to this menu:
-  * Autobuild Settings/Saving Settings +  * [[#Auto_Build_Settings_File|Autobuild Settings/Saving Settings]] 
-  * Get Signals +  * [[#Get_Signals_from|Get Signals]] 
-  * Combine Sides +  * [[#Combine_sides?|Combine Sides]] 
-  * Compare conditions using tags +  * [[#Compare_conditions_using_tags|Compare conditions using tags]] 
-  * Refine using signal +  * [[#Refine_Using_Signal|Refine using signal]]\\
-=====Dialog=====+
 {{ :autopop2.png?400}} {{ :autopop2.png?400}}
  
-==== Contents ==== +=====Dialog=====
- +
- +
-  * [[#Auto_Build_Settings_File|1 Auto Build Settings File]] +
-  * [[#Get_Signals_from|2 Get Signals from]] +
-  * [[#Combine_sides?|3 Combine sides?]] +
-  * [[#Compare_conditions_using_tags|4 Compare conditions using tags]] +
-  * [[#Refine_Using_Signal|5 Refine Using Signal]] +
  
 ==== Auto Build Settings File ==== ==== Auto Build Settings File ====
Line 25: Line 16:
 a) browse for a settings file stored on a local PC\\ a) browse for a settings file stored on a local PC\\
 b) save the existing settings as an .xml file\\ b) save the existing settings as an .xml file\\
 +
 ==== Get Signals from ==== ==== Get Signals from ====
  
Line 44: Line 36:
  
 {{ :sidetags.png?700 }}\\ {{ :sidetags.png?700 }}\\
-    * The **Affected Side Right** and **Affected Side Left** parameters describe which motion file tags are used to indicate that the relevant participants's affected side is right or left respectively, while the **Affected Side Label** and **Intact Side Label** parameters allow you to specify how the left and right signal names should be prefixed according to the relevant subject's affected side. \\Although developed with clinical populations in mind, this feature can be used to simplify the process of combining signals across sides of the body to account for handedness, footedness, etc.+     * The **Affected Side Right** and **Affected Side Left** parameters describe which motion file tags are used to indicate that the relevant participants's affected side is right or left respectively, while the **Affected Side Label** and **Intact Side Label** parameters allow you to specify how the left and right signal names should be prefixed according to the relevant subject's affected side. \\Although developed with clinical populations in mind, this feature can be used to simplify the process of combining signals across sides of the body to account for handedness, footedness, etc.
  
-For baseball pitching or hitting: 
  
-  * Baseball (options below)+  * **For baseball pitching or hitting** (options below): Signals will combined according to the handedness of the pitcher or batter.
  
-{{:baseballoptions.png}}+{{ :baseballoptions.png?700 }}
  
-Signals will combined according to the handedness of the pitcher or batter. 
  
-The **Right Dominant Tag** and **Left Dominant Tag** parameters describe which motion file tags are used to indicate that the relevant pitcher/hitter is right- or left-dominant respectively. The **Dominant Arm Label**, **Nondominant Arm Label**, **Lead Leg Label**, and **Trail Leg Label** parameters allow you to specify how signals for each limb will be prefixed. Finally, the start event and end event define the event sequence for extracting traces from the signal.+     The **Right Dominant Tag** and **Left Dominant Tag** parameters describe which motion file tags are used to indicate that the relevant pitcher/hitter is right- or left-dominant respectively. The **Dominant Arm Label**, **Nondominant Arm Label**, **Lead Leg Label**, and **Trail Leg Label** parameters allow you to specify how signals for each limb will be prefixed. Finally, the start event and end event define the event sequence for extracting traces from the signal.
  
 +\\
 ==== Compare conditions using tags ==== ==== Compare conditions using tags ====
  
-For however many tags are specified, there will be a group created with the tag name appended (ex. Group_TM).+For however many tags are specified, there will be a group created with the tag name appended (ex. Group_TM).\\ \\
  
 ==== Refine Using Signal ==== ==== Refine Using Signal ====
 +{{ :refinements.png?200}}
 To further refine your signals, you can create custom refinements that are either global values or individual values from the Visual3D workspace. You can also use the Less Than/More Than function to import only signals below or above a certain threshold. To further refine your signals, you can create custom refinements that are either global values or individual values from the Visual3D workspace. You can also use the Less Than/More Than function to import only signals below or above a certain threshold.
- 
-{{:refinements.png}} 
  
  
  
other/inspect3d/documentation/dialogs/auto_populate_groups.1734462457.txt.gz · Last modified: 2024/12/17 19:07 by wikisysop