- Ensure vest fit is ‘snug’ to avoid any movement of the device separate to that of the athletes torso. Loose fitting vests will lead to erroneous inertial sensor data being recorded.
See: Vector Vest Size Guide
- Where possible use the same device with the same athlete. This will remove any small inter-device differences that may exist.
- Ensure the device is placed in the vest the correct way around - LED's facing outward and the Catapult Logo at the bottom. Mounting the device upside down or back to front will invalidate the inertial sensor data.
- We recommend Bands are applied consistently across athletes:
-
Absolute Bands - Ensure all bands are the same for all athletes so you are comparing like for like. For example, absolute Velocity bands may be something similar to the following:
- Band 1: 0-0.2m/s
- Band 2: 0.2-2m/s
- Band 3: 2-4m/s
- Band 4: 4-5.5m/s
- Band 5: 5.5-7m/s
- Band 6: >7m/s
-
Relative Bands - although values are individualised ensure the bands are representing the same information. For example, relative Velocity Bands might be something like below:
- Band 1: 0 - Maximal Aerobic Speed (MAS)
- Band 2: MAS - 30% Anaerobic Speed Reserve (ASR)
- Band 3: >30% ASR - Maximum Sprint Speed
See: Bands and How to Set Absolute and Relative Velocity Bands
-
Absolute Bands - Ensure all bands are the same for all athletes so you are comparing like for like. For example, absolute Velocity bands may be something similar to the following:
-
If comparing data between Teams, ensure Team Settings are consistent across within accounts.
- Note, if you are working with a multi-sport institute sport specific differences might be relevant.
See: Team settings
- Note, if you are working with a multi-sport institute sport specific differences might be relevant.
- Consider using standardised naming convention for activities.
- For example, YYYYMMDD [SPORT] [TEAM] [ACTIVITY TYPE:MATCH/TRAINING] [AM/PM]
- For example, YYYYMMDD [SPORT] [TEAM] [ACTIVITY TYPE:MATCH/TRAINING] [AM/PM]
- Use of standardised period names
- Make use of the Period admin feature (OpenField Cloud > Settings > Period Admin) to input standardised drill names. This way every time this drill is performed it is named in exactly the same way.
See: Period Admin How to Add Standard Period Names - This makes it easier to use our Training Wizard tool in a prescriptive capacity.
See: Training wizard
- Make use of the Period admin feature (OpenField Cloud > Settings > Period Admin) to input standardised drill names. This way every time this drill is performed it is named in exactly the same way.
- Accurate editing of periods and rotations
- New Period: Shift + Left Click and Drag
- Benching: Shift + Ctrl + Left Click and Drag
See: Graphing Data, How to create edit and delete Periods and Benching within periods
- Tagging athlete participation on a period and activity level.
See: Participation Tags
- Tagging Activity types (Match Day, MD-1, MD-2 etc..)
See: Activity and period tagging
- Tagging extra information
- Tagging information like the result of the game or when injuries occurred will help you leverage greater insight from your data down the line.
See: Cloud tagging
- Tagging information like the result of the game or when injuries occurred will help you leverage greater insight from your data down the line.
- Flagging erroneous data
- Look out for velocity spikes and drop out in heart rate data.
See: Graphing Data and Flagging Data
- Look out for velocity spikes and drop out in heart rate data.
- Accurately classify athlete positions in activities.
- This will help with creating accurate positional averages.
See: How to Change Position History
- This will help with creating accurate positional averages.
- Where available add your analyst’s xml into activity as an annotation layer for added context.
See: Hudl SportsCode Data Import
- Delete duplicate or erroneous activities.
Best Practice for Good Data Hygiene
