Differences

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

--- inspect3d:documentation:dialogs:auto-populate_groups [2024/06/18 20:20] – sgranger
+++ inspect3d:documentation:dialogs:auto-populate_groups [2024/07/12 13:26] (current) – removed sgranger
@@ Line 1: / Line 1: @@
-{{{{{{{{autopop2.png
-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
-  * get signals
-  * combine sides
-  * compare conditions using tags
-  * refine using signal
-these features are still being enhanced, so feel free to make requests.
-===== contents =====
-  * [[#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 =====
-the user can either:
-a) browse for a settings file stored on a local pc
-b) save the existing settings as an .xml file
-===== get signals from =====
-the signal type corresponds to the signal types in visual3d workspaces, and signal folder also corresponds to the folder structure in the corresponding viusal3d folder.
-this section will create a query and condition for each signal in the folder specified.
-===== combine sides? =====
-there are two main types of data that the following options can be used to categorize:
-for general gait mechanics you can use the following options
-  * do not combine sides
-signals will not be combined under any rule and one query will be built for each signal found.
-  * combine left/right
-signals will be combined in left/right pairs across the body with the appropriate changes made to event sequences.
-  * combine side based on tag (options below)
-sidetags.png
-signals will be combined according to the subject's affected side.
-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)
-baseballoptions.png
-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.
-===== compare conditions using tags =====
-for however many tags are specified, there will be a group created with the tag name appended (ex. group_tm).
-===== refine using signal =====
-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
-}}}}}}}}