Normative Data From CMO Library: Difference between revisions
Line 55: | Line 55: | ||
==Step 2: Creating a script to define the signals in the normal database== | ==Step 2: Creating a script to define the signals in the normal database== | ||
===Option 1: Using a | ===Option 1: Using a Premade Pipeline=== | ||
If you already have a premade pipeline, you can skip ahead to Step 3. | If you already have a premade pipeline, you can skip ahead to Step 3. |
Revision as of 13:11, 31 May 2023
Language: | English • français • italiano • português • español |
---|
Introduction
Building a database of "control" values takes place in four steps.
- Organize & Catalog the CMO files
- Create a script to define the signals we want to create normal signals for.
- Create the normal database.
- Save the normal database for use in the future.
Sample Files
You can download the sample files here.
The downloaded file contains:
- 1. A sample CMO library containing two CMO files (Sub01_Walk.cmo & Sub02_Walk.cmo)
- 2. A sample report template (SampleReport.rgt)
- 3. A sample script to create a normal database (SampleScript.v3s)
- 4. A sample normal database (NormalDatabase.vnd)
Step 1: Organize & Catalog the CMO files
The first time you load the CMO library, you must organize the files. You do not need to do this each time you load the CMO Library, however, if you move the CMO files to different locations on your computer, this section should be done again.
1. Organize all the CMO files that you intend to query from into folders within a hierarchy.
If using the sample files, you must unzip the file. You will see the CMO files in the CMO_Lib folder.
NOTE The CMO files can be in subfolders as well.
2.Set Visual3D to point to the CMO Library (CMO Library -> Set CMO Library Path).
If using the sample files, point to the CMO_Lib folder.
3. Catalog the Library (CMO Library -> Maintenance -> Catalog CMO Files).
NOTE: When you select "Catalog CMO Files", Visual3D goes through all the CMO files, and ensures that the CMX file is up to date with the CMO file. If you have not deleted your CMX files, or moved the CMO/CMX files to different locations, you do not need to do this. Typically, I recommend cataloging the CMO files the first time you use the library.
Step 2: Creating a script to define the signals in the normal database
Option 1: Using a Premade Pipeline
If you already have a premade pipeline, you can skip ahead to Step 3.
Note: If you are using a premade pipeline any variables you wish to save in the .vnd file needs to be saved using the Global_Normalized_Signal_Mean.
- Global_Normalized_Signal_Mean
- /SIGNAL_TYPES=LINK_MODEL_BASED+LINK_MODEL_BASED
- /SIGNAL_NAMES=RKNEE_ANGLE+LKNEE_ANGLE
- /SIGNAL_FOLDER=ORIGINAL+ORIGINAL
- /SIGNAL_COMPONENTS=X+X
- /START_LABEL=
- /END_LABEL=
- /EVENT_SEQUENCE= RHS+RHS++LHS+LHS
- ! /EXCLUDE_EVENTS=
- /RESULT_NAME=KNEE_FLEXION
- ! /RESULT_FOLDER=ORIGINAL
- /NORMALIZE_POINTS=101
- /CREATE_STANDARD_DEVIATION=TRUE
- ! /CALCULATE_PER_FILE=FALSE
- ;
Option 2: Creating Script based off a Report Template
To automatically create the script, follow the instructions below, you will need a report template:
1. Load a report template. You can do this two ways:
- A. Open a CMO that has the report/graph of the values you wish to create ”normal” data for.
- You can open one of the example CMO files
- B. Open a report template that contains the data values you wish to create ”normal” data for.
- You can open the sample report template (SampleReport.rgt)
2. Create script:
- 2. In the pop up window:
3. View the created script in the Pipeline.
|
4. Save the Pipeline script.
We have now defined what we want to create normal values for. The normal data has NOT been created yet. So now we need to clear the workspace and load the raw data for this script. This will be accomplished in the next step.
Note: An alternative to the Wizard approach is to create/edit the command from pipeline directly using the Global_Normalized_Signal_Mean command. Note that the wizard added the desired data to the list at the bottom of the Global_Normalized_Signal_Mean command dialog box. You can enter and ADD new values here as well.
Step 3: Create the normal database
1. Clear out the entire Visual3D workspace
|
2. Browse the CMO Library.
|
3. Set the Active File to EACH_CMO_WORKSPACE
|
4. Execute the script to create the normal database
|
Step 4: Save the normal database
1. Check that the P2D signals were created.
Note: The P2D format is simply a historical format for 2D point data storage, and is maintained to provide backward compatibility. |
2. Save the Normal Data as a ”Normal” database. You can save the normal database as a .vnd file, or a .cmo file.
|
- To save as a .cmo file:
- Close the CMO Library by going to CMO Library -> Unload CMO Library (Unbrowse)
- Save the workspace as a CMO file (File -> Save)