<div dir="ltr">Hi Mike.<div><br></div><div>You mean select the XDMF "Reader", not "Writer" when you open the file correct?</div><div><br></div><div><div>In theory XDMF3 should read almost anything XDMF2 could. The main practical differences in my recollection are:</div></div><div><br></div><div>+ xdmf3 doesn't leak memory and is faster and less of a memory hog, especially with time varying data, in my experience.<br></div><div><div>+ xdmf3's field data arrays work better and in particular support arbitrary width arrays</div></div><div>+ Thanks to Michal Habera's Google Summer of Code project xdmf3 master (in nightly binaries and will appear in PV 5.5) has support for "other" centered (more than 1 per cell) data in support of FEniCS higher order cells.<br></div><div><div><div>+ xdmf3 has a much better suite of tests and contribution path than xdmf2 ever did</div></div><div><br></div><div>= xdmf3 had a boost dependency up until about a week ago (will appear in PV 5.5).</div></div><div><br></div><div>- xdmf3 tends to complain on files that use default/implied values in the xml entries.<br></div><div>- xdmf3 doesn't automatically parallelize structured datasets when read in parallel<br></div><div>- xdmf3 doesn't support strides for structured datasets</div><div>- xdfm3 doesn't support "hyperslab, list or range" temporal specifications</div><div>- xdmf3 lacks support for function specifications</div><div>- xdmf3's notion of subset is slightly different than xdmf2 (2's were relative to cell, 3's are relative to face/edge or something to that effect)<br></div><div><br></div><div>If you can share one of your files I'll take a look.</div><div><br></div><div>thanks</div><div><br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>David E DeMarle<br>Kitware, Inc.<br>Principal Engineer<br>21 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-881-4909</div></div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Sep 28, 2017 at 8:57 AM, Michael Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Where might I find the differences between XDMF version 2 and 3? Our project writes a .xdmf file along side our HDF5 file so that ParaView can visualize the data. Ever since ParaView version 5.x was released with the XDMF 3 included we always have to select the "XDMF Writer" when opening the file. If we select the either of the XDMF 3 writers no data is loaded. I was wanting to figure out if there is something we need to adjust in our XDMF files so that the XDMF 3 readers work correctly with our data/files.<br>
<br>
Thanks<br>
--<br>
Michael Jackson | Owner, President<br>
BlueQuartz Software<br>
[e] <a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a><br>
[w] <a href="http://www.bluequartz.net" rel="noreferrer" target="_blank">www.bluequartz.net</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/<wbr>ParaView</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/paraview</a><br>
</blockquote></div><br></div>