visual3d:tutorials:pipeline:generic_pipeline_to_create_cmz
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:tutorials:pipeline:generic_pipeline_to_create_cmz [2024/06/19 14:06] – created sgranger | visual3d:tutorials:pipeline:generic_pipeline_to_create_cmz [2025/02/12 16:56] (current) – [Export & Save] sgranger | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Almost every step that can be accomplished using the user interface can also be accomplished using a pipeline command - the pipeline is essentially a set of commands/ | + | ====== Generic Pipeline |
- | It' | + | The Visual3D **Command Pipeline** can accomplish nearly every step used in the application' |
- | [[https:// | + | It's always recommended to learn the manual steps PRIOR to writing a pipeline command - learning the interface will help you build your pipeline. A full command pipeline tutorial is available as part of the Visual3D typical processing session: |
- | When writing | + | Download the [[https:// |
- | ====== Load Static Trial ====== | + | When writing a pipeline to build a CMZ file, your script should follow the general procedure outlined below. Although not in order, the commands used in this sample pipeline are listed. |
- | - [[Visual3D: | + | ===== Load Static Trial ===== |
- | | + | |**Command**|**Description**| |
- | | + | |[[Visual3D: |
- | - Set necessary model metrics (most metrics should be calculated based on markers, but height and weight always need to be entered manually): | + | |[[Visual3D: |
- | - [[Visual3D: | + | |[[Visual3D: |
- | - [[Visual3D: | + | |
- | ====== Load Dynamic Trials ====== | ||
- | - [[Visual3D: | + | ===== Load Dynamic Trials ===== |
- | | + | |**Command**|**Description**| |
- | | + | |[[Visual3D: |
+ | |[[Visual3D: | ||
- | ====== Process Target and Analog Signals ====== | + | ===== Process Target and Analog Signals ===== |
+ | |**Command**|**Description**| | ||
+ | |[[Visual3D: | ||
+ | |[[Visual3D: | ||
+ | |[[Visual3D: | ||
+ | |[[Visual3D: | ||
+ | |[[Visual3D: | ||
- | - [[Visual3D: | + | ===== Gait Events ===== |
- | - [[Visual3D: | + | |
- | - [[Visual3D: | + | |
- | - [[Visual3D: | + | |
- | - [[Visual3D: | + | |
- | - Overground plates: 20 N | + | |
- | - Treadmill: 50 N | + | |
- | - Gap fill & Filter Target Data: | + | |
- | - [[Visual3D: | + | |
- | - [[Visual3D: | + | |
- | - Filter Analog data: | + | |
- | - [[Visual3D: | + | |
- | - If using treadmill data ONLY use [[Visual3D: | + | |
- | - [[Visual3D: | + | |
- | ====== Gait Events | + | ==== Gait Events |
- | ===== Gait Events with Force Platforms ===== | + | The following commands are involved in **checking for clean force assignments**. For example, refer to the [[Visual3D: |
- | - [[Visual3D: | + | |**Command**|**Description**| |
- | | + | |[[Visual3D: |
- | - Plot vertical component of KINETIC_KINEMATIC:: | + | |[[Visual3D: |
- | - [[Visual3D: | + | |[[Visual3D: |
- | - Plot vertical component of KINETIC_KINEMATIC:: | + | |[[Visual3D: |
- | | + | |[[Visual3D: |
- | | + | |[[Visual3D: |
- | | + | |
- | - Remove any force assignment that is not [[Visual3D: | + | |
- | - Remove any partial force assignments (this includes force assignments at the start/end of the trial) | + | |
- | | + | |
- | | + | |
- | ===== Gait Events WITHOUT Force Platforms ===== | + | ==== Gait Events WITHOUT Force Platforms ==== |
+ | When force data is not available, there are several methods for computing gait events using kinematic data, an overview of this process can be seen in [[Visual3D: | ||
- | - [[Visual3D: | ||
- | ====== Report and Data Review | + | ===== Report and Data Review ===== |
- | + | |**Command**|**Description**| | |
- | | + | |[[Visual3D: |
- | - Stop pipeline to review data prior to export: | + | |[[Visual3D: |
- | - [[Visual3D: | + | |
- | - [[Visual3D: | + | |
- | + | ||
- | Notes: | + | |
+ | **NOTE**: | ||
* Many users are skipping report templates - but it's highly recommended to even create a simple report template to review data prior to export. No data collection is perfect, and reviewing the data prior to exporting ensures the data is a quality assurance step. | * Many users are skipping report templates - but it's highly recommended to even create a simple report template to review data prior to export. No data collection is perfect, and reviewing the data prior to exporting ensures the data is a quality assurance step. | ||
- | * Instructions to create a report template can be found [[Visual3D: | + | * Instructions to create a report template can be found [[Visual3D: |
- | * The report template contains any signals defined using the [[Visual3D: | + | * The report template contains any signals defined using the [[Visual3D: |
- | + | ||
- | ====== Signal Definitions and Processing ====== | + | |
- | + | ||
- | - [[Visual3D: | + | |
- | - [[Visual3D: | + | |
- | + | ||
- | ====== Export ====== | + | |
- | - [[Visual3D: | + | ===== Signal Definitions and Processing ===== |
+ | |**Command**|**Description**| | ||
+ | |[[Visual3D: | ||
+ | |[[Visual3D: | ||
- | ====== Save ====== | + | ===== Export & Save ===== |
+ | |**Command**|**Description**| | ||
+ | |[[Visual3D: | ||
+ | |[[Visual3D: | ||
- | - [[Visual3D: | ||
visual3d/tutorials/pipeline/generic_pipeline_to_create_cmz.1718805975.txt.gz · Last modified: 2024/06/19 14:06 by sgranger