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

20000614: Several questions



Chris,

To increase the default number of grids in a decoded grid file, use the -m
option to dcgrib (such is shown for in the examples). For example -m 5000
will allow up to 5000 grids in a file. This number can be up to 10000 max.

With the addition of the 54 and 60 hour eta grids you will need this for the 
211 grids.
You definitely need to use it for the 212 grids.

1394 was about the number of grids before the addition of the extra forecast 
times
in the 211. Now I have today:
 GRID FILE: $MODEL/2000061512_eta211.gem                                        
                                                            

 GRID NAVIGATION: 
     PROJECTION:          LCC                 
     ANGLES:                25.0   -95.0    25.0
     GRID SIZE:           93  65
     LL CORNER:              12.19   -133.46
     UR CORNER:              57.29    -49.38

 GRID ANALYSIS BLOCK: 
      UNKNOWN ANALYSIS TYPE 

 Number of grids in file:  1704


Secondly, your Xvfb session is the same as any other display, where yur can only
have 255 colors max- and if you have multiple scripts running, then you will 
have to contend
with their color requests. Any hung gf processes will be eating colors as well.


Thirdly, you can use the environmental variable GEMCOLTBL to define a different 
color table 
than the default coltbl.xw (remember that this only has an effect for displays 
that you aren't
running ntl on). Recall, that we set your color #0 in coltbl.xw to be white for 
your background.
You can create a dupplicate table and set the color back to black. Then make
sure that your environmental variable is set when you run your radar gif 
generation.

Steve Chiswell
Unidata User Support


>From: address@hidden (Chris Hennon)
>Organization: UCAR/Unidata
>Keywords: 200006150104.e5F14bT05107

>Hello.
>
>I've got a few questions regarding both data receipt and gempak:
>
>1)  For the last couple of weeks, both my eta and ngm grids have been
>missing whole forecast periods.  For example, my eta file for 12z today
>was missing both the 42 and 48 hour fields.  I realize that some of these
>may be due to data problems upstream, but this has been a consistent
>theme.  When I run "gdinfo" on the grid, I noticed that the max number of
>grids is 1500, and my current eta grid has 1394:
>
> GEMPAK-GDINFO>r
>
> GRID FILE: 2000061412_eta_grid211.gem                                        
>       
>
> GRID NAVIGATION: 
>     PROJECTION:          LCC                 
>     ANGLES:                25.0   -95.0    25.0
>     GRID SIZE:           93  65
>     LL CORNER:              12.19   -133.46
>     UR CORNER:              57.29    -49.38
>
> GRID ANALYSIS BLOCK: 
>      UNKNOWN ANALYSIS TYPE 
>
> Number of grids in file:  1394
>
> Maximum number of grids in file:   1500
>
>Including the 42 and 48 hour grids would have put it over the limit.  If
>this was part of the problem, would I have to modify the dcgrib decoder to
>increase the max number of grids?  Is there possibly another reason why I
>haven't been getting all of the grids?
>
>2)  I'm running MANY scripts via the cron.  I have installed Xvfb and have
>sent all of the jobs to that display (1.) to eliminate color conflicts
>with the console.  Despite this, I've been having problems with color
>allocation for some of my satellite imagery scripts.  It seems to be a
>random type thing, and affects approximately 30% of all the images.  The
>log file always says:
>
>[GEMPLT -46]  NCLRAL - Can not allocate read/write colors.
>[GEMPLT -64]  NCBALOC  - Color bank not allocated.
>
>and a blank map is produced.  I could run the same script 10 times in a
>row and this error would only occur 2-3 times.  Any ideas on what's going
>on here?  This doesn't seem to occur with my other image producing
>scripts.  Do the satellite scripts compete with other concurrently running
>processes (i.e. other gempak scripts) for colors?
>
>3)  By default my background color for all of my plots is white.  However,
>I'd like to change my background color to black for my radar plots ONLY.
>Again, many scripts are being run at the same time.  If I try to run
>"gpcolor" to change my background color within the radar scripts, I assume
>that will change the background color to black for all of my other scripts
>which are currently running?  Is there a workaround?  How can I have a
>black background only for my radar plots?
>
>That's it.  Thanks!
>
>Chris
>
>