diff options
author | jthorn <jthorn@e296648e-0e4f-0410-bd07-d597d9acff87> | 2002-06-16 16:46:40 +0000 |
---|---|---|
committer | jthorn <jthorn@e296648e-0e4f-0410-bd07-d597d9acff87> | 2002-06-16 16:46:40 +0000 |
commit | a98b694e18fcf946de0610241e15967406257430 (patch) | |
tree | 1baafecda56af0b680611a5a333ce4d057f42b21 /schedule.ccl | |
parent | ce3c9ef872fdfa9c5f6327ff41c837718e2993f0 (diff) |
[[This is a redo of my "cvs import" of 2002/06/11, this time using proper
cvs operations (commit/delete/add) to preserve the full CVS history of this
thorn.]]
This is a major cleanup/revision of AEIThorns/Exact.
Major user-visible changes:
* major expansion of doc/documentation.tex
* major expansion of documentation in param.ccl file
* rename all parameters, systematize spacetime/coordinate/parameter names
(there is a perl script in par/convert-pars.pl to convert old parameter
files to the new names)
* [from Mitica Vulcanov] many additions and fixes to
cosmological solutions and Schwarzschild-Lemaitre
* fix stress-energy tensor computations so they work -- before they were
all disabled in CVS (INCLUDES lines were commented out in interface.ccl)
due to requiring excessive friendship with evolution thorns
and/or public parameters; new code copies parameters to restricted
grid scalars, which Cactus automagically "pushes" to friends
* added some more tests to testsuite, though these don't yet work fully
Additional internal changes:
* rename many Fortran subroutines (and a few C ones too)
so their names start with the thorn name
to reduce the chances of name collisions with other thorns
* move all metrics to subdirectory so the main source directory isn't
so cluttered
* move two files containing subroutines which were never called
(they didn't belong in this thorn, but somehow got into cvs by accident)
into new archive/ directory
* some (small) improvements in efficiency -- the exact_model parameter
is now decoded from a keyword (string) to an integer once at INITIAL,
and that integer tested by the stress-energy tensor code,
rather than requiring a separate series of string tests at each grid
point (!) like the old stress-energy tensor code did
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinInitialData/Exact/trunk@91 e296648e-0e4f-0410-bd07-d597d9acff87
Diffstat (limited to 'schedule.ccl')
-rw-r--r-- | schedule.ccl | 35 |
1 files changed, 21 insertions, 14 deletions
diff --git a/schedule.ccl b/schedule.ccl index bccb4fe..f8faeab 100644 --- a/schedule.ccl +++ b/schedule.ccl @@ -1,23 +1,32 @@ # Schedule definitions for thorn Exact +# $Header$ ####################################################################### # PARAMCHECK ####################################################################### -schedule Exact_ParamCheck at CCTK_PARAMCHECK +Schedule Exact_ParamCheck at PARAMCHECK { - LANG: C -} "Check for sensible parameter combinations" +LANG: C +} "do consistency checks on our parameters" ####################################################################### # INITIAL DATA ####################################################################### +# decode/copy parameters into grid scalars +# (to share them properly so Calc_Tmunu code can see them even +# though it's compiled in other thorns) +Schedule Exact__decode_pars at INITIAL +{ +LANG: Fortran +} "decode/copy thorn Exact parameters into grid scalars" + # Initial data (g and K) from a trivial slice through an exact solution. if (CCTK_Equals(initial_data,"exact")) { - schedule exactinitialize at CCTK_INITIAL + schedule Exact__initialize at CCTK_INITIAL { LANG: Fortran } "Set initial data from exact solution on a trivial slice" @@ -29,7 +38,7 @@ if (CCTK_Equals(initial_data,"exact")) if ( (CCTK_Equals(initial_data,"slice")) && ! (CCTK_Equals(evolution_method,"slice")) ) { - schedule slice_initialize at CCTK_INITIAL + schedule Exact__slice_initialize at CCTK_INITIAL { STORAGE: Exact_slice LANG: Fortran @@ -45,7 +54,7 @@ if ( (CCTK_Equals(initial_data,"slice")) && ! (CCTK_Equals(evolution_method,"sli if ( (CCTK_Equals(initial_lapse,"exact")) || (CCTK_Equals(initial_shift,"exact")) ) { - schedule exactgauge at CCTK_INITIAL + schedule Exact__gauge at CCTK_INITIAL { LANG: Fortran } "Set initial lapse and/or shift from exact solution on a trivial slice" @@ -55,13 +64,13 @@ if ( (CCTK_Equals(initial_lapse,"exact")) || (CCTK_Equals(initial_shift,"exact") if ( (CCTK_Equals(lapse_evolution_method,"exact")) || (CCTK_Equals(shift_evolution_method,"exact")) ) { - schedule Exact_RegisterSlicing at CCTK_STARTUP + schedule Exact__RegisterSlicing at CCTK_STARTUP { LANG: C } "Register slicings" - schedule exactgauge at CCTK_PRESTEP - { + schedule Exact__gauge at CCTK_PRESTEP + { LANG: Fortran } "Set evolution lapse and/or shift from exact solution on a trivial slice" } @@ -83,12 +92,12 @@ if ( (CCTK_Equals(evolution_method,"slice")) && (CCTK_Equals(initial_data,"slice STORAGE: Exact_slicetemp1 STORAGE: Exact_slicetemp2 - schedule slice_initialize at CCTK_INITIAL + schedule Exact__slice_initialize at CCTK_INITIAL { LANG: Fortran } "Set initial data from exact solution on arbitrary slice" - schedule slice_evolve at CCTK_EVOL + schedule Exact__slice_evolve at CCTK_EVOL { LANG: Fortran } "Evolve arbitrary slice and extract Cauchy data" @@ -100,10 +109,8 @@ if ( (CCTK_Equals(evolution_method,"slice")) && (CCTK_Equals(initial_data,"slice if (CCTK_Equals(overwrite_boundary,"exact")) { - schedule exactboundary at CCTK_POSTSTEP + schedule Exact__boundary at CCTK_POSTSTEP { LANG: Fortran } "Overwrite g and K on the boundary with exact solution data" } - - |