Inspect3D Pipeline: Difference between revisions

From Software Product Documentation
Jump to navigation Jump to search
mNo edit summary
 
(4 intermediate revisions by the same user not shown)
Line 3: Line 3:
|}
|}


=Introduction=
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
# Removing BAD events or tags that were created in the CMZ file by Inspect3D


Inspect3D can be used to run pipelines/update the CMZ files in your CMO Library by:
==Specify the Pipeline==
* Creating BAD events or tags to indicate traces that were excluded in Inspect3D
* Update force assignments based on excluded traces
* Creating events or tags to indicate traces that are included in Inspect3D
* Run external pipeline scripts on the active data
* Remove BAD events or tags that were created in the CMZ file by Inspect3D


==Data to Run Pipeline On==
===Excluded Data===


The following options will run the pipeline on:
There are three methods for adding an event in order to exclude signals:
# <b>All Queried Data:</b> Every workspace that in the root directory
# <b>All Plotted Data:</b> Every workspace/trial that is plotted
## <b>All data in Selected Queries:</b> All workspaces in selected groups
## <b>Only Plotted Data:</b> Selected workspaces in selected groups
# <b>Active Plot Data:</b> 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>Only Plotted Data:</b> Selected workspaces in selected groups
# <b>Highlighted Data:</b> Highlighted sequences
 
=Pipeline Options=
 
==Excluded Data==
 
<b>Add Event to Exclude Signals:</b>
* 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 20:
** 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


<b>Add Tag to Exclude Trial:</b>
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


<b>Update Force Assignments</b>
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===
 
For all data that is included (i.e. not Excluded), create a tag or event during that cycle.
 
==Run External Scripts==
 
Run a 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.
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).


==Remove Exclusions==
===Remove Exclusions===


Remove exclusions will remove events that were created to exclude from group definitions (ex. BAD, or Bad_LAnkleAngle_X). You can also remove Tags.
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]]

Latest revision as of 18:57, 23 August 2023

Inspect3D can be used to run pipelines and update the CMZ files in your CMO Library by:

  1. Creating BAD events or tags to indicate traces that were excluded in Inspect3D
  2. Updating force assignments based on excluded traces
  3. Creating events or tags to indicate traces that are included in Inspect3D
  4. Removing BAD events or tags that were created in the CMZ file by Inspect3D

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).

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.

Retrieved from ""