sift:application:update_cmzs_dialog
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sift:application:update_cmzs_dialog [2024/07/17 15:10] – sgranger | sift:application:update_cmzs_dialog [2024/11/15 16:49] (current) – [Remove Exclusions] wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | The updateCMZs Dialog {{: | + | The updateCMZs Dialog {{: |
- | - Creating | + | - Create |
- | - Updating | + | - Update |
- | - Creating | + | - Create |
- | - Removing BAD events or tags that were created | + | - Remove |
{{: | {{: | ||
- | ==== UpdateCMZs Dialog | + | ---- |
+ | ===== Excluded Traces ===== | ||
- | === Excluded Data === | + | {{ : |
- | {{: | + | Adding an Event to Exclude Signals will alter the workspace files to include the specified event during the bad cycle. |
+ | * This will also update the query definitions to exclude any trace containing the specified " | ||
There are three methods for adding an event in order to exclude signals: | 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, such as AnkleAngle_BAD will be created during the bad cycle and the group definition of AnkleAngle will now exclude any sequences containing AnkleAngle_BAD | * This means an event, such as AnkleAngle_BAD will be created during the bad cycle and the group definition of AnkleAngle will now exclude any sequences containing AnkleAngle_BAD | ||
* Exclude all traces for this side when any data is excluded | * Exclude all traces for this side when any data is excluded | ||
+ | * This means an event will be created for ALL queried signals, during the specified cycle, on the SAME SIDE of the body (R/L) | ||
* Exclude all traces when data is excluded (regardless of side) | * Exclude all traces when data is excluded (regardless of side) | ||
- | * Creates a general | + | * This means an event will be created for ALL queried signals, during the specified cycle, regardless of side |
It is also possible to add tags in order to exclude specific trials: | It is also possible to add tags in order to exclude specific trials: | ||
- | |||
* A trial that contains excluded data will be tagged with the specified tag name | * A trial that contains excluded data will be tagged with the specified tag name | ||
- | \\ | + | ---- |
+ | ===== Update Force Assignment ===== | ||
- | === Update Force Assignment === | + | {{ : |
It is possible to update force assignments during specified cycles: | 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 | + | * For any groups that contain the specified text (ex. Force,GRF), delete force assignments during |
- | {{: | + | ---- |
+ | ===== 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). | + | 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 | ||
- | If you have created events or tags to exclude data, it is always possible to remove these events or tags from your CMZ file. | + | {{ : |
- | {{: | + | If you want to remove events or tags from the loaded library, including those you have created to exclude data, it is always possible to remove them by selecting the tags or events. |
sift/application/update_cmzs_dialog.1721229006.txt.gz · Last modified: 2024/07/17 15:10 by sgranger