Couldn't write average result

Discussion of how to use ROMS on different regional and basin scale applications.

Moderators: arango, robertson

Post Reply
Message
Author
shuwen
Posts: 10
Joined: Wed Dec 22, 2010 2:12 am
Location: University of Rhode Island

Couldn't write average result

#1 Unread post by shuwen »

Hi all,
Today I updated my ROMS version from 3.4 to 3.6, but when I tried to repeat an old case, it seems that with v3.6 I couldn't write out the average files.The log file always stopped at:

STEP Day HH:MM:SS KINETIC_ENRG POTEN_ENRG TOTAL_ENRG NET_VOLUME
C => (i,j,k) Cu Cv Cw Max Speed

0 0 00:00:00 3.863642E-03 1.838183E+04 1.838183E+04 1.766190E+15
(150,032,30) 1.036462E-02 8.008380E-03 0.000000E+00 9.310335E-01
DEF_HIS - creating history file, Grid 01: /home/mydir/ocean_his_0001.nc
WRT_HIS - wrote history fields (Index=1,1) into time record = 0000001
DEF_AVG - creating average file, Grid 01: /home/mydir/ocean_avg_0001.nc

You can tell there seems to be no error with the model set-up. But I found there is one more information I don't understand:
forrtl: severe (174): SIGSEGV, segmentation fault occurred roms

Moreover, with the v3.4, I can successfully get the monthly-averaged nc files. At first I thought it might relate to the data size for averaging, while after trying daily-average, 10day-average, the case always stopped at this point.
I am wondering would some one please give me a clue for the solutions?
Thanks for any reply in advance!

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

Re: Couldn't write average result

#2 Unread post by kate »

See this thread. Which compiler are you using? What version?

shuwen
Posts: 10
Joined: Wed Dec 22, 2010 2:12 am
Location: University of Rhode Island

Re: Couldn't write average result

#3 Unread post by shuwen »

Hi Kate,
Thanks for your reply! I am using ifort compiler system and the version is the newest 3.6 (just updated yesterday).
Actually now the average file could successfully be generated only if I don't defining 2D variables, i.e. ubar, vbar, zeta. That's really bizarre.

Post Reply