Hi Chris,
Thank you! Your infos help me a lot!
It does not work yet, but I will check the data with print/describe and get
deeper into OpenDX.
Greetings!
Fabian
Chris Pelkie <[EMAIL PROTECTED]> writes:
> On Thursday, Jun 10, 2004, at 03:43 America/New_York, Fabian Braennstroem
> wrote:
>
>
>
> This will determine the type of object. I suspect you are getting a Group of 2
> Fields, which is a general purpose object and not a suitable input to some
> modules that can't deal with arbitrary polymorphs like Group. So first try
> Select(0) on the output of Import, prior to Streamline.
>
> Sorry, but I don't understand this :-(
>
> Generally, when we give 'help' (if you can call it that), we (or at least I)
> capitalize the names of DX modules.
> So "Select(0)" means insert a Select module into your data flow (in this case,
> after Import), and set its only
> parameter to "0" (the default). This will Select out member 0 from the input
> if
> that input is a Group. "Group"
> is not a DX module but a DX Object type. I capitalized it because it's a
> formal
> name.
>
> However, now that you've changed to U-V 2-vector, you won't have a Group any
> more so Select will probably
> whine. (so don't do it unless you want to see what happens).
>
>
> But I still think you want to join U and V to make [U,V].
>
> I did this; I changed U and V to a 2-Vector-float. Now, I have a nice
> 'AutoGlyph'-Output, but still 'Streamline' has problems:
>
> Streamline: Missing data: connections
>
> Isn't that strange!?
>
> Greetings!
> Fabian
>
> Yes, esp. if you are still defining a grid in your input file. Though you
> could
> have only 'line' connections and Streamline needs 'quads' (or maybe
> 'triangles') in the 2D case and 'cubes' or 'tetrahedra' in the 3D case, since
> it has to interpolate through the spatial domain, and the connections define
> how the positions carrying the data are joined over the continuous spatial
> domain. This is the sort of thing you can find with Print("rd") attached to
> the
> output of your Import (or other) module. You see what DX sees as a result of
> how you specified your input file and how Import has interpreted that
> specification.
> Or you can use Describe which is easier to understand for DX beginners because
> it gives less detailed info than Print.
>
>
>
>
>
> _______________________________
> Chris Pelkie
> Scientific Visualization Producer
> 622 Rhodes Hall, Cornell Theory Center
> Ithaca, NY 14853
