HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » other » inspect3d » tutorials » Metadata
other:inspect3d:tutorials:metadata

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
other:inspect3d:tutorials:metadata [2025/01/17 15:02] – wikisysopother:inspect3d:tutorials:metadata [2025/01/17 15:14] (current) – wikisysop
Line 45: Line 45:
 ==== Refining Hitting Data ==== ==== Refining Hitting Data ====
  
-From here on it is assumed that you either have: a) built CMZs from scratch using the hitting data set, or b) downloaded the pre-made CMZs linked above.+From here on it is assumed that you either have:  
 +   * a) built CMZs from scratch using the hitting data set, or  
 +   * b) downloaded the pre-made CMZs linked above.
  
 The zip file openbiomechanics-main has a metadata file for the hitting data set which you can view at your convenience. This metadata file has a number of categories including player age, bat weight, hitting side etc. The zip file openbiomechanics-main has a metadata file for the hitting data set which you can view at your convenience. This metadata file has a number of categories including player age, bat weight, hitting side etc.
Line 53: Line 55:
 We start by loading library with the hitting data set, navigating to the Query Builder dialog, and opening the Auto-Populate dialog. Ensure that "Baseball" is checked. Find the "Refine using signal" checkbox and click "Add". Then you can enter your query refinements. We start by loading library with the hitting data set, navigating to the Query Builder dialog, and opening the Auto-Populate dialog. Ensure that "Baseball" is checked. Find the "Refine using signal" checkbox and click "Add". Then you can enter your query refinements.
  
-{{:autobuilder_hit.png}}+{{ :autobuilder_hit.png?700 }}
  
 When refining queries it can be helpful to have the metadata file open, so that you can see the values it contains. Note that in this case, accessing athlete_age has been set as a global metric, and you will not be able to find the meta folder unless Global Value is checked. When refining queries it can be helpful to have the metadata file open, so that you can see the values it contains. Note that in this case, accessing athlete_age has been set as a global metric, and you will not be able to find the meta folder unless Global Value is checked.
Line 67: Line 69:
 In the example below, we can see that there are four headers (static_model, dynamic_file, walking_speed and subject_mass). In the example below, we can see that there are four headers (static_model, dynamic_file, walking_speed and subject_mass).
  
-{{:metattut1.png}}+{{ :metattut1.png?700 }}
  
 Here you can edit the description fields and subject specific fields. After you are satisfied with the fields, click "Apply" to build CMZs and load the library. Here you can edit the description fields and subject specific fields. After you are satisfied with the fields, click "Apply" to build CMZs and load the library.
Line 79: Line 81:
 If you navigate from the Query Builder dialog to the Auto-Populate menu, there is an option called "Refine Using Signal". Click to enable this checkbox, and then press "Add". In the image below, I have loaded a pre-built auto-settings file, but also have the signal refinement dialog open. If you navigate from the Query Builder dialog to the Auto-Populate menu, there is an option called "Refine Using Signal". Click to enable this checkbox, and then press "Add". In the image below, I have loaded a pre-built auto-settings file, but also have the signal refinement dialog open.
  
-{{:qbuilder.png}}+{{ :qbuilder.png?700 }}
  
 Since I want to refine my data by walking speed in this example, I name the refinement "3.0", choose the data under METRIC>meta>walking_speed>X and indicate that the value must be "Equal to" 3.0. I can then save my refinements as an .xml file which can be loaded at any time if I want to re-query my library. Since I want to refine my data by walking speed in this example, I name the refinement "3.0", choose the data under METRIC>meta>walking_speed>X and indicate that the value must be "Equal to" 3.0. I can then save my refinements as an .xml file which can be loaded at any time if I want to re-query my library.
Line 85: Line 87:
 Press save and then create and close the auto-populate window. Back in the query builder you should see queries that reflect the refinements you just made. Press save and then create and close the auto-populate window. Back in the query builder you should see queries that reflect the refinements you just made.
  
-{{:autopopmenu.png}}+{{ :autopopmenu.png?700 }}
  
 ==== Visualizing Refined Queries ==== ==== Visualizing Refined Queries ====
Line 93: Line 95:
 We can now used the refined queries to visualize different relationships between speed and subject kinematics, as seen in the example below: We can now used the refined queries to visualize different relationships between speed and subject kinematics, as seen in the example below:
  
-{{:asisy.jpg}}+{{ :asisy.jpg?700 }}
  
 In this example we can see the how the trajectory for the ASIS markers changes as walking speed changes for Subject 1. In this example we can see the how the trajectory for the ASIS markers changes as walking speed changes for Subject 1.
other/inspect3d/tutorials/metadata.1737126164.txt.gz · Last modified: 2025/01/17 15:02 by wikisysop