[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 960612: ncgen

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 960612: ncgen
  • Date: Wed, 12 Jun 1996 11:33:56 -0600
>Organization: PNNL
>Keywords: 199606120126.AA17210

Connor,

> Thanks for your rapid reply!  I have a summer student working with me,
> Brian Ermold, and he is currently using my mail account.  We are running
> ncdump.exe and ncgen.exe on a Pentium running Win95.  We have downloaded
> both the older 16-bit versions and the 32-bit versions.  We also have
> nctest.exe, but I'm not really sure of its use.
> 
> Ultimately, we will be using the Matlab mexcdf interface on the Pentium.
> I'n not sure if you'll remember, but I had some difficulty using the mexcdf
> interface with the Mac version of Matlab.  This is all taken care of now
> though, the Mac version of mexcdf works great now.  Of course, once I got
> that working I was moved from the Mac platform to a Win95 platform on this
> new Pentium.  So back to square one...
> 
> Before using the mexcdf interface, I wanted to have a means of validating
> its performance, so I asked Brian to create an ascii dump of an existing
> netcdf file.  I told him we could verify the consistency of ncgen and
> ncdump by feeding the output of ncdump back into ncgen, ultimately creating
> a netcdf file duplicating the original content.  We have tried to do this
> for a couple of netcdf datafiles and have not had any luck.  In one case we
> get a "string to long" error.  From the line number indicated in the error
> message, it seems to correspond to an attempt to read a string 1440
> characters long.  In another case, we get an "unable to parse" message.
> The line indicated does not look suspicious to me.  Everything looks
> syntactically correct, quotes are properly closed, delimiters seem fine,
> etc..
> 
> I will have Brian ftp the ncdump generated output to you, if you would
> provide us with a destination.  Russ, thanks again for your assistance.

Try using anonymous FTP to put it in the incoming/russ/ directory of
ftp.unidata.ucar.edu.

If this doesn't work, I'll have to wait until sour system administrator does
whatever else is needed to permit anonymous downloads.

--Russ