I'm not super-familiar with the IO portions of MPI, but I think that you might
be running afoul of the definition of "collective." "Collective," in MPI
terms, does *not* mean "synchronize." It just means that all functions must
invoke it, potentially with the same (or similar) parameters.
Hen
Did this issue get resolved? You might also want to look at our FAQ category
for large clusters:
http://www.open-mpi.org/faq/?category=large-clusters
On Jun 22, 2011, at 9:43 AM, Thorsten Schuett wrote:
> Thanks for the tip. I can't tell yet whether it helped or not. However, with
> you
Ouch. :-(
Have you talked to PGI? If a compiler segv's when compiling OMPI, it's almost
always their fault, not ours...
(sorry to be a weasel here, but there's little we can do if the compiler itself
segv's)
On Jun 21, 2011, at 12:58 PM, Brock Palen wrote:
> Has anyone else had issues buil
Greetings Alan. Sorry for the delay in replying.
We don't have a definite timeline for when 1.5 will transition to become 1.6
(i.e., the "super stable" equivalent of the 1.5 series). We are looking at it
more in terms of features -- when we have the desired set of features (which,
as a natura
w00t! Many thanks, Barnet -- this is great!
On Jun 14, 2011, at 10:50 AM, Barnet Wagman wrote:
> I've put together a simple system for running OMPI on EC2 (Amazon's cloud
> computing service). If you're interested, see
>
> http://norbl.com/ppe-ompi.html
>
>
> Barnet Wagman
>
>
>
> _
