<div dir="ltr">I briefly looked at that a couple of weeks ago. Sorry I didn't get back to you before now.<div><br></div><div>My findings were:</div><div><div>1) xdm3writer performs the same as xdmf2writer </div><div>2) I didn't find a compression option.</div><div><br></div></div><div>So, in other words, I don't have a quick fix and someone needs to put some development time in to improve it.</div><div>The good news is that there is lots of room for improvement and it shouldn't be too hard to do better on the writer end. It is very likely that the ARL guys will have ideas of on ways to compress within libxdmf.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div>David E DeMarle<br>Kitware, Inc.<br>R&D Engineer<br>21 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-881-4909</div>
<br><div class="gmail_quote">On Wed, Sep 17, 2014 at 10:16 AM, Su, Simon M CTR USARMY ARL (US) <span dir="ltr"><<a href="mailto:simon.m.su.ctr@mail.mil" target="_blank">simon.m.su.ctr@mail.mil</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">thanks Dave. We will remember that when we do the compile after 4.2 release...<br>
<br>
I tried xdmf3 writer using the File->Save Data option in PV v4.2.0-RC1-75-gf64ee7a and the 82M pvd file still turn into a 4.4G h5 file. Not sure if something that I am not doing right? Is there like a compression flag that I can turn on? thanks...<br>
<br>
thanks<br>
-simon<br>
<div style="font-family:Times New Roman;color:#000000;font-size:16px">
<hr>
<div style="direction:ltr"><font color="#000000" face="Tahoma"><b>From:</b> David E DeMarle [<a href="mailto:dave.demarle@kitware.com" target="_blank">dave.demarle@kitware.com</a>]<br>
<b>Sent:</b> Wednesday, September 17, 2014 11:56 AM<br>
<b>To:</b> Ben Boeckel<br>
<b>Cc:</b> Su, Simon M CTR USARMY ARL (US); <a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a><br>
<b>Subject:</b> Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON<br>
</font><br>
</div><div><div class="h5">
<div></div>
<div>
<div dir="ltr">
<div><font face="arial, sans-serif">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.</font></div>
<div><font face="arial, sans-serif"><br>
</font></div>
<div><font face="arial, sans-serif">To get around it I downloaded my own boost (no need to compile it) and made the my PV build use it by:</font></div>
<span style="font-family:arial,sans-serif;font-size:13px">In cmakecache.txt </span>
<div><span style="font-family:arial,sans-serif;font-size:13px">set Boost_NO_SYSTEM_PATHS:BOOL=ON</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">set Boost_NO_BOOST_CMAKE:BOOL=ON</span><br>
</div>
<div><span style="font-family:arial,sans-serif;font-size:13px">Then it will ask for an respect your choice of boost headers to use.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
</div>
<div class="gmail_extra"><br clear="all">
<div>David E DeMarle<br>
Kitware, Inc.<br>
R&D Engineer<br>
21 Corporate Drive<br>
Clifton Park, NY 12065-8662<br>
Phone: <a href="tel:518-881-4909" value="+15188814909" target="_blank">518-881-4909</a></div>
<br>
<div class="gmail_quote">On Tue, Sep 16, 2014 at 12:55 PM, Ben Boeckel <span dir="ltr">
<<a href="mailto:ben.boeckel@kitware.com" target="_blank">ben.boeckel@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span>On Tue, Sep 16, 2014 at 16:22:38 +0000, Su, Simon M CTR USARMY ARL (US) wrote:<br>
> I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file<br>
> size is still increase 10 fold when saving pvd file to xmf format.<br>
><br>
> However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with<br>
> -DModule_vtkIOXdmf3:BOOL=ON<br>
><br>
> cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/<br>
> paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa -DPARAVIEW_ENABLE_PYTHON:BOOL=ON<br>
> -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF<br>
> -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a<br>
><br>
> I got whole bunch of boost related cmake error with cmake version 3.0.0 and<br>
> cmake version 2.8.12.2. Some of the error messages are included at the end of<br>
> this email.<br>
><br>
> I am able to compile RC1-22-g9ca4e44 version ok but without Module_vtkIOXdmf3<br>
> set to ON. Is there anything on the boost side that I am not setting it right?<br>
> I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 installed.<br>
<br>
</span>Looks to be a CMake-ified boost. It worked here on Fedora with 1.54.0<br>
(which I don't believe is built using CMake anymore). It seems that it<br>
doesn't support multiple find_package calls. Try setting<br>
Boost_NO_BOOST_CMAKE to ON to force the FindBoost.cmake logic to kick<br>
in.<br>
<br>
--Ben<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">
http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">
http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div></div></div>
</div>
</div>
</blockquote></div><br></div>