Eigenfrequencies from complex eigenvalues do not match to the eigenfrequencies from "convert2frequencies" #84
Unanswered
SimonAndreas
asked this question in
Q&A on usage of Exudyn
Replies: 1 comment 2 replies
-
Your description is sound, however, with the limited amount of information, I cannot see the exact problem. Make sure that you correctly compute the frequency because Another thing is the different sorting you may have to consider. Provide more output, exudyn version, etc., then it should become more clear. If your system matrices are M,K, D, the two approaches should match well. In any case, you can try ignoreAlgebraicEquations=True, in order to see if problems also occur in case that you remove constraints. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am performing a modal analysis on a crane structure using the function "ComputeODE2Eigenvalues".
My model consists of two beams, based on 2D beam elements, a rigid body, generic joints, distance constraints, a springDamper element and coordinate constraints.
The function seems to work well when I have "computeComplexEigenvalues = False" and "convert2Frequencies = True". From this I get the natural frequencies directly and sorted.
However, when I want to obtain complex eigenvalues, using "computeComplexEigenvalues = True", "convert2Frequencies = False" and "useAbsoluteValues = False", I get different eigenfrequencies.
I convert the complex eigenvalues to natural frequencies in [Hz] as follows: f_n = np.abs(complexEigenValue)/(2*np.pi). I sort the eigenfrequencies as well.
I use the same approach as in the "complexEigenvaluesTest.py" (TM). In this TestModel, the frequencies DO match between the two different methods.
Beta Was this translation helpful? Give feedback.
All reactions