On Fri, Mar 13, 2015 at 12:28 PM, Manav Bhatia <[email protected]> wrote:
> Thanks for the correction, John. I had meant to say "float". > > At my end, I have temporarily changed all "floats" to "double" in the > metis/parmetis files in libmesh, but this is a temporary fix. > > It would be better to source it from the respective headers. But that > raises another point: as of now, it seems like the metis.h in contrib has a > hardcoded value of real width to be 32. I understand that this saves memory > space, but would there be a motivation to keep this scalar type to be > consistent with the rest of the library? > The floating point stuff is bad... converting double to float certainly has loss of precision issues, but I'm also worried about the case when PETSc and libmesh are configured with --with-64-bit-indices and --with-dof-id-bytes=8, respectively, and we continue using int when passing data through the libmesh/Metis-Parmetis interfaces. -- John ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
