ah I think i understand what is going on.
The data comes from a finite element code that has in the center of the
element a node with seven degrees of freedom
I would like to use something like construct again to do [a.0, a.1, a.2] and
use that as the shape 3 vector field
how do i keep the volumetric field information? that streamline needs?
by the way i think the positions connections data fields are associated with
the right fields in this block at the bottom of my file.
object "field1"
class field
component "positions" value "coordinates"
component "connections" value "elements"
component "data" value "solution1"
the rest of the field.....
object "coordinates"
class array
type float
rank 1
shape 3
items 38855
data follows
object "elements"
class array
type int
rank 1
shape 8
items 34560
attribute "element type" string "cubes"
data follows
object "solution1"
class array
type double
rank 1
shape 7
items 38855
attribute "dep" string "positions"
data follows
thomas
On Saturday 11 March 2006 16:06, Chris Pelkie wrote:
> If it's really called "elements" in your dx file, that's the problem.
> It MUST be called "connections".
>
> You are free to call them anything you want but DX looks for
> 'positions', 'connections', and 'data' when it gets down to business.
> You can either rename it in the input file or Rename
> ("elements","connections").
>
> Otherwise, it looks correct and should work, assuming data is 'class
> array type float rank 1 shape 3" and I think it has to be "dep
> positions".
>
> On Mar 11, 2006, at 4:42 AM, Thomas Geenen wrote:
> > yes that puzzled me also. about the volumes, my dx files has this
> > to say about
> > it
> >
> > objects "elements"
> > class array
> > type int
> > rank 1
> > shape 8
> > items 34560
> > attribute "element type" string"cubes"
> > data follows
> >
> > so unstructured cubes
> > how do i do a construct like trick to create volumes.
> > Maybe autogrid?
> >
> > Thomas
> >
> > On Saturday 11 March 2006 01:38, Chris Pelkie wrote:
> >> The Construct trick doesn't help here. When you send a list of values
> >> to 'origin', you get a line of connected points.
> >>
> >> Streamline requires a volumetric field to interpolate through.
> >>
> >> I'm not sure why your original field isn't working, unless you don't
> >> have volumetric elements (like tets, probably, if it's unstructured).
> >>
> >> On Mar 10, 2006, at 9:47 AM, Thomas Geenen wrote:
> >>> Hi all,
> >>>
> >>> it seems to be a bit quit in the forum....
> >>> I got a very basic question.
> >>> I try to get streamlines working for me and up till now it doesn't.
> >>> I got a 3D velocity field on an unstructured grid. I create glyph's
> >>> for it and
> >>> display it. so far so good. next I want to add streamlines so I
> >>> pass the same
> >>> data that I pass to autoglyph to streamlines. This results in an
> >>> error
> >>> message saying that streamlines expects a 3D floating point vector
> >>> field. So
> >>> I make an explicit vector field by extracting th positions from the
> >>> field and
> >>> passing it to the origin part of a construct block. next I extract
> >>> the data
> >>> part and compute the velocity vectors explicitly again by computing
> >>> [a.0,
> >>> a.1, a.2] extract the data part and pass it to the data part of the
> >>> construct
> >>> block. However streamlines still complains about the field not
> >>> being a 3D
> >>> vector field. What else do I have to do to make streamlines happy??
> >>>
> >>> tia
> >>> Thomas
