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

20050810: IDV - Throwing exception with a Vis5D topo file

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: 20050810: IDV - Throwing exception with a Vis5D topo file
  • Date: Wed, 10 Aug 2005 22:12:35 -0600
>From: "Steve Aulenbach" <address@hidden>
>Organization: NCAR/CGD
>Keywords: 200508101748.j7AHm6KJ017653 IDV Vis5D topo file

Hi Steve-

>Institution: NCAR
>Package Version: 1.2RC1
>Operating System: OSX 10.3.9
>Hardware Information: Dual 1.8 Ghz PowerPC G5, 2 GB DDR SDRAM
>Inquiry: Produced a \"valid\" .topo file with Vis5D maketopo. It is attached. 
> The Vis5D program topoinfo returns this:
>
>0[252]0 bangkok:~/acmeVis5D/vis5d+-1.2.1/util > topoinfo acme.topo
>Topo file: acme.topo
>North bound: 38.5572 deg
>South bound: 41.4877 deg
>West bound: -107.495 deg
>East bound: -103.605 deg
>Rows: 109
>Columns: 109
>min height: 1296 meters
>max height: 4044 meters
>% water flags: 0

A couple of points about this file.  Your north bound is less than your
south bound.  Vis5D uses positive west longitudes, so the values should be:

North bound: 41.4877 deg
South bound: 38.5572 deg
West bound: 107.495 deg
East bound: 103.605 deg

>
>IDV does not like acme.topo. Opening it as a Vis5D file throws the following e
> xception:

Thanks for finding this bug.  A change was made between the 1.2b2 and 1.2RC1
versions that broke this.

>visad.VisADException: FieldImpl.extract: range must be a TupleType
>       at visad.FieldImpl.extract(FieldImpl.java:1373)
>       at ucar.unidata.data.grid.GridUtil.extractParam(GridUtil.java:1653)
>       at ucar.unidata.data.grid.Vis5DDataSource.getField(Vis5DDataSource.java
> :291)
>       at ucar.unidata.data.grid.Vis5DDataSource.getDataInner(Vis5DDataSource.
> java:216)
>       at ucar.unidata.data.DataSourceImpl.getData(DataSourceImpl.java:1273)
>       at ucar.unidata.data.DirectDataChoice.getData(DirectDataChoice.java:316
> )
>       at ucar.unidata.data.DataChoice.getData(DataChoice.java:521)
>       at ucar.unidata.data.DataInstance.getData(DataInstance.java:204)
>       at ucar.unidata.data.DataInstance.getData(DataInstance.java:169)
>       at ucar.unidata.data.grid.GridDataInstance.init(GridDataInstance.java:1
> 75)
>       at ucar.unidata.data.grid.GridDataInstance.<init>(GridDataInstance.java
> :138)
>       at ucar.unidata.idv.control.GridDisplayControl.doMakeDataInstance(GridD
> isplayControl.java:215)
>       at ucar.unidata.idv.control.DisplayControlImpl.setData(DisplayControlIm
> pl.java:2186)
>       at ucar.unidata.idv.control.PlanViewControl.setData(PlanViewControl.jav
> a:388)
>       at ucar.unidata.idv.control.PlanViewControl.init(PlanViewControl.java:3
> 05)
>       at ucar.unidata.idv.control.DisplayControlImpl.init(DisplayControlImpl.
> java:951)
>       at ucar.unidata.idv.control.DisplayControlImpl.init(DisplayControlImpl.
> java:796)
>       at ucar.unidata.idv.ControlDescriptor.initControl(ControlDescriptor.jav
> a:741)
>       at ucar.unidata.idv.ControlDescriptor$1.run(ControlDescriptor.java:699)
>       at ucar.unidata.util.Misc$2.run(Misc.java:778)

I've fixed it for the 1.2 release, so when that comes out on Friday, you
should be all set.  If you'd like to try it earlier, let me know.

You'll still need to fix the lats/lons in your file.  If you make a
new one and want me to try it before the release, let me know.

Don
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.