EinsteinExact

Barry Wardell and Ian Hinder

10 May 2012

Abstract

The EinsteinExact arrangement provides a collection of thorns which compute exact solutions to the Einstein equation and set the 3 + 1 ADM variables provided by the ADMBase thorn. The solutions may be computed either as initial data, or at each iteration of an evolution. The computation is done analytically from expressions for the metric which are taken from a database of solutions provided by the Metrics package for Mathematica. Adding new solutions to EinsteinExact only requires that the metric be added to this database.

1 Introduction

The EinsteinExact code relies on the fact that a given analytic expression for the 4-metric gab (and its inverse gab) of a spacetime may be decomposed into the 3 + 1 ADM variables,

gab = α2 + βkβk βi βi γij ,gab = 1α2 βiα2 βiα2 γij βiβjα2 , (1)

where α is the lapse, βi is the shift and γij is the three metric on the slice. The ADMBase variables for the lapse, shift and three metric may therefore be directly obtained from components of the four metric and its inverse:

α = 1 g00,βi = α2g0i,γ ij = gij. (2)

Another ADMBase variable which must be set is the extrinsic curvature Kij. This may be written as

Kij = 1 2ααnγij (3)

where is the Lie derivative and n is the normal to the slice. Explicitly expanding this out gives

Kij = 1 2α(tγij + Diβj + Djβi) = 1 2α(tγij + βk kγij + γikjβk + γ kjiβk) (4)

which is readily computed from the previous analytic expressions for α, βi and γij. Finally, the ADMBase variables for the time derivatives for the lapse and shift are computed by analytically differentiating α and βi with respect to t.

2 Obtaining EinsteinExact

The latest version of EinsteinExact will always be available from the project git repository:

git clone git://github.com/barrywardell/EinsteinExact

3 Using EinsteinExact

The EinsteinExact thorns are designed to work with Cactus as part of the Einstein Toolkit. All requirements are therefore already included with the Einstein Toolkit.

To use an EinsteinExact thorn, include the thorn for your desired spacetime in your thornlist and in the ActiveThorns section of your parameter file and set either the ADMBase::initial_data or ADMBase::evolution_method parameters (or both) described below. It is also necessary to set the ADMBase::initial_lapse, ADMBase::initial_dtlapse, ADMBase::initial_shift and ADMBase::initial_dtshift parameters in order for storage to be allocated for all ADMBase variables set by EinsteinExact.

As each thorn sets the ADM variables for a specific spacetime in some particular coordinate system it only makes sense to have one thorn in the arrangement activated at a time.

4 Common parameters

Although there is a separate Cactus thorn for each supported spacetime, all thorns are generated from the same Kranc script and therefore share some common parameters. The parameters supported by all thorns are listed in this section.

4.0.1 ADMBase::initial_data

The ADM variables can be set by EinsteinExact as initial data for an evolution. Each EinsteinExact thorn extends the ADMBase::initial_data keyword parameter with another option corresponding to the name of the thorn. If the parameter is set to the thorn name, then initial data for the ADM variables will be set by the thorn in the ADMBase_InitialData schedule bin.

4.0.2 ADMBase::evolution_method

The setting of the ADM variables can optionally be done at each step in an evolution. Each EinsteinExact thorn extends the ADMBase::evolution_method keyword parameter with another option corresponding to the name of the thorn. If the parameter is set to the thorn name, then the ADM variables will be set by the thorn at each iteration during the ANALYSIS schedule bin.

4.0.3 ADMBase::initial_lapse

Each EinsteinExact thorn extends this keyword parameter with another option corresponding to the name of the thorn. This parameter is currently ignored by the EinsteinExact code but must be set nonetheless in order to ensure storage is allocated for the lapse variable.

4.0.4 ADMBase::initial_shift

Each EinsteinExact thorn extends this keyword parameter with another option corresponding to the name of the thorn. This parameter is currently ignored by the EinsteinExact code but must be set nonetheless in order to ensure storage is allocated for the shift variables.

