Differences

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

--- alexvisual [2025/08/13 17:54] – wikisysop
+++ alexvisual [2025/08/13 19:09] (current) – wikisysop
@@ Line 90: / Line 90: @@
   ;
-. Now, this subject performed 125 trials. Since the main research question being proposed is about fatigue, the 125 trials are divided into 4 sections (quarters) so that each quarter can be analyzed separately and compared. To create the proper tags for this, conditional statements are used and depending on which iteration of the for-loop the pipeline is on, different tags to mark which quarter the trial took place are assigned. The quarters are: Q1 (Trial 1-31), Q2 (Trial 32-63), Q3 (Trial 64-94), Q4 (Trial 95-125).
+. Now, this subject performed 125 trials. Since the main research question being proposed is about fatigue, the 125 trials are divided into 4 sections (quarters) so that each quarter can be analyzed separately and compared. To create the proper tags for this, conditional statements are used and depending on which iteration of the for-loop the pipeline is on, different tags to mark which quarter the trial took place are assigned. The quarters are: Q1 (Trial 1-31), Q2 (Trial 32-63), Q3 (Trial 64-94), Q4 (Trial 95-125).\\
- a. For Q1 and Q4, the conditional statements are relatively simple and the expression is true if the iteration count is greater or less than the quarter number.
+ **a.** For Q1 and Q4, the conditional statements are relatively simple and the expression is true if the iteration count is greater or less than the quarter number.
   Conditional_Statement
@@ Line 109: / Line 109: @@
   ;
- b. For Q2 and Q3, nested conditional statements must be used to satisfy the lower and upper bounds.
+ **b.** For Q2 and Q3, nested conditional statements must be used to satisfy the lower and upper bounds.
   Conditional_Statement
@@ Line 135: / Line 135: @@
   /ITERATION_PARAMETER_NAME= QuarterTwo
   ;
+. The order of the pipeline in its current state at this point would be:
+  * Set_Pipeline_Parameter_To_Folder_Path
+  * Set_Pipeline_Parameter_To_List_Of_Files
+  * For_Each
+  * File_New
+  * File_Open
+  * Select_Active_File
+  * Assign_Tags_To_Files
+  * Assign_Tags_To_Files
+  * Conditional_Statement
+  * Assign_Tags_To_Files
+  * Conditional_Statement_End
+  * Conditional_Statement
+  * Conditional_Statement
+  * Assign_Tags_To_Files
+  * Conditional_Statement_End
+  * Conditional_Statement_End
+  * Conditional_Statement
+  * Conditional_Statement
+  * Assign_Tags_To_Files
+  * Conditional_Statement_End
+  * Conditional_Statement_End
+  * Conditional_Statement
+  * Assign_Tags_To_Files
+  * Conditional_Statement_End
+  * File_Save_As
+  * End_For_Each
+===Event Tags===
+In biomechanical data analysis, it is necessary to have defined events such as 'start', 'stop' where the movements are consistent and the data can be normalized. In this free throw dataset, a large portion of the time-series data is spent with the subject catching the pass and walking to the free throw line. This is not important data to answer the research question so it is cut out in this section. After some trial and error, the right hand was used as the event indicator. When the right hand was at its lowest was the start of the free throw and when the right hand was at its highest was the end of the follow through, a repeatable motion. See the gif below for a visual and graph of the start and end of the repeatable free throw motion.
+{{:visual3d:tutorials:event_freethrow.gif}}
+Now that it is understand where the events are, they can be added to the pipeline.
+. Add 'Event_Global_Minimum' which will get the lowest point on the graph corresponding to the lowest point of the right hand.
+  Event_Global_Minimum
+  ! name the event
+  /RESULT_EVENT_NAME=START
+  /SIGNAL_TYPES=KINETIC_KINEMATIC
+  ! right hand
+  /SIGNAL_FOLDER=P0001:RHA
+  ! center of gravity
+  /SIGNAL_NAMES=CGPOS
+  ! z-component
+  /SIGNAL_COMPONENTS=Z
+  ! /FRAME_OFFSET=0
+  ! /TIME_OFFSET=
+  ! /EVENT_SEQUENCE=
+  ! /EXCLUDE_EVENTS=
+  ! /EVENT_SEQUENCE_INSTANCE=0
+  ! /EVENT_SUBSEQUENCE=
+  ! /SUBSEQUENCE_EXCLUDE_EVENTS=
+  ! /EVENT_SUBSEQUENCE_INSTANCE=0
+  ! /THRESHOLD=
+  ;
+. Add 'Event_Global_Maximum' which will get the highest point on the graph corresponding to the highest point of the right hand.
+  Event_Global_Maximum
+  /RESULT_EVENT_NAME=END
+  /SIGNAL_TYPES=KINETIC_KINEMATIC
+  /SIGNAL_FOLDER=P0001:RHA
+  /SIGNAL_NAMES=CGPOS
+  /SIGNAL_COMPONENTS=Z
+  ! /FRAME_OFFSET=0
+  ! /TIME_OFFSET=
+  ! /EVENT_SEQUENCE=
+  ! /EXCLUDE_EVENTS=
+  ! /EVENT_SEQUENCE_INSTANCE=0
+  ! /EVENT_SUBSEQUENCE=
+  ! /SUBSEQUENCE_EXCLUDE_EVENTS=
+  ! /EVENT_SUBSEQUENCE_INSTANCE=0
+  ! /THRESHOLD=
+  ;
+. This step isn't required, but for interest, an event between can be added that will put an event at the midpoint between the start and end events.
+  Event_Between
+  /NEW_EVENT_NAME=MIDSHOT
+  ! /RANGE_INSTANCE=0 !includes all events
+  /EVENT_SEQUENCE=START+END
+  ! /EXCLUDE_EVENTS=
+  ! /FRAME_OFFSET=0
+  ! /TIME_OFFSET=
+  ! /PERCENT_OFFSET=
+  ;
+. All 3 of these event commands can be added in order after the last 'Conditional_Statement_End' and before the 'File_Save_As' in the pipeline.
+===Computing Joint Angles===
+Now that all the tags and events are created, the final step is to calculate kinematic variables and specifically in this case, joint angles. The joint angles for the lower limb model will be calculated (ankle, knee, and hip joint).
+. Navigate to the **Compute Model Based Data** window.