visual3d:documentation:pipeline:event_commands:event_delete
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:pipeline:event_commands:event_delete [2024/07/16 19:27] – created sgranger | visual3d:documentation:pipeline:event_commands:event_delete [2025/02/28 19:00] (current) – [Examples] wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Under Construction... | + | ===== Event Delete ===== |
+ | |||
+ | ==== Overview ==== | ||
+ | The **Event_Delete** command is used to remove an existing event from a dataset based on specified conditions. This command allows users to delete all instances of an event, target specific occurrences, | ||
+ | |||
+ | This command is particularly useful for refining datasets by removing redundant, incorrectly placed, or unnecessary events, ensuring accuracy i n biomechanical event analysis. | ||
+ | |||
+ | The functionality of this command can also be achieved by right-clicking on an event in the data tree, **Delete Event** us an option on the context menu. The interactive selection from the data tree can be shown here: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ==== Pipeline Command ==== | ||
+ | The command below is as seen in the Visual3D application. | ||
+ | |||
+ | < | ||
+ | Event_Delete | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! /TIME= | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | ==== Command Parameters ==== | ||
+ | The following table shows the command parameters and descriptions: | ||
+ | |||
+ | |**Parameter** | ||
+ | |**/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |**!/ | ||
+ | |||
+ | ==== Dialog ==== | ||
+ | Due to the simplicity of this command and the interactive selection option, this command does not display a dialog box when clicked, instead parameters can be edited within the text editor. | ||
+ | |||
+ | ==== Examples ==== | ||
+ | The following examples will go through the use of the **Event_Delete** command in the Visual3D application. | ||
+ | |||
+ | === Example 1: Deleting All Instances of an Event === | ||
+ | The first example shows the process of removing the " | ||
+ | |||
+ | After running the Automatic_Gait_Events command as shown below, the EVENT_LABEL folder will be created housing all of the events: | ||
+ | |||
+ | < | ||
+ | Automatic_Gait_Events | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | Then, we can use the **For_Each** command to iterate through each of the events we want to delete, and the **Event_Delete** command to actually delete. | ||
+ | |||
+ | < | ||
+ | For_Each | ||
+ | / | ||
+ | ! / | ||
+ | / | ||
+ | ; | ||
+ | |||
+ | Event_Delete | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! / | ||
+ | ! /TIME= | ||
+ | ; | ||
+ | |||
+ | End_For_Each | ||
+ | / | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | {{: | ||
+ | |||
+ | === Example 2: Deleting a Specific Instance of an Event === | ||
+ | In this example, imagine analyzing a gait cycle where a participant takes two steps with their right foot and then two steps with their left foot. | ||
+ | |||
+ | If primarily interested in analyzing the first step taken with each foot, in this situation, only the second instance of toe-off for each foot should be deleted. | ||
+ | |||
+ | < | ||
+ | Event_Delete | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | / | ||
+ | ! /TIME= | ||
+ | ; | ||
+ | |||
+ | Event_Delete | ||
+ | / | ||
+ | ! / | ||
+ | ! / | ||
+ | / | ||
+ | ! /TIME= | ||
+ | ; | ||
+ | </ | ||
+ | |||
+ | |||
visual3d/documentation/pipeline/event_commands/event_delete.1721158069.txt.gz · Last modified: 2024/07/16 19:27 by sgranger