<div dir="ltr">Hi Bucky,<div><br></div><div>ParaView 4.3 uses a reader code from the CosmoTools library. This is unlike previous versions which had a built-in reader. The new reader code is up-to-date with the current HACC output and is maintained the the HACC team. Hence the difference. Looking at the CosmoTools library, there seems to be a compile time option to set the integer types to 32 bits (TYPE_IDS_64BITS). However, since this is a compile time option in CosmoTools, the only way to get at this is to recompile CosmoTools and ParaView. If you are interested in pursuing this option, we can help. We can't really change the binaries we distribute since the 64 bit tags is currently what HACC outputs.</div><div><br></div><div>Best,</div><div>-berk</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 30, 2015 at 10:50 AM, Kashiwa, Bucky <span dir="ltr"><<a href="mailto:bak@lanl.gov" target="_blank">bak@lanl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We have been very happily reading classical *.cosmo formatted datafiles<br>
using version 3.98.1, but when reading the same files in subsequent<br>
versions (4.0, 4.1, 4.2, 4.3) the data get read, but wrongly interpreted.<br>
I did the diff of the PCosmoReader.h between v3.98.1 and v4.3.1 which<br>
suggested to me that the last number in the cosmo data (called ¹tag¹) is<br>
now int64_t rather than integer. So if we write the cosmo data with type<br>
MPI_2INTEGER (~ fortran kind=SELECTED_INT_KIND(15)) then the data are read<br>
correctly by the v4.3.1 cosmo reader (without byte swap).<br>
<br>
If I select the ŒAdaptive cosmo reader¹ from the reader list, it displays<br>
a button for the ¹Tag Size¹ which can be 32-bit or 64-bit. This button<br>
does not appear on the ŒCosmology Files¹ choice from the reader list.<br>
<br>
Could it be that the build system is somehow failing to place the ¹Tag<br>
Size¹ button on the ŒCosmology Files¹ Properties panel? If so, it would<br>
be wonderful to get it put there so that we can have the choice of Tag<br>
Size on the very useful .cosmo datafiles. If not, please let us know if<br>
we are stuck with a 64-bit Tag Size.<br>
<br>
Thanks very much.<br>
======================================================================73<br>
<>Bucky Kashiwa PhD, PE <> Post: MS B216, Los Alamos, NM 87545 <><br>
<> Ofc: TA3-SM123-RM276 <>Email: <a href="mailto:bak@lanl.gov">bak@lanl.gov</a>, <a href="mailto:kashiwa@qwest.net">kashiwa@qwest.net</a> <><br>
<>Voice: <a href="tel:505-667-8812" value="+15056678812">505-667-8812</a> <> Fax: <a href="tel:505-665-5926" value="+15056655926">505-665-5926</a> <><br>
<> Home: <a href="tel:505-988-7332" value="+15059887332">505-988-7332</a> <> Cell: <a href="tel:505-795-5581" value="+15057955581">505-795-5581</a> <><br>
=======================================================================73<br>
<br>
<br>
_______________________________________________<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/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/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=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/mailman/listinfo/paraview</a><br>
</blockquote></div><br></div>