Re: [OMPI users] flex.exe

Don't we ship the flex-generated code in the tarball anyway? If so, why do we ship flex.exe? On Jan 21, 2010, at 12:14 PM, Barrett, Brian W wrote: > I have to agree with the two requests here. Having either a windows tarball > or a windows build tools tarball doesn't seem too burdensom, and co

Re: [OMPI users] ScaLAPACK and OpenMPI > 1.3.1

Hi Nathan, On Thu, Jan 21, 2010 at 02:48:51PM -0600, Champagne, Nathan J. (JSC-EV)[Jacobs T echnology] wrote: > >We started having a problem with OpenMPI beginning with version 1.3.2 >where the program output can be correct, junk, or NaNs (result is not >predictable). The output is the

Re: [OMPI users] ScaLAPACK and OpenMPI > 1.3.1

First off, thanks for your efforts to help. >In that case i wonder what version of scalapack/blacs you are using? We are using ScaLAPACK 1.8.0 with BLACS v1.1 (with patch03).

Re: [OMPI users] ScaLAPACK and OpenMPI > 1.3.1

On Thu, 2010-01-21 at 15:40 -0600, Champagne, Nathan J. (JSC-EV)[Jacobs Technology] wrote: > >What is a correct result then? > > The correct results are output by v1.3.1. The filename in the archive is > "sol_1.3.1_96.txt". > > >How often do you get junk or NaNs compared to correct result. > We

Re: [OMPI users] ScaLAPACK and OpenMPI > 1.3.1

>What is a correct result then? The correct results are output by v1.3.1. The filename in the archive is "sol_1.3.1_96.txt". >How often do you get junk or NaNs compared to correct result. We haven't been able to quantify it. It almost seems random; similar to using a variable that's unintialize

Re: [OMPI users] ScaLAPACK and OpenMPI > 1.3.1

On Thu, 2010-01-21 at 14:48 -0600, Champagne, Nathan J. (JSC-EV)[Jacobs Technology] wrote: > We started having a problem with OpenMPI beginning with version 1.3.2 > where the program output can be correct, junk, or NaNs (result is not > predictable). The output is the solution of a matrix equation

[OMPI users] ScaLAPACK and OpenMPI > 1.3.1

We started having a problem with OpenMPI beginning with version 1.3.2 where the program output can be correct, junk, or NaNs (result is not predictable). The output is the solution of a matrix equation solved by ScaLAPACK. We are using the Intel Fortran compiler (version 11.1) and the GNU compil

Re: [OMPI users] flex.exe

I have to agree with the two requests here. Having either a windows tarball or a windows build tools tarball doesn't seem too burdensom, and could even be done automatically at make dist time. Brian - Original Message - From: users-boun...@open-mpi.org To: us...@open-mpi.org Sent: Th

Re: [OMPI users] flex.exe

Am Donnerstag, den 21.01.2010, 11:52 -0500 schrieb Michael Di Domenico: > openmpi-1.4.1/contrib/platform/win32/bin/flex.exe > > I understand this file might be required for building on windows, > since I'm not I can just delete the file without issue. > > However, for those of us under import res

[OMPI users] flex.exe

openmpi-1.4.1/contrib/platform/win32/bin/flex.exe I understand this file might be required for building on windows, since I'm not I can just delete the file without issue. However, for those of us under import restrictions, where binaries are not allowed in, this file causes me to open the tarbal

[OMPI users] checkpointing multi node and multi process applications

Hi Josh/all, I have upgraded the openmpi to v 1.4  but still get the same error when I try executing the application on multiple nodes: ***  Error: expected_component: PID information unavailable!  Error: expected_component: Component Name information unavailable! ***