On Tue, May 31, 2016 at 3:23 AM, Lorenzo Zanon <[email protected]>
wrote:
> Hello,
>
> I solved the problem. During the "online" run, I was writing down the
> coefficients of the reduced solution u_N in data files, which were then
> read in a separate run to compute the error bound. I converted this
> writing/reading from data files to binary; the precision is now preserved.
>
The ASCII writing in legacy_write_offline_data_to_files() is done through
the Xdr class, but that should be writing 16 digits:
xdr_cxx.C, line 746:
*out << std::scientific
> << std::setprecision(16);
It looks like these lines were added in aff6b5ea, back on 2015-10-26,
though, so if you have al libmesh from before that, the precision might
have been lower.
--
John
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