4.0.5 ADMBase::initial_dtlapse

Each EinsteinExact thorn extends this keyword parameter with another option corresponding to the name of the thorn. This parameter is currently ignored by the EinsteinExact code but must be set nonetheless in order to ensure storage is allocated for the dtlapse variable.

4.0.6 ADMBase::initial_dtshift

Each EinsteinExact thorn extends this keyword parameter with another option corresponding to the name of the thorn. This parameter is currently ignored by the EinsteinExact code but must be set nonetheless in order to ensure storage is allocated for the dtshift variables.

4.0.7 Origin: timeoffset, positionx, positiony, positionz

These parameters specify the position at which the origin of the spacetime should be located.

4.0.8 Lapse: lapsefactor

Factor that should rescale the lapse such that α = 1 lapsefactorα. This has the effect of rescaling the time coordinate so that t = lapsefactort. Note that this also has the effect of rescaling the shift by a factor 1 lapsefactor (see xform.nb for more details).

4.0.9 Shift: shiftaddx, shiftaddy, shiftaddz

Shift that should be added to the metric. This has the effect of adding an offset to the spatial coordinates so that x = x shiftaddxt, y = y shiftaddyt, z = z shiftaddzt (see xform.nb for more details).

4.0.10 Lorentz Boost: boostx, boosty, boostz

Lorentz-boost the spacetime by a velocity vi = [boostx,boosty,boostz]. This applies a Lorentz boost transformation to the coordinates of the form

t r = γ γβT γβI + γ2(γ + 1)ββT t r . (5)

4.0.11 Rotation: theta, phi, psi

The spacetime may have an arbitrary 3D rigid rotation applied to it. This rotation is specified by the theta, phi and psi parameters which correspond to the Euler angles of the rotation. The conventions used are such that the rotations are given by the three rotation matrices [1]:

Rϕ = cos (ϕ) sin (ϕ)0 sin (ϕ)cos (ϕ)0 0 0 1 , R𝜃 = 1 0 0 0 cos (𝜃) sin (𝜃) 0 sin (𝜃)cos (𝜃) , Rψ = cos (ψ) sin (ψ)0 sin (ψ)cos (ψ)0 0 0 1 . (6)

5 Included spacetimes

This section lists all spacetimes currently supported by EinsteinExact.

5.1 GaugeWave

Description: 4D flat spacetime in Cartesian gauge wave coordinates
Thorn name: GaugeWave
Parameters: amp, period
Metric:

gab = ampsin 2π(xt) period 1 0 00 0 1 ampsin 2π(xt) period 00 0 0 10 0 0 0 1 (7)

5.2 KerrSchild

Description: Kerr spacetime in Kerr-Schild coordinates
Thorn name: KerrSchild
Parameters: M, a
Metric:

gab = 2Mr3 a2z2+r4 1 2Mr3(ay+rx) a2+r2 a2z2+r4 2Mr3(ryax) a2+r2 a2z2+r4 2Mr2z a2z2+r4 2Mr3(ay+rx) a2+r2 a2z2+r4 2Mr3(ay+rx)2 a2+r2 2 a2z2+r4 + 12Mr3(ay+rx)(ryax) a2+r2 2 a2z2+r4 2Mr2z(ay+rx) a2+r2 a2z2+r4 2Mr3(ryax) a2+r2 a2z2+r4 2Mr3(ay+rx)(ryax) a2+r2 2 a2z2+r4 2Mr3(ryax)2 a2+r2 2 a2z2+r4 + 1 2Mr2z(ryax) a2+r2 a2z2+r4 2Mr2z a2z2+r4 2Mr2z(ay+rx) a2+r2 a2z2+r4 2Mr2z(ryax) a2+r2 a2z2+r4 2Mrz2 a2z2+r4 + 1 (8)

where

r(x,y,z) = a2 + x2 + y2 + z2 2 + 4a2 z2 a2 + x2 + y2 + z2 2 (9)

5.3 Minkowski

Description: 4D flat spacetime in Cartesian coordinates
Thorn name: Minkowski
Metric:

gab = 1000 0 1 0 0 0 010 0 0 0 1 (10)

5.4 ShiftedGaugeWave

Description: 4D flat spacetime in Cartesian shifted gauge wave coordinates
Thorn name: ShiftedGaugeWave
Parameters: amp, period
Metric:

gab = ampsin 2π(xt) period 1 ampsin 2π(xt) period 00 ampsin 2π(xt) period ampsin 2π(xt) period + 100 0 0 10 0 0 0 1 (11)

5.5 Vaidya

Description: A Vaidya spacetime with mass function m(v) = M (1 + Tanh[v dM / M]2)
Thorn name: Vaidya2
Parameters: M, dM
Metric:

gab = 2m r 1 2mx r2 2my r2 2mz r2 2mx r2 2mx2 r3 + 1 2mxy r3 2mxz r3 2my r2 2mxy r3 2my2 r3 + 1 2myz r3 2mz r2 2mxz r3 2myz r3 2mz2 r3 + 1 (12)

where

r(x,y,z) = x2 + y2 + z2 (13)
m(t,x,y,z) = M tanh 2 dM t + x2 + y2 + z2 M + 1 (14)

5.6 ModifiedSchwarzschildBL

Description: Modified Schwarzschild spacetime in Brill-Lindquist coordinates with a radially dependent mass inside the black hole
Thorn name: ModifiedSchwarzschildBL
Parameters: M, epsilon
Metric:

gab = 1 0 0 0 0 1 + M(r) 2r 4 0 0 0 0 1 + M(r) 2r 4 0 0 0 0 1 + M(r) 2r 4 (15)

where

r(x,y,z) = x2 + y2 + z2 (16)
M(r) = 4r 8r2 2 +[cos (4πr M )1] M 4π2 M : r < M2 M : r M2 (17)

6 Modifying EinsteinExact

6.1 Generating the code

The script which generates the thorns requires the Kranc and Metrics Mathematica packages to be installed. Kranc is included with the Einstein Toolkit and the Metrics package is included in the Metrics directory.

To regenerate the code make from within the m directory.

6.2 Adding a spacetime

To add a new spacetime to EinsteinExact, simply create a new file for the spacetime under m/Metrics/metrics/ and then add this spacetime to the thorns = and spacetimes = lines at the end of the Kranc script in m/EinsteinExact.m. Also consider adding a regression test to the EinsteinExact_test thorn and correctness tests under the tests directory.

If you think this spacetime would be of use to others, please consider submitting a patch. As all of the spacetimes in the EinsteinExact arrangement come from them Metrics database it is highly preferable to have new spacetimes added to the upstream repository for the Metrics package. The version of the Metrics package used by EinsteinExact can then be updated.

6.3 Updating the Metrics database

The Metrics database exists as a separate git repository. For convenience, a version of it is included with EinsteinExact under the m/Metrics directory. This is a version of the standalone Metrics repository which has been merged using the git-subtree command1 .

If a new version of the Metrics package becomes available, the version in the EinsteinExact repository may be updated using the following command:

git subtree pull --prefix=m/Metrics --squash git://github.com/barrywardell/Metrics master

This will pull in new changes from the Metrics repository and merge them with the EinsteinExact repository under the m/Metrics directory.

7 Tests

7.1 Correctness tests

There are correctness tests for the EinsteinExact thorns under the tests directory. These tests include:

In addition, the Metrics package has independent correctness tests which check that the provided metrics are correct.

7.2 Regression tests

Each thorn provided by EinsteinExact has a corresponding regression test in the EinsteinExact_code thorn which checks that no new bugs are introduced in the code.

8 Acknowledgments

Erik Schnetter contributed helpful comments and suggestions, along with some patches for the code.

References

[1]   Eric W. Weisstein, Euler Angles, MathWorld–A Wolfram Web Resource. http://mathworld.wolfram.com/EulerAngles.html