[mailto:paraview-boun...@paraview.org] On Behalf Of Su, Simon
M CTR USARMY ARL (US)
Sent: Wednesday, September 17, 2014 1:07 PM
To: David E DeMarle
Cc: paraview@paraview.org
Subject: Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with
-DModule_vtkIOXdmf3:BOOL=ON
thanks Dave I will pass
thanks for the tip. I got the new reader compiled, but I am disappointed to see
that it crashes immediately on my existing data (which can be read in parallel,
with the old xdmf2 reader).
ERROR: In
/apps/pilatus/ParaView/src/ParaView/VTK/Common/Core/vtkDataArrayTemplate.txx,
line 148
I had similar config problems in the DoD HPC machines I tested on. The root
cause was that the system boost was CMakefied and find boost didn't like it
but insisted on using it.
To get around it I downloaded my own boost (no need to compile it) and made
the my PV build use it by:
In
There are some annoying and minor differences in the XDMF xml format in the
new and old versions.
For example case sensitivity and changes in treatment of default values. My
first intuition is that these are the cause.
Jean if you can provide me with a minimal example that demonstrates the
-RC1-75-gf64ee7a with
-DModule_vtkIOXdmf3:BOOL=ON
I had similar config problems in the DoD HPC machines I tested on. The root
cause was that the system boost was CMakefied and find boost didn't like it but
insisted on using it.
To get around it I downloaded my own boost (no need to compile
, September 17, 2014 11:56 AM
*To:* Ben Boeckel
*Cc:* Su, Simon M CTR USARMY ARL (US); paraview@paraview.org
*Subject:* Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with
-DModule_vtkIOXdmf3:BOOL=ON
I had similar config problems in the DoD HPC machines I tested on. The
root cause
: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with
-DModule_vtkIOXdmf3:BOOL=ON
I briefly looked at that a couple of weeks ago. Sorry I didn't get back to you
before now.
My findings were:
1) xdm3writer performs the same as xdmf2writer
2) I didn't find a compression option.
So, in other
Hello,
I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file
size is still increase 10 fold when saving pvd file to xmf format.
However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with
-DModule_vtkIOXdmf3:BOOL=ON
cmake -DCMAKE_BUILD_TYPE=release
On Tue, Sep 16, 2014 at 16:22:38 +, Su, Simon M CTR USARMY ARL (US) wrote:
I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the
file
size is still increase 10 fold when saving pvd file to xmf format.
However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with
