-
Notifications
You must be signed in to change notification settings - Fork 135
Adding acoustic example #1458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding acoustic example #1458
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1458 +/- ##
==========================================
- Coverage 80.32% 80.31% -0.01%
==========================================
Files 43 43
Lines 6780 6778 -2
==========================================
- Hits 5446 5444 -2
Misses 1334 1334 |
Hi @germa89 yes the duplicate results are due to complex numbers used in the solution. The SET command has an option to read in the real, imaginary, amplitude, or phase angle. The model does not use the Fluid130 element. It's a far-field element type so I imagine the intent was to run the analysis with and without it to see its effect. Since the with version was not set up the ET could be deleted. |
Remind me to review once Mike's suggestions have been incorporated. |
I do not think that is the right command. I guess you mean to use something like I tried that, and still shows both. >>> mapdl.run("SET,LIST, , , 0")
***** INDEX OF DATA SETS ON RESULTS FILE *****
SET TIME/FREQ LOAD STEP SUBSTEP CUMULATIVE
1 220.00 1 1 1
2 220.00 1 1 1
3 240.00 1 2 2
4 240.00 1 2 2
5 260.00 1 3 3
6 260.00 1 3 3
7 280.00 1 4 4
8 280.00 1 4 4
9 300.00 1 5 5
10 300.00 1 5 5
11 320.00 1 6 6
12 320.00 1 6 6
13 340.00 1 7 7
14 340.00 1 7 7
15 360.00 1 8 8
16 360.00 1 8 8
17 380.00 1 9 9
18 380.00 1 9 9
19 400.00 1 10 10
20 400.00 1 10 10
21 420.00 1 11 11
22 420.00 1 11 11
23 440.00 1 12 12
24 440.00 1 12 12
25 460.00 1 13 13
26 460.00 1 13 13
27 480.00 1 14 14
28 480.00 1 14 14
29 500.00 1 15 15
30 500.00 1 15 15
31 520.00 1 16 16
32 520.00 1 16 16
33 540.00 1 17 17
34 540.00 1 17 17
35 560.00 1 18 18
36 560.00 1 18 18
37 580.00 1 19 19
38 580.00 1 19 19
39 600.00 1 20 20
40 600.00 1 20 20
41 620.00 1 21 21
42 620.00 1 21 21
43 640.00 1 22 22
44 640.00 1 22 22
45 660.00 1 23 23
46 660.00 1 23 23
47 680.00 1 24 24
48 680.00 1 24 24
49 700.00 1 25 25
50 700.00 1 25 25
51 720.00 1 26 26
52 720.00 1 26 26
53 740.00 1 27 27
54 740.00 1 27 27
55 760.00 1 28 28
56 760.00 1 28 28
57 780.00 1 29 29
58 780.00 1 29 29
59 800.00 1 30 30
60 800.00 1 30 30
61 820.00 1 31 31
62 820.00 1 31 31
63 840.00 1 32 32
64 840.00 1 32 32
65 860.00 1 33 33
66 860.00 1 33 33
67 880.00 1 34 34
68 880.00 1 34 34
69 900.00 1 35 35
70 900.00 1 35 35
71 920.00 1 36 36
72 920.00 1 36 36
73 940.00 1 37 37
74 940.00 1 37 37
75 960.00 1 38 38
76 960.00 1 38 38
77 980.00 1 39 39
78 980.00 1 39 39
79 1000.0 1 40 40
80 1000.0 1 40 40 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Nice work!
@germa89 the KIMG field of SET does not change the behavior of listing the result sets. But it does change which results are read from the rst file into the mapdl database (memory). The time history processor reads both real and imaginary data; we then have tools to work with that if needed. Like ABS which operates on a complex time history variable and returns the amplitude. |
Close #1428 by adding example to gallery.
Notes
FLUID30
andFLUID130
) but I believe only one is used.mapdl.set("LIST")
gives the frequencies duplicated. I believe it is related with complex values, but I'm not sure.Pinging @akaszynski and @mikerife for feedback.