20020212: NMAP can't find data

Ruth,

NMAP2 will rely on the datatype.tbl file. NMAP has some additional
configuration tables in $GEMTBL/nmap. I find that the NMAP2 interface is
easier to use for the time selection widget for casestudies,
so let me start by assuming you will use that program.

The datatype.tbl file (as I package it here)  has a template for
ship data as:
SHIP         $GEMDATA/ship             YYYYMMDDHH_sb.gem 

Your ship data is in the $GEMDATA/ship directory which matches
the above template. But, you apparently have daily files. The
template above will be trying to match hourly files. You could
change the datatype.tbl template for daily files, or create
hourly files out of the daily files.

For model data, when you select the "grid" data type, NMAP2
prpvides a list of known models to search for from those referenced in
$GEMTBL/nmap/mod_res.tbl. Nogaps is one of the models found in 
the mod_res.tbl file for various restore "nts" products. WGen
you select "nogaps" in the data selection widget, NMAP2
then uses that grid file title to seatch datatype.tbl for
the template that will match that model.

The datatype.tbl file has:
NOGAPS       $MODEL                    YYYYMMDDHH_nogaps240.gem

Your files are called: YYYYMMDDHH_nogaps2.gem. The existing template
is based on the data being provided on grid #240 by FNMOC on
the IDD. Since your data does not match the template, it won't be found.
I presume your data is on grid #2 based on the file name. Your options are:

1) rename your files to match the supplied template

or

2) change the datatype.tbl template to match your files (if that
doesn't conflict with real-time data you might be getting from
FNMOC)

or most robust:
3) Add another NOGAPS template to the datatype.tbl file. Call it
NOGAPS2 (to signify nogaps on grid 2). Use the line identical to NOGAPS
keeping all spaces so that the columns line up, it would look like:
NOGAPS2      $MODEL                    YYYYMMDDHH_nogaps2.gem etc......

Then, add the "nogaps2" datatype to the various nts restore file entries
in $GEMTBL/nmap/mod_res.tbl that you want to be available with this
gridded data set. The next time you start NMAP2, it will search for
the models listed in mod_res.tbl, find nogaps2, and add it to
the selection widget.

For NMAP, to deal with the ship data, you would have to edit the template in
$GEMTBL/nmap/master.nmap since nmap was developed before the datatype.tbl 
functionality.

Steve Chiswell






>From: Ruth Platner <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200202122108.g1CL8px27211

>Hi,
>
>I'm having trouble getting NMAP or NMAP2 to find some of my data. NMAP
>finds some types of data, but not others, so I think there must be
>something wrong with the names of the path or files so that they don't
>match the $GEMTBL/config/datatype.tbl file for NMAP.
>
>In Gemenviron I have the following:
>
>   setenv GEMDATA   /bize/rlp/gempak
>   setenv OBS           $GEMDATA
>   setenv MODEL         $GEMDATA/model
>   setenv SAO           $GEMDATA/surface
>   setenv RAW_SAO       $GEMDATA/surface
>   setenv RAW_SYN       $GEMDATA/syn
>   setenv RAW_SB        $GEMDATA/sb
>
>the directory /bize/rlp/gempak contains these subdirectories:
>
>zephyros gempak 77% pwd
>/bize/rlp/gempak
>zephyros gempak 78% ls
>      model/         ship/      surface/   syn/       upperair/
>
>NMAP finds the data in directory surface which has files with names such
>as
>20010301_sao.gem  20010317_syn.gem  20010404_sb.gem   20010421_sao.gem
>
>and NMAP finds the data in syn which has files with names such as
>20010301_syn.gem  20010318_syn.gem  20010405_syn.gem  20010422_syn.gem
>
>But NMAP can not find the nogaps data in the model/nogaps directory.
>Examples of the names there are:
>2001040100_nogaps2.gem  2001041012_nogaps2.gem  2001042700_nogaps2.gem
>
>NMAP also cannot find data in the ship directory. The names there have
>this format:
>20010301_sb.gem  20010315_sb.gem  20010330_sb.gem  20010413_sb.gem
>
>I'm not sure if NMAP requires the structure of each data file name to
>follow exactly what is in $GEMTBL/config/datatype.tbl. There are small
>differences for the file names that NMAP can't find. The datatype.tbl
>has YYYYMMDDHH_sb.gem but my ship data doesn't have an hour in it's
>name. Should I make changes to datatype.tbl, or to my file names?
>Similarly, the nogaps data is listed in datatype.tbl as
>YYYYMMDDHH_nogaps240.gem, but our data is YYYYMMDDHH_nogaps2.gem.
>
>This is archived data that we've received from another source, it's not
>being created by our pqact configuration. We are able to run gempak on
>these files, the trouble is just getting NMAP to find the data.
>
>I'm running gempak.56e on Solaris.
>
>Thanks,
>
>Ruth
>
>
>
>