The Visual3D Command Pipeline can accomplish nearly every step used in the application's user interface. The pipeline is essentially a set of commands/functions that allow you to streamline your data processing and reproducible for other subjects.

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: Command Pipeline tutorial.

Download the Create CMZ ZIP File which contains a sample pipeline script used to make CMZs.

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.

The following commands are involved in checking for clean force assignments. For example, refer to the Clean Foot Strike documentation. A “clean” foot strike indicates that measurements from the force platform are able to be used for analysis, and will not cause incorrect events to be created or produce “bad” kinetic calculations (GRF, Joint Moments, etc.).

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 Example - Kinematic Gait Events.

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.
• Instructions to create a report template can be found here.
• The report template contains any signals defined using the Compute Model Based Function.