[Paraview] ParaView Digest, Vol 114, Issue 20

Jimmy Chen migichen at gmail.com
Thu Oct 10 01:57:42 EDT 2013


Samuel,

Thank you very much for the timely help.  The pvd example is very
helpful.  Although the client may still want all segments in a single
file, at least we now know what tool to use for the segment-selection
interface.  I'll keep looking for a single-file format but I doubt
there is any.

Thanks,
Jimmy

------------------------------
Date: Tue, 08 Oct 2013 09:23:31 -0600
From: Samuel Key <samuelkey at bresnan.net>
Subject: Re: [Paraview] Which polygon file reader in Paraview has
        interface to show/hide separate segments?
To: paraview at paraview.org
Message-ID: <52542373.1030108 at bresnan.net>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

Jimmy,

I have attached a file named 'fmavto.pvd' that is an ASCII-text file. It
is a meta-file that references a series of XML-formatted *.vtu files.

ParaView reads the *.pvd file and then knows how to "assemble" the files
referenced within the *.pvd file. The important key-words in the *.pvd
files are 'timestep=...' and 'file=...' Note that the individual *.vtu
files contain the data needed for a displayable graphics object.

The key-word 'name=...' is gratuitous user-information. The key-word
'name=...' for a couple of ParaView versions around 2007 would pass this
user-information to the Extract Block filter; currently (PV version
4.0.1) the ASCII-text strings are no longer passed to the Extract Block
filter.

However, the Extract Block filter does reflect the structure implied by
the *.pvd file; the filter simply uses the ubiquitous and
not-very-helpful C-language off-set addresses of 0,1,2,3,... for the
block names.

Because of the large number of ASCII-text files that can be generated in
a transient dynamic simulation with multiple material domains using the
vtk-formats, sometime back I switched to the EnSight binary-formatted
output. In this format it is possible to provide names that will appear
in the Extract Block filter.

Hope this helps,

Regards,

Sam Key

On 10/7/2013 8:35 PM, Jimmy Chen wrote:
> Samuel,
>
> Thank you very much for the quick reply.  I tried your EnSight example
> and could select different polygons by using "Extract Blocks" filter.
> VTK's example EnSight datasets also allows doing so.
>
> Besides, *.vtp or *.pvtp files are not working for me.   What content
> should be put into vtp files to enable Paraview "Extract Blocks"?  If
> you also have a working vtp example that will be very helpful.
>
> Thanks and best regards,
> Jimmy
>
> -------------------------------------------------------------
> Date: Mon, 07 Oct 2013 09:03:40 -0600
> From: Samuel Key <samuelkey at bresnan.net>
> Subject: Re: [Paraview] Which polygon file reader in Paraview has
>          interface to show/hide separate segments?
> To: paraview at paraview.org
> Message-ID: <5252CD4C.7090805 at bresnan.net>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Jimmy,
>
> I have had success with two different ParaView readers doing what you
> have described.
>
> It is material domains that I want to examine as distinct. However,
> ParaView does not care if it is a serially-generated set of material
> domain, a set of processor domain results, or any criterion you want to
> use. Each domain needs to be a "displayable graphics object."
>
> Case(1) *.vtp XML format
>
> Case(2) EnSight Gold format using that format's Part-construct.
>
> In either case, ParaView's Extract Group filter allows one to select any
> combination of domains to display. Multiple extracted sub-domains can
> appear together in one window and/or in separate windows.
>
> A small file that will let you explore this capability is attached.
>
> Samuel W Key
> FMA Development, LLC
> 1005 39th Ave NE
> Great Falls, Montana 59404
> USA
>
>
>
> On 10/6/2013 9:14 PM, Jimmy Chen wrote:
>> Hello,
>>
>> We generate several segments of polygonal meshes and our client wants
>> to store them into a single file and to view on Paraview.  Since the
>> data contains several pre-segmented mesh pieces, they want to view
>> each piece separately in Paraview. Is there a file format supporting
>> composite datasets and has a Paraview interface to show some of them?
>>
>> We have looked into .vtp and .pvtp formats.
>> For .vtp XML format, although we can store different segment in
>> different <piece> tags, Paraview seem to regard them as one piece of
>> data.
>> For .pvtp format, each component is stored into a different file,
>> which is not what our client want.
>>
>> Although we can always create our reader plugin for Paraview, I am
>> wondering whether there already exists this kind of file format saving
>> segments in one file, with a segment-selectable Paraview interface.
>>
>>
>> Thanks and have a nice day.
>> Jimmy Chen
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Copy of fmavto.pvd
Type: text/xml
Size: 5356 bytes
Desc: not available
URL: <http://www.paraview.org/pipermail/paraview/attachments/20131008/8ba2936c/attachment-0001.bin>

On Tue, Oct 8, 2013 at 12:00 PM,  <paraview-request at paraview.org> wrote:
> Send ParaView mailing list submissions to
>         paraview at paraview.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://www.paraview.org/mailman/listinfo/paraview
> or, via email, send a message with subject or body 'help' to
>         paraview-request at paraview.org
>
> You can reach the person managing the list at
>         paraview-owner at paraview.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ParaView digest..."
>
>
> Today's Topics:
>
>    1. Re: How to connect to X Server automatically when
>       doingcatalyst live data visualization. (Andy Bauer)
>    2. Re: Which polygon file reader in Paraview has interface to
>       show/hide separate segments? (Samuel Key)
>    3. Re: Plotting an integrated variable over time (Moreland, Kenneth)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 8 Oct 2013 09:43:31 -0400
> From: Andy Bauer <andy.bauer at kitware.com>
> Subject: Re: [Paraview] How to connect to X Server automatically when
>         doingcatalyst live data visualization.
> To: ??? <xiemaojin at sccas.cn>
> Cc: paraview <paraview at paraview.org>
> Message-ID:
>         <CAMaOp+HUCFfDz+3hvBedr-fFq0CBQuAdvAUmydR9fQSucnNXxA at mail.gmail.com>
> Content-Type: text/plain; charset="gb2312"
>
> Hi,
>
> I think this is an issue with the set up of your cluster. Unless ParaView
> uses OSMesa to do rendering it needs a window for rendering.
>
> Regards,
> Andy
>
>
> On Tue, Oct 8, 2013 at 5:40 AM, ??? <xiemaojin at sccas.cn> wrote:
>
>> Hi All,
>>
>> ** **
>>
>> I'm annoying by a Paraview catalyst problem. When doing parallel live data
>> insitu visualization in client-server mode, I have to manually login to all
>> desktops of all server nodes first, else it'll complain that "cannot
>> connect to X Server"
>>
>> * *
>>
>> As our simulation cluster equips with two CUDA enable GPU cards in each
>> node, how should I configure it to make Paraview take use of GPU
>> acceleration function while don't need to login to desktops each time I
>> decide to launch a parallel visualization task?
>>
>> ** **
>>
>> I have some fundamental knowledge about parallel visualization with OpenGL
>> and Cg/GLSL under Linux cluster, that's I have to configure XDisplay under
>> /etc/X11/xorg.conf and call XOpenDisplay() in my code to make GPU
>> acceleration available. Does this similar to paraview or help to understand
>> the Paraview's style?
>>
>> ** **
>>
>> BTW, is there a way to make the visualization nodes available to multiple
>> end users?  Currently, if one login to the node?s desktop, others cannot
>> login to the nodes? desktop again.
>>
>> ** **
>>
>> My environment is a GPU cluster,  CentOS and Paraview 4.0.0
>>
>> ** **
>>
>> Thank you.
>>
>>
>> ------------------------------
>> Maojin XIE
>>
>>
>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.paraview.org/pipermail/paraview/attachments/20131008/8654647b/attachment-0001.htm>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 08 Oct 2013 09:23:31 -0600
> From: Samuel Key <samuelkey at bresnan.net>
> Subject: Re: [Paraview] Which polygon file reader in Paraview has
>         interface to show/hide separate segments?
> To: paraview at paraview.org
> Message-ID: <52542373.1030108 at bresnan.net>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Jimmy,
>
> I have attached a file named 'fmavto.pvd' that is an ASCII-text file. It
> is a meta-file that references a series of XML-formatted *.vtu files.
>
> ParaView reads the *.pvd file and then knows how to "assemble" the files
> referenced within the *.pvd file. The important key-words in the *.pvd
> files are 'timestep=...' and 'file=...' Note that the individual *.vtu
> files contain the data needed for a displayable graphics object.
>
> The key-word 'name=...' is gratuitous user-information. The key-word
> 'name=...' for a couple of ParaView versions around 2007 would pass this
> user-information to the Extract Block filter; currently (PV version
> 4.0.1) the ASCII-text strings are no longer passed to the Extract Block
> filter.
>
> However, the Extract Block filter does reflect the structure implied by
> the *.pvd file; the filter simply uses the ubiquitous and
> not-very-helpful C-language off-set addresses of 0,1,2,3,... for the
> block names.
>
> Because of the large number of ASCII-text files that can be generated in
> a transient dynamic simulation with multiple material domains using the
> vtk-formats, sometime back I switched to the EnSight binary-formatted
> output. In this format it is possible to provide names that will appear
> in the Extract Block filter.
>
> Hope this helps,
>
> Regards,
>
> Sam Key
>
> On 10/7/2013 8:35 PM, Jimmy Chen wrote:
>> Samuel,
>>
>> Thank you very much for the quick reply.  I tried your EnSight example
>> and could select different polygons by using "Extract Blocks" filter.
>> VTK's example EnSight datasets also allows doing so.
>>
>> Besides, *.vtp or *.pvtp files are not working for me.   What content
>> should be put into vtp files to enable Paraview "Extract Blocks"?  If
>> you also have a working vtp example that will be very helpful.
>>
>> Thanks and best regards,
>> Jimmy
>>
>> -------------------------------------------------------------
>> Date: Mon, 07 Oct 2013 09:03:40 -0600
>> From: Samuel Key <samuelkey at bresnan.net>
>> Subject: Re: [Paraview] Which polygon file reader in Paraview has
>>          interface to show/hide separate segments?
>> To: paraview at paraview.org
>> Message-ID: <5252CD4C.7090805 at bresnan.net>
>> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>>
>> Jimmy,
>>
>> I have had success with two different ParaView readers doing what you
>> have described.
>>
>> It is material domains that I want to examine as distinct. However,
>> ParaView does not care if it is a serially-generated set of material
>> domain, a set of processor domain results, or any criterion you want to
>> use. Each domain needs to be a "displayable graphics object."
>>
>> Case(1) *.vtp XML format
>>
>> Case(2) EnSight Gold format using that format's Part-construct.
>>
>> In either case, ParaView's Extract Group filter allows one to select any
>> combination of domains to display. Multiple extracted sub-domains can
>> appear together in one window and/or in separate windows.
>>
>> A small file that will let you explore this capability is attached.
>>
>> Samuel W Key
>> FMA Development, LLC
>> 1005 39th Ave NE
>> Great Falls, Montana 59404
>> USA
>>
>>
>>
>> On 10/6/2013 9:14 PM, Jimmy Chen wrote:
>>> Hello,
>>>
>>> We generate several segments of polygonal meshes and our client wants
>>> to store them into a single file and to view on Paraview.  Since the
>>> data contains several pre-segmented mesh pieces, they want to view
>>> each piece separately in Paraview. Is there a file format supporting
>>> composite datasets and has a Paraview interface to show some of them?
>>>
>>> We have looked into .vtp and .pvtp formats.
>>> For .vtp XML format, although we can store different segment in
>>> different <piece> tags, Paraview seem to regard them as one piece of
>>> data.
>>> For .pvtp format, each component is stored into a different file,
>>> which is not what our client want.
>>>
>>> Although we can always create our reader plugin for Paraview, I am
>>> wondering whether there already exists this kind of file format saving
>>> segments in one file, with a segment-selectable Paraview interface.
>>>
>>>
>>> Thanks and have a nice day.
>>> Jimmy Chen
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Copy of fmavto.pvd
> Type: text/xml
> Size: 5356 bytes
> Desc: not available
> URL: <http://www.paraview.org/pipermail/paraview/attachments/20131008/8ba2936c/attachment-0001.bin>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 8 Oct 2013 15:23:30 +0000
> From: "Moreland, Kenneth" <kmorel at sandia.gov>
> Subject: Re: [Paraview] Plotting an integrated variable over time
> To: "Scott, W Alan" <wascott at sandia.gov>, "paraview at paraview.org"
>         <paraview at paraview.org>
> Message-ID: <CE797EEE.112CB%kmorel at sandia.gov>
> Content-Type: text/plain; charset="us-ascii"
>
> After you run the IntegrateVariables filter, you probably see the results in a new spreadsheet view. Just select the row containing the integrated variables and run the Plot Selection Over Time filter.
>
> -Ken
>
> From: <Scott>, Walter Scott <wascott at sandia.gov<mailto:wascott at sandia.gov>>
> Date: Monday, October 7, 2013 7:38 PM
> To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
> Subject: [EXTERNAL] [Paraview] Plotting an integrated variable over time
>
> A customer of mine asked the following:
>
>
> Hello,
> I am trying to plot a variable that has been created using the PythonCalculator filter.  First, I create a Cell variable.  Then, I would like to integrate/sum all values for this variable and plot this result as a function of time.
>
> I can use the "IntegrateVariables" filter to look at results individually, but how can I create a variable that can be plotted within ParaView?
>
>
> Thanks,
>
> Alan
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.paraview.org/pipermail/paraview/attachments/20131008/8f193883/attachment-0001.htm>
>
> ------------------------------
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
> End of ParaView Digest, Vol 114, Issue 20
> *****************************************


More information about the ParaView mailing list