Nan,
Because the potential set of input unit strings to both packages is
infinite, I concentrated on trying to keep the interpretation algorithm
in the UDUNITS-2 package compatible with that of the UDUNITS-1 package
so that the UDUNITS-2 package would interpret any string the same way
the UDUNITS-
Jonathan Gregory wrote:
Dear Steve et al.
We can distinguish udunits-2 as a standard for units strings, and udunits-2
as software. If we say that CF uses udunits-2 as its reference, programs in
Fortran can still use udunits-1 to process the units strings, in nearly all
cases, though obviously a
Steve,
I just tried adding u as a prefix, and it certainly worked (although I
also can't say if it would have any unintended consequences, I only use
a small set of unit strings).
I don't use Fortran personally, so a lack of a Fortran interface
wouldn't be a problem for me. Of course, we wou
Dear Steve et al.
We can distinguish udunits-2 as a standard for units strings, and udunits-2
as software. If we say that CF uses udunits-2 as its reference, programs in
Fortran can still use udunits-1 to process the units strings, in nearly all
cases, though obviously a ununits-2 Fortran interfac
Andrew,
The "u" prefix can be added to the UDUNITS-2 database by inserting the line
u
in the set of other "symbol" definitions for the value "1e-6" in the
database file "$(prefix)/share/udunits/udunits2-prefixes.xml".
At this time, however, I can't say whether or not doing so will ha
Hi Steve -
Are all the terms in the new vocabulary backwards compatible, other
than non-ASCII characters and log units?
I just spent some time looking on the unidata web site to see if I could
find any information on changes to basic units names - additions or
otherwise. I'd thought there migh
Steve,
The UDUNITS-1 library had a bug in it. The bug was that "g" was
interpreted as meaning "gravity" (i.e., "standard_free_fall") rather
than "gram". This was corrected in version 1.12.10 of the UDUNITS-1
package, which was released on 2009-09-17.
The UDUNITS-2 package did not have this bug
Andrew,
> I'm running into some problems regarding units in CF-compliant files.
> Up until now I've been using udunits 1 to check units, but I recently
> tried the CF checker which uses udunits2. There are some unit strings
> which are valid in one but not the other. In particular, I am dealing
>
