jwh
Junior Member level 1
Folks,
I'm using ansysedt on RHEL with an HPC pool license. I am simulating an HFSS model (driven) across a parametric sweep. The analysis is utilizing the direct solver with an interpolating frequency sweep. The analysis configuration is utilizing 40 cores with 10 tasks on the local machine (48 cores on this machine). The Job Distribution is setup such that the direct solver memory is not enabled for distribution. Two levels of distribution levels are selected, with 10 distributed solutions at the first level.
When I run the parametric analysis, all but the last 10 models run in parallel with no issues. These last ten, however, run and then hang indefinitely. I can see ten h3fd processes running with corresponding progress bars in the ansysedt GUI. As each of these processes finish, I see that each process transitions to "sending solution file: solverUsage.txt" and a see corresponding HFSSCOMENGINE.exe processes (see the top output below).
I'm confused in that there are twenty of these processes instead of ten (aside from the fact that these processes hang indefinitely). I've killed the processes and started the analysis again with the same behavior.
I'd like to figure out a) why this is happening, b) how to stop it, and c) how to avoid this behavior in the future.
39652 h** 20 0 25.2g 20g 16m S 400.3 4.0 26:48.48 hf3d 56296 h** 20 0 1772m 87m 61m S 99.8 0.0 1159:49 HFSSCOMENGINE.e 56574 h** 20 0 1772m 85m 61m S 99.8 0.0 882:18.94 HFSSCOMENGINE.e 56780 h** 20 0 1772m 85m 61m S 99.8 0.0 1038:21 HFSSCOMENGINE.e 56984 h** 20 0 1772m 87m 61m S 99.8 0.0 1122:13 HFSSCOMENGINE.e 57207 h** 20 0 1772m 87m 61m S 99.8 0.0 985:15.85 HFSSCOMENGINE.e 57420 h** 20 0 1772m 87m 61m S 99.8 0.0 1061:50 HFSSCOMENGINE.e 57644 h** 20 0 1772m 87m 61m S 99.8 0.0 1223:12 HFSSCOMENGINE.e 57970 h** 20 0 1772m 85m 61m S 99.8 0.0 1174:53 HFSSCOMENGINE.e 56101 h** 20 0 1772m 87m 61m S 99.5 0.0 1180:47 HFSSCOMENGINE.e 34279 h** 20 0 7570m 660m 199m S 2.3 0.1 199:36.56 ansysedt.exe 55630 h** 20 0 22560 2604 1064 R 1.6 0.0 28:11.46 top 30476 h** 20 0 103m 4136 1168 S 0.0 0.0 9:12.90 sshd 30477 h** 20 0 114m 2624 1384 S 0.0 0.0 0:00.35 tcsh 34093 h** 20 0 104m 1760 1168 S 0.0 0.0 0:00.04 ansysedt 34292 h** 20 0 1025m 7876 5860 S 0.0 0.0 0:24.88 mwrpcss 55951 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE 56154 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE 56430 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.08 HFSSCOMENGINE 56638 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE
56842 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE 57063 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE
57270 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE 57502 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.08 HFSSCOMENGINE
57820 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.08 HFSSCOMENGINE 58067 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.12 HFSSCOMENGINE
58211 h** 20 0 1772m 87m 61m S 0.0 0.0 0:24.57 HFSSCOMENGINE.e
Thank you.
Regards,
J
I'm using ansysedt on RHEL with an HPC pool license. I am simulating an HFSS model (driven) across a parametric sweep. The analysis is utilizing the direct solver with an interpolating frequency sweep. The analysis configuration is utilizing 40 cores with 10 tasks on the local machine (48 cores on this machine). The Job Distribution is setup such that the direct solver memory is not enabled for distribution. Two levels of distribution levels are selected, with 10 distributed solutions at the first level.
When I run the parametric analysis, all but the last 10 models run in parallel with no issues. These last ten, however, run and then hang indefinitely. I can see ten h3fd processes running with corresponding progress bars in the ansysedt GUI. As each of these processes finish, I see that each process transitions to "sending solution file: solverUsage.txt" and a see corresponding HFSSCOMENGINE.exe processes (see the top output below).
I'm confused in that there are twenty of these processes instead of ten (aside from the fact that these processes hang indefinitely). I've killed the processes and started the analysis again with the same behavior.
I'd like to figure out a) why this is happening, b) how to stop it, and c) how to avoid this behavior in the future.
39652 h** 20 0 25.2g 20g 16m S 400.3 4.0 26:48.48 hf3d 56296 h** 20 0 1772m 87m 61m S 99.8 0.0 1159:49 HFSSCOMENGINE.e 56574 h** 20 0 1772m 85m 61m S 99.8 0.0 882:18.94 HFSSCOMENGINE.e 56780 h** 20 0 1772m 85m 61m S 99.8 0.0 1038:21 HFSSCOMENGINE.e 56984 h** 20 0 1772m 87m 61m S 99.8 0.0 1122:13 HFSSCOMENGINE.e 57207 h** 20 0 1772m 87m 61m S 99.8 0.0 985:15.85 HFSSCOMENGINE.e 57420 h** 20 0 1772m 87m 61m S 99.8 0.0 1061:50 HFSSCOMENGINE.e 57644 h** 20 0 1772m 87m 61m S 99.8 0.0 1223:12 HFSSCOMENGINE.e 57970 h** 20 0 1772m 85m 61m S 99.8 0.0 1174:53 HFSSCOMENGINE.e 56101 h** 20 0 1772m 87m 61m S 99.5 0.0 1180:47 HFSSCOMENGINE.e 34279 h** 20 0 7570m 660m 199m S 2.3 0.1 199:36.56 ansysedt.exe 55630 h** 20 0 22560 2604 1064 R 1.6 0.0 28:11.46 top 30476 h** 20 0 103m 4136 1168 S 0.0 0.0 9:12.90 sshd 30477 h** 20 0 114m 2624 1384 S 0.0 0.0 0:00.35 tcsh 34093 h** 20 0 104m 1760 1168 S 0.0 0.0 0:00.04 ansysedt 34292 h** 20 0 1025m 7876 5860 S 0.0 0.0 0:24.88 mwrpcss 55951 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE 56154 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE 56430 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.08 HFSSCOMENGINE 56638 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE
56842 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE 57063 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE
57270 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.07 HFSSCOMENGINE 57502 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.08 HFSSCOMENGINE
57820 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.08 HFSSCOMENGINE 58067 h** 20 0 104m 1736 1124 S 0.0 0.0 0:00.12 HFSSCOMENGINE
58211 h** 20 0 1772m 87m 61m S 0.0 0.0 0:24.57 HFSSCOMENGINE.e
Thank you.
Regards,
J
