remove ADMCoupling from test cases, use ML_ADMConstraints instead of (nonexistent) ADMConstraints

Exact: switch to new Tmunu interface

Exact: convert tmunu source for to free-form Fortran

no other change

Exact: no longer be FRIEND with ADMCoupling

this was required to support the old style Tmunu interface

Exact: fix adding to Tmunu grid functions

Exact: remove ADMCoupling from tests

Exact: use ML_ADMConstraints instead of ADMConstraints

Exact: regenerate deSitter test data

identical to told data in overlapping region of grid

IDAxiOddBrillBH: remove ADMCoupling from tests

TwoPunctures: remove ADMCoupling from tests

DistortedBHIVP: remove ADMCoupling from tests

RotatingDBHIVP: remove ADMCoupling from tests

TOVSolver: remove ADMCoupling from tests

Hydro_InitExcision: remove ADMCoupling from tests

IDAxiBrillBH: remove ADMCoupling from tests

IDConstraintViolate: remove ADMCoupling from tests

TOVSolver:: remove ADMCoupling from tests

TwoPunctures: replace ADMConstraints by ML_ADMConstraints in test

TwoPunctures: regenerate constraint data

verified that results are identical to ADMConstraints if:

• one uses 1 boundary and ghost point

• modifies ML_ADMConstraints for 2nd order accuracy

• modifes ML_ADMConstraints to run in ANALYSIS rather than MoL_PostStep

TOVSolver: replace ADMConstraints by ML_ADMConstraints in tests

TOVSolver: regenerate test data

increased boundary size to as required by ML_ADMConstraints, test passes with old data (except some norms) if

• ML_ADMConstraints is changed to use 2nd order FD

IDConstraintViolate: replace ADMConstraints by ML_ADMConstraints in test

IDConstrainViolate: regenerate test data

verified that old data passes with ML_ADMConstraints if:

• one changes ML_ADMConstraints to be 2nd order

• runs ML_ADMConstraints in ANALYSIS

• changes the b/c to static