Inspect3D Pipeline: Difference between revisions
m (Edited for formatting.) |
|||
Line 3: | Line 3: | ||
|} | |} | ||
Inspect3D can be used to run pipelines and update the CMZ files in your CMO Library by: | |||
# Creating BAD events or tags to indicate traces that were excluded in Inspect3D | |||
# Updating force assignments based on excluded traces | |||
# Creating events or tags to indicate traces that are included in Inspect3D | |||
# Running external pipeline scripts on the active data | |||
# Removing BAD events or tags that were created in the CMZ file by Inspect3D | |||
Running a pipeline on data consists of two steps: first, selecting the data; and second, specifying the pipeline. | |||
== | ==Select the data== | ||
There are four options for specifying which data the pipeline should be run on: | |||
# <b>All Queried Data:</b> | # <b>All Queried Data:</b> The pipeline will run on every workspace that in the root directory | ||
# <b>All Plotted Data:</b> | # <b>All Plotted Data:</b> The pipeline will run on every workspace and trial that is currently plotted | ||
## <b>All data in Selected Queries:</b> The pipeline will run on the selected groups' workspaces | |||
## <b>Only Plotted Data:</b> Only the plotted workspaces in the selected groups | |||
# <b>Active Plot Data:</b> The pipeline will run on all the workspaces that are plotted in the active plot (indicated by gray bounding box) | |||
## <b>All data in Selected Queries:</b> All workspaces in selected groups | ## <b>All data in Selected Queries:</b> All workspaces in selected groups | ||
## <b>Only Plotted Data:</b> | ## <b>Only Plotted Data:</b> Only the plotted workspaces in selected groups | ||
# <b>Highlighted Data:</b> The pipeline will run on any data that is highlighted within the plots. | |||
# <b>Highlighted Data:</b> | |||
=Pipeline | ==Specify the Pipeline== | ||
==Excluded Data== | ===Excluded Data=== | ||
There are three methods for adding an event in order to exclude signals: | |||
* Only exclude individual traces | * Only exclude individual traces | ||
** This means an event Bad_LAnkleAngle_X will be created during the bad cycle and the group definition of AnkleAngle_X will now exclude any sequences containing Bad_LAnkleAngle_X | ** This means an event Bad_LAnkleAngle_X will be created during the bad cycle and the group definition of AnkleAngle_X will now exclude any sequences containing Bad_LAnkleAngle_X | ||
Line 35: | Line 35: | ||
** Creates a general event "BAD" and all currently loaded group definitions will now exclude any sequences containing BAD | ** Creates a general event "BAD" and all currently loaded group definitions will now exclude any sequences containing BAD | ||
It is also possible to add tags in order to exclude specific trials: | |||
* An trial that contains excluded data will be tagged with the specified tag name | * An trial that contains excluded data will be tagged with the specified tag name | ||
Finally, it is possible to update force assignments during specified cycles: | |||
* For any groups that contain the specified text (ex. Force,GRF) delete force assignments during those cycles | * For any groups that contain the specified text (ex. Force,GRF) delete force assignments during those cycles | ||
==Included Data== | ===Included Data=== | ||
Besides tagging data to be excluded, it is also possible to create a tag or event for all data that is included (i.e. not excluded). | |||
==Run External Scripts== | ===Run External Scripts=== | ||
Run a pipeline script (v3s file) that was created manually/in Visual3D. | Run a [[Pipeline_Commands_Reference|pipeline script] (v3s file) that was created manually/in Visual3D. | ||
<b>NOTE:</b> Within the script, there is no need to loop over workspaces or trials since Inspect3D will do this for you. | <b>NOTE:</b> Within the script, there is no need to loop over workspaces or trials since Inspect3D will do this for you. | ||
==Remove Exclusions== | ===Remove Exclusions=== | ||
If you have created events or tags to exclude data, it is always possible to remove these events or tags from your CMZ file. | |||
[[Category: Inspect3D]] | [[Category: Inspect3D]] |
Revision as of 17:15, 31 October 2022
Inspect3D can be used to run pipelines and update the CMZ files in your CMO Library by:
- Creating BAD events or tags to indicate traces that were excluded in Inspect3D
- Updating force assignments based on excluded traces
- Creating events or tags to indicate traces that are included in Inspect3D
- Running external pipeline scripts on the active data
- Removing BAD events or tags that were created in the CMZ file by Inspect3D
Running a pipeline on data consists of two steps: first, selecting the data; and second, specifying the pipeline.
Select the data
There are four options for specifying which data the pipeline should be run on:
- All Queried Data: The pipeline will run on every workspace that in the root directory
- All Plotted Data: The pipeline will run on every workspace and trial that is currently plotted
- All data in Selected Queries: The pipeline will run on the selected groups' workspaces
- Only Plotted Data: Only the plotted workspaces in the selected groups
- Active Plot Data: The pipeline will run on all the workspaces that are plotted in the active plot (indicated by gray bounding box)
- All data in Selected Queries: All workspaces in selected groups
- Only Plotted Data: Only the plotted workspaces in selected groups
- Highlighted Data: The pipeline will run on any data that is highlighted within the plots.
Specify the Pipeline
Excluded Data
There are three methods for adding an event in order to exclude signals:
- Only exclude individual traces
- This means an event Bad_LAnkleAngle_X will be created during the bad cycle and the group definition of AnkleAngle_X will now exclude any sequences containing Bad_LAnkleAngle_X
- Exclude all traces for this side when any data is excluded
- Exclude all traces when data is excluded (regardless of side)
- Creates a general event "BAD" and all currently loaded group definitions will now exclude any sequences containing BAD
It is also possible to add tags in order to exclude specific trials:
- An trial that contains excluded data will be tagged with the specified tag name
Finally, it is possible to update force assignments during specified cycles:
- For any groups that contain the specified text (ex. Force,GRF) delete force assignments during those cycles
Included Data
Besides tagging data to be excluded, it is also possible to create a tag or event for all data that is included (i.e. not excluded).
Run External Scripts
Run a [[Pipeline_Commands_Reference|pipeline script] (v3s file) that was created manually/in Visual3D.
NOTE: Within the script, there is no need to loop over workspaces or trials since Inspect3D will do this for you.
Remove Exclusions
If you have created events or tags to exclude data, it is always possible to remove these events or tags from your CMZ file.