[Thread Prev][Thread Next][Index]

RE: Error writing CDF file



Steve Hankin pointed out that I should be using the file command, since
that's for ASCII files.  True enough, but I'd already trialed-and-errored it
using use.  Here's how I did that...maybe you can see my error. (I get no
Ferret errors with this, but the resulting .nc file has an undefined L axis
"..." when I want multiple time steps.

use nov50-mar51-ndjfm-t100.nc
SAVE/clobber/title="T100 NDFFM for 1950-2000"/file=nov-mar-ltm-1950-2000.nc
t100
CANCEL DATA nov50-mar51-ndjfm-t100
!*********************************
use nov51-mar52-ndjfm-t100.nc
SAVE/append/file="/research/NDJFM/NetCDF/nov-mar-ltm-1950-2000.nc" t100
CANCEL DATA nov51-mar52-ndjfm-t100
!*********************************
use nov52-mar53-ndjfm-t100.nc
SAVE/append/file="/research/NDJFM/NetCDF/nov-mar-ltm-1950-2000.nc" t100
CANCEL DATA nov52-mar53-ndjfm-t100

...and so on through each annual NDJFM file.  Each of these annual files do
not have the L axis defined.  It has a "...".  They are created with an @ave
transform.  Could this be a problem?  How can I create a NetCDF file using a
@ave transform and have a defined L axis?

Any assistance would be appreciated.  Being stuck is UN-FUN!

Bruce



Bruce W. Ford
---------------------------
http://www.EverythingDulcimer.com
"The Internet Home for Dulcimer Enthusiasts"

Spread the Word!

-----Original Message-----
From: Steve Hankin [mailto:Steven.C.Hankin@noaa.gov]
Sent: Monday, July 21, 2003 12:34 PM
To: Bruce W. Ford
Cc: Ansley Manke
Subject: Re: Error writing CDF file


Hi Bruce,

Are you sure that you should be reading a file named *.nc with a FILE
command.  A .nc ending usually indicates a netCDF file -- which should be
opened with a USE command (and does not require you to specify a GRID
definition.)  The FILE command is for reading ASCII (or IEEE binary) files.

(If this helps you to find a solution please post a brief summary to
ferret_users to close the discussion.)

    - steve

===============

"Bruce W. Ford" wrote:

> Despite me following the Ch 10 Sec 2 example 3 (Writing a multiple time
> axis CDF file) in the documentation with the following code:
>
> DEF AXIS/x=100e:70w:1 xaxis
> DEF AXIS/y=20s:65n:1 yaxis
> DEF AXIS/t=1:1:1 taxis1
> DEF GRID/x=xaxis/y=yaxis/t=taxis1 grid1
> FILE/GRID=grid1/VAR="t100" nov50-mar51-ndjfm-t100.nc
> SAVE/clobber/title="T100 NDFFM for
> 1950-2000"/file=nov-mar-ltm-1950-2000.nc t100
> CANCEL DATA nov50-mar51-ndjfm-t100
> !*********************************
> DEF AXIS/t=2:2:1 taxis1
> DEF GRID/t=taxis1 grid1
> FILE/GRID=grid1/VAR="t100"
> "/research/NDJFM/NetCDF/nov51-mar52-ndjfm-t100.nc"
> SAVE/title="T100 NDFFM for
> 1950-2000"/file="/research/NDJFM/NetCDF/nov-mar-ltm-1950-2000.nc"/append
> t100
> CANCEL DATA nov51-mar52-ndjfm-t100
>
> I get this error with the first write attempt:
>
> > SAVE/clobber/title="T100 NDFFM for
> > 1950-2000"/file=nov-mar-ltm-1950-2000.nc t100
> > Last or next-to-last record read:
> > CDF: Success
> >  **TMAP ERR: Last or next-to-last record read:
> > CDF
> >              Last or next-to-last record read:
> > CDF
> >              Data set: ./nov50-mar51-ndjfm-t100.nc
> >              Data file: ./nov50-mar51-ndjfm-t100.nc
> > LIST/FORMAT=CDF/clobber/title="T100 NDFFM for
> > 1950-2000"/file=nov-mar-ltm-1950-2000.nc t100
> > Command file, command group, or REPEAT execution aborted
>
> This could have something to do with the way the NDJFM means were
> calculated (with the @ave).  When I show data, I get:
>
> > yes? show data
> >      currently SET data sets:
> >     1> ./nov50-mar51-ndjfm-t100.nc  (default)
> >  name     title                             I         J
> > K         L
> >  T100     T100                             1:191     1:86
> > ...       1:1
>
> Help...I'm at my Ferret wits end again.
>
> Bruce

--

Steve Hankin, NOAA/PMEL -- Steven.C.Hankin@noaa.gov
7600 Sand Point Way NE, Seattle, WA 98115-0070
ph. (206) 526-6080, FAX (206) 526-6744



[Thread Prev][Thread Next][Index]

Dept of Commerce / NOAA / OAR / PMEL / TMAP

Contact Us | Privacy Policy | Disclaimer | Accessibility Statement