On Sep 6, 2014, at 11:00 AM, Allin Cottrell wrote:
> On Sat, 6 Sep 2014, Ralph Castain wrote:
>
>> On Sep 6, 2014, at 7:52 AM, Allin Cottrell wrote:
>>
>>> On Fri, 5 Sep 2014, Ralph Castain wrote:
>>>
On Sep 5, 2014, at 3:34 PM, Allin Cottrell
On Sat, 6 Sep 2014, Ralph Castain wrote:
On Sep 6, 2014, at 7:52 AM, Allin Cottrell wrote:
On Fri, 5 Sep 2014, Ralph Castain wrote:
On Sep 5, 2014, at 3:34 PM, Allin Cottrell wrote:
I suspect there is a new (to openmpi 1.8.N?) warning with respect to
On Sep 6, 2014, at 7:52 AM, Allin Cottrell wrote:
> On Fri, 5 Sep 2014, Ralph Castain wrote:
>
>> On Sep 5, 2014, at 3:34 PM, Allin Cottrell wrote:
>>
>>> I suspect there is a new (to openmpi 1.8.N?) warning with respect to
>>> requesting a number of MPI
Hello Gus,
Thanks once again for your help and guidance. I just want to let you know that
I was able to resolve the problem; I actually changed the locations of the
libraries before configuring; for example I set:
BLAS_LIBS = -lmkl_intel_lp64 -lmkl_sequential -lmkl_coreLAPACK_LIBS
=
On Fri, 5 Sep 2014, Ralph Castain wrote:
On Sep 5, 2014, at 3:34 PM, Allin Cottrell wrote:
I suspect there is a new (to openmpi 1.8.N?) warning with respect to
requesting a number of MPI processes greater than the number of "real"
cores on a given machine. I can provide a
On Sep 5, 2014, at 10:44 AM, McGrattan, Kevin B. Dr.
wrote:
> I am testing a new cluster that we just bought, which is why I am loading
> things this way. I am deliberately increasing network traffic. But in
> general, we submit jobs intermittently with various
On Sep 5, 2014, at 3:34 PM, Allin Cottrell wrote:
> I suspect there is a new (to openmpi 1.8.N?) warning with respect to
> requesting a number of MPI processes greater than the number of "real" cores
> on a given machine. I can provide a good deal more information is that's