•
|
One study with an Eigenfrequency study step for computing the eigenfrequencies and corresponding eigenmodes.
|
•
|
One study with a Model Reduction study step, in which the ROM is created. It references the eigenfrequency study, as well as an embedded Frequency Domain study step. The latter can mainly be considered as a placeholder which is a mandatory input to the model reduction. In case you have already computed the eigenmodes, you can change the setting of the Training study in this node to point to the corresponding existing eigenfrequency study, and then delete the newly generated one.
|
The Model Reduction study step is set up to be suitable for a random vibration analysis. In particular, it is required the Ensure reconstruction capability is selected.
|
•
|
A Global Reduced Model Inputs node, in which you define the control parameters for the ROM. All loads that represents random excitations must have a value multiplied by one of such parameters.
|
•
|
A Frequency Domain, Modal Reduced-Order Model node. This is a placeholder for the ROM to be created.
|
•
|
A Random Vibration node. Here, you prescribe the PSD functions and the cross-correlation functions, if needed. They can be function of frequency only (the internal variable freq); it is not possible to prescribe a coordinate dependency.
|
1
|
Add a Random Vibration (PSD) study.
|
2
|
In the Global Reduced Model Inputs node, add all required control parameters. The values that you assign to the parameters are not important. Control parameters are used in the same manner as ordinary parameters in expressions for the loads in the physics interface. You need as many control parameters as you have different PSD functions.
|
For the common case that a number of support points have the same acceleration PSD, the support acceleration can be replaced by a frame acceleration load, using the Base Excitation feature. This is how vibration testing is analyzed. See also Absolute Versus Relative Accelerations.
|
4
|
If you want any scalar outputs, define them as Variables under Definitions in the component. You can use, for example, probes or functions like at3() to create scalar outputs. It is also possible to compute scalar results using, for example, Point Evaluation during result presentation. Such evaluations will, however, require a larger computational effort than scalar outputs that are part of the ROM definition.
|
5
|
In case you want to reuse a previously computed eigenfrequency study, go to the Model Reduction study step. Change the settings for Training study in the Model Reduction Settings section to point to the correct eigenfrequency study.
|
6
|
Run the study containing the Model Reduction study step. It will automatically create a ROM that can be used for all further evaluations.
|
7
|
Define the PSD and cross-correlation functions required for representing the loading as functions under Global Definitions. These functions should depend on frequency only.
|
It is common that an input PSD is provided in terms of straight lines in a log-log diagram of PSD value versus frequency, f. To mimic this behavior, you can use an interpolation function (say int1) where you enter pairs of log(f) and log(PSD) values. You then reference this function through an expression like exp(int1(log(freq[1/Hz]))). This will provide a linear interpolation in a log-log space.
|
8
|
10
|
If the correlation type is Cross-correlated, enter also the off-diagonal part of the Correlation matrix.
|
11
|
To make these settings available for result evaluation, run Update Solution for the model reduction study.
|
You cannot use ordinary variables like <phys>.mises or <phys.disp> as arguments to the q2sq() operator. The reason is that the argument must never evaluate to zero.
|
|