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

[IDD #TTR-495389]: Slow access to local datasets through ADDE

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: [IDD #TTR-495389]: Slow access to local datasets through ADDE
  • Date: Fri, 08 Feb 2008 10:51:13 -0700
Hi Samuel,

re:
> Thanks again.  I can leave the port configuration on Shu alone, but please
> try not to break anything.

I always try to not break things ;-)

> A few things I've noticed though:
> 
> I'll have to change around 60 datasets/directories for NIMAGE data.

Yup.  You will need to make changes both to the dataset definitions AND to
the LDM pqact processing.  The ADDE dataset changes should be very easy as
the DSSERVE commands that were run to create the datasets in the first place
should be available in ~mcidas/data/LSSERVE.BAT.  You can make a copy of
this file and make the changes to each dataset in the copy:

<as 'mcidas'>
cd $MCDATA
cp ~/data/LSSERVE.BAT MYSERVE.BAT
-- edit MYSERVE.BAT and make any/all changes needed to match revamped LDM
   pqact processing actions
batch.k MYSERVE.BAT

Please note that you can run BATCH (batch.k) over and over again until you
are satisfied with your definitions.

> I've started with the GOES-EAST 1km VIS (GINIEAST/GE1KVIS), and that seemed to
> work pretty well,

Very good.

> however, when I tried to access the "GINI 1km VIS East CONUS - 
> Today"(GINEAST/GE1KVIST)
> dataset I created using \CURDAY IDV runs out of memory, even when trying to 
> display
> a single image.  What's up with that?

The \CURDAY construct will have nothing to do with the loading of those images 
in the
IDV.  \CURDAY only helps to reduce the number of images that the server has to 
look
at to come up with a time-sorted list of files in the dataset.

The GINI 1km Vis images (East and West) are BIG.  Uncompressed they are on the
order of 17 MB each.  Loading the entire image into the IDV requires lots of 
memory,
so you may need to modify your IDV's startup to be able to use more memory.  
Details
of doing this and other things in the IDV are available in the IDV Users Guide 
and/or
online workshop materials.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: TTR-495389
Department: Support McIDAS
Priority: Normal
Status: Closed