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

20050729: GEMPAK - Inability to show/loop analysis grids.

Stonie,

In regard to the NEXR plot which uses the $NMAP_RESTORE/radar/nexr/n0r
restore file, comment out or remove the "GDATTIM=last" line at the
top of the input, as it is overriding the time widget selection.
This was my oversight in leaving the GDATTIM parameter in the file, and
not a NCEP bug. I suspect there could be some utility in using the gdattim
explicitly.

Similarly, comment out the GDATTIM line for the RCMG plot in
$NMAP_RESTORE/radar/rcm/reflectivity, etc.

After removing the GDATTIM=last, you should see the time bar populated with
the range of times in the file.

The time binning is a feature for surface observations, and not applicable to
gridded data.

Steve Chiswell
Unidata User Support




>From: "Stonie R. Cooper" <address@hidden>
>Organization: Planetary Data, Incorporated
>Keywords: 200507291534.j6TFYLjo017543

>Steve and Tom,
>
>Through 5.8.1, one was able to bring up an analysis grid via NMAP2 and click 
>on a single time to display a timeline of all times available.  This also 
>allowed one to have a analysis grid layer on an image that updated with the 
>image.  Finally, this also allowed one to loop several time intervals of an 
>analysis grid.
>
>With 5.8.2a, this feature stopped be accessible; if you bring up an analysis 
>grid, such as rcmg or nexr, you can now only see the specific time you 
>clicked on in the timeline, and when layering with an image, the analysis 
>grid does not continue to update with the image, instead only showing the 
>single time that was selected - and was available.  And as only one time 
>shows in the timeline, there is no longer any looping capability with 
>analysis grids.
>
>My guess is that this is related to the new time binning feature - but the 
>"Bin Source" button is grayed out for analysis grids, making it impossible to 
>deselect or otherwise in order to bring back the old functionality.
>
>I hoped that my previous emails may have caused this bug to be fixed in 
>5.8.3a, but I find that 5.8.3a is still broke in this respect.
>
>I appreciate your duties and that I am not a member of the university 
>community, but would have to think that such functionality would be equally 
>important to NCEP and the university community.
>-- 
>Stonie Cooper,
>Planetary Data, Incorporated
>(402) 727-6599
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.