HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » event_commands » Event Between
visual3d:documentation:pipeline:event_commands:event_between

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:event_commands:event_between [2025/04/16 15:46] – Revised section header levels to reflect in the ToC. wikisysopvisual3d:documentation:pipeline:event_commands:event_between [2025/04/29 15:22] (current) – [Example 2: Identify a MidSwing Gait Event] wikisysop
Line 2: Line 2:
 ===== Overview ===== ===== Overview =====
  
-The **Event_Between** pipeline command __creates a new event label based on the time interval between two existing events in the C3D File (i.e. between the first and last events).__ This command is useful when analyzing motion data that requires identifying specific time points between known events.+The **Event_Between** pipeline command creates a __new event label__ based on the time interval between two existing events in the C3D File (i.e. between the first and last events). This command is useful when analyzing motion data that requires identifying specific time points between known events.
  
 This function allows users to: This function allows users to:
Line 33: Line 33:
 |**! /PERCENT_OFFSET=** |Specifies percent offset from first even of sequence.| |**! /PERCENT_OFFSET=** |Specifies percent offset from first even of sequence.|
  
-Offsets (**FRAME_OFFSET**, **TIME_OFFSET**, and **PERCENT_OFFSET**) allow fine control over the event placement, only one may be active and specified when the command is executed. By default, value is 0.+**Note:** Offsets (**FRAME_OFFSET**, **TIME_OFFSET**, and **PERCENT_OFFSET**) allow fine control over the event placement, only one may be active and specified when the command is executed. By default, value is 0.
  
 ===== Dialog ===== ===== Dialog =====
Line 111: Line 111:
 <code> <code>
 Compute_Model_Based_Data Compute_Model_Based_Data
-/RESULT_NAME= Left_Hip_Angle +/RESULT_NAME=Left_Hip_Angle 
-! /SUBJECT_TAG= +/SUBJECT_TAG=ALL_SUBJECTS
 /FUNCTION=JOINT_ANGLE /FUNCTION=JOINT_ANGLE
-/SEGMENT=Left_Hip +/SEGMENT=LTH 
-! /REFERENCE_SEGMENT=LAB +/REFERENCE_SEGMENT=RPV 
-! /RESOLUTION_COORDINATE_SYSTEM=LAB+/RESOLUTION_COORDINATE_SYSTEM=
 ! /USE_CARDAN_SEQUENCE=FALSE ! /USE_CARDAN_SEQUENCE=FALSE
 ! /NORMALIZATION=FALSE ! /NORMALIZATION=FALSE
Line 131: Line 131:
 ! /TREADMILL_SPEED=0.0 ! /TREADMILL_SPEED=0.0
 ; ;
 +</code>
  
 +
 +<code>
 Compute_Model_Based_Data Compute_Model_Based_Data
-/RESULT_NAME= Left_Knee_Angle +/RESULT_NAME=Left_Knee_Angle 
-! /SUBJECT_TAG= +/SUBJECT_TAG=ALL_SUBJECTS
 /FUNCTION=JOINT_ANGLE /FUNCTION=JOINT_ANGLE
-/SEGMENT=Left_Knee +/SEGMENT=LSK 
-! /REFERENCE_SEGMENT=LAB +/REFERENCE_SEGMENT=LTH 
-! /RESOLUTION_COORDINATE_SYSTEM=LAB+/RESOLUTION_COORDINATE_SYSTEM=
 ! /USE_CARDAN_SEQUENCE=FALSE ! /USE_CARDAN_SEQUENCE=FALSE
 ! /NORMALIZATION=FALSE ! /NORMALIZATION=FALSE
Line 165: Line 168:
 /RESULT_METRIC_NAME= Left_Hip_Angle_at_MidSwing /RESULT_METRIC_NAME= Left_Hip_Angle_at_MidSwing
 ! /APPLY_AS_SUFFIX_TO_SIGNAL_NAME=FALSE ! /APPLY_AS_SUFFIX_TO_SIGNAL_NAME=FALSE
-! /SIGNAL_COMPONENTS=+! /SIGNAL_COMPONENTS= 
 ! /COMPONENT_SEQUENCE= ! /COMPONENT_SEQUENCE=
 /EVENT_NAME= MidSwing /EVENT_NAME= MidSwing
Line 195: Line 198:
 </code> </code>
  
-Following this, the [[visual3d:documentation:pipeline:event_commands:event_threshold|Event_Threshold]] command is used to create an event named **Max_Knee_Flexion** when the **Left_Knee_Angle** exceeds 45 degrees, identifying the point of maximum knee flexion during the swing phase.+Following this, the [[visual3d:documentation:pipeline:event_commands:event_threshold|Event_Threshold]] command is used to create an event named **Max_Knee_Flexion** (X-Component) when the **Left_Knee_Angle** exceeds 45 degrees (this should be different based on user data), identifying the point of maximum knee flexion during the swing phase.
 <code> <code>
 Event_Threshold Event_Threshold
-/RESULT_EVENT_NAME= Max_Knee_Flexion +/RESULT_EVENT_NAME=Max_Knee_Flexion 
-/SIGNAL_TYPES= LINK_MODEL_BASED+/SIGNAL_TYPES=LINK_MODEL_BASED
 ! /SIGNAL_FOLDER=ORIGINAL ! /SIGNAL_FOLDER=ORIGINAL
-/SIGNAL_NAMES= Left_Knee_Angle +/SIGNAL_NAMES=Left_Knee_Angle 
-! /SIGNAL_COMPONENTS=+/SIGNAL_COMPONENTS=X
 ! /FRAME_OFFSET=0 ! /FRAME_OFFSET=0
 ! /TIME_OFFSET= ! /TIME_OFFSET=
-! /EVENT_SEQUENCE=+/EVENT_SEQUENCE=LTO+LHS
 ! /EXCLUDE_EVENTS= ! /EXCLUDE_EVENTS=
 ! /EVENT_SEQUENCE_INSTANCE=0 ! /EVENT_SEQUENCE_INSTANCE=0
Line 212: Line 215:
 ! /EVENT_SUBSEQUENCE_INSTANCE=0 ! /EVENT_SUBSEQUENCE_INSTANCE=0
 ! /EVENT_INSTANCE=0 ! /EVENT_INSTANCE=0
-/THRESHOLD= 45 +/THRESHOLD=45 
-! /ON_ASCENT=+/ON_ASCENT=TRUE
 ! /ON_DESCENT= ! /ON_DESCENT=
 ! /FRAME_WINDOW=8 ! /FRAME_WINDOW=8
Line 220: Line 223:
 ; ;
 </code> </code>
 +
 +As you can see in the following image, the two events made have been placed in the correct locations.
 +
 +{{:visual3d:documentation:pipeline:event_commands:ex2_graph_output.png?600|}}
visual3d/documentation/pipeline/event_commands/event_between.1744818392.txt.gz · Last modified: 2025/04/16 15:46 by wikisysop