aboutsummaryrefslogtreecommitdiff
path: root/schedule.ccl
diff options
context:
space:
mode:
authorjthorn <jthorn@edbb7e70-9571-45d5-a481-0a560a9b4751>2004-06-11 13:13:24 +0000
committerjthorn <jthorn@edbb7e70-9571-45d5-a481-0a560a9b4751>2004-06-11 13:13:24 +0000
commitb4ccd972722662265f48f834aecdc5bfed35f224 (patch)
tree54f6c9479de88f7f05caee65c6a4b03a719e51ea /schedule.ccl
parent1217bad7bc48d3285cc31d1e1e224a3bef11b451 (diff)
This thorn guide describes a fancy mechanism for registering gauge
conditions. But at present, few (if any?) thorns seem to actually use it. So... add a description of the way most (all?) gauge thorns actually work at present, so the next innocent who comes along isn't quite so confused as I was... :) git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinBase/CoordGauge/trunk@57 edbb7e70-9571-45d5-a481-0a560a9b4751
Diffstat (limited to 'schedule.ccl')
0 files changed, 0 insertions, 0 deletions