The pipeline processing dialog contains two buttons above the middle list box.

The Main Pipeline refers to the pipeline that has been loaded manually by the user.

The CMO Recalc Script by default contains the LINKMODEL based calculation definitions. The user can, however, add pipeline commands to this list box manually. These commands will be processed whenever the RECALC button is executed.

Note: that any items that are in the CMO Recalc Script when a Report Template is saved are stored in the report template.

When the RECALC button is pressed. The following processing occurs:

1. If use processed analog is set, re-process force platforms.
2. Rebuild all models in the Workspace
3. Compute landmarks and model pose (e.g. position and orientation of all segments) for all #files in the Workspace
4. Assign Force Platforms to Segments
5. Compute Assigned Forces
6. Compute Kinematics
7. Compute Kinetics
8. Compute Center of Mass.
9. Execute the RECALC pipeline
10. Update the display dialogs for any new data
11. Recompute the Report graphs

LINK_MODEL_BASED signals in the report are always recalculated. LINK_MODEL_BASED signals not in the report are not recalculated.

DERIVED, METRIC and other signals are not recalculated by default. These calculations can be placed into the recalc pipeline by generating the pipeline you desire, save the pipeline, switch to the CMO recalc pipeline (using the radio button, shown below), click the 'Open Pipeline' button and append the saved pipeline to the existing recalc pipeline.

By adding the calculations to the recalc pipeline, these will be recalculated when the recalc button is pressed. The recalc pipeline is saved in the .cmo file so it will always be there, and it is also saved in the report template so that when you open the report the items which should be recalculated (or calculated for a first time) are performed.

If the button is checked to display the Recalc pipeline, the pipeline list box will be shaded pink.

Selecting the button to save the pipeline will save the contents of the Recalc pipeline.

Selecting the button to open the pipeline will either replace or append the existing Recalc Pipeline.

Deleting the Recalc pipeline will remove the Recalc pipeline from the workspace.

When a report template is added to the Workspace, all of the report graphs are deleted and all of the model based data definitions contained in the report template are appended to the CMO Recalc Script. For design reasons we elected not to delete the existing model based data because we felt it was easier for users to delete entries from the CMO Recalc Script than to re-create the model based data that they created before opening the report template. However, when the RECALC button is pressed, the old Compute Model Based signals will be removed from the RECALC pipeline.

By default, ALL_FILES are active for the Recalc Pipeline.

It is possible to “trick” Visual3D by inserting Select_Active_File commands into the RECALC pipeline, which allows you to selectively determine which files are being re-processed, but you need to be careful because the RECALC pipeline is a critical part of the Report Template, so only do this when you want the changes to persist in your report template.

If a signal is defined in the RECALC pipeline, removing (or) renaming the signal in the data tree won't do the trick. As soon as the RECALC pipeline is executed the signal will re-appear. You need to remove the signal from both the RECALC pipeline and the data tree.

All model based signals are automatically added to the RECALC pipeline when they are created.

Visual3D checks for duplicate entries in the RECALC pipeline, but it is possible that a user can inadvertently add duplicates to the pipeline.

Removing an item from the RECALC pipeline does not remove the item from the data tree (e.g. the Workspace). The signal in the data tree no longer has a definition, however, so changing the properties of the model, which would normally change the related model based signals, will not modify the signal as expected.

If you aren't sure, you can save the cmo file, then remove all the model based signals from the data tree, select RECALC and see what signals didn't re-appear.

If you are missing a specific signal, re-open the saved cmo file and check the history of the signal missing from the RECALC pipeline. Version 4.5 of Visual3D allows you to copy the history (e.g. the model based definition), so you can paste it into the RECALC pipeline.

You can edit the commands in the RECALC pipeline directly. In the pipeline dialog, select the button (check box) to make the RECALC pipeline editable and edit a command.

You can also select Compute Model Based Data under the Model menu option, and edit the definition there. Visual3D will automatically search for a model based signal of the same name in the data tree and replace the properties.