benchmark case running problem

Report or discuss software problems and other woes

Moderators: arango, robertson

Post Reply
Message
Author
ywang152
Posts: 20
Joined: Wed Mar 27, 2019 2:31 am
Location: Stevens Institute of Technology

benchmark case running problem

#1 Post by ywang152 » Thu May 09, 2019 4:41 pm

Dear all,

I have one problem when I run benchmark case with oceanM: It seems the "Header file" and "Header directory" showing in the output log file of running, are immutable... I pasted the content of it:
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Benchmark Test, Idealized Southern Ocean, Small Grid

Operating system : Linux
CPU/hardware : x86_64
Compiler system : gfortran
Compiler command : /opt/openmpi401/bin/mpif90
Compiler flags : -frepack-arrays -O3 -ffast-math -ffree-form -ffree-line-length-none -ffree-form -ffree-line-length-none -ffree-form -ffree-line-length-none

Input Script : ocean_benchmark1.in

SVN Root URL : https://www.myroms.org/svn/src/trunk
SVN Revision : 904M

Local Root : /home/ywang/roms/trunk
Header Dir : /home/ywang/roms/Projects/Upwelling
Header file : upwelling.h
Analytical Dir: /home/ywang/roms/Projects/Upwelling

''''''''''''''''''''''''''''''''''''''''''''''''''''''
After checking, I am sure the build.bash has the right path of $MY_PROJECT_DIR, and the $ROMS_APPLICATION is BENCHMARK, corresponding to benchmark.h. Please find attachment to see the build.bash file.
What I did was:
I finished compilation, which gave me the executable file oceanM, and run it with command: mpirun -np 4 oceanM ocean_benchmark1.in > test1_oceanM.log.
Then, I got blow up error after seconds:

Code: Select all

 Analytical header files used:

     ROMS/Functionals/ana_btflux.h
     ROMS/Functionals/ana_grid.h
     ROMS/Functionals/ana_initial.h
     ROMS/Functionals/ana_smflux.h
     ROMS/Functionals/ana_stflux.h
     ROMS/Functionals/ana_vmix.h
 Found Error: 01   Line: 350      Source: ROMS/Utility/close_io.F

 ROMS/TOMS - Blows up ................ exit_flag:   1


 MAIN: Abnormal termination: BLOWUP.
I saw someone got the same problem because the header file is not right, and I have the same mistake. But my re-compilation didn't work at all. Running the output oceanM keep showing the wrong header path and header file.
Thanks for your help in advance!

Best regards
Yifan
Attachments
test1_oceanM.log
(28.8 KiB) Downloaded 21 times
build.bash
(17.78 KiB) Downloaded 21 times

ywang152
Posts: 20
Joined: Wed Mar 27, 2019 2:31 am
Location: Stevens Institute of Technology

Re: benchmark case running problem

#2 Post by ywang152 » Thu May 09, 2019 6:41 pm

Hello everyone,

I would like to add some additional information:

I tried to compile and run benchmark case with oceanS and everything looked fine. It finished after 167 seconds. Also tried oceanG (compiled with the same build.bash file but opened "USE_DEBUG=on"), which was finished after 1600 seconds, with some error messages:

Code: Select all

[ywang@riis retest_Benchmark]$ mpirun -np 4 oceanG ocean_benchmark1.in > test1_oceanG.log

Program received signal 8 (SIGFPE): Floating-point exception.

Program received signal 8 (SIGFPE): Floating-point exception.

Program received signal 8 (SIGFPE): Floating-point exception.

Backtrace for this error:
  + /lib64/libc.so.6() [0x3adc632510]
  + function wclock_off_ (0x496C5D)
    at line 238 of file timers.f90
  + function __ocean_control_mod_MOD_roms_finalize (0x403C51)
    at line 245 of file ocean_control.f90

Backtrace for this error:
  + /lib64/libc.so.6() [0x3adc632510]
  + function wclock_off_ (0x496C5D)
    at line 238 of file timers.f90
  + function __ocean_control_mod_MOD_roms_finalize (0x403C51)
    at line 245 of file ocean_control.f90
  + in the main program
    at line 116 of file master.f90
  + /lib64/libc.so.6(__libc_start_main+0xfd) [0x3adc61ed1d]
  + in the main program
    at line 116 of file master.f90
  + /lib64/libc.so.6(__libc_start_main+0xfd) [0x3adc61ed1d]

Backtrace for this error:
  + /lib64/libc.so.6() [0x3adc632510]
  + function wclock_off_ (0x496C5D)
    at line 238 of file timers.f90
  + function __ocean_control_mod_MOD_roms_finalize (0x403C51)
    at line 245 of file ocean_control.f90
  + in the main program
    at line 116 of file master.f90
  + /lib64/libc.so.6(__libc_start_main+0xfd) [0x3adc61ed1d]
--------------------------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

  Process name: [[40721,1],2]
  Exit code:    5
--------------------------------------------------------------------------
The header path and header name problem didn't happen when I use oceanS and oceanG. It seems only when I try to run benchmark case with oceanM,the header path and name will be the same as that of Upwelling case. The error message got after running oceanG may be the clue.
I would be appreciated if anyone could give me some input. Thank you.

Best regards
Yifan

Post Reply