Tutorial: Gait Profile Score and Movement Analysis Profile Pipeline NormalDB

Redirect to:

• Normative Data From CMO Library

Introduction

We are still working on this page...

MainPage

Create Normal Database

The intention of this section is to teach users how to create a normal database specifically for the provided script. However, the Visual3D is very flexible and normal databases can be created with any information. To find out more about how to do use the normal database function, please read the Normative_Data_From_CMO_Library tutorial.

The following steps describe the steps to create a normal database for this specific purpose.

1. Organize the CMO files

Assuming you have already created CMO files for your control database, organize the CMO files on your computer so that all control subjects are stored in one location. The CMO files may be located within subfolders, but make sure to remove any CMO files you do not want included in your control database.

NOTE: When you create a CMO file, a CMX file is created as well. The CMO Library opens the CMX file, so make sure each CMO file has a CMX file. If it does not, Visual3D can do this for you later in "Step 4. Open CMO Library".

2. Define relevant signals in CMO files

Make sure the model template has all the relevant segments to create your Link Model Based signals.

Since the Compute Model Based commands (which define the Link Model Based signals) are stored in the report template, you can simply open the report template. If you already have a report template in your CMO file, you can append the report template by using the pipeline command or by going to File -> Append Report Template.

Save the updated CMO file for each control subject.

3. Create script to create normal database

Open a blank workspace in Visual3D and load a control CMO file. Apply the relevant report template. The report template should only have the relevant kinematic variables plotted, an example of this can be found here.

Create the normal database script:

A. Click CMO Library -> Create Normal Database Script for Graphed Report Means

B. Enter the folder name that you want the results to go into: GPS_CONTROL

C. Enter the number of points you want to normalize to: 51

D. Do not check "Create the normals only for graphs that have means already graphed" & click Continue.

E. The relevant commands were then added to the Pipeline workshop. This script can be used to create the control database.

Save the report template as NormalizeControlData.v3s and clear the workspace (do not save the CMO file you opened for this step). An example of the NormalizeControlData.v3s script can be found here

4. Open CMO Library

Open a blank workspace in Visual3D.

If some of your CMO files do not have the associated CMX files:

CMO Library -> Maintenance -> Catalog CMO Files

This step will take some time and your workspace will appear to freeze, but it is still working.

Once all the CMX file exist, open the CMO Library:

A. CMO Library -> Browse CMO Library

B. Do you want to browse the CMO Library catalog? Click Yes

5. Create normal database using script

Create the normal database:

A. Set the active file to EACH_CMO_WORKSPACE

B. Load the normal database script (Pipeline -> Open Pipeline)

C. In the pipeline workshop click "Execute"

6. Export normal database as VND file

Export the normal database:

A. Set the active file to GLOBAL

B. Expand the P2D folder

C. Right click on the GPS_CONTROL folder -> Export folder to Normal Database (.vnd). Save the control database as ControlData.vnd