Ocean Modeling Discussion

ROMS/TOMS

Search for:
It is currently Wed Jul 18, 2018 3:07 am




Post new topic Reply to topic  [ 8 posts ] 

All times are UTC

Author Message
PostPosted: Sun Jul 08, 2018 5:32 pm 
Offline

Joined: Wed Jun 27, 2018 9:51 pm
Posts: 7
Location: Tenerife
Hello everyone.

I have configured ROMS with Upwelling. I'm running ocean_benchmark3.in and it gives me an error.

Code:
ROMS/TOMS - Output NetCDF summary for Grid 01:

 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 have looked for solutions to similar errors, but I can not find the fault. Attached the complete log of the execution in case someone can guide me.

Thank you very much for your time.


Attachments:
out.log [30.54 KiB]
Downloaded 1 time
Top
 Profile  
Reply with quote  
PostPosted: Sun Jul 08, 2018 8:03 pm 
Offline
User avatar

Joined: Wed Jul 02, 2003 5:29 pm
Posts: 3451
Location: IMS/UAF, USA
I managed to run BENCHMARK3 for the requested 200 steps. One difference I see - mine:
Code:
 Header file   : benchmark.h

yours:
Code:
 Header file   : upwelling.h\

You need to recompile with the BENCHMARK options turned on.


Top
 Profile  
Reply with quote  
PostPosted: Mon Jul 09, 2018 9:30 am 
Offline

Joined: Wed Jun 27, 2018 9:51 pm
Posts: 7
Location: Tenerife
Thank you very much Kate.

Indeed, I ran ocean_benchmark3.in compiling first with benchmark.h instead of upwelling.h, and the following result came out:
Code:
ROMS/TOMS: DONE... Monday - July 9, 2018 - 11:24:59 AM

I'm learning and I'm a little lost yet. If I compile with the Header file upwelling.h, what Input Script can I use?

Thank you so much for everything.


Top
 Profile  
Reply with quote  
PostPosted: Mon Jul 09, 2018 3:14 pm 
Offline
User avatar

Joined: Wed Jul 02, 2003 5:29 pm
Posts: 3451
Location: IMS/UAF, USA
You can use ocean_upwelling.in.


Top
 Profile  
Reply with quote  
PostPosted: Tue Jul 10, 2018 6:00 pm 
Offline
User avatar

Joined: Wed Jul 02, 2003 5:29 pm
Posts: 3451
Location: IMS/UAF, USA
Back to the benchmark3 case, I got it to run with gfortran. However, with ifort, I get:
Code:
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source             
oceanG             0000000001E8B685  Unknown               Unknown  Unknown
oceanG             0000000001E892A7  Unknown               Unknown  Unknown
oceanG             0000000001E373F4  Unknown               Unknown  Unknown
oceanG             0000000001E37206  Unknown               Unknown  Unknown
oceanG             0000000001DE54A6  Unknown               Unknown  Unknown
oceanG             0000000001DE90A0  Unknown               Unknown  Unknown
libpthread.so.0    00007FE027B177E0  Unknown               Unknown  Unknown
oceanG             0000000001BD7A74  mp_exchange_mod_m        1544  mp_exchange.f90
oceanG             0000000000C33109  ini_fields_mod_mp         252  ini_fields.f90
oceanG             0000000000C19938  ini_fields_mod_mp          65  ini_fields.f90
oceanG             00000000006AE853  main3d_                   154  main3d.f90
oceanG             000000000040D70E  ocean_control_mod         181  ocean_control.f90
oceanG             000000000040BFF7  MAIN__                    108  master.f90
oceanG             000000000040B88E  Unknown               Unknown  Unknown
libc.so.6          00007FE0266D5D1D  Unknown               Unknown  Unknown
oceanG             000000000040B769  Unknown               Unknown  Unknown
The line in question is:
Code:
1543       CALL wclock_on (ng, model, 61, 1473,                              &
1544      &                "ROMS/Utility/mp_exchange.F"//":mp_exchange3d")
Does anyone else get the same result?

By the way, I had to comment out this line in Compilers/Linux-ifort.mk:
Code:
FFLAGS += -Wl,-no_compact_unwind


Top
 Profile  
Reply with quote  
PostPosted: Wed Jul 11, 2018 6:33 am 
Offline

Joined: Wed Jun 27, 2018 9:51 pm
Posts: 7
Location: Tenerife
Hello Kate.

I ran benchmark3 case with Ifort and I did not get any errors. Do you want some configuration file to happen to you?


Top
 Profile  
Reply with quote  
PostPosted: Wed Jul 11, 2018 3:07 pm 
Offline
User avatar

Joined: Wed Jul 02, 2003 5:29 pm
Posts: 3451
Location: IMS/UAF, USA
If we're both using the same ROMS trunk code, then maybe it's something in the version of ifort I'm using:
Code:
chinook04 186% which mpif90
/opt/scyld/openmpi/1.10.7/intel/bin/mpif90
chinook04 187% which ifort
/usr/local/pkg/compiler/ifort/2016.3.210-GCC-5.4.0-2.26/compilers_and_libraries_2016.3.210/linux/bin/intel64/ifort


Top
 Profile  
Reply with quote  
PostPosted: Thu Jul 12, 2018 7:45 am 
Offline

Joined: Wed Jun 27, 2018 9:51 pm
Posts: 7
Location: Tenerife
That is my version:
Code:
$ which mpif90
/opt/cesga/intel/2017/impi/2017.4.239/bin64/mpif90
$ which ifort
/opt/cesga/intel/2017/compilers_and_libraries_2017.5.239/linux/bin/intel64/ifort


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 8 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group