visual3d:documentation:pipeline:general_information:recalc_pipeline
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:documentation:pipeline:general_information:recalc_pipeline [2024/07/17 15:11] – sgranger | visual3d:documentation:pipeline:general_information:recalc_pipeline [2026/03/17 15:13] (current) – wikisysop | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | The pipeline | + | The [[visual3d: |
| + | - The **Main Pipeline** refers to the pipeline that has been loaded manually by the user. | ||
| + | - The **CMO Recalc Script** by default contains the [[visual3d: | ||
| - | The **Main Pipeline** refers to the pipeline that has been loaded manually by the user. | + | ===== What RECALC accomplishes ===== |
| - | The **CMO Recalc Scrip**t by default contains | + | When the user presses |
| - | + | - (If [[visual3d: | |
| - | **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 25: | Line 20: | ||
| - Recompute the Report graphs | - Recompute the Report graphs | ||
| - | LINK_MODEL_BASED signals | + | LINK_MODEL_BASED signals are recalculated |
| - | + | ||
| - | DERIVED, METRIC and other signals are not recalculated by default. These calculations can be placed into the recalc | + | |
| {{: | {{: | ||
| - | 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. | ||
| - | |||
| - | === Saving the Recalc Pipeline === | ||
| - | |||
| - | 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. | ||
| - | === Opening | + | Adding the calculations to the RECALC pipeline will cause them to be recalculated when the RECALC button is pressed. The RECALC pipeline is saved in the [visual3d: |
| - | 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. | + | ==== Acting on Active Files ==== |
| - | === Recalc Pipeline | + | By default, [[visual3d: |
| - | By default, ALL_FILES are active for the Recalc Pipeline. | + | ==== Removing a signal from the Workspace ==== |
| - | It is possible to " | + | If a signal |
| - | === Removing a signal from the Workspace | + | ==== Warning about editing |
| - | If a signal is defined in the RECALC pipeline, removing | + | Removing an item from the RECALC pipeline |
| - | All model based signals are automatically added to the RECALC pipeline | + | If you aren't sure, you can save the CMZ file, then remove all the model based signals |
| - | Visual3D checks for duplicate entries in the RECALC pipeline, but it is possible that a user can inadvertently add duplicates to the pipeline. | ||
| - | === Warning about editing | + | ===== Modifying and Saving |
| - | Removing an item from the RECALC pipeline | + | If the button is checked to display |
| - | If you aren't sure, you can save the cmo file, then remove all the model based signals from the data tree, select RECALC | + | 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: |
| - | 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 | + | You can also append pipeline commands to the RECALC pipeline |
| - | === Modifying | + | It is also possible to save, edit, or delete |
| + | - Selecting the button to save the pipeline will save the contents | ||
| + | - 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. | ||
| - | 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. | + | ===== Opening |
| - | 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 | + | When a report template is added to the Workspace, all of the report graphs are deleted |
visual3d/documentation/pipeline/general_information/recalc_pipeline.1721229062.txt.gz · Last modified: by sgranger
