Problem reading input files

Report or discuss software problems and other woes

Moderators: arango, robertson

Post Reply
Message
Author
pmaccc
Posts: 39
Joined: Wed Oct 22, 2003 6:59 pm
Location: U. Wash., USA

Problem reading input files

#1 Post by pmaccc » Fri Sep 27, 2019 9:51 pm

I have an idealized simulation in which I am adding a complex river source condition. The goal is to make a boundary source/sink pattern that is like the mouth of an estuary with the usual tidally averaged two layer exchange flow. I am using preprocessing tools and a recent version or ROMS that I have successful run in many different cases. The problem is that this one hangs during initialization, right after reading the ocean_ini.nc and river.nc files, and the values from these files reported in the log file are consistent with what I put in them. At that point I expect that it will read the ocean_bry.nc file, which is there and created from the _ini file using well tested code. Instead it does nothing - no crash, no error message, no more log file entries. Any suggestions for how I might approach debugging this would be much appreciated.

Thanks,

Parker

User avatar
wilkin
Posts: 510
Joined: Mon Apr 28, 2003 5:44 pm
Location: Rutgers University
Contact:

Re: Problem reading input files

#2 Post by wilkin » Sun Sep 29, 2019 4:44 pm

ROMS usually reads meteorology surface forcing after rivers and before boundaries. Is this skipped in your case because of the idealized config?

Can you force ROMS to confirm it has opened the boundary file, say by giving in the wrong name in roms.in to trigger a 'file not found'. That was you know for sure it closed out the rivers file.

Do you have A LOT of point sources in the rivers file? Maybe you're hitting some limit.

Sometimes, compiling and running in serial gives more informative error messages when file I/O at start up is the issue.
John Wilkin: DMCS Rutgers University
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu

Post Reply