Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.

Re: More GriddedNDSet Questions

Hi Ken, Bill:

I'll see if I can lend a hand here, but it won't likely be until
later this week.

Tom

Kenneth Evans wrote:


If you're ready to compile VisAD from its source…


I thought I was and have done that before. There are two problems:
1. I am on Windows and when I extracted the new visad_src.jar, there seems to be no Makefile.WinNT in the visad directory.
2. I recall it didn’t make the visad.jar before. The way I am set up now, it would be easy to replace the JAR file but not easy to set the build path. (The reason is that it is set up as an Eclipse plug-in.) So how do I make the JAR.
The third problem is that I am leaving for Germany and France on Friday (and would like to have this working). Consequently, my time is limited for the trial and error approach. 

I can also do Cygwin builds, but I recall that didn’t work before.

Thanks for any help,

-Ken

------------------------------------------------------------------------
*From:* owner-visad@xxxxxxxxxxxxxxxx [mailto:owner-visad@xxxxxxxxxxxxxxxx] *On Behalf Of *Bill Hibbard 
*Sent:* Sunday, April 15, 2007 3:17 PM
*To:* Kenneth Evans, Jr.; Visad
*Subject:* RE: More GriddedNDSet Questions

Ken,

All the evidence you present says that the system is using
texture mapping with your Linear2DSet and not using texture
mapping with your Gridded2DDoubleSet (the slowness is
consistent with not using texture mapping). If you're ready to
compile VisAD from its source, you could uncomment the
print statements for the computation of the isTextureMap
and curvedTexture flags, in the ShadowFunctionOrSetType.java
file in the visad package. Uncomment two sets of print
statements, between (at least in the old version of source
on my home machine) lines 453-477 and lines 713-733.
It would be a good idea to eliminate all displayed data
except the Field of interest, so you don't confuse with the
print output of other data.

Feel free to send the results to the list, and we'll try to
figure out what's happening.

Good luck,
Bill

----- Original Message -----
From: "Kenneth Evans, Jr."
To: Visad
Subject: RE: More GriddedNDSet Questions
Date: Sat, 14 Apr 2007 12:01:57 -0500


Bill,
I am attaching a picture of what I get with the Gridded2DDouble set. They are triangles and don’t extend beyond the plot range, whereas with the Linear2D set, they are pixels and extend .5 pixel beyond the plot boundary (presumably TextureMaps). Moreover, the display is verrry slow in the Gridded2DDouble case. The lines of code that are different in the two cases are: 

// Create the domain set

if(xVals2D == null && yVals2D == null) {

// Define a linear domain set with the indices

domainSet = new *Linear2DSet*(xMin, xMax, nX, yMin, yMax, nY);

System./out/.*println*("Linear2DSet");

} else {

xVals1D = new double[1][nX * nY];

yVals1D = new double[1][nX * nY];

xVals1D[0] = VUtils./convert2DArrayTo1DArray/(xVals2D, nY, nX);

yVals1D[0] = VUtils./convert2DArrayTo1DArray/(yVals2D, nY, nX);

domainSet = new *Gridded2DDoubleSet*(domainType, new double[][] {

xVals1D[0], yVals1D[0]}, nX, nY);

System./out/.*println*("Gridded2DDoubleSet");

}
This is from a generic 2D plot class. If you give it x and y values it uses the Gridded2DDoubleSet, otherwise the Linear2DSet. I can send the whole file, if necessary. The domainTypes are defined: 

// Define types

xType = RealType./getRealType/(xLabel, null, null);

yType = RealType./getRealType/(yLabel, null, null);

RealType[] domainTypes = new RealType[2];

domainTypes[0] = xType;

domainTypes[1] = yType;

domainType = new *RealTupleType*(domainTypes);
The fact that it is slow is more important to me than that is using triangles.
gmc.getTextureEnable returns true in both cases. I don’t explicitly set it. 

The VisAD version is the Jan 07 version.

Thanks,

-Ken

------------------------------------------------------------------------
*From:* owner-visad@xxxxxxxxxxxxxxxx [mailto:owner-visad@xxxxxxxxxxxxxxxx] *On Behalf Of *Bill Hibbard 
*Sent:* Monday, April 09, 2007 5:46 PM
*To:* Kenneth Evans, Jr.; Visad
*Subject:* RE: More GriddedNDSet Questions

Hi Ken,

Pairs of triangles indicate that the system is not using curved
texture maps. I don't understand why it would use square
texture maps with your LinearSet and not use curved texture
maps with your GriddedSet, unless (according to my reading
of the code in VisAD) you are making transparent surfaces.
I doubt that sending an image will help.

Good luck,
Bill
What I see is pairs of triangles when I zoom in. That is probably what a curved texture map looks like? I can send an image if that would help, but I don’t think I am seeing anything unusual. It’s just it is different when using a Gridded2DSet than when using a Linear2DSet, even though the grid data is equivalent. 



--

<http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=en-mail_a_01>

<< Gridded2DSet.Triangles.png >>


--

<http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=en-mail_a_01>



==============================================================================
To unsubscribe visad, visit:
http://www.unidata.ucar.edu/mailing-list-delete-form.html
==============================================================================
  • 2007 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the visad archives: