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

[IDV #WJD-414815]: GFS 2.5 degree catalogue

Hi Bill-

> Full Name: bill fingerhut
> Email Address: address@hidden
> Organization: lyndon state college
> Package Version: 2.5b1 build date:2008-03-26 07:05 UTC
> Operating System: Windows XP
> Hardware: Java: home: C:\Documents and Settings\waf01060\Program 
> Files\IDV_2.5b1\jre version: 1.5.0_11 j3d:1.3.2 fcs (build12)
> Description of problem: The GFS 1 degree catalogue of grids is so usefull, I 
> decided to move on to the 2.5
> degree grids (on motherlode).
> 
> Using the data chooser to selesct times from the 2.5 degree grids is very 
> interesting.
> What one selects is not at all close to what one gets. See the attached 
> current state.
> The data chooser shows several times at one hour intervals near the begining 
> of the
> model run, which are not available and one will actually get very different 
> times
> (according to the display labels). To see which times are actually available 
> I selected
> all, the default.

This was caused by a bug.  For the data source, the list of times
shows all available times.  For an individual field, it should
show just the times for that field.  If you selected a field
like geopotential height anomaly, you would get the list of
all times.  If you then selected another field like geopotential
height, you would see just the times for that field.  If you then
went back to the geopotential height anomaly, you'd get the
correct times.  We have fixed this problem in the latest nightly
build so that the correct times are shown on the first selection.  
Thanks for noticing it.  There is an albedo field that has the
hourly time fields right at the beginning.   I think these are
being filed incorrectly and will look into removing them.
 

> Another issue is that there is a couple of days that are not in the 1 degree 
> or 2.5
> degree catalogues. It would be nice to have those times so that a continuous
> animation can be created from the initial time to the last forecast. Missing 
> a couple of
> days in the middle seems strange.

I'll look into this on Monday.  Is it always the same forecast
period that is missing (e.g days 6 and 7)?
 
> Perhaps these problems have the same cause - baulky code?

Some of this is code, the other is most likely a wrong pattern
action in the LDM.

Don Murray

Ticket Details
===================
Ticket ID: WJD-414815
Department: Support IDV
Priority: Normal
Status: Open