[Commits] commit/EinsteinEvolve: 5 new changesets

[Bitbucket]

5 new commits in EinsteinEvolve:

https://bitbucket.org/einsteintoolkit/einsteinevolve/commits/8022c78654f4/
Changeset:   8022c78654f4
Branch:      None
User:        rhaas80
Date:        2020-07-28 15:47:39+00:00
Summary:     GRHydro: remove ADMCoupling from tests

Affected #:  15 files

https://bitbucket.org/einsteintoolkit/einsteinevolve/commits/352c2431ec56/
Changeset:   352c2431ec56
Branch:      None
User:        rhaas80
Date:        2020-07-28 15:47:39+00:00
Summary:     GRHydro_InitData: remove ADMCoupling from tests

Affected #:  2 files

https://bitbucket.org/einsteintoolkit/einsteinevolve/commits/6b8d26f51553/
Changeset:   6b8d26f51553
Branch:      None
User:        rhaas80
Date:        2020-07-28 15:47:39+00:00
Summary:     GRHydro: remove ADMCoupling from tests

Affected #:  12 files

https://bitbucket.org/einsteintoolkit/einsteinevolve/commits/e511916f8ba6/
Changeset:   e511916f8ba6
Branch:      None
User:        rhaas80
Date:        2020-07-28 15:47:39+00:00
Summary:     GRHydro: use ML_ADMConstraints in tests

Affected #:  196 files

https://bitbucket.org/einsteintoolkit/einsteinevolve/commits/6adaab9b2d92/
Changeset:   6adaab9b2d92
Branch:      rhaas/noadmcoupling
User:        rhaas80
Date:        2020-07-28 15:47:39+00:00
Summary:     GRHydro: regenerate constraint data for tests that used ADMConstraints

ADMConstraints and ML_ADMConstraints differ in detail:

* ML_ADMConstraints is always 4th order accurate FD, ADMConstraints
  depends on ADMMacros's order
* ML_ADMConstraints uses a "flat" boundary condition with boundary width
  width, ADMConstraints uses "static" (zero in practise) and 1 point
  wide (at least in this set of tests)

I have verified that the test using ML_ADMConstraints pass with the old
ADMConstraints data if one modifies ML_ADMConstraints to

* use 2nd order finite differencing
* pretends the boundary is 1 point wide

Affected #:  96 files

Repository URL: https://bitbucket.org/einsteintoolkit/einsteinevolve/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.