possble a little bug in varinfo.dat

Bug reports, work arounds and fixes

Moderators: arango, robertson

Post Reply
Message
Author
leon
Posts: 78
Joined: Mon Mar 03, 2008 4:14 am

possble a little bug in varinfo.dat

#1 Unread post by leon »

In file "varinfo.dat",

Code: Select all

'river_dye_'                                       ! Input
  'river runoff dye concentration'
  'kilogram meter-3'                               ! [kg/m3]
  'river_dye, scalar, series'
  'ocean_time'
  'idRtrc(inert(i))'
  'nulvar'
  1.0d0
I think the

Code: Select all

"ocean_time"
should be

Code: Select all

"river_time"
. Am I right?

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

Re: possble a little bug in varinfo.dat

#2 Unread post by kate »

Set it how you need it to be set for your input files. I've had files with both bio_time and ocean_time and had to change the bio variables accordingly. varinfo.dat is a tool for you to use and modify.

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

Re: possble a little bug in varinfo.dat

#3 Unread post by wilkin »

The name of the time variable associated with any particular data variable in a ROMS netcdf file can be set in a number of ways. These are documented in WikiROMS at
https://www.myroms.org/wiki/index.php/varinfo.dat
and in my posting at the end of thread
viewtopic.php?f=17&t=1816&p=6528&hilit= ... .dat#p6528

So the Vinfo(5) value of "river_time" here is not a bug - simply a default. My personal recommendation is to always overrule the varinfo.dat default by assigning a "time" attribute for every variable in the netcdf file - this avoids any ambiguity.
John Wilkin: DMCS Rutgers University
71 Dudley Rd, New Brunswick, NJ 08901-8521, USA. ph: 609-630-0559 jwilkin@rutgers.edu

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

Re: possble a little bug in varinfo.dat

#4 Unread post by kate »

wilkin wrote:My personal recommendation is to always overrule the varinfo.dat default by assigning a "time" attribute for every variable in the netcdf file - this avoids any ambiguity.
This is the cleanest way to go. However, depending on how you write your attributes in the NetCDF file, you may end up with a null character at the end of the string. Fortran doesn't know to make that go away before doing the string comparison (or we haven't taught ROMS that yet).

Post Reply