| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Tom
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@429 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
|
| |
applied to both grid function and grid array variables. Should be done
only for grid functions, of course.
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@424 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
| |
continue if the user specified invalid values for the partition parameters.
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@417 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
| |
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@366 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
|
|
| |
was limited to work for 1D, 2D, and 3D arrays only.
Now arrays of arbitrary dimensions can be managed by PUGH with automatic
topology setup.
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@344 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
| |
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@338 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
| |
Tom
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@324 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
int PUGH_SetPartitionInfo (int dim, const char *partition_info[])
to set partition information externally.
Note that this bypasses the parameter evaluation for manual topology setting.
But since we don't want to make these parameters steerable (which would
suggest to people they can change the topology at runtime) we implemented
this kind of hack.
It's used by BAM and shouldn't be anywhere else.
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@308 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rather than doing it sequentially on individual arrays.
Nothing changes for the CCTK routines overloaded by PUGH.
For BAM and other thorns which don't care about groups there is now
a separate interface to synchronize individual arrays.
Also eliminated the restriction to synchronize 1D and 3D arrays only
- now it should do arbitrary dims (not yet tested).
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@222 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
|
|
| |
should begin with PUGH.
Tom
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@211 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is lowered to being simply a special case of a grid array, pGA. Grid arrays
can all have different sizes, which means that now the size of a GA is moved
from the GH to a structure on the GA, along with a lot of other connectivity
and additional information which was formerly on the GH.
If you need to care about these changes, take a look at the files in
src/include/pGH.h and src/include/pGA.h, to see the new structures
(I'll leave the old files pGF.h and SetupPGF.c around for a while to compare with).
Also, look at a PUGH dependent file which has already been converted, such
as CactusPUGHIO/IOASCII/src/Write1D.c.
Warning:
This commit breaks the development versions of IOHDF5 and IsoSurfacer, these
will be fixed real quick.
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@182 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
|
|
|
|
|
|
|
|
|
| |
and return values.
Fixing CactusPUGH-PUGH 264.
Thomas
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@176 b61c5cb5-eaca-4651-9a7a-d64986f99364
|
|
Contributed by Matei Ripeneau
Here are his notes (hopefully there will soon be PUGH docs to add them to):
1. Purpose
Allow manual (user specified) grid partitioning
2. Parameters
I've added the following parameters to ./PUGH/param.ccl
KEYWORD partition "Is the partition manual/automatic"
{
"automatic" :: "even implicit partition"
"manual" :: "specified by partition_#d_XYZ .."
} "automatic"
STRING partition_1d_X "Tells how to partition on direction X" ...
STRING partition_2d_X "Tells how to partition on direction X" ...
STRING partition_2d_Y "Tells how to partition on direction Y" ...
STRING partition_3d_X "Tells how to partition on direction X" ...
STRING partition_3d_Y "Tells how to partition on direction Y" ...
STRING partition_3d_Z "Tells how to partition on direction Z" ...
(all these strings have default "")
How to specify a manual partition?
Simpler to explain using an example: partitioning a grid space with 30 x 30 x
30 points for a configuration with 8 processors can be specified as:
PUGH::partition = "manual"
PUGH::partition_1d_X = "" // uses default
PUGH::partition_2d_X = "16:14"
PUGH::partition_2d_Y = "7:9:5:9"
PUGH::partition_3d_X = "16:14"
PUGH::partition_3d_Y = "12:18"
PUGH::partition_3d_Z = "17:13"
Even if PUGH::partition = "manual" an empty string like PUGH::partition_1d_X =
"" will lead to default (even) partition on that direction
git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGH/trunk@174 b61c5cb5-eaca-4651-9a7a-d64986f99364
|