| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@143 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
| |
until a better solution is found
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@142 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
| |
and CCTK_POSTRESTRICT. Previously, the constraints would have contained undefined (or poison) values after regridding.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@141 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@133 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@131 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
| |
variables exist.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@130 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
constraints_persist=yes:
Calculate constraints at POSTINITIAL (after MoL_PostInitial and
MoL_PostStep) and at EVOL (after MoL_Evolution).
Re-apply the constraint boundary conditions at POSTREGRID and
POSTRESTRICT.
(This method is closer to the way in which time-evolved quantities are
handled.)
Introduce a new schedule group ADMConstraintsBoundariesGroup which
applies only the constraint boundaries.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@129 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that mesh refinement boundaries can be interpolated in time. Add
parameter ADMConstraints::constraints_timelevels, which defaults to 1.
Add parameter ADMConstraints::constraints_prolongation_type, which
chooses the interpolator for the constraints. It defaults to
"Lagrange".
Document that the parameter ADMConstraints::excise is not only
deprecated, but also unused.
Schedule constraint calculation in a group ADMConstraintsGroup, so
that it can be easily scheduled at several times.
If constraints persist, then schedule constraint calculate in EVOL
after the MoL integration. Re-calculate the constraints in the
POSTREGRID bin.
If the constraints do not persist, then calculate them in the ANALYSIS
bin as usual.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@126 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
after ADMBase_InitialData. This makes it possible to set up all ADM
data in these two groups, and then e.g. convert to the BSSN variables
after these groups still in the bin "initial". Various other thorns,
such as dissipation or multipatch, can now apply transformations to
the initial data in the bin "postinitial". This simplifies the
interaction between various thorns.
Change various thorns to use these two groups.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@115 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
|
| |
mode. This removes warnings from thorn Boundary when run in
MultiPatch.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@113 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@96 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@95 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
| |
The parameter constraint_communication has no effect now and is deprecated.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@91 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@87 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
|
|
|
|
|
| |
properly with Cartoon.
Cartoon is now properly called by selecting variables for 'None'
boundary condition, and defining their proper tensortypealias in
interface.ccl. Note that this illustrates how to trigger an entire
schedule group in the ANALYSIS time bin.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@84 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
|
|
|
|
| |
Will give a warn 0 if metric_type is "static conformal" but
the initial data has not provided second derivatives of the
conformal factor.
Tom
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@63 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ADMConstraints::constraints does not exist any more, it has been replaced
by two separate groups:
ADMConstraints::hamiltonian
ADMConstraints::momentum
The reason for this change is that cartoon needs to have groups that correspond
to scalars, vectors or tensors.
These changes were coded by Ryoji, even if I am commiting them.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@51 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@29 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
IMPORTANT: if you don't have a src/schedule directory, please
do an "update -d" or your code won't compile!
You can now create schedule groups and schedule items (other groups
or functions) IN a group. You may then schedule a group AT a
particular CCTK entry point, or inside another group.
There is a new keyword WHILE in the schedule specification. The
argument(s) to this are the full names of integer scalars, and the
item which is scheduled WHILE will be executed while this integer, or
these integers, are non-zero. Note that currently there is little
checking of the type of these scalars, 'though this will be coming
soon.
BEFORE, AFTER, or WHILE can take a list of arguments of the form
(a,b,c) to stop you having to do something like
BEFORE a BEFORE b BEFORE c
So the full format of a schedule statement is
SCHEDULE [GROUP] <name> <AT entrypoint | IN group> [BEFORE|AFTER <item | (item...)>] [WHILE <integer gridscalar>]
{
[LANG: <language>]
[COMM: <group(s)>]
[STORAGE: <groups(s)]
[TRIGGERS: <groups(s)]
} "<description>"
Note that even for a group you need to provide
{
} "<description>"
'though that may be relaxed soon.
Also TRIGGERS are now on a group basis, not on a variable basis.
So, for example, to test this I had
--------------------------------------
SCHEDULE TEST1_InitialData AT INITIAL
{
LANG: Fortran
} "Initialise"
SCHEDULE TEST1_InitialData AT EVOL
{
LANG: Fortran
} "Initialise"
SCHEDULE TEST1_Evolve IN testit
{
LANG: Fortran
} "Evolution routine"
SCHEDULE GROUP testit WHILE test1::foo_int_scalar AT EVOL AFTER TEST1_InitialData
{
} "Test a group within a group. "
---------------------------------------
where the initialisation routine set test1::foo_int_scalar to 4 and
the evolution routine decremented it. The group "testit" is redundant here
as only one thing is scheduled in it, the WHILE and AFTER could have gone
directly onto the scheduling of TEST1_Evolve.
Apart from the checking of the while stuff, the perl does a fair amount of
checking that groups exist. It doesn't yet check that a group you
are scheduling at or in exists, and neither does the C, so please check the
screen output of the final schedule tree. Checks for this an for
unreachable groups will go in, but perhaps not in the next week.
There's also some tidying up which needs to go in, but this stuff
passes all the tests that the unmodified code does.
I have also tried to make the output of the CST a bit more useful, 'though
now it's a wee bit long-winded.
Please send me comments if you want more output of various things, or would
like the current output, or how the WHILE stuff works, changed.
Tom
IMPORTANT: if you don't have a src/schedule directory, please
do an "update -d" or your code won't compile!
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@18 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
| |
register the GF symmetries at every timestep!
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@10 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
| |
|
|
|
|
|
| |
to work.
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@4 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
|
|
constraints, so I'll try again ...
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/ADMConstraints/trunk@2 b7a48df3-cbbf-4440-997f-b4b717c9f7fc
|
