Loadstep ID Management in HyperView

This topic outlines the loadstep ID management policy in HyperView when multiple result files are loaded. Basically, HyperView will attempt to use the corresponding ID slot, if it is available, when creating loadsteps. The following example below illustrates this policy.

Example

There are four result files in this example, and we will assume that result file "A" has loadstep IDs 101, 102, and 103, result file “B” has loadstep IDs 101, 102, and 103, result file “C” has loadstep IDs 1, 2, and 3, and result file “D” has loadstep IDs 4, 101, and 102.
  • Result file “A” is loaded into HyperView.
    The loadstep IDs will be:
    • 101
    • 102
    • 103
  • Result file “B” is loaded into HyperView.
    The loadstep IDs will be:
    • 101
    • 102
    • 103
    • 104
    • 105
    • 106
  • Result file “C” is loaded into HyperView.
    The loadstep IDs will be:
    • 1
    • 2
    • 3
    • 101
    • 102
    • 103
    • 104
    • 105
    • 106
  • Result file “D” is loaded into HyperView.
    The loadstep IDs will be:
    • 1
    • 2
    • 3
    • 4
    • 101
    • 102
    • 103
    • 104
    • 105
    • 106
    • 107
    • 108

Creating Derived Subcases

It is important to understand the HyperView numbering policy (shown above) when creating configuration files for a derived loadstep. The order in which the result files are added into a HyperView session is important, especially if the various result files have the same loadstep IDs. Follow the steps outlined below in order to see a brief example of how the numbering policy works in HyperView.

Step 1:
  1. Start a HyperView session.
  2. Load result file “A” and result file “B”.
  3. Create a Linear Superposition loadstep using all of the available loadsteps: 101, 102, 103, 104, 105, and 106 (with scale factors of 1, 2, 3, 4, 5, and 6, respectively).

    The loadsteps coming from result file “A” will have scale factors of 1, 2, and 3. The loadsteps coming from result file “B” will have scale factors of 4, 5, and 6.

  4. Save a configuration file.
Step 2:
  1. Start a HyperView session.
  2. Now change the order of loading the result file, load result file “B” first this time and then load result file “A”.
  3. Loadsteps 101, 102, and 103 are coming from result file “B”, and 104, 105, and 106 are coming from result file “A”.
  4. Next, load the configuration file previously created in Step 1.

    Observe that the applied scale factors are applied interchangeably.