Page 1 of 1

Why my running be killed?

Posted: Mon Jan 27, 2020 5:19 am
by cdd
Hi,

When i run gyre-tasc5 with command "gyre_force test.in(
test.in
(620 Bytes) Downloaded 327 times
)", the os always kill my program. I use command "dmesg | grep -E -i -B100 'killed process" to check the killed process, it give me below message:

[17917.578876] [ 6990] 1000 6990 2281642 1942615 18173952 302903 0 gyre_force
[17917.578878] Out of memory: Kill process 6990 (gyre_force) score 877 or sacrifice child
[17917.578895] Killed process 6990 (gyre_force) total-vm:9126568kB, anon-rss:7770460kB, file-rss:0kB, shmem-rss:0kB

The screen output is below:
ubuntu64@ubuntu64-virtual-machine:~/software/gyre-tasc5$ ./gyre_force 4u182030_force.in
gyre_force [5.2]
================
Compiler : GCC version 8.3.0
Compiler options : -I /usr/include/x86_64-linux-gnu -I /home/ubuntu64/software/mesasdk/include -march=sandybridge -mmmx -mno-3dnow -msse -msse2 -msse3 -mssse3 -mno-sse4a -mcx16 -msahf -mno-movbe -mno-aes -mno-sha -mpclmul -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-sgx -mno-bmi2 -mno-pconfig -mno-wbnoinvd -mno-tbm -mavx -mno-avx2 -msse4.2 -msse4.1 -mno-lzcnt -mno-rtm -mno-hle -mno-rdrnd -mno-f16c -mno-fsgsbase -mno-rdseed -mno-prfchw -mno-adx -mfxsr -mxsave -mxsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf -mno-prefetchwt1 -mno-clflushopt -mno-xsavec -mno-xsaves -mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi -mno-avx5124fmaps -mno-avx5124vnniw -mno-clwb -mno-mwaitx -mno-clzero -mno-pku -mno-rdpid -mno-gfni -mno-shstk -mno-avx512vbmi2 -mno-avx512vnni -mno-vaes -mno-vpclmulqdq -mno-avx512bitalg -mno-movdiri -mno-movdir64b --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=3072 -mtune=sandybridge -O2 -std=f2008 -ffpe-summary=none -finit-real=snan -fbacktrace -fmax-errors=25 -ffpe-trap=invalid,overflow,zero -fopenmp
OpenMP Threads : 2
Input filename : 4u182030_force.in
Model Init
==========

Reading from MESA file
File name profile13.data.GYRE
File version 1.01
Read 513 points
No need to add central point

Mode Search
===========

Mode parameters
l : 2
m : 0

Building frequency scan
added scan interval : 0.4845E-06 -> 0.1454E-05 (100 points, LINEAR)

Building x grid
Found inner turning points, x range 0.0000 -> 0.0001
Adding 260550 inner point(s)
Adding 909551 global point(s) in iteration 1
Adding 31850 global point(s) in iteration 2
Adding 3 global point(s) in iteration 3
Adding 0 global point(s) in iteration 4
Final grid has 1 segment(s) and 1202467 point(s):
Segment 1 : x range 0.0000 -> 1.0000 (1 -> 1202467)

Killed

It seems that gyre_force run out of memory. I attached the files i use in the running, and hope anyone can give me any suggestion. Thank you for any help in advance.

Best Regards
Chen

Re: Why my running be killed?

Posted: Mon Jan 27, 2020 9:17 am
by rhtownsend
Hi Chen --

Looking at the output you posted, it seems you are looking for modes in a dimensionless frequency interval 0.4845E-06 -> 0.1454E-05. These very low frequencies correspond to very high-order g modes. In order to resolve the spatial oscillations of these modes, GYRE attempts to create a very fine spatial grid. Unfortunately, your computer does not have enough memory to hold this grid, hence the program crashes.

cheers,

Rich

Re: Why my running be killed?

Posted: Tue Jan 28, 2020 9:34 am
by cdd
Hi Rich,

I run this with dimesionless frequency range and can get needed frequency successfully. So thank you for your reply and help very much!

Best Wishes
Chen

Re: Why my running be killed?

Posted: Wed Jan 29, 2020 4:51 pm
by joelongjiamian
For what it's worth, I'm also running into memory issues from remeshing the grid even for computing radial p-modes (so no g-mode mixing expected). I can confirm that increasing the minimum frequency of the search interval relieves the memory pressure (I use Δν/10 as the lower bound of the interval, which has been working fairly decently).