User Tools

Site Tools


visual3d:documentation:pipeline:result_types

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:result_types [2024/06/19 12:49] sgrangervisual3d:documentation:pipeline:result_types [2024/07/17 15:45] (current) – created sgranger
Line 1: Line 1:
 +====== Result Types ======
 +
 <code> <code>
-   /result_types+   /Result_Types
 </code> </code>
  
Line 8: Line 10:
  
 <code> <code>
-   /result_types +   /RESULT_TYPES 
 </code> </code>
  
-the type of the result signal+The type of the result signal
  
-for example:+For example:
  
 <code> <code>
-   event_label  +   EVENT_LABEL  
-   analog  +   ANALOG  
-   target  +   TARGET  
-   parameters  +   PARAMETERS  
-   force  +   FORCE  
-   cofp  +   COFP  
-   freemoment  +   FREEMOMENT  
-   metric  +   METRIC  
-   kinetic_kinematic  +   KINETIC_KINEMATIC  
-   link_model_based  +   LINK_MODEL_BASED  
-   derived  +   DERIVED  
-   p2d +   P2D 
 </code> </code>
  
-note that very most commands the [[visual3d:documentation:pipeline:general_information:signal_types|signal_types]] determines the allowable result_types.+Note that very most commands the [[Visual3D:Documentation:Pipeline:General_Information:Signal_Types|Signal_Types]] determines the allowable Result_Types.
  
-for example, a target cannot usually be turned into an analog+For example, a TARGET cannot usually be turned into an ANALOG
  
  
  
visual3d/documentation/pipeline/result_types.1718801371.txt.gz · Last modified: 2024/06/19 12:49 by sgranger