Output results wrong when NAVG==1 in the .in file

Bug reports, work arounds and fixes

Moderators: arango, robertson

Post Reply
Message
Author
CBian
Posts: 39
Joined: Mon Dec 28, 2009 4:01 pm
Location: Ocean University of China

Output results wrong when NAVG==1 in the .in file

#1 Unread post by CBian »

When I set NAVG ==1 in the .in file. The u,v results in output file ocean_avg.nc are not right. The u, v will accumulate with time-step.

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

Re: Output results wrong when NAVG==1 in the .in file

#2 Unread post by wilkin »

Yes, I recently had occasion to test this logic myself and the NAVG=1 case (if indeed that is logical?) gives inconsistent results. Values of NAVG > 1 work just fine.

Since NAVG = 1 is effectively a ROMS "history" record, or "snapshot", I think you can manage happily with the functionality of the code as it exists.
John Wilkin: DMCS Rutgers University
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu

Post Reply