Hi Bill- This bug was finally fixed in the nightly build. Only took 2 years. ;-) Don > Full Name: bill fingerhut > Email Address: address@hidden > Organization: lyndon state college retired > Package Version: 2.5 build date:2008-05-08 07:05 UTC > Operating System: Windows XP > Hardware: Java: home: C:\Program Files\IDV_2.5\jre version: 1.5.0_11 > j3d:1.3.2 fcs (build12) > Description of problem: Selecting 'all levels' did get me past the error > message. I now have a display. > BTW, I defaulted to the 1000mb level although I did not specify a level. That > must have > been left over from another day. Once I specified all levels, it worked. > > So, I proceeded to compare IPV at the same time and 250 mb > between the NAM and GFS. The results look quite similar, > except that the values from the GFS are negative. They should be positive in > almost all > situations. (Hopefully, the current state shows this.) Any thoughts on why ? > > Bill > > > -----Original Message----- > From: Unidata IDV Support [mailto:address@hidden > Sent: Fri 6/6/2008 12:24 PM > To: Fingerhut, William A @ LSC > Cc: address@hidden > Subject: [IDV #QQP-632804]: displaying IPV from model data > > Hi Bill- > > > Full Name: bill fingerhut > > Email Address: address@hidden > > Organization: lyndon state college > > Package Version: 2.5 build date:2008-05-08 07:05 UTC > > Operating System: Windows XP > > Hardware: Java: home: C:\Documents and Settings\waf01060\Program > > Files\IDV_2.5\jre version: 1.5.0_11 j3d:1.3.2 fcs (build12) > > Description of problem: Creating display: Contour Plan View > > org.python.core.PyException > > > > I've encountered a little problem displaying IPV from model data. > > > > First I chose a dataset: Latest NCEP NAM CONUS 80 km > > from > > http://motherlode.ucar.edu:8080/thredds/dodsC/model/NCEP/NAM/CONUS_80km/NAM_CONUS_80km_20080514_0000.grib1 > > Then I entered the dataset properties, and chose one time - the first. > > Then from the menu: Data --> Latest NCEP NAM CONUS 80 km --> 3D grid --> > > Derived --> Isentropic Potential Vorticity --> Contour Plan --> Ok. And an > > error occurs. > > > > I have a bundle that works okay, so I was curious about the differences. It > > uses the > > method: DerivedGridFactory.createIPV (Temperature, Absolute_vorticity). So, > > I entered > > this call in: Data --> Formulas --> Grids --> Define a grid diagnostic, and > > it worked fine. > > So, the method seems okay; maybe there is a problem using the menu to call > > this > > method ? > > The problem is that in the latest versions of the IDV, the default is to > select a particular level for plan vies, not the read the entire volume. > When you select the Isentropic Potential Vorticity, make sure the Level is > set to All Levels, or select a range of levels. It would work automatically > for cross sections and isosurfaces because they use multiple levels (All by > default). > > When you use the formula, the default is to use all levels, regardless of > the display. We'll look into having formulas that need multiple levels > specify so in the XML so the user won't get caught by this. > > Don > > ****************** > > Stack trace: > > Traceback (innermost last): > > File "<string>", line 1, in ? > > at visad.FlatField.derivative(FlatField.java:4044) > > > > at visad.FlatField.derivative(FlatField.java:4485) > > > > at > > ucar.unidata.data.grid.DerivedGridFactory.partial(DerivedGridFactory.java:2191) > > > > at > > ucar.unidata.data.grid.DerivedGridFactory.createIPV(DerivedGridFactory.java:1782) > > > > at > > ucar.unidata.data.grid.DerivedGridFactory.createIPV(DerivedGridFactory.java:1708) > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > > > at java.lang.reflect.Method.invoke(Method.java:585) > > > > > > visad.VisADException: visad.VisADException: derivative: d_partial_s not in > > domain or reference > > > > > > > > > Ticket Details > =================== > Ticket ID: QQP-632804 > Department: Support IDV > Priority: Normal > Status: Open > > > > Ticket Details =================== Ticket ID: QQP-632804 Department: Support IDV Priority: Critical Status: Closed
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.