User Tools

Site Tools


visual3d:documentation:pipeline:metric_commands:metric_compute_gait_signal_stats

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
visual3d:documentation:pipeline:metric_commands:metric_compute_gait_signal_stats [2024/06/17 18:20] – created sgrangervisual3d:documentation:pipeline:metric_commands:metric_compute_gait_signal_stats [2025/01/11 13:31] (current) wikisysop
Line 1: Line 1:
 +====== Metric Compute Gait Signal Stats ======
  
- +These discrete gain metrics are part of the common cohort of [[https://www.sciencedirect.com/science/article/abs/pii/0167945796000061 | Gait Parameters]].
- +
- +
-These discrete gain metrics are part of the common cohort of [[[https://www.sciencedirect.com/science/article/abs/pii/0167945796000061|Gait Parameters]]].+
  
 Create user defined statistics for a set of signals. The following stats are computed for the signals selected for each side of the body selected. Create user defined statistics for a set of signals. The following stats are computed for the signals selected for each side of the body selected.
  
-====== Signal_Stats ======+===== Signal_Stats =====
  
 Signal value at Heel Strike Signal value at Heel Strike
Line 46: Line 44:
 Swing (Count)= number of swing phases used Swing (Count)= number of swing phases used
 Cycle (Count)= number of cycles used. Cycle (Count)= number of cycles used.
-====== Command_Dialog ======+===== Command_Dialog =====
  
-[[GaitSignalStatsDlg.jpg]]+{{:GaitSignalStatsDlg.jpg}}
  
-====== Pipeline_Command ======+===== Pipeline_Command =====
  
 The pipeline command is as follows: The pipeline command is as follows:
Line 73: Line 71:
 ! /MERGE_COMPONENTS=FALSE ! /MERGE_COMPONENTS=FALSE
 **;** **;**
-====== Resulting_Signals ======+===== Resulting_Signals =====
  
 Several of the command parameters affect the signal that is created. Several of the command parameters affect the signal that is created.
  
-===== Example1 =====+==== Example1 ====
  
 This group of commands results in a metric signal being created in the SIGNAL_STATS folder that is the same name as /Signal_Names parameter and it contains values related to the X-Component of the signal. This group of commands results in a metric signal being created in the SIGNAL_STATS folder that is the same name as /Signal_Names parameter and it contains values related to the X-Component of the signal.
Line 89: Line 87:
  
  
-===== Example2 =====+==== Example2 ====
  
 This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string _Stats to the name in the /Signal_Names parameter and it contains values related to the X-Component of the signal. This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string _Stats to the name in the /Signal_Names parameter and it contains values related to the X-Component of the signal.
Line 101: Line 99:
  
  
-===== Example3 =====+==== Example3 ====
  
 This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string "_Stats_X" to the name in the /Signal_Names parameter and it contains values related to the X-Component of the signal. This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string "_Stats_X" to the name in the /Signal_Names parameter and it contains values related to the X-Component of the signal.
Line 113: Line 111:
  
  
-===== Example4 =====+==== Example4 ====
  
 This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string "_Stats_X" to the name in the /Signal_Names parameter containing values related to the X-Component of the signal; "_Stats_Y" to the name in the /Signal_Names parameter containing values related to the Y-Component of the signals.;"_Stats_Z" to the name in the /Signal_Names parameter containing values related to the Z-Component of the signals.. This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string "_Stats_X" to the name in the /Signal_Names parameter containing values related to the X-Component of the signal; "_Stats_Y" to the name in the /Signal_Names parameter containing values related to the Y-Component of the signals.;"_Stats_Z" to the name in the /Signal_Names parameter containing values related to the Z-Component of the signals..
Line 122: Line 120:
 /COMPONENT_SEQUENCE=ALL /COMPONENT_SEQUENCE=ALL
 /MERGE_COMPONENTS=FALSE /MERGE_COMPONENTS=FALSE
-===== Example5 =====+==== Example5 ====
  
 This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string "_Stats" to the name in the /Signal_Names parameter containing values related to the X-Component of the signal; The resulting signal contains 3 frames of data. The first row is related to the X-Component, the second row is related to the Y-Component and the third row is related to the Z-Component. This group of commands results in a metric signal being created in the SIGNAL_STATS folder that appends the string "_Stats" to the name in the /Signal_Names parameter containing values related to the X-Component of the signal; The resulting signal contains 3 frames of data. The first row is related to the X-Component, the second row is related to the Y-Component and the third row is related to the Z-Component.
Line 131: Line 129:
 /COMPONENT_SEQUENCE=ALL /COMPONENT_SEQUENCE=ALL
 /MERGE_COMPONENTS=TRUE /MERGE_COMPONENTS=TRUE
- 
- 
  
  
visual3d/documentation/pipeline/metric_commands/metric_compute_gait_signal_stats.1718648427.txt.gz · Last modified: 2024/06/17 18:20 by sgranger