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

[IDV #TGX-684536]: winb barb plan view

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: [IDV #TGX-684536]: winb barb plan view
  • Date: Wed, 28 Jan 2009 16:53:19 -0700
Hi Mark-

> I have two entries for aliases of u and v:
> u:  u_10m_gr and u_gr_p
> v:  v_10m_gr and v_gr_p
> I had the order of these aliases mixed in the alias editor.  In one the
> 10m was before the pressure surface, and vice versa.  When I corrected
> the alias editor so they occurred in the same order, all was fine.

Yeah,  that's a tricky one.   Another way to do this would be to 
create a Parameter Group where you specify what goes with what.
Use the Tools->Parameter Groups Editor menu.  That way there is no
abmiguity.

> I was correct in that it was user error.  I was incorrect as to where
> the user error was located.  It was located in the operation of IDV
> instead of the creation of the CF files.

At least you found the error of your ways. ;-)

Don

> Unidata IDV Support wrote:
> > Hi Mark-
> >
> >> Full Name: Mark Seefeldt
> >> Email Address: address@hidden
> >> Organization: University of Colorado
> >> Package Version: 2.6u1 build date:2009-01-24 20:38 UTC
> >> Operating System: Linux
> >> Hardware: Java: home: /usr/local/idv/IDV_2.6u1/jre version: 1.6.0_11 
> >> j3d:1.5.2 fcs (build4)
> >> Description of problem: Creating display: Wind Barb Plan View
> >> org.python.core.PyException
> >>
> >> The problem has to be in my data file, but not sure as to where or what.
> >> The data file can be downloaded at:
> >> http://foehn.colorado.edu/seefeldt/mm5post.nc
> >>
> >> I have aliased the u_10m_gr v_10m_gr wind values to u and v in IDV.
> >> When I try to do a plan view of wind barbs, I get this error.
> >
> > Does Flow Vectors show up as a derived field in the Fields?  If so,
> > what does is say that it is using to create them.  When I add in the
> > aliases, I see:
> >
> > Flow Vectors (from u_10m_gr & v_10m_gr)
> >
> > Is that what you are getting?
> >
> > I don't have any problem displaying them though.
> >
> > Don Murray
> >
> >> ******************
> >> Stack trace:
> >> Traceback (innermost last):
> >> File "<string>", line 1, in ?
> >> at visad.FieldImpl.combine(FieldImpl.java:1064)
> >> at visad.FieldImpl.combine(FieldImpl.java:998)
> >> at 
> >> ucar.unidata.data.grid.DerivedGridFactory.combineGrids(DerivedGridFactory.java:995)
> >> at 
> >> ucar.unidata.data.grid.DerivedGridFactory.combineGrids(DerivedGridFactory.java:948)
> >> at 
> >> ucar.unidata.data.grid.DerivedGridFactory.createFlowVectors(DerivedGridFactory.java:779)
> >> 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:597)
> >>
> >> visad.VisADException: visad.VisADException: FieldImpl.combine: domain 
> >> dimensions of inputfields must match
> >>
> >>
> >>
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: TGX-684536
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> >
> 
> 


Ticket Details
===================
Ticket ID: TGX-684536
Department: Support IDV
Priority: Normal
Status: Open