visual3d:documentation:pipeline:general_information:recalc_pipeline
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
visual3d:documentation:pipeline:general_information:recalc_pipeline [2024/06/14 17:27] – created sgranger | visual3d:documentation:pipeline:general_information:recalc_pipeline [2025/04/15 17:50] (current) – Cleaned up page and added many links. wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | |**Language: | + | ====== |
- | |===== Contents =====\\ \\ \\ \\ * [[#What_processing_happens|1 What processing happens]]\\ * [[# | + | The [[visual3d: |
+ | - The **Main Pipeline** refers to the pipeline that has been loaded manually by the user. | ||
+ | - The **CMO Recalc | ||
- | The pipeline processing dialog contains two buttons above the middle list box. | + | ===== What RECALC accomplishes ===== |
- | The **Main Pipeline** refers to the pipeline that has been loaded manually by the user. | + | When the user presses |
- | + | - (If [[visual3d: | |
- | The **CMO Recalc Scrip**t 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 | + | |
- | + | ||
- | **Note:** that any items that are in the **CMO Recalc Script** when a Report Template is saved are stored in the report template. | + | |
- | + | ||
- | ==== What processing happens ==== | + | |
- | + | ||
- | When the RECALC button is pressed. The following | + | |
- | + | ||
- | - If **use processed analog** | + | |
- Rebuild all models in the Workspace | - Rebuild all models in the Workspace | ||
- | - Compute | + | - Compute |
- Assign Force Platforms to Segments | - Assign Force Platforms to Segments | ||
- Compute Assigned Forces | - Compute Assigned Forces | ||
Line 27: | Line 20: | ||
- Recompute the Report graphs | - Recompute the Report graphs | ||
- | LINK_MODEL_BASED signals in the report are always | + | LINK_MODEL_BASED signals |
- | 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' | + | {{: |
- | [[File: | + | Adding |
- | By adding | + | |
- | ==== Saving the Recalc Pipeline | + | ==== Acting on Active Files ==== |
- | If the button is checked to display the Recalc pipeline, the pipeline list box will be shaded pink. | + | By default, |
- | + | ||
- | 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. | + | |
- | + | ||
- | ==== Opening a Report Template ==== | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | ==== Recalc Pipeline Processing acts on the Active Files ==== | + | |
- | + | ||
- | By default, ALL_FILES are active for the Recalc Pipeline. | + | |
- | + | ||
- | It is possible to " | + | |
==== Removing a signal from the Workspace ==== | ==== Removing a signal from the Workspace ==== | ||
- | 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. | + | 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. |
- | All model based signals are automatically added to the RECALC pipeline | + | ==== Warning about editing |
- | 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 |
- | ==== Warning about editing | + | If you aren't sure, you can save the CMZ 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 CMZ 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), |
- | 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. | + | ===== Modifying and Saving |
- | If you are missing a specific signal, re-open | + | If the button is checked to display |
- | ==== Modifying | + | 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 [[visual3d: |
- | You can edit the commands in the RECALC pipeline | + | It is also possible to save, edit, or delete |
+ | - Selecting the button to save the pipeline | ||
+ | - Selecting | ||
+ | - Deleting | ||
- | 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. | + | ===== Opening |
+ | 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. | ||
- | Retrieved from "" | ||
visual3d/documentation/pipeline/general_information/recalc_pipeline.1718386043.txt.gz · Last modified: 2024/06/14 17:27 by sgranger