[Paraview] dataset questions

[John Doe]

Looking in the vtk file formats document, I can see that the xml
format allows multiple pieces in the same unstructured mesh.  This
should suit my purposes.

I am assuming I can have two pieces per region.  One piece would be
for point and line data.  The other piece would be for triangle data.
I assume it would be ok for the two region to share the same
coordinates?

Thanks,

Juan

On Thu, Jun 5, 2008 at 3:23 PM, John Doe <ufnoise at gmail.com> wrote:
> Hi Sam,
>
> Thanks for the excellent ideas.
>
> Since:
> 1 I have on average 2 triangles for every line.
>
> 2. And having zero data for the triangles interspersed with nonzero
> data for the lines may not work out so well.
>
> Perhaps I can have a vtk file for lines and a vtk file for triangles?
>
> I can only find documentation online for the vtk format.  Is there
> documentation for the pvd format?  The example file I saw online is
> xml like, I guess this implies that I'd have to use xml for the
> individual data files?
>
> Thanks,
>
> Juan
>
>
>
> On Thu, Jun 5, 2008 at 1:57 PM, SamuelKey <samuelkey at comcast.net> wrote:
>> Juan,
>>
>> For what it is worth here is my 2 centavos,
>>
>> First, I would consider the VTK XML data format.
>>
>> Second, I have found that it works really well to consider each *.vt* file
>> as an independently displayable graphics object. One then uses a *.pvd
>> meta-file (an ASCII "mother" file) to get PV to read them all at once.
>>
>> Parallel generated data sets are managed this way. I use this approach to
>> generate separate objects based on material type. PV does not care (or know)
>> that they were not generated in parallel. As independently displayable
>> graphics objects, they need to have their own point sets. PV doesn't worry
>> about one or more points having "matching" locations.
>>
>> Each object has its own set of iso-surfaces so that on boundaries the data
>> from each side is used and you get disconnected iso-surfaces which in my
>> case is exactly what I want.
>>
>> The question of different fields/data on different objects someone else will
>> need to answer. (You can always flesh out zero's.)
>>
>> Sam Key
>>
>> John Doe wrote:
>>>
>>> I was going to use implement a vtk writer for my program.  I would
>>> like to use the vtk ascii datafile format.  A few questions:
>>>
>>> 1. I have multiple regions.  Some of these regions share coordinates
>>> at an interface.  Do I have to average the data on both sides of the
>>> interface, or is there a way to put 2 values at the same point?  Will
>>> paraview complain about duplicate coordinates (collinear points)?
>>>
>>> 2. Some data fields only exist in certain regions.  Does that mean I
>>> have to set 0 values in the regions the field does not exist?
>>>
>>> 3. I have points, lines, and triangles.  If I put data on lines, does
>>> that mean I have to define the same data fields on all of the other
>>> cell types in my design as well?  For example, I have current flowing
>>> along lines, but not through triangles.  So it wouldn't make sense to
>>> have current data defined for the triangles.
>>>
>>> Thanks,
>>>
>>> Juan
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>
>