Re: [Paraview] [Non-DoD Source] XDMF crash

The load time is because Paraview needs a moment to load the data for the new timestep in. When you switch variables all the data is in memory already. This is done because Paraview is designed to work with large datasets. For higher scale implementations it wouldn't be feasible to have all

Re: [Paraview] Embedding the Visualizer app in the browser within an iframe

Hi Debopam, Here is the link for the live the documentation: => http://kitware.github.io/paraviewweb/docs/windows_10.html The source file for it is available below: => https://github.com/Kitware/paraviewweb/blob/master/documentation/content/docs/windows_10.md Thanks again for your

Re: [Paraview] [Non-DoD Source] XDMF crash

I already tried XPath pointers, but it takes a few seconds in ParaView when I click to the next time frame --- whereas it takes only 0.1s to change the color when I switch the Active Variable for the ColorMap in ParaView's dropdown. I thought using SubSet, ParaView might "recognize" that it is

Re: [Paraview] Windows plugin compatibility with Paraview

On Wed, Jan 25, 2017 at 11:08:00 -0600, Chris Marsh wrote: > I would like to build and make available a pre-compiled windows binary for > a filter I have developed. I would like to avoid the (windows) user having > to compile the filter as well as paraview. Therefore I am wondering what > compiler

Re: [Paraview] [Non-DoD Source] XDMF crash

>From my understanding of your method, you want to use the progression of >"time" to iterate across attribute displays? You don't need GridType="Subset" for that (and I don't think Xdmf3 uses that designation anyway). Just use XPointers to point the grids to the topology and geometry of the

Re: [Paraview] [Non-DoD Source] XDMF crash

Hello Mr. Burns, thank you very much for your helpful answer. I changed the XDMF file. But now I have another question. Now I have problems with GridType="SubSet". ParaView doesn't view the second and third timestep. Their grids are referenced as SubSet from the first grid. This is the reason

Re: [Paraview] [EXTERNAL] Paraview 5.2.0: max time limit of 4095 for annotated .vtu file?

Thanks! You definitely did a good job with that bug report! Alan From: david.b...@csiro.au [mailto:david.b...@csiro.au] Sent: Wednesday, January 25, 2017 12:32 AM To: Scott, W Alan ; paraview@paraview.org Cc: david.b...@csiro.au Subject: RE: [EXTERNAL] [Paraview] Paraview

[Paraview] Windows plugin compatibility with Paraview

I would like to build and make available a pre-compiled windows binary for a filter I have developed. I would like to avoid the (windows) user having to compile the filter as well as paraview. Therefore I am wondering what compiler is used to produce the official Paraview builds so-as to avoid ABI

Re: [Paraview] Time Source for Data Arrays

I have examined Utkarsh's example because it is similar to one of my projects. Thanks. Yet, I am sorry to say I cannot execute it cleanly, without a small edit. I run PV 5.2. I execute script.py from the Python Shell. An image of the can is displayed, yet what is not working is that the

Re: [Paraview] [Non-DoD Source] XDMF crash

This is because the Xdmf3 reader does not support the Hyperslab Timetype. One Time item per grid is the preferred method. Andrew Burns Software Engineer | SAIC Phone: 410-306-0409 ARL DSRC andrew.j.burns35@mail.mil -Original Message- From: ParaView

[Paraview] XDMF crash

I generated the following XDMF file and tried to open it in ParaView. When I open it, I get a dialog with three readers to choose: - XDMF reader - XDMF3 reader - XDMF3 reader (Top Level Partition) I can open the file with "XDMF reader", but when I open it with the other two readers, ParaView