sift:tutorials:clean_your_data
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sift:tutorials:clean_your_data [2024/07/17 15:22] – sgranger | sift: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:// | ||
==== Data ==== | ==== Data ==== | ||
Line 11: | Line 12: | ||
==== Loading the library ==== | ==== Loading the library ==== | ||
- | {{: | + | {{ : |
- | 1. Click {{: | + | 1. Click {{: |
- | 2. Click {{: | + | 2. Click {{: |
- | 3. Click {{: | + | 3. Click {{: |
This step selects the path to the data you are using. If you intend to modify the data, e.g., by correcting invalid assignments, | This step selects the path to the data you are using. If you intend to modify the data, e.g., by correcting invalid assignments, | ||
Line 26: | Line 27: | ||
==== Defining queries and calculating groups ==== | ==== Defining queries and calculating groups ==== | ||
- | 1. Navigate to the [[Sift: | + | 1. Navigate to the [[Sift: |
- | 2. To create a new query definition, click the {{: | + | 2. To create a new query definition, click the {{: |
2.1. Type GRF in the **Query Name** text box in top-right and click **Save**. | 2.1. Type GRF in the **Query Name** text box in top-right and click **Save**. | ||
- | {{: | + | {{: |
- | 3. While the GRF query is selected, click the {{: | + | 3. While the GRF query is selected, click the {{: |
3.1. Type R_GRF in the **Condition Name** text box in the top-right. | 3.1. Type R_GRF in the **Condition Name** text box in the top-right. | ||
Line 42: | Line 43: | ||
3.2.1. **Signals**: | 3.2.1. **Signals**: | ||
- | {{: | + | {{: |
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. | ||
- | {{: | + | {{: |
3.2.3. **Refinements**: | 3.2.3. **Refinements**: | ||
- | {{: | + | {{: |
- | 3.3. Click {{: | + | 3.3. Click {{: |
4. For this tutorial, define a second condition within the same group to account for the left side. This can be done by modifying the existing sub-group: | 4. For this tutorial, define a second condition within the same group to account for the left side. This can be done by modifying the existing sub-group: | ||
- | 4.1. While the GRF group is selected, click the {{: | + | 4.1. While the GRF group is selected, click the {{: |
4.1.1. In the Signals tab, change the NAME to L_GRF and leave the other parameters as they are. | 4.1.1. In the Signals tab, change the NAME to L_GRF and leave the other parameters as they are. | ||
Line 64: | Line 65: | ||
4.1.3. Leave the Refinements tab as it was. | 4.1.3. Leave the Refinements tab as it was. | ||
- | 4.2. Click {{: | + | 4.2. Click {{: |
- | {{: | + | {{: |
You should now see one query (GRF) in the **Queries** list and two conditions (R_GRF and L_GRF) in the **Conditions** list. At this point in the tutorial these definitions have been created but they have not been applied to the signals in the loaded library. To do this, click on **Calculate All Queries** (or **Calculate Selected Queries**, since there is only one group in this tutorial). | You should now see one query (GRF) in the **Queries** list and two conditions (R_GRF and L_GRF) in the **Conditions** list. At this point in the tutorial these definitions have been created but they have not been applied to the signals in the loaded library. To do this, click on **Calculate All Queries** (or **Calculate Selected Queries**, since there is only one group in this tutorial). | ||
Line 87: | Line 88: | ||
Your graph should now resemble the image below. | Your graph should now resemble the image below. | ||
- | {{: | + | {{: |
2. Use your cursor to select only lines on the graph that you wish to inspect. Click on single traces in order to examine individual curves without the other curves ' | 2. Use your cursor to select only lines on the graph that you wish to inspect. Click on single traces in order to examine individual curves without the other curves ' | ||
- | {{: | + | {{: |
Line 108: | Line 109: | ||
3.1 When traces are excluded, two notable differences should appear in the Queried Data subwindow. First, the previously selected, but now excluded data should not be visible on the graph. Second, the **Workspaces** widget will indicate when traces have been excluded. Specifically, | 3.1 When traces are excluded, two notable differences should appear in the Queried Data subwindow. First, the previously selected, but now excluded data should not be visible on the graph. Second, the **Workspaces** widget will indicate when traces have been excluded. Specifically, | ||
- | {{: | + | {{: |
4. If you want to visualize the data you have excluded alongside the remaining data, go to the [[Sift: | 4. If you want to visualize the data you have excluded alongside the remaining data, go to the [[Sift: | ||
- | {{: | + | {{: |
Line 119: | Line 120: | ||
5.1 Select the traces of interest by clicking and dragging on the plot. | 5.1 Select the traces of interest by clicking and dragging on the plot. | ||
- | 5.2 Click the {{: | + | 5.2 Click the {{: |
5.3 The Show [[Sift: | 5.3 The Show [[Sift: | ||
Line 125: | Line 126: | ||
6. Once all of the desired exclusions have been made, the original data is ready to be updated. | 6. Once all of the desired exclusions have been made, the original data is ready to be updated. | ||
- | {{: | + | {{: |
==== Updating the original data ==== | ==== Updating the original data ==== | ||
- | 1. | + | {{: |
- | {{:UpdateCMZActive.png}} | + | |
+ | 1. Now that the incorrect force assignments have been identified in our data set, it is possible to update the original [[Visual3D: | ||
- | Now that the incorrect force assignments have been identified in our data set, it is possible to update the original [[Visual3D: | ||
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: | 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: | ||
sift/tutorials/clean_your_data.1721229739.txt.gz · Last modified: 2024/07/17 15:22 by sgranger