[petsc-dev] Comparing binary output files in test harness

[Scott Kruger]

Could you file a gitlab issue on this?

Offhand, I think it'd be best to modify petscdiff to check the suffix
and then pass it off to exodiff.  This would be more easily extended to
other file types (e.g., h5diff).  

Scott

On 2021-02-19 04:59, Blaise A Bourdin did write:
> Hi,
> 
> I would like to write better tests for my exodus I/O functions and compare the binary files written to the drive instead of the output of the examples.
> For instance, would it be possible to do the following:
> 	ex26 -i <input mesh> -o output1.exo; mpirun -np 2 ex26 -i <input mesh> -o output2.exo; exodiff output1.exo output2.exo
> And check the result of exodiff, or run exodiff between output1.exo or output2.exo and a stored binary result?
> 
> Regards,
> Blaise
> 
> -- 
> A.K. & Shirley Barton Professor of  Mathematics
> Adjunct Professor of Mechanical Engineering
> Adjunct of the Center for Computation & Technology
> Louisiana State University, Lockett Hall Room 344, Baton Rouge, LA 70803, USA
> Tel. +1 (225) 578 1612, Fax  +1 (225) 578 4276 Web http://www.math.lsu.edu/~bourdin
> 

-- 
Scott Kruger
Tech-X Corporation               kruger at txcorp.com
5621 Arapahoe Ave, Suite A       Phone: (720) 466-3196
Boulder, CO 80303                Fax:   (303) 448-7756