HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » event_commands » Event TPR File
visual3d:documentation:pipeline:event_commands:event_tpr_file

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:documentation:pipeline:event_commands:event_tpr_file [2025/04/28 18:31] – wikisysopvisual3d:documentation:pipeline:event_commands:event_tpr_file [2025/04/28 18:43] (current) – wikisysop
Line 1: Line 1:
 =====Event TPR File===== =====Event TPR File=====
  
-====Overview====+=====Overview=====
 The Event_TPR_File command is used to match a pre-saved signal pattern to a signal in the   The Event_TPR_File command is used to match a pre-saved signal pattern to a signal in the  
 current selected trial. When the shape of the signal matches the pattern, an event is created at that frame. current selected trial. When the shape of the signal matches the pattern, an event is created at that frame.
Line 7: Line 7:
   * The signal that the pattern is being matched to must exist in the trial.   * The signal that the pattern is being matched to must exist in the trial.
  
-====Pipeline Command====+=====Pipeline Command=====
 The command below is as seen on the Visual3D application, it has many parameters as there are many options to manipulate this command: The command below is as seen on the Visual3D application, it has many parameters as there are many options to manipulate this command:
  
Line 24: Line 24:
 </code> </code>
  
-====Command Parameters====+=====Command Parameters=====
 The following table shows the command parameters and descriptions: The following table shows the command parameters and descriptions:
 |**Parameter**        |**Description**| |**Parameter**        |**Description**|
Line 37: Line 37:
 |**!/TOLERANCE=20.0** | The matching threshold. Lower values = stricter match (e.g., 10.0 = tight match). | |**!/TOLERANCE=20.0** | The matching threshold. Lower values = stricter match (e.g., 10.0 = tight match). |
  
-====Dialog====+=====Dialog=====
 The dialog for this command simplifies pattern-based event creation: The dialog for this command simplifies pattern-based event creation:
  
Line 48: Line 48:
   * **Tolerance**: Controls how strictly the signal must match the pattern. Smaller values mean tighter matching.   * **Tolerance**: Controls how strictly the signal must match the pattern. Smaller values mean tighter matching.
  
-====Examples====+=====Examples=====
 The following example will go through the use of the Event_TPR_File command within the Visual3D application. The following example will go through the use of the Event_TPR_File command within the Visual3D application.
  
-===Example: Assigning Events to Event-less Trial based on TPR===+====Example 1: Assigning Events to Event-less Trial based on TPR====
  
 This command is not as intuitive for use as the Event_TPR_Signal when it comes to performing TPR on and placing events on specified signals. This command is not as intuitive for use as the Event_TPR_Signal when it comes to performing TPR on and placing events on specified signals.
-  * It is more useful for assigning events to the whole file if you have already generated a .tps file (target pattern signal) or you could also simply use a .c3d like Event_TPR_Signal. +  * It is more useful for assigning events to the whole file if you have already generated a .tps file (target pattern signal) or you could also simply use events from another .c3d, like Event_TPR_Signal. 
-  * An important thing to note is that this command is highly dependent on what is saved in the TPR file - which must be done properly using **Event_TPR_Signal** or **Event_Save_TPR_Signal**+  * An important thing to note is that this command is dependent on what is saved in the TPR file - which must be done properly using **Event_TPR_Signal** or **Event_Save_TPR_Signal**
  
 The following steps can be taken for this example: The following steps can be taken for this example:
Line 82: Line 82:
  
 ---- ----
- 
-====Notes==== 
- 
  
  
visual3d/documentation/pipeline/event_commands/event_tpr_file.1745865090.txt.gz · Last modified: 2025/04/28 18:31 by wikisysop