[Paraview] Hierachy in ParaView : VTK Multiblock file format ?

[Aurélien Marsan]

Hi Paul,

What you want to do with MultiBlockDataSet is not yet implemented.
(show/hide some parts, like in Catia maybe ?)
I think I have read some feature request on this, but I can't find it again.

In my opinion, you should work with simple Block, that you group with the
filter "Group Datasets", when you want to do the same action for several
blocks.

As example : with a multiblock dataset, I would like to have one block with
> physical data (radiosity, daylight factor..), other blocks without physical
> data (only geometry)
>
----> You can do this, and build a MultiBlock with Block that didn't contain
the same data.
Paraview will only say "partial" when you will display a data that is not on
all the blocks. I don't think it will try to interpolate the quantity on the
blocks where it is not.

Regards,

Aurélien


2010/6/15 paul.barrere <paul.barrere at laposte.net>

> Hello,
>
> I am a french student : I apologize for my poor English.
>
> I use ParaView to visualize results from  a lighting software, I'm a
> beginner in ParaView. I would like to create a hierarchy in the dataset (to
> hide / show one building ; show results only on the ground and so on). How
> can I manage this ?
>
> - Can I use multiblock dataset file format (.vtm .vtmb ...) ? Where can I
> find any documentation about these file formats ? Does I have to use VTK to
> create these files ?
> - What is the purpose of a block ? As example : with a multiblock dataset,
> I would like to have one block with physical data (radiosity, daylight
> factor..), other blocks without physical data (only geometry) ; or display
> some buildings with a color etc. I want to have only one file with all this
> information.
>
> Thank you for your answer,
> Yours faithfully,
>
> paul barrère
> (trainee at CNRS Cerma laboratory, nantes, France)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20100616/05ddc1f0/attachment-0001.htm>