← Back to team overview

ffc team mailing list archive

Re: [HG FFC] Added test suite to verify correctness of tabulate_tensor() compared to reference values.

 

Hi,

This is my standard procedure for FFC development:

  1. Modify FFC
  2. Run regression tests
  3. Regression tests fails
  4. Look at code, to see if it makes sense
  5. Generate new references
  6. Push to repository


Instead of step 4 it would obviously be better to actually check if the new code
still computes the right thing. To this end I've created a module that verifies
if tabulate_tensor() is correct according to some reference. The module needs
ufc_benchmark to run.

have a look at ffc/src/test/verify_tensor/test.py

./test.py -h


Kristian



Quoting FFC <ffc@xxxxxxxxxx>:

> One or more new changesets pushed to the primary ffc repository.
> A short summary of the last three changesets is included below.
> 
> changeset:   1201:46afb0cbcaf0b24300bdcc387ceed426d530fda3
> tag:         tip
> user:        "Kristian Oelgaard <k.b.oelgaard@xxxxxxxxxx>"
> date:        Wed Sep 10 10:45:24 2008 +0200
> files:       src/test/verify_tensors/references/README
> src/test/verify_tensors/test.py
> description:
> Added test suite to verify correctness of tabulate_tensor() compared to
> reference values.
> 
> 
> changeset:   1200:e71fefc4b7a9e0551360d71a0554a4b2628e12a6
> user:        "Kristian Oelgaard <k.b.oelgaard@xxxxxxxxxx>"
> date:        Tue Sep 09 13:50:53 2008 +0200
> files:       src/ffc/compiler/codegeneration/quadrature/reduce_operations.py
> description:
> Minor bug fix for quadrature representation.
> 
> 
> changeset:   1199:2b9342b28e97b64522fcd18f10750e9d348c2347
> user:        "Kristian Oelgaard <k.b.oelgaard@xxxxxxxxxx>"
> date:        Mon Sep 08 19:59:31 2008 +0200
> files:       ChangeLog TODO
> description:
> Update TODO and ChangeLog with display of operation count.
> 
> ----------------------------------------------------------------------
> For more details, visit http://www.fenics.org/hg/ffc
> _______________________________________________
> FFC-dev mailing list
> FFC-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/ffc-dev
> 




Follow ups

References