Unfortunately, that's not much of a description to go on to know where the
problem is.
In general, you should look to ensure that:
a) you are sending exactly what you think you are sending (e.g., print out a
sample value or two before and/or after you send)
b) you are receiving exactly what y
On Apr 23, 2012, at 11:53 AM, Jeffrey Squyres wrote:
> Here's a description of MPI_MPROBE:
>
>http://blogs.cisco.com/performance/what-is-mpi_mprobe/
Oops -- this is the link I really meant to send:
http://blogs.cisco.com/performance/mpi-forum-roundup/
--
Jeff Squyres
jsquy...@cisco.co
Additionally, the MPI-3 MPI_MPROBE function will definitely help in this area.
We have it implemented in the Open MPI development trunk; it's slated for
release in the Open MPI 1.7 series. Here's a description of MPI_MPROBE:
http://blogs.cisco.com/performance/what-is-mpi_mprobe/
On Apr 2
You might also be able to use MPI_Probe() to get the status of the
incoming message and query the size before posting the MPI_Recv() operation.
~Jim.
On 4/23/12 6:41 AM, Constantinos Makassikis wrote:
Assuming the type of the elements in the array is known, you'll probably
have to do it in tw
Assuming the type of the elements in the array is known, you'll probably
have to do it in two steps:
1) Broadcast the number of elements in the array
2) Broadcast the array itself
HTH,
--
Constantinos
On Mon, Apr 23, 2012 at 12:41 PM, seshendra seshu wrote:
> Hi,
> I am using stacks , where i
