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

20020131: Flakiness with a couple of things

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: 20020131: Flakiness with a couple of things
  • Date: Thu, 31 Jan 2002 15:40:24 -0700
Sounds like you may have too many files in a directory.

I have no trouble with garp sitting running for months....but I scour
to 60 (about 5 hours) products.

Garp, I believe is limited to 200 times in the time selection menu.

Steve

On Thu, 31 Jan 2002, Kevin Polston wrote:

> Steve,
>
> Got a couple of questions for you.  I have noticed recently when running NMAP2
> that if I try to display an SRM image from any site.......90% or more of the 
> time
> it causes NMAP2 to crash and disappear. I don't understand what would be 
> causing
> this unless it is a problem with the data in some way.  I used to be able to
> display SRM images with no problem and now it seems NMAP2 doesn't like it.  I 
> can
> display other products such as VIL and CR just fine.  Not only does it bomb 
> NMAP2
> but also I tried it with NSAT and the same thing happens.
>
> On a related note.....whenever I open up GARP to display something it usually
> works fine but if I leave it for longer than 5 minutes then GARP bombs out 
> (ie, it
> just shuts down or whatever and disappears off the screen). When I do a check 
> from
> a terminal window to see if that process is running I find that the process 
> is not
> running...... so for whatever reason that just bombs out the program too. But 
> it
> will display data and stay on screen for 3-5 minutes or so. If I am actively 
> using
> GARP and looking at different types of weather data then it seems like it will
> stay on the screen while I am working with it but,  for example, if I load a
> profiler time-height plot (or any other type of imagery for that matter) and 
> leave
> it for a few minutes...that's when it likes to bomb out.
>
> Maybe you have an idea as to why this happens but I don't. Any help is
> appreciated. Thanks.
>
> KP
>