Device Location Setting – Basketball Movement Profile / Indoor Analytics

The Basketball Movement Profile / Indoor Analytics algorithm is designed to detect and categorise basketball and other indoor movements when devices are worn either:

• In a Catapult vest
• On the athlete’s waist (front or back)

To ensure accurate results, the correct Device Location must be set before processing device data.

Device Location is configured at the Team level in OpenField Cloud and applies to all athletes within that team once the setting has been synced to OpenField Console.

Required OpenField Console Version

Support for all three Device Locations (Vest, Waist–Front, Waist–Back) requires:

• OpenField Console v3.15.0 or higher

Earlier versions of Console only support:

• Vest
• Waist (legacy setting, now mapped to Waist–Back)

Available Device Location Settings

Each team can be configured with one of the following Device Locations:

1. Vest (Default)

• Applied automatically to all new and existing teams unless changed.

2. Waist–Back

• If your team previously used the legacy “Waist” setting, it now defaults to Waist–Back.
• Device is worn on the posterior (back) of the athlete.

3. Waist–Front

• Device is worn on the anterior (front) of the athlete.
• Selecting this option triggers sensor axis inversion during processing (see below).

How to Set the Device Location

1. Log in to OpenField Cloud.
2. Navigate to Settings > Teams.
3. Select the desired team.
4. Scroll to Device Location.
   
   
5. Choose one of:
   • Vest
   • Waist–Back
   • Waist–Front
6. If Waist–Front is selected, a confirmation pop-up will appear explaining that device axes will be inverted during processing.
   
   
7. Select Save Changes.
8. Open OpenField Console and run a Sync to apply the updated setting locally.

Devices Axes Inversion (Waist-Front)

When Are Device Axes Inverted?

Device sensor axes will be inverted when:

• Raw files are processed or reprocessed
• The athlete belongs to a team with Waist–Front enabled

Device axes will NOT be inverted when:

• The team is set to Vest
• The team is set to Waist–Back (previously Waist)

Why Are Device Axes Inverted?

For optimal functionality, T7 devices should be worn with LEDs facing outward (away from the athlete's body). See also How to Put Vector Devices into the Garment (T7)

In OpenField Cloud, existing inertial parameters assume the device is worn on the back (posterior). As a result, orientation-sensitive parameters (i.e. IMA Accelerations, IMA Decelerations, IMA Change of Directions) are defined according to this default sensor orientation.

When worn on the front (anterior), the device is effectively mounted “back-to-front” relative to the default orientation. To maintain correct parameter naming and interpretation, the device axes are inverted during data processing.

This ensures that all orientation-sensitive inertial metrics (including IMA Accelerations, Decelerations, and Change of Directions) are accurately represented.

Parameters Affected by Device Axes Inversion

Any parameter dependent on sensor orientation will be affected.

These include:

• IMA Accelerations
• IMA Decelerations
• IMA Change of Directions (CoDs)
• IMA Clockface accelerations
• Selected parameters derived from sport-specific algorithms and plugins:
  • Rugby Scrums and Lineouts
  • American Football Lineman Contacts 
  • Ice Hockey Stride Force
  • Tennis Movement Profile & Stroke Detection 

Parameters NOT Affected by Device Axes Inversion

The following parameters are orientation-independent and will show no or negligible changes:

Velocity-Derived Parameters

• Total Distance
• Banded Distance
• Velocity-derived Accelerations
• Metabolic Power

For T7 devices, velocity-derived parameters are available only for LPS (via a ClearSky installation). T7 devices do not support GPS.

Other Metrics

• Basketball Movement Profile
• Indoor Jumps
• Total PlayerLoad
• Banded PlayerLoad

Reprocessing Historical Data After Changing Device Location Setting

If you update the Device Location setting, historical data must be reprocessed to apply the new axis orientation.

Steps:

1. Update the Device Location in OpenField Cloud (per team).
2. Sync OpenField Console.
3. Reprocess required Raw Files in the Data Transfer screen. See also Reprocessing Raw Files/Session Data
4. Sync OpenField to upload updated summary data per activity to the Cloud.

Alternatively, contact Support for assistance with reprocessing historical data.

Best Practice Recommendations

• Always confirm the intended device wear location before the season begins.
• Ensure Console is updated to v3.15.0+.
• Reprocess historical data if switching between Waist–Back and Waist–Front.
• Communicate internally before changing a Team-level setting, as it affects all athletes within that team.