visual3d:documentation:pipeline:signal_commands:signal_management_commands
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| visual3d:documentation:pipeline:signal_commands:signal_management_commands [2024/06/14 17:30] – created sgranger | visual3d:documentation:pipeline:signal_commands:signal_management_commands [2024/07/17 15:46] (current) – created sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Contents | + | ====== |
| + | |||
| + | ==== Contents | ||
| Line 15: | Line 17: | ||
| - | ===== Signal Management | + | ==== Signal Management ==== |
| - | ==== Global_Normalized_Signal_Mean | + | === Global_Normalized_Signal_Mean === |
| Time normalize a signal (in this case Knee Flexion Angle) between events (RHS to RHS) for Right Knee angles and (LHS to LHS) for Left Knee angles, and compute a GLOBAL mean and Standard Deviation. Note: the Global_Normalized_Signal_Mean command only works on one component at at time for each signal. (You must select either Y, Y or Z as the SIGNAL_COMPONENTS.) | Time normalize a signal (in this case Knee Flexion Angle) between events (RHS to RHS) for Right Knee angles and (LHS to LHS) for Left Knee angles, and compute a GLOBAL mean and Standard Deviation. Note: the Global_Normalized_Signal_Mean command only works on one component at at time for each signal. (You must select either Y, Y or Z as the SIGNAL_COMPONENTS.) | ||
| Line 23: | Line 25: | ||
| First add the Global_Normalized_Signal_Mean command to the pipeline. Double click on the command to launch the dialog. | First add the Global_Normalized_Signal_Mean command to the pipeline. Double click on the command to launch the dialog. | ||
| - | [[File: | + | {{:GMSM_1.jpg}} |
| select the RKNEE_ANGLE Signal and the event sequence (e.g RHS to RHS) and select **Add A New Signal** | select the RKNEE_ANGLE Signal and the event sequence (e.g RHS to RHS) and select **Add A New Signal** | ||
| - | [[File: | + | {{:GNSM_2.jpg}} |
| select the LKNEE_ANGLE Signal and the event sequence (e.g LHS to LHS) and select **Add A New Signal** | select the LKNEE_ANGLE Signal and the event sequence (e.g LHS to LHS) and select **Add A New Signal** | ||
| - | [[File: | + | {{:GNSM_3.jpg}} |
| - | Enter the **P2D Result Signal Name** and click **Create Standard Deviation** Button | + | Enter the **P2D Result Signal Name** and click **Create Standard Deviation** Button {{:GNSM_4.jpg}} |
| When you select **OK** the text representation of the command should be as follows: | When you select **OK** the text representation of the command should be as follows: | ||
| Line 61: | Line 63: | ||
| **Note:** The Output signal is a P2D Signal, which is associated with every file. The resulting signal, therefore, is stored in the GLOBAL_WORKPACE | **Note:** The Output signal is a P2D Signal, which is associated with every file. The resulting signal, therefore, is stored in the GLOBAL_WORKPACE | ||
| - | === Meta-Command - Create_Global_Means_For_Left_Right | + | == Meta-Command - Create_Global_Means_For_Left_Right == |
| A Meta-Command can be created for processing all 3 components of a number of model based signals using one pipeline command. | A Meta-Command can be created for processing all 3 components of a number of model based signals using one pipeline command. | ||
| Line 128: | Line 130: | ||
| </ | </ | ||
| - | ==== Find Representative Signal | + | === Find Representative Signal === |
| Find the signal that is most representative of a set of signals. This implementation is based on the following article: | Find the signal that is most representative of a set of signals. This implementation is based on the following article: | ||
| Line 152: | Line 154: | ||
| </ | </ | ||
| - | ==== Merge_Data | + | === Merge_Data === |
| Merges data from more than one data name into a single signal either by **APPEND_TO_END** (appending one signal to the end of another signal) or by **MERGE_AS_NEW_COMPONENTS** (treat each original signal as a component of the new signal) | Merges data from more than one data name into a single signal either by **APPEND_TO_END** (appending one signal to the end of another signal) or by **MERGE_AS_NEW_COMPONENTS** (treat each original signal as a component of the new signal) | ||
| Line 173: | Line 175: | ||
| **Note:** If the Signal_Components parameter is empty, all components of the signals will be used. | **Note:** If the Signal_Components parameter is empty, all components of the signals will be used. | ||
| - | ==== Copy_Folder | + | === Copy_Folder === |
| Makes a copy of an existing folder. If the new folder already exists, select whether these signals should be overwritten (replaced). | Makes a copy of an existing folder. If the new folder already exists, select whether these signals should be overwritten (replaced). | ||
| Line 186: | Line 188: | ||
| </ | </ | ||
| - | ==== Rename_Folder | + | === Rename_Folder === |
| Rename the specified data tree folder. | Rename the specified data tree folder. | ||
| Line 198: | Line 200: | ||
| </ | </ | ||
| - | ==== Delete_Folder | + | === Delete_Folder === |
| Deletes the specified folder. **Note:** that ORIGINAL folders cannot be deleted. | Deletes the specified folder. **Note:** that ORIGINAL folders cannot be deleted. | ||
| Line 209: | Line 211: | ||
| </ | </ | ||
| - | ==== Remove_Signals | + | === Remove_Signals === |
| Remove a signal from the Workspace. **Note:** that Visual3D will not allow the user to delete ORIGINAL signals. | Remove a signal from the Workspace. **Note:** that Visual3D will not allow the user to delete ORIGINAL signals. | ||
| Line 231: | Line 233: | ||
| </ | </ | ||
| - | ==== Rename_Signals | + | === Rename_Signals === |
| Rename a signal in the Workspace. | Rename a signal in the Workspace. | ||
| Line 248: | Line 250: | ||
| </ | </ | ||
| - | |||
| - | Retrieved from "" | ||
visual3d/documentation/pipeline/signal_commands/signal_management_commands.1718386231.txt.gz · Last modified: 2024/06/14 17:30 by sgranger