| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/Boundary/trunk@266 6a38eb6e-646e-4a02-a296-d141613ad6c4
|
| |
|
|
| |
git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/Boundary/trunk@244 6a38eb6e-646e-4a02-a296-d141613ad6c4
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
restriction comes from specifying a set of faces using a single signed
32 bit integer. It may be possible to use two more bits, which would
provide an extra dimension, but this seems unnecessary at the moment.
Note that (as pointed out by Erik Schnetter, on the flesh mailing list)
we are assuming that the integer is at least 32 bits, which is not
guaranteed by C. Might this pose a problem? Should we restrict
ourselves to (16-1)/2 = 7 dimensions?
git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/Boundary/trunk@235 6a38eb6e-646e-4a02-a296-d141613ad6c4
|
| |
|
|
| |
git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/Boundary/trunk@187 6a38eb6e-646e-4a02-a296-d141613ad6c4
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
cactuscode.org development web page.
Registers a routine implementing radiative boundary conditions under
the boundary condition name "Radiative". The registered routine is a
wrapper for the existing radiative boundary conditions. For the
moment this uses hard-wired parameters, and calls BndRadiativeVI()
sequentially on each variable requested for radiative boundary
conditions.
git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/Boundary/trunk@186 6a38eb6e-646e-4a02-a296-d141613ad6c4
|
|
|
included commits to RCS files with non-trunk default branches.
git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/Boundary/trunk@3 6a38eb6e-646e-4a02-a296-d141613ad6c4
|
