Re: [ferret_users] missing value for binary data and single to double conversion

To: Russ Fiedler <russell.fiedler@xxxxxxxx>

Subject: Re: [ferret_users] missing value for binary data and single to double conversion

From: Ryo Furue <furue@xxxxxxxxxx>

Date: Thu, 25 Aug 2016 12:18:19 +0900

Cc: ferret users <ferret_users@xxxxxxxx>

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=noaa-gov.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:x-original-sender:x-original-authentication-results:precedence :mailing-list:list-id:list-post:list-help:list-archive :list-unsubscribe; bh=JYhhDSxEiGg5IaGwz3Py3oYCVf1NsofXmw49UlJqbow=; b=qBouOFpdzBqRJhnvjRKTOhywnvSwXH9sqGT2fZ1nAJwc6uOgTN8CpOT4MM4aqeLHex O4RCan3x/LNyjYiqW4I7QGxZ1Zn/A60w5aRYSLJlFfHjvfnRf7KadGwoW/yCLI61vZVX 8nlOymyEO+8fynA2OkMsGeM0de20GcPXLwh1xUQcBHYJ3tXJBjFY1BIbZlJoGAtyhLKT qjjYtPI3YP9G8qLjJKghiBh4QaLvwSmPjhvvZzQvn8Yt7S39xkLO3kX6kajrR169UlVF yOdwU2QwA4XhsohDftf3UBtznCamGkBvkSr1btH/g82P+i8Wtb6Svsd4kXxJI1ORU/tm JATg==

In-reply-to: <57BE36E0.6040701@csiro.au>

List-archive: <https://groups.google.com/a/noaa.gov/group/ferret_users/>

List-help: <https://support.google.com/a/noaa.gov/bin/topic.py?topic=25838>, <mailto:ferret_users+help@noaa.gov>

List-id: <ferret_users.noaa.gov>

List-post: <https://groups.google.com/a/noaa.gov/group/ferret_users/post>, <mailto:ferret_users@noaa.gov>

List-unsubscribe: <mailto:googlegroups-manage+809428289204+unsubscribe@googlegroups.com>, <https://groups.google.com/a/noaa.gov/group/ferret_users/subscribe>

Mailing-list: list ferret_users@xxxxxxxx; contact ferret_users+owners@xxxxxxxx

References: <CAEwQpaK_LFfQhZESUo=T05R2KTswanAb1HFjx6=ZDj_fpxw=-g@mail.gmail.com> <57BE36E0.6040701@csiro.au>

Sender: owner-ferret_users@xxxxxxxx

Hi Russ,

You can now (at least of v4.2.1.1) specify the precision of output in ncdump with the "-p float_digits[,double_digits]" option.

ncdump -h -p 9,17 file.nc

should get you full precision.

Thanks! That suggests that ncdump should default to -p 9,17. Remember gfortran displays 17 digits? That decision by the implementers of gfortran was made (I guess) not to lose a single bit when writing to ascii and reading it again. ncdump and ncgen are conceptual counterparts of ascii WRITE and READ of Fortran. (I already wrote such a message as this to unidata.)

Regards,

Ryo