PUGHSlab.git - [no description]

	Commit message (Collapse)	Author	Age
*	Updated documentation.	tradke	2003-01-30
\| \| \| \|	git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGHSlab/trunk@96 10716dce-81a3-4424-a2c8-48026a0d3035
*	Added email addresses of author(s)/maintainer(s) of this thorn.	tradke	2002-06-07
\| \| \| \|	git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGHSlab/trunk@86 10716dce-81a3-4424-a2c8-48026a0d3035
*	adding note: interface will change	lanfer	2000-07-20
\| \| \| \|	git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGHSlab/trunk@30 10716dce-81a3-4424-a2c8-48026a0d3035
*	Usable version of thorn Hyperslab which extracts M-dimensional orthogonal	tradke	2000-06-02
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	subspaces from an N-dimensional data space. The Hyperslab API consists of 2 routines: - Hyperslab_GetLocalHyperslab() which returns a hyperslab from the processor's local data. This will probably be used for IO methods that want to output the hyperslab chunks in parallel (as is done currently by IOHDF5 and IOFlexIO). - Hyperslab_GetHyperslab() which collects hyperslab chunks from all processors using MPI and returns the global hyperslab data. This is used in IOASCII where the output is done by only one processor. Open questions: - How to specify the directions in which to span the hyperslab. - Putting the parameters passed to Hyperslab routines into structures rather than passing them individually. git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGHSlab/trunk@22 10716dce-81a3-4424-a2c8-48026a0d3035
*	first take at Hyperslab - truly develomental	lanfer	2000-04-28
	git-svn-id: http://svn.cactuscode.org/arrangements/CactusPUGH/PUGHSlab/trunk@2 10716dce-81a3-4424-a2c8-48026a0d3035