| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Previous version would introduce a sign error in some cases. In
practice, this bug affected only the second order second derivative,
and the first order one sided derivative.
|
|
|
|
|
|
|
| |
SKIPPED:
Tools/TensorFactory/ComponentsTools3.m
Tools/TensorFactory/ComponentsTools3.nb
|
| |
|
| |
|
|
|
|
|
|
| |
SKIPPED:
Distribution/build-distribution
|
|
|
|
| |
manually specify that certain symbols are allowed; e.g. inherited parameters; which Kranc cannot know about itself.
|
|
|
|
| |
More descriptive error messages when calculations fail validation checks.
|
| |
|
|
|
|
|
|
| |
SKIPPED:
Distribution/build-distribution
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and divisions of grid spacing. CreateDifferencingHeader returns a
list of 'pre-definitions' which are then computed outside the equation
loop by CalculationFunction. AKA "why can't my compiler do such a
simple optimization?"
Partial derivatives are now assumed to commute, so occurrences of
PD[f,2,1] are replaced in the equations by PD[f,1,2]. The unused ones
are automatically not computed, as before. I wish that this had made a
noticeable speed improvement (would have been big), but the compiler
must have been intelligent enough to see these.
Added khalf, kthird, ktwothird, kfourthird, keightthird computed
outside the loop. What compiler on earth would not see these
optimizations??
Factor out common expressions i.e. xx_ y_ + xx_ z_ -> xx(y+z). Intel,
I have lost all respect for you.
Remove RegularExpression from schedule matching, as it is not
supported in Mathematica 4. Replaced with a simple StringMatchQ.
|
| |
|
|
|
|
|
|
| |
SKIPPED:
Distribution/build-distribution
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so that the calculation only happens if cctk_iteration % calc_every ==
calc_offset.
Fixed CollectList in KrancThorn.m (it was disabled).
Enabled MMA Simplify for expressions even when a CollectList has not
be specified.
Changed SYNC logic in KrancThorn.m: Calculations are now only SYNCed
if they are restricted to the interior of the grid (using
Where). Previously, all calculations were synced. This is a
performance issue. Further, calculations in MoL_CalcRHS and
MoL_RHSBoundaries are *never* SYNCed now. The SYNC of the evolved
variables that always happens in cactus_boundaries.c should be enough.
WARNING: you probably want to test that this does not break your code.
|
|
|
|
|
|
| |
SKIPPED:
Distribution/files
|
|
|
|
| |
Symmetry.h and Boundary.h. Anyone know why these were commented out?
|
| |
|
|
|
|
| |
Support for new calculation convention
|
|
|
|
|
|
|
| |
wrapper function which calls a hand-written function in GenericFD
depending on the loop type required. A function pointer to the 'Body'
function is provided, and the Body function is autogenerated.
Advantage is that the looping logic is now hand-written.
|
|
|
|
|
|
| |
Include Symmetry.h
Fix return type and values for scheduled functions (i.e. void)
|
|
|
|
|
|
| |
Add verbose parameter
Add some support for SummationByParts (should still compile if thorn is not present)
|
| |
|
|
|
|
|
|
| |
SKIPPED:
Distribution/build-distribution
|
| |
|
| |
|
|
|
|
| |
Declarations for new looping constructs from GenericFD.c
|
|
|
|
| |
normals etc
|
|
|
|
| |
Fortran compiler.
|
|
|
|
| |
actually schedule storage for them, rather than scheduling only one...
|
| |
|
|
|
|
|
|
| |
SKIPPED:
Distribution/files
|
|
|
|
| |
the current directory for Kranc, which can be a symlink.
|
|
|
|
|
|
|
|
|
| |
Change version number to 2.0.7-cvs
SKIPPED:
Distribution/build-distribution
|
|
|
|
|
|
|
|
| |
SKIPPED:
Examples/Maxwell/EMTT2.m
Examples/Maxwell/EMTT2.par
Examples/Maxwell/EMTT2.th
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
which is designed to be much easier to use and much easier to
maintain. Instead of multiple types of thorn, there is just one, and
most of the functionality from the old types is present in this new
type. Some functionality (for example the TRIGGERS mechanism for
evaluated quantities) has not been implemented, but if there is demand
these things can be added. The new API is documented in
Doc/KrancDoc.tex and there is an example in Examples/Maxwell/EMTT2.m.
This is such a significant change that the major version number of
Kranc has been increased from 1 to 2.
|
| |
|
|
|
|
| |
notation etc.
|
|
|
|
| |
Modify symmetry handling slightly
|
|
|
|
| |
Tidy up qualifyGFName function slightly
|
| |
|
|
|
|
|
|
|
|
| |
Fixed bug whereby physical boundary conditions could be called in
symmetry zones, and in some cases this could lead to accessing
unallocated memory and segfaults. This would never have generated
incorrect output, as these points would be overwritten by the symmetry
thorn anyway.
|
|
|
|
|
|
| |
Mathematica 5.1
Also modified shorthands function
|
|
|
|
|
|
|
|
|
|
| |
suggestion.
Removed spurious output.
CreateMoLRegistration source now requires that the group names should
be passed in with an implementation prefix. This is what is currently
done, so the change should be harmless.
|
|
|
|
|
| |
in lines 411 and 489 the definition of D3_c4
for Fortran and C had dxi instead of dzi, so it gave wrong results for dx != dz
|
|
|
|
|
| |
applied to groups (the goups were always associated with the default base thorn,
which is not always true).
|