Dear Christian, Ian, and others,

Sorry for the misunderstanding. We intended to supply our interpolation operators to ET without any preconditions. Note that the code we contribute is no silver bullet; there is a lot of careful bookkeeping that must be done to construct an MHD code around these infrastructure improvements. Our hope was that our contribution would bring us closer to those in the ET community who have multipatch code, which could be beneficial to us. Our idea is that we play an advisory role in helping the multipatch team with construction of such an MHD code, which would expedite the process greatly, and allow the multipatch code to be shared with us.

Sincerely,

The Illinois Numerical Relativity Group
-Zach Etienne
-Yuk Tung Liu
-Vasilis Paschalidis
-Stu Shapiro


On Mon, Nov 28, 2011 at 5:38 PM, Ian Hinder <ian.hinder@aei.mpg.de> wrote:

On 29 Nov 2011, at 00:03, Christian D. Ott wrote:

What you would get -- and what everybody gets who contributes -- is
respect, pride, and acknowledgement (and citations) for contributing
code to the Einstein Toolkit as open source. Should you decide to
actively help with the Toolkit and its maintenance, you will also be
able to co-author a future follow-up ET paper.

You also get many eyes on your code, which may spot bugs that would be missed otherwise.  Additionally, ET members ensure that the code builds and runs successfully on a large number of machines for each ET release.  A recent example is the work done to make sure the PITT Null Code, a recent contribution, worked on a number of machines where it was failing.  Further, as part of the ET, the community will ensure that the code remains compatible with any possible changes in Cactus or other thorns that it depends on.  In other words, now that you have written the code, the community can help with the unglamorous "maintenance" that it requires.