Hi,
Now it works fine after I did a restart to my computer.
Thanks,
Ilan Levy
-----Original Message-----
From: Don Murray [mailto:dmurray@xxxxxxxxxxxxxxxx]
Sent: December 17, 2009 8:46 AM
To: Levy,Ilan [Ontario]
Cc: jeff mcwhirter; idvusers@xxxxxxxxxxxxxxxx
Subject: Re: [idvusers] Data Transect on 3D grid
Hi Ilan-
I'm not sure why this isn't working for you. make2D is in the 2.7u2 and
2.8b1 releases and the error indicates that the IDV can't find it. Did
you use make2D(slice) as the diagnostic?
Selectthe Edit->Formulas->Jython Library menu to bring up the Jython
Library. Expand the System tab and select the Grid routines. Use the
search facility and look for make2D. Does that get highlighted?
Another option is to try using:
GridUtil.make2DGridFromSlice(slice)
as the diagnostic which is what make2D actually calls.
If that doesn't work, please send a note to
support-idv@xxxxxxxxxxxxxxxx. We can diagnose that off the list.
Thanks.
Don Murray
Levy,Ilan [Ontario] wrote:
> I have tried what you suggest, and I'm getting the following error:
> Traceback (innermost last):
> File "<string>", line 1, in ?
> NameError: make2D
>
> I also tried to create a 2D subset of my data and use the Data
> Transect, but then I get the following error:
> visad.VisADException: input has wrong dimension
> at
> visad.CartesianProductCoordinateSystem.toReference(CartesianProductCoo
> rd
> inateSystem.java:166)
> at visad.CoordinateSystem.toReference(CoordinateSystem.java:844)
> at
> ucar.unidata.idv.control.CrossSectionControl.convertToDisplay(CrossSec
> ti
> onControl.java:1082)
> at
> ucar.unidata.idv.control.CrossSectionControl.getXYPosition(CrossSectio
> nC
> ontrol.java:1016)
> at
> ucar.unidata.idv.control.CrossSectionControl.initDone(CrossSectionCont
> ro
> l.java:522)
> at
> ucar.unidata.idv.control.DisplayControlImpl.init(DisplayControlImpl.ja
> va
> :1086)
> at
> ucar.unidata.idv.ControlDescriptor.initControl(ControlDescriptor.java:
> 97
> 9)
> at
> ucar.unidata.idv.ControlDescriptor$1.run(ControlDescriptor.java:904)
> at ucar.unidata.util.Misc$3.run(Misc.java:1061)
>
>
> Ilan
>
> -----Original Message-----
> From: Don Murray [mailto:dmurray@xxxxxxxxxxxxxxxx]
> Sent: December 16, 2009 12:40 PM
> To: jeff mcwhirter
> Cc: Levy,Ilan [Ontario]; idvusers@xxxxxxxxxxxxxxxx
> Subject: Re: [idvusers] Data Transect on 3D grid
>
> I agree with Jeff that we could look into adding this, but for now,
> here's a way to do it:
>
> - Load in your grid.
> - Select the Formulas data source.
> - Select the "Grids->Define a grid diagnostic" formula
> - Select the "Cross Section->Data Transect" display.
>
> For the formulas, enter make2D(slice)
>
> When the field selector pops up, select the field and the level that
> you want for the slice parameter.
>
> That should create the display.
>
> Don Murray
>
> jeff mcwhirter wrote:
>> Levy,Ilan [Ontario] wrote:
>>> Hi,
>>> I have a 3D grid (model output) and I'm trying to draw a Data
>>> Transect. However I do not have this option under the Probes
>>> display,
>
>>> only if I choose one of the 2D grids (lat&lon).
>>>
>>> What I want is a line plot of the grid values along a line at the
>>> surface level.
>>> I've tried this on IDV 2.7u2 and 2.8b1.
>>>
>> Right now the data transect display is only applicable to 2D gridded
>> fields. I guess we could support 3D and allow the user to select a
>> level like we do in the plan view displays.
>>
>> -Jeff
>>
>> _______________________________________________
>> idvusers mailing list
>> idvusers@xxxxxxxxxxxxxxxx
>> For list information, to unsubscribe, visit:
>> http://www.unidata.ucar.edu/mailing_lists/
>
> --
> *************************************************************
> Don Murray UCAR Unidata Program
> dmurray@xxxxxxxxxxxxxxxx P.O. Box 3000
> (303) 497-8628 Boulder, CO 80307
> http://www.unidata.ucar.edu/staff/donm
> *************************************************************
--
*************************************************************
Don Murray UCAR Unidata Program
dmurray@xxxxxxxxxxxxxxxx P.O. Box 3000
(303) 497-8628 Boulder, CO 80307
http://www.unidata.ucar.edu/staff/donm
*************************************************************
