[Paraview] paraview making up numbers

Berk Geveci berk.geveci at kitware.com
Thu Jul 3 14:23:39 EDT 2008


No, I am afraid it did not make into the documentation yet. It is easy
to create an example using ParaView. Load 2 unstructured grids, group
them together using the Group filter and then write the output as a
vtm file.

-berk

On Thu, Jul 3, 2008 at 12:35 PM, John Doe <ufnoise at gmail.com> wrote:
> Is there any documentation for the multi-block format?  It is not part
> of the file formats document I found online.
>
> Thanks,
>
> Juan
>
> On Wed, Jul 2, 2008 at 2:43 PM, Berk Geveci <berk.geveci at kitware.com> wrote:
>> It is required that all pieces in an XML unstructured file have the
>> exact same set of arrays. It is by coincidence that you are
>> experiencing crashes. You need to use multi-block dataset to group
>> together pieces with different fields. You may want to look at using
>> the XML-based multi-block file format (vtm extension) or EnSight
>> format for this. The former is not well documented yet, I am afraid.
>>
>> -berk
>>
>> On Tue, Jul 1, 2008 at 4:46 PM, John Doe <ufnoise at gmail.com> wrote:
>>> I have devices composed of pieces using an unstructured mesh in the
>>> xml file format.  Some of the pieces don't have data in them.  It
>>> appears that paraview makes up numbers for these regions.  Sometimes
>>> the numbers are unphysical, e.g. 1e+307.  Sometimes the numbers seem
>>> to be based on data from adjacent pieces.  Is there any way to tell
>>> paraview to use a reasonable values in regions for which data is not
>>> presented.
>>>
>>> This becomes important as each region (piece) of my device can have
>>> completely different physics.
>>>
>>> Thanks,
>>>
>>> Juan
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>
>


More information about the ParaView mailing list