array scalars%sc_w is out of range?

Report or discuss software problems and other woes

Moderators: arango, robertson

Post Reply
Message
Author
FengZhou
Posts: 52
Joined: Wed Apr 07, 2004 10:48 pm
Location: 2nd Institute of Oceanography,SOA

array scalars%sc_w is out of range?

#1 Unread post by FengZhou »

Hi, all,

I just tried ROMS3 and compiled the codes successfully with Upwelling case and a realistic case. But there is an error during executing the latter. The message is :

0: Subscript out of range for array scalars%sc_w (set_scoord.f90: 49)
subscript=0, lower bound=0, upper bound=-1, dimension=1



my set-up is
5.0000E+00 theta_s S-coordinate surface control parameter.
4.0000E-01 theta_b S-coordinate bottom control parameter.
4.000 Tcline S-coordinate surface/bottom layer width (m) used
in vertical coordinate stretching.
While in ROMS2.2, there is no such error.

Do you have any clue?

Thanks in advance!

zhou

User avatar
kate
Posts: 4091
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

#2 Unread post by kate »

ROMS 3 needs you to specify the grid dimensions in the input file: Lm, Mm, and N. What do you have for N?

FengZhou
Posts: 52
Joined: Wed Apr 07, 2004 10:48 pm
Location: 2nd Institute of Oceanography,SOA

#3 Unread post by FengZhou »

hi,Kate,

Thanks for your reply.
My grid dimension is as following( need only to input into External/byesea.h in Roms3 ?):
Lm == 167 ! Number of I-direction INTERIOR RHO-points
Mm == 243 ! Number of J-direction INTERIOR RHO-points
N == 30 ! Number of vertical levels

while in ROMS2, they were written in Modules/mod_param.F, right?

hmin = 8
hmax= 2500

zhou

User avatar
kate
Posts: 4091
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

#4 Unread post by kate »

This wasn't the PGI compiler, was it? I had something like that happen to me, where it forgot about the allocated memory. Anyone have a clue?

FengZhou
Posts: 52
Joined: Wed Apr 07, 2004 10:48 pm
Location: 2nd Institute of Oceanography,SOA

#5 Unread post by FengZhou »

Yes, I use PGI compiler.

zhang
Posts: 27
Joined: Fri Mar 11, 2005 9:17 pm
Location: Woods Hole Oceanographic Institution

#6 Unread post by zhang »

which version of pgi are you using?

User avatar
kate
Posts: 4091
Joined: Wed Jul 02, 2003 5:29 pm
Location: CFOS/UAF, USA

#7 Unread post by kate »

I have PGI 7.0.2 and see this with my most complex domain. Upwelling runs fine, as do all three sizes of Benchmark. Sorry I haven't pushed on it further, but we've had Pathscale and Sunstudio longer and I've got other issues to solve. In the debugger, I can see the memory for scalars%sc_w where it gets allocated, then it's not there later, when trying to write to it the first time.

FengZhou
Posts: 52
Joined: Wed Apr 07, 2004 10:48 pm
Location: 2nd Institute of Oceanography,SOA

#8 Unread post by FengZhou »

zhang wrote:which version of pgi are you using?
my pgi is 7.0.3.

other information:
Model Input Parameters: ROMS/TOMS version 3.0
Wednesday - January 30, 2008 - 3:19:38 PM
-----------------------------------------------------------------------------

Bohai-YellowSea-EastChinaSea, 1/12 degree

Operating system : Linux
CPU/hardware : i686
Compiler system : pgi
Compiler command : mpif90
Compiler flags : -g -C -Mfree

FengZhou
Posts: 52
Joined: Wed Apr 07, 2004 10:48 pm
Location: 2nd Institute of Oceanography,SOA

#9 Unread post by FengZhou »

Hi, all,

problem is probably fixed. I forgot to define the nudging block for the realistic case. Its running just by undefining the nudging items. Now I am tracking on...

Thank you all.

Post Reply