HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » sift » tutorials » Clean your Data
sift:tutorials:clean_your_data

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
sift:tutorials:clean_your_data [2024/07/26 14:57] – sgrangersift:tutorials:clean_your_data [2024/11/28 19:13] (current) – [Clean your Data] wikisysop
Line 1: Line 1:
 ====== Clean your Data ====== ====== Clean your Data ======
  
-This tutorial will show you how to use Sift as a data cleaning, or quality assurance, tool. You will learn how to check for and correct faulty force assignments from all files at once, thereby removing any artifacts from the data. This is particularly useful for lab managers (or supervisors) who may not be familiar with the raw data, or collaborators that were not involved in the collection process.+This tutorial will show you how to use Sift as a data cleaning, or quality assurance, tool. You will learn how to check for and correct faulty force assignments from all files at once. This is particularly useful for lab managers (or supervisors) who may not be familiar with the raw data, or collaborators that were not involved in the collection process.
  
 +If you prefer, a video tutorial is available outlining the same process. It is available at this link: [[https://youtu.be/zgjnGTxhjEc?feature=shared|Sift Tutorial Video 2: Cleaning Data]]
 ==== Data ==== ==== Data ====
  
Line 26: Line 27:
 ==== Defining queries and calculating groups ==== ==== Defining queries and calculating groups ====
  
-1. Navigate to the [[Sift:Application:Explore_Page|Explore Page]] and click on the {{:sift_query_builder.png}} **Query Builder** icon to open the [[Sift:Application:Query_Builder_Dialog|Query Builder dialog]].+1. Navigate to the [[Sift:Application:Explore_Page|Explore Page]] and click on the {{:sift_query_builder.png?20}} **Query Builder** icon to open the [[Sift:Application:Query_Builder_Dialog|Query Builder dialog]].
  
 2. To create a new query definition, click the {{:sift_action_add.png?20}} addition button in the empty **Queries** list. 2. To create a new query definition, click the {{:sift_action_add.png?20}} addition button in the empty **Queries** list.
Line 42: Line 43:
 3.2.1. **Signals**: This tab allows the user to select specific signals according to their names in the [[Visual3D:Documentation:Visual3D_Signal_Types:Data_Tree_Summary_|Visual3D Data Tree]]. For this tutorial, select the signal: TYPE - LINK_MODEL_BASED, FOLDER - ORIGINAL, NAME - R_GRF, and COMPONENT - Z. 3.2.1. **Signals**: This tab allows the user to select specific signals according to their names in the [[Visual3D:Documentation:Visual3D_Signal_Types:Data_Tree_Summary_|Visual3D Data Tree]]. For this tutorial, select the signal: TYPE - LINK_MODEL_BASED, FOLDER - ORIGINAL, NAME - R_GRF, and COMPONENT - Z.
  
-{{ :ConditionCleanTut.png?400}}+{{:ConditionCleanTut.png?400}}
  
 3.2.2. **Events**: This tab allows the user to specify the desired event sequence to extract data from. For instance, the right gait cycle could be extracted using the event sequences RON, ROFF or RHS, RHS. For this tutorial select the RON and ROFF events and leave the default normalization values of 101 for the number of points and cubic for the spline type. 3.2.2. **Events**: This tab allows the user to specify the desired event sequence to extract data from. For instance, the right gait cycle could be extracted using the event sequences RON, ROFF or RHS, RHS. For this tutorial select the RON and ROFF events and leave the default normalization values of 101 for the number of points and cubic for the spline type.
  
-{{ :ConditionsEventsCleanTut.png?400}}+{{:ConditionsEventsCleanTut.png?400}}
  
 3.2.3. **Refinements**: This tab allows the user to refine their selected signal using two separate and distinct methods: according to the signals contained within the [[Visual3D:Documentation:Definitions:File_Formats:CMO_Format|CMO files]], or according to Tags. For this tutorial, Refine using tags by leaving the **Use AND Logic** checkbox unchecked and selecting the SLOW, NORMAL, and FAST tags. 3.2.3. **Refinements**: This tab allows the user to refine their selected signal using two separate and distinct methods: according to the signals contained within the [[Visual3D:Documentation:Definitions:File_Formats:CMO_Format|CMO files]], or according to Tags. For this tutorial, Refine using tags by leaving the **Use AND Logic** checkbox unchecked and selecting the SLOW, NORMAL, and FAST tags.
  
-{{ :RefinementsCleanTut.png?400}}+{{:RefinementsCleanTut.png?400}}
  
 3.3. Click {{:sift_apply.png?20}} **Save** to create the condition. 3.3. Click {{:sift_apply.png?20}} **Save** to create the condition.
Line 130: Line 131:
 ==== Updating the original data ==== ==== Updating the original data ====
  
-1. +{{:UpdateCMZActive.png?400}} 
-{{ :UpdateCMZActive.png?400}}+ 
 +1. Now that the incorrect force assignments have been identified in our data set, it is possible to update the original [[Visual3D:Documentation:Definitions:CMO_Library_|CMZ]] data by clicking the {{:sift_update_cmz.png?20}} **Update CMZ Files** item in the application's tool bar to open the [[Sift:Application:Update_CMZs_Dialog|Update CMZ Dialog]]. This opens a dialog that provides different options for processing excluded data.
  
-Now that the incorrect force assignments have been identified in our data set, it is possible to update the original [[Visual3D:Documentation:Definitions:CMO_Library_|CMZ]] data by clicking the {{:sift_update_cmz.png?20}} **Update CMZ Files** item in the application's tool bar to open the [[Sift:Application:Update_CMZs_Dialog|Update CMZ Dialog]]. This opens a dialog that provides different options for processing excluded data. 
 2. The **Excluded Traces** options allow the user to add a BAD event to the excluded traces. This option is helpful if the intention is to [[Visual3D:Documentation:Definitions:Tag|tag]] the bad data, re-open the original data, and make manual corrections one trace at a time. 2. The **Excluded Traces** options allow the user to add a BAD event to the excluded traces. This option is helpful if the intention is to [[Visual3D:Documentation:Definitions:Tag|tag]] the bad data, re-open the original data, and make manual corrections one trace at a time.
  
sift/tutorials/clean_your_data.1722005839.txt.gz · Last modified: 2024/07/26 14:57 by sgranger