Re: multiNetCDF descriptor, LAS, and OpenDAP

[Matt Fulgo <Matt.Fulgo@xxxxxxxxxxxxxxx>]

I have tried all of the aforementioned solutions and none have worked.
However, I do believe that they have helped me narrow down the problem...

When I tried to execute the script by itself:
yes? go "jnls/std_initialize" "NCOMCCS/h002/expt_09.0/s3d" "1" "1"
"Salinity"
I received an error about the &FORMAT_RECORD, this was due to the
linux/Fortan 77 issues.  After fixing this and rerunning the script, I was
informed that the maximum datasets for a descriptor is 500 - I had 912.
(Does anyone know where this is set, as I will eventually need to fix
this?)  So now, I'm down to a dataset of one NetCDF file, receiving the
same error whether I run it though LAS or ferret and whether I use the
provided jnl or simply try loading the data myself.  Here are some of the
things that I have tried and the results:

yes? go "jnls/std_initialize" "NCOMCCS/h002/expt_09.0/s3d.des" "1" "1"
"Salinity"
 **TMAP ERR: non-existent or not on line yes? set data
"NCOMCCS/h002/expt_09.0/s3d"
             No files on-line from data set **TMAP ERR: non-existent or
not on line
             Data set: NCOMCCS/h002/expt_09.0/s3d.des No files on-line
from data set set data "NCOMCCS/h002/expt_09.0/s3d.des"  Data set:
NCOMCCS/h002/expt_09.0/s3d.des
Command file, command group, or REPEAT execution aborted

yes? set data
"http://supply.nrlssc.navy.mil/cgi-bin/nph-dods/NCOMCCS/h002/expt_09.0/nc/s3d/s3d.ncom.h002.090.nest1.20001001_00000000.nc";
 ** unknown netCDF error code: -31
is this a CDF file ?

yes? set data
"http://www.ferret.noaa.gov/cgi-bin/nph-dods/data/levitus_climatology.nc";
On Wed, 25 May 2005, Roland Schweitzer wrote:
 ** unknown netCDF error code: -31
is this a CDF file ?

The last two are rather puzzling.  Again,

Thanks for all your help,
-Matt

> Hi,
>
> I suspect that the problem lies with the environment which LAS uses to
> run Ferret.  Your las.xml configuration specifies the ".des" file with a
> relative path.  The environment that Ferret uses when run by LAS is
> specified in las/server/Ferret_config.pl.  I'm not an expert on how
> Ferret resolves relative path names, but one solution would be to
> include the full path name /blah/blah/NCOMCCS/h002/expt_09.0 in
> Ferret_config.pl in the FER_DESCR variable and refer to the file only by
> 's3d.des' in the data set configuration.
>
> Roland
>
> Matt Fulgo wrote:
>
> >Greeting all,
> >
> >I am trying to setup a dataset in LAS using a descriptor file.  The
> >dataset is separated to one file per variable per timestep.  After
> >configuring LAS and creating the des file, I get the following error from
> >LAS:
> >
> >Adding an acceptable error string: "*** NOTE: ".
> > 	NOAA/PMEL TMAP
> > 	FERRET v5.70
> > 	Linux(g77) 2.4.20 - 06/28/04
> > 	25-May-05 12:35
> >
> >yes? cancel mode verify
> >yes? cancel mode interp
> >yes? canc data/all
> >yes? go std_initialize "NCOMCCS/h002/expt_09.0/s3d.des" "1" "1" "Salinity"
> > **TMAP ERR: non-existent or not on line
> >             No files on-line from data set
> >             Data set: NCOMCCS/h002/expt_09.0/s3d.des
> >set data "NCOMCCS/h002/expt_09.0/s3d.des"
> >Command file, command group, or REPEAT execution aborted
> >
> >The descriptor file is as follows:
> >
> > &FORMAT_RECORD
> >     D_TYPE = ' MC',
> >     D_FORMAT = ' 1A',
> >     D_SOURCE_CLASS = 'MODEL OUTPUT',
> > /
> > &BACKGROUND_RECORD
> >      D_EXPNUM = '0001',
> >      D_TITLE = '',
> >      D_T0TIME = '01-Oct-2000 00:00:00.00',
> >      D_TIME_UNIT = 43200,
> >      D_TIME_MODULO = .FALSE.,
> > /
> > &MESSAGE_RECORD
> >      D_MESSAGE = ' ',
> >      D_ALERT_ON_OPEN = F,
> >      D_ALERT_ON_OUTPUT = F,
> > /
> > &EXTRA_RECORD
> > /
> > &STEPFILE_RECORD
> >       s_filename =
> >'http://supply.nrlssc.navy.mil/cgi-bin/nph-dods/NCOMCCS/h002/expt_09.0/nc/s3d/s3d.ncom.h002.090.nest1.20001001_00000000.nc',
> >       S_START = 0,
> >       S_END = 0,
> >       S_DELTA = 1,
> >       S_NUM_OF_FILES = 1,
> >       S_REGVARFLAG = ' ',
> > /
> > &STEPFILE_RECORD
> >       s_filename =
> >'http://supply.nrlssc.navy.mil/cgi-bin/nph-dods/NCOMCCS/h002/expt_09.0/nc/s3d/s3d.ncom.h002.090.nest1.20001001_12000000.nc',
> >       S_START = 1,
> >       S_END = 1,
> >       S_DELTA = 1,
> >       S_NUM_OF_FILES = 1,
> >       S_REGVARFLAG = ' ',
> > /
> > &STEPFILE_RECORD
> >       s_filename =
> >'http://supply.nrlssc.navy.mil/cgi-bin/nph-dods/NCOMCCS/h002/expt_09.0/nc/s3d/s3d.ncom.h002.090.nest1.20001002_00000000.nc',
> >       S_START = 2,
> >       S_END = 2,
> >       S_DELTA = 1,
> >       S_NUM_OF_FILES = 1,
> >       S_REGVARFLAG = ' ',
> > /
> >---------other 909 records not included------------
> > &STEPFILE_RECORD
> >       s_filename = '**END OF STEPFILES**'
> > /
> >
> >I have heard rumors of a 72 column limit for descriptor files, could this
> >have anything to do with the failure?  Any help is appreciated and
> >
> >Thanks in advance,
> >Matt
> >
> >
>
>
>