Running Symmetry

What is Running Symmetry?

Running Symmetry in OpenField is the measure of load imbalance between the right and left leg when running.

In OpenField, Running Symmetry is broken down into an event by event basis, with each event able to be analysed individually, or an entire session collectively. 

A negative running imbalance % is indicative of an x% additional load on the left side (where x is the running imbalance value).
A positive running imbalance % is indicative of an x% additional load on the right side (where x is the running imbalance value).

Practical applications of Running Symmetry include:

• Rehabilitation - See changes over time as the athlete improves during the process of rehabilitation
  
  
• Return to Play - Use Running Symmetry as an objective return to play marker
  
  
• Athlete Screening- Use Running Symmetry on a weekly basis to identify changes in running mechanics

Running Symmetry Data Quality 

The Running Symmetry analysis relies heavily on quality data to maintain accuracy. Data Quality can be maintained by:

• Device Fit - Ensure the unit is tightly fitted to the body to minimise bouncing of the unit
  
  
• Running Surface - An undulating or irregular surface will influence results as the athlete will adapt as required. For consistent results ensure a consistent surface is used
  
  
• Straight Line Running - Straight line running as by nature is more symmetrical that nonlinear running. For consistent results run in straight lines
  
  
• Constant Speed - Significant acceleration and decelerations are generally not symmetrical activities and are usually excluded for the analysis. For consistent results run at constant speeds.

Running Symmetry Effort/Series Thresholds

Running Symmetry Efforts are only calculated if they meet the set Minimum Velocity and Minimum Consecutive Footstrikes thresholds. For a Running Symmetry Effort to be calculated, the velocity must exceed the Minimum Velocity for all Footstrikes, in addition to the amount of consecutive Footstrikes in this effort to be above the minimum Footstrike threshold.

For example, a Running Symmetry Effort will be calculated if a Device detects 8 or more consecutive Footstrikes, where the Velocity is over 3.3m/s during each Footstrike. (Default Thresholds of 3.3m/s and 8 Consecutive Footstrikes)

To set the Velocity and Footstrike Thresholds on the Cloud (this will determine which Running Symmetry Efforts will be calculated by default, and subsequently synced to the cloud):

1. Login to the OpenField Cloud
   
   
2. Navigate to Settings -> Teams
   
   
3. Scroll down and set the 'Running Symmetry - Minimum Speed Threshold' and 'Running Symmetry - Minimum Number of Consecutive Footstrikes'. By default these are set to 3.3m/s and 8 respectively.
   
   
   
   
4. Hit Save Changes - Note if 'Use Running Symmetry in Indoor Mode' is selected, by Default OpenField will calculate and sync up Running Symmetry events without using Velocity data (less accurate). Tick this if you are collecting indoor data and wish to calculate Running Symmetry in the absence of Velocity data.
   
   
5. On the OpenField Console, run a Fast Sync to sync down any changes
   
   

Analysing Running Symmetry Efforts/Series

Running Symmetry Efforts can be analysed on the Console in the Table of Events/Efforts Console Widget, and on the Cloud in a Cloud Widget.

To Process and Analyse Running Symmetry:

1. In the OpenField Console, Download and Process Data from the Devices post session.
   If you wish to analyse previously downloaded data, reprocess raw files via the Data Transfer Screen. See Reprocessing Raw Files for more information.
   
   
2. Load the Activity for the Files processed in Step 1.
   
   
3. In a Console Dashboard, create a new Table of Events/Efforts Console Widget, and select 'Running Symmetry'
   
   
   
   
4. By Default, the Running Symmetry Effort Calculation Thresholds in the Table of Events will match the Settings set in the cloud.
   
   
   
   
5. If desired, change the Minimum Speed and Minimum Footstrikes threshold, to change the calculated Running Symmetry Efforts as displayed in the Console Widget. Note this does not change the Running Symmetry Thresholds in the Cloud, or for Running Symmetry Data synced to the Cloud (the Cloud Data respects the Thresholds set in the Team Settings)
   
   
   
   
6. Run a Fast Sync to sync Running Symmetry data to the Cloud
   
   
7. Login to the OpenField Cloud
   
   
8. On a Cloud Dashboard, create a new Cloud Widget. Navigate to Parameters and select the desired Running Symmetry Parameters
   
   
   
   
9. View the Running Symmetry Data in the Cloud Widget
   
   

Running Symmetry Parameters and Definitions

The below Running Symmetry Parameters are available for analysis:

• Running Imbalance (%) -  Average percentage load difference between left and right legs, across all Running Symmetry Series/Efforts. A negative running imbalance % is indicative of an x% additional load on the left side (where x is the running imbalance value).
  A positive running imbalance % is indicative of an x% additional load on the right side (where x is the running imbalance value).
  
  
• Footstrikes - The count of footstrikes across all Running Symmetry series/efforts (that meet the minimum thresholds set)
  
  
• Running Deviation - the % deviation from running in a straight line
  
  
• Running Series # - the total amount of Running Symmetry Series/Efforts detected