Ocean Modeling Discussion

ROMS/TOMS

Search for:
It is currently Fri Nov 24, 2017 3:58 am




Post new topic Reply to topic  [ 8 posts ] 

All times are UTC

Author Message
PostPosted: Mon Feb 16, 2015 7:59 pm 
Offline

Joined: Wed Feb 03, 2010 6:59 pm
Posts: 90
Location: Universidad Autonoma de Baja California Sur
Hello All

I'm having a problem by the time i try to run ROMS, this is what i got

ggv@SNI01 ~/roms/Projects/Leo $ ./oceanO <leo.in >out00.txt

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x7FACD9F6A7D7
#1 0x7FACD9F6ADDE
#2 0x7FACD96ACD3F
#3 0x414C37 in read_fltpar_
#4 0x409155 in inp_par_
#5 0x403699 in __ocean_control_mod_MOD_roms_initialize
Segmentation fault

I attach my floats file

I really appreciate your help on this

Thanks in advance


Attachments:
Leofloats.in [13.27 KiB]
Downloaded 37 times
Top
 Profile  
Reply with quote  
PostPosted: Tue Feb 17, 2015 9:14 pm 
Offline
User avatar

Joined: Tue Jul 01, 2003 4:12 am
Posts: 478
Location: NIWA
I suggest you get into read_fltpar with a debugger or (my choice) add some WRITE statements.

It would be helpful if your compiler told you the line number at which the error occurred. Most compilers can be persuaded to do this. For Gfortran (on most platforms) you just need to set the USE_DEBUG make variable.


Top
 Profile  
Reply with quote  
PostPosted: Wed Feb 18, 2015 4:11 pm 
Offline

Joined: Wed Feb 03, 2010 6:59 pm
Posts: 90
Location: Universidad Autonoma de Baja California Sur
Hello Mike

Thanks for your comment, acrually we have solve that problem, what we are facing now iare the DT and dt, time steps. We are running on a large domain (figure atteched) and we can not fine aa adecuate pair of the to make Roms run, it blows up at the very start, here i attach the file too (out00.txt).

Thanks in advance Mike


Attachments:
Figure.docx [1.11 MiB]
Downloaded 43 times
out00.txt [38.68 KiB]
Downloaded 33 times
Top
 Profile  
Reply with quote  
PostPosted: Wed Feb 18, 2015 5:42 pm 
Offline
User avatar

Joined: Wed Jul 02, 2003 5:29 pm
Posts: 3254
Location: IMS/UAF, USA
I suggest you set NINFO to 1 so that diag can check for extreme values every timestep. Then you can perhaps see what is going bad before the whole grid is full of NaN. When it saves a record to the restart file like that, look at it with your favorite viewer, ncview or whatever you like. Where is it blowing up? Perhaps you should also look at your boundary and forcing files. What are you doing with the ZCLIMATOLOGY?


Top
 Profile  
Reply with quote  
PostPosted: Fri Aug 14, 2015 10:55 pm 
Offline

Joined: Wed Mar 18, 2015 3:40 pm
Posts: 43
Location: Universidade Federal Fluminense
Hello Every one. I am having the the following error error message (see the log file in attachment) ; my compiler is gfortran;
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Any help please


Attachments:
sofala.log [11.41 KiB]
Downloaded 35 times
Top
 Profile  
Reply with quote  
PostPosted: Fri Aug 14, 2015 11:13 pm 
Offline
User avatar

Joined: Wed Jul 02, 2003 5:29 pm
Posts: 3254
Location: IMS/UAF, USA
Quote:
#4 0x4C9809 in check_multifile_
#5 0x433911 in initial_
Can you show us the part of your ocean.in that refers to the boundary, climatology and forcing files? Which version of ROMS is this, exactly?


Top
 Profile  
Reply with quote  
PostPosted: Tue Aug 18, 2015 3:01 am 
Offline

Joined: Wed Mar 18, 2015 3:40 pm
Posts: 43
Location: Universidade Federal Fluminense
Dear Kate
thank you for replying.my ROMS version 3.7.
I send in attachment my ocean.in

Kindest Regards


Attachments:
ocean.in [116.92 KiB]
Downloaded 34 times
Top
 Profile  
Reply with quote  
PostPosted: Wed Aug 19, 2015 4:44 pm 
Offline
User avatar

Joined: Wed Jul 02, 2003 5:29 pm
Posts: 3254
Location: IMS/UAF, USA
Code:
     NFFILES ==                           ! number of unique forcing files

     FRCNAME ==                ! forcing file 1, grid 1
I suggest you put NFFILES == 1 even if you don't have any files. Also, provide some bogus filename for the forcing file. ROMS will allocate the FRC object to have NFFILES elements in it, so I don't know what it would do with a blank there. Nothing good, obviously. Also, you want a filename for FRCNAME just for error reporting. If ROMS thinks it needs a forcing file, it will try to open it, and the error is more meaningful with "unable to open file: some_bogus_forcing.nc" than with a blank filename.


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 1 guest


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:  
Powered by phpBB® Forum Software © phpBB Group