Differences

This shows you the differences between two versions of the page.

--- visual3d:documentation:pipeline:event_commands:event_sequence_delete [2025/04/17 16:26] – [Command Parameters] wikisysop
+++ visual3d:documentation:pipeline:event_commands:event_sequence_delete [2025/04/28 19:05] (current) – wikisysop
@@ Line 1: / Line 1: @@
 ====== Event Sequence Delete ======
-=====Event_Sequence_Delete=====
+=====Overview=====
-/
+The `Event_Sequence_Delete` command **removes a previously defined event sequence** from the motion file.
-/
+  * Event sequences are often used to group event pairs (e.g., LHS to LTO) into meaningful motion phases. This command allows you to cleanly remove those sequences if no longer needed or if you’re regenerating them.
+  * Use cases include cleaning up a trial before re-defining new event sequences and removing incorrect or outdated gait cycle definitions.
+  * A **requirement** is that the event sequence to be deleted must already exist, and its name must match exactly.
+=====Pipeline Command=====
+The pipeline command is shown below as seen in the Visual3D application.
-====Overview====
-- The `Event_Sequence_Delete` command **removes a previously defined event sequence** from the motion file.
-- Event sequences are often used to group event pairs (e.g., LHS to LTO) into meaningful motion phases. This command allows you to cleanly remove those sequences if no longer needed or if you’re regenerating them.
-- Found under **Pipeline > Event Commands**, it's helpful when refining or resetting pipeline logic.
-- **Use cases:**
-  - Cleaning up a trial before re-defining new event sequences.
-  - Removing incorrect or outdated gait cycle definitions.
-- **Requirements:**
-  - The event sequence to be deleted must already exist, and its name must match exactly.
-====Pipeline Command====
 <code>
 Event_Sequence_Delete
@@ Line 22: / Line 17: @@
 </code>
-====Command Parameters====
+=====Command Parameters=====
+The following table shows the command parameters and descriptions.
 |**Parameter**             |**Description**|
 |**/EVENT_SEQUENCE_NAME=** | The name of the event sequence you want to delete (e.g., `LeftGaitCycle`). |
-====Dialog====
+=====Dialog=====
-The command can be edited in a text editor or in the dialog form. To edit in the dialog pop-up form, either click the **Edit** button in the pipeline workshop or double-click the command.
+Due to the simplicity of this command, there is no dialog box and it can be edited within the text editor.
-|[IMAGE of Event_Sequence_Delete dialog]|
+=====Examples=====
+The following example shows the use of the Event_Sequence_Delete command in the Visual3D application,
-- Provides a dropdown list of all event sequences in the file.
+====Example 1: Delete and Redefine Sequence=====
-- You must select or manually type the **exact name** of the sequence to delete.
-- There is **no undo**, so make sure this command appears at the right stage in the pipeline.
-====Examples====
+The functionality of this command is very straightforward. Simply type in the name of the event sequence desired to be deleted.
+In the following example, an event sequence named 'RightCycle' will be deleted and redefined afterwords.
-===Simple Example===
-Delete the gait cycle sequence called `LeftStride`:
-<code>
-Event_Sequence_Delete
-/EVENT_SEQUENCE_NAME=LeftStride
-;
-</code>
-===Complex Example===
-Use in a workflow where you are replacing event sequences:
 <code>
 Event_Sequence_Delete
@@ Line 54: / Line 44: @@
 Event_Define_Event_Sequence
 /EVENT_SEQUENCE_NAME=RightCycle
-/EVENT_SEQUENCE=RHS, RTO
+/EVENT_SEQUENCE=RHS+RTO
 /EXCLUDE_EVENTS=
 /INSIDE_OF_SEQUENCE=
@@ Line 67: / Line 57: @@
 ====Notes====
-- Deleting an event sequence **does not delete the events themselves**, only the sequence structure.
-- Useful during iterative workflows where event phases are updated repeatedly.
+  * Deleting an event sequence **does not delete the events themselves**, only the sequence structure.
-- Be cautious: if other commands depend on the sequence you remove, those commands may fail or behave unexpectedly.
+  * Useful during iterative workflows where event phases are updated repeatedly.