On Fri, Feb 10, 2017 at 3:21 PM, Salazar De Troya, Miguel < salazardet...@llnl.gov> wrote:
> Hello all > > Suppose I am running a simulation in parallel and I want to compare that > solution to a previous run of the same problem. Is there any way to have > libMesh print the solution with the same order so I can compare that > solution with a previous one? It would be for testing purposes to make sure > I am getting the same solution always. What’s the current approach in > libMesh for testing? > There are a few different ways of doing this. If you are writing Exodus files, the exodiff utility which comes with the SEACAS tools ( https://github.com/gsjaardema/seacas) can be used to diff two Exodus files (and even write the diff to a third file for inspection) while ignoring the node and element numbering (use the -m option to exodiff). Building exodiff from scratch is a bit challenging, but if you have MOOSE installed it's available in the contrib/ directory. Another approach would be to use the src/apps/compare.C utility, but I don't know if that still actually works. Looks like it's been quite a while since anyone has done more than just keep it compiling. -- John ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
