[Paraview] Internalisation of, 2D vs 3D
Moreland, Kenneth
kmorel at sandia.gov
Tue Sep 9 10:42:50 EDT 2008
All coordinates of all data sets are defined in 3D Cartesian coordinates.
That's just the way VTK was designed. Allowing for variable length
coordinates would be a significant burden on many developers.
You will have to pad your coordinates with 0's in the Z components.
-Ken
On 9/9/08 8:15 AM, "philippe DAVID" <pdavid at scconsultants.com> wrote:
> ok,
> when I load a 2D vtu, Paraview complains about "number of components is
> different" and crashes.
> all my Z components can be set to 0, but I would like to avoid setting for
> instance a probe
> line in a 3D env, where the only relevant plane is X*Y : in this last case the
> probe is not
> aligned with the X*Y plane.
>
>
> thanks anyway
> Philippe DAVID
> Sciences Computers Consultants
> Direct:(33)-4-77-49-75-81
> Std:(33)-4-77-49-75-80
>
>
> Moreland, Kenneth said the following on 09/09/2008 15:42:
>>
>>>
>>> does somebody have been heard about internationalisation in Paraview (or
>>> internationalised version) ?
>>>
>>>
>>
>>
>> Not to my knowledge. I don't think this has achieved a high enough priority
>> on anyone's list to implement yet.
>>
>>
>>
>>>
>>> Is it possible to load a 2D vtu rather a 3D in Paraview ?
>>>
>>>
>>
>>
>> Neither ParaView nor VTK treats 2D unstructured grids differently than 3D
>> unstructured grids. I can only assume that you mean a vtu file containing
>> only 2D cells that lie on a plane. Simply load it into ParaView as you
>> normally would.
>>
>> -Ken
>>
>>
>>
>>
>>
>>
More information about the ParaView
mailing list