visual3d:documentation:pipeline:model_based_data_commands:compute_model_based_data
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:pipeline:model_based_data_commands:compute_model_based_data [2024/07/12 14:05] – created sgranger | visual3d:documentation:pipeline:model_based_data_commands:compute_model_based_data [2024/07/17 15:46] (current) – created sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| === Compute_Model_Based_Data === | === Compute_Model_Based_Data === | ||
| Line 27: | Line 27: | ||
| This command structure is the same regardless of whether the command is in the Pipeline or RECALC Pipeline. When this signal is created, the definition of the model based item is stored automatically in the RECALC pipeline. | This command structure is the same regardless of whether the command is in the Pipeline or RECALC Pipeline. When this signal is created, the definition of the model based item is stored automatically in the RECALC pipeline. | ||
| - | {{Compute_Model_Based_Data.jpg}} | + | {{:Compute_Model_Based_Data.jpg}} |
| For example, the Right Knee Angle signal could be represented as: | For example, the Right Knee Angle signal could be represented as: | ||
| - | {{RightKneeAngle2.jpg}} | + | {{:RightKneeAngle2.jpg}} |
| If the text representation of this signal is opened, the following information will be stored | If the text representation of this signal is opened, the following information will be stored | ||
| Line 59: | Line 59: | ||
| In other words, it appears that the dialog was created as follows: | In other words, it appears that the dialog was created as follows: | ||
| - | {{RightKneeAngle1.jpg}} | + | {{:RightKneeAngle1.jpg}} |
| This is because the lower level representations are stored with the standard Visual3D acronyms (e.g. those names that are used under the covers), whereas the interface to Visual3D uses the names that are mapped by the config files. | This is because the lower level representations are stored with the standard Visual3D acronyms (e.g. those names that are used under the covers), whereas the interface to Visual3D uses the names that are mapped by the config files. | ||
visual3d/documentation/pipeline/model_based_data_commands/compute_model_based_data.1720793106.txt.gz · Last modified: 2024/07/12 14:05 by sgranger