- discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] mpich 3.0.1 Ubuntu, Debian and Slackware packages (x86 and amd64)
by Dave Goodell 21 Dec '12

21 Dec '12

Downloads page updated. Thanks! -Dave On Dec 21, 2012, at 5:46 AM CST, Marcelo Soares Souza wrote: > mpich 3.0.1 packages > > * Ubuntu 12.04.1 LTS (Precise Pangolin) > > - amd64 > http://www.cebacad.net/files/mpich/ubuntu/mpich-3.0.1/mpich_3.0.1-1ubuntu_a… > > - x86 > http://www.cebacad.net/files/mpich/ubuntu/mpich-3.0.1/mpich_3.0.1-1ubuntu_i… > > * Debian 7.0 (Wheezy) > > - amd64 > http://www.cebacad.net/files/mpich/debian/mpich-3.0.1/mpich_3.0.1-1debian_a… > > - x86 > http://www.cebacad.net/files/mpich/debian/mpich-3.0.1/mpich_3.0.1-1debian_i… > > * Slackware 14.0 > > - amd64 > http://www.cebacad.net/files/mpich/slackware/mpich-3.0.1/mpich-3.0.1-x86_64… > > - x86 > http://www.cebacad.net/files/mpich/slackware/mpich-3.0.1/mpich-3.0.1-i486-g… > > -- > Abraços > Marcelo Soares Souza > http://marcelo.cebacad.net > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

mpich 3.0.1 Ubuntu, Debian and Slackware packages (x86 and amd64)
by Marcelo Soares Souza 21 Dec '12

21 Dec '12

mpich 3.0.1 packages * Ubuntu 12.04.1 LTS (Precise Pangolin) - amd64 http://www.cebacad.net/files/mpich/ubuntu/mpich-3.0.1/mpich_3.0.1-1ubuntu_a… - x86 http://www.cebacad.net/files/mpich/ubuntu/mpich-3.0.1/mpich_3.0.1-1ubuntu_i… * Debian 7.0 (Wheezy) - amd64 http://www.cebacad.net/files/mpich/debian/mpich-3.0.1/mpich_3.0.1-1debian_a… - x86 http://www.cebacad.net/files/mpich/debian/mpich-3.0.1/mpich_3.0.1-1debian_i… * Slackware 14.0 - amd64 http://www.cebacad.net/files/mpich/slackware/mpich-3.0.1/mpich-3.0.1-x86_64… - x86 http://www.cebacad.net/files/mpich/slackware/mpich-3.0.1/mpich-3.0.1-i486-g… -- Abraços Marcelo Soares Souza http://marcelo.cebacad.net

1 0

Re: [mpich-discuss] MPICH 3.0.1 packages available from MacPorts.
by Pavan Balaji 20 Dec '12

20 Dec '12

Thanks, Eric, for the super-quick port. Updated the mpich download with the new download information. http://www.mpich.org/downloads/ -- Pavan On 12/20/2012 08:05 PM US Central Time, Eric A. Borisch wrote: > mpich 3.0.1 is available via MacPorts as either 'mpich' (tracks stable > revs) or 'mpich-devel' (tracks stable and candidates.) > > I will be working with other package maintainers to move dependencies > off of 'mpich2' and over to 'mpich' (v3.0.1) in the very near future. > > - Eric > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

MPICH 3.0.1 packages available from MacPorts.
by Eric A. Borisch 20 Dec '12

20 Dec '12

mpich 3.0.1 is available via MacPorts as either 'mpich' (tracks stable revs) or 'mpich-devel' (tracks stable and candidates.) I will be working with other package maintainers to move dependencies off of 'mpich2' and over to 'mpich' (v3.0.1) in the very near future. - Eric

1 0

Re: [mpich-discuss] -binding sockets not recognised
by Pavan Balaji 20 Dec '12

20 Dec '12

On 12/20/2012 01:33 AM US Central Time, Davide Parise wrote: > I am doing some benchmark to onpinize my cluster. it looks like the > only value that my mpiexec takes on the -binding option is rr. All > the others give me an error saying "binding mode unknown". Any clue > why ? I am using the last version of MPI compiled with the intel > compiler and default options. Are you using the right mpiexec? Are you using a new-ish version? Are you using mpich? :-) FYI, -binding has been replaced with -bind-to to make it conceptually easier to understand, though it's still maintained as an alias to -bind-to. mpiexec -bind-to -help will give you all the available options. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

mpich 3.0 Ubuntu, Debian and Slackware packages (x86 and amd64)
by Marcelo Soares Souza 20 Dec '12

20 Dec '12

* Ubuntu 12.04.1 LTS (Precise Pangolin) - amd64 http://www.cebacad.net/files/mpich/ubuntu/mpich-3.0/mpich_3.0-1ubuntu_amd64… - x86 http://www.cebacad.net/files/mpich/ubuntu/mpich-3.0/mpich_3.0-1ubuntu_i386.… * Debian 7.0 (Wheezy) - amd64 http://www.cebacad.net/files/mpich/debian/mpich-3.0/mpich_3.0-1debian_amd64… - x86 http://www.cebacad.net/files/mpich/debian/mpich-3.0/mpich_3.0-1debian_i386.… * Slackware 14.0 - amd64 http://www.cebacad.net/files/mpich/slackware/mpich-3.0/mpich-3.0-x86_64-goa… - x86 http://www.cebacad.net/files/mpich/slackware/mpich-3.0/mpich-3.0-i486-goa-1… -- Marcelo Soares Souza http://marcelo.cebacad.net

1 0

-binding sockets not recognised
by Davide Parise 20 Dec '12

20 Dec '12

Dear All, I am doing some benchmark to onpinize my cluster. it looks like the only value that my mpiexec takes on the -binding option is rr. All the others give me an error saying "binding mode unknown". Any clue why ? I am using the last version of MPI compiled with the intel compiler and default options. Thanks, Davide

1 0

Re: [mpich-discuss] Account Request / Bug report MPI_Type_create_f90_real
by Dave Goodell 19 Dec '12

19 Dec '12

A note (mainly for other MPICH devs): I have created a trac account for Harald and sent him his account information off-list. -Dave On Dec 19, 2012, at 9:23 AM CST, Harald Klimach wrote: > Hi there, > > I installed MPICH2 3.0rc1 using GCC 4.7.2 and found a problem with MPI_Type_create_f90_real. > It is very similar to the problem I reported in OpenMPI under: https://svn.open-mpi.org/trac/ompi/ticket/3432 > > Running the following program: > > program test_mpi > use mpi > implicit none > > integer, parameter :: rk_prec = 15 > integer, parameter :: rk = selected_real_kind(rk_prec) > > integer :: rk_mpi > integer :: iError > real(kind=rk) :: a_real > real(kind=rk) :: res > > call MPI_Init(iError) > call mpi_type_create_f90_real(rk_prec, MPI_UNDEFINED, rk_mpi, iError) > write(*,*) 'MPI_REAL8:', MPI_REAL8 > write(*,*) 'MPI_DOUBLE_PRECISION:', MPI_DOUBLE_PRECISION > write(*,*) 'type_create_f90_real:', rk_mpi > a_real = 1.0 > call MPI_Reduce(a_real, res, 1, rk_mpi, MPI_MIN, 0, MPI_COMM_WORLD, iError) > call MPI_Finalize(iError) > > end program test_mpi > > > Results in the following output and error: > > MPI_REAL8: 1275070505 > MPI_DOUBLE_PRECISION: 1275070495 > type_create_f90_real: -1946157049 > Fatal error in PMPI_Reduce: Invalid MPI_Op, error stack: > PMPI_Reduce(1217)........: MPI_Reduce(sbuf=0x7fff43637108, rbuf=0x7fff436370f8, count=1, dtype=USER<f90_real>, MPI_MIN, root=0, MPI_COMM_WORLD) failed > MPIR_MINF_check_dtype(71): MPI_Op MPI_MIN operation not defined for this datatype > > > Further the quadruple precision data type is not properly supported: > MPI_Type_create_f90_real will complain about wrong exponent, regardless of its value, > while MPI_REAL16 is available and the Reduction operation does not complain, it produces > wrong results. Again there is a similar problem with OpenMPI, as reported under: > https://svn.open-mpi.org/trac/ompi/ticket/3433 > > Thanks a lot, > Harald Klimach > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Create account for bug tracker
by Dave Goodell 19 Dec '12

19 Dec '12

A tree-based scan pattern can cause a problem, for example. Basically, the MPI library is allowed to play with the associativity of the operations in order to provide better performance. The operation provided in the MPI standard example is not associative: (w,j) = (u,i)*(v,j), with w={ u+v if i=j, v if i!=j } i,j are booleans (0 or 1) If this operator is associative, then it must hold that: ((a,x)*(b,y))*(c,z) = (a,x)*((b,y)*(c,z)), for all (a,x),(b,y),(c,z) So here's a counterexample proving non-associativity: (a,x) = (a,0) (b,y) = (b,1) (c,z) = (c,0) The left-hand side of the equation yields "(c,0)", while the right-hand side yields "(a+c,0)", which are clearly not equal. The scheme that I worked out a while ago to deal with this problem involves adding a third variable to the pair, turning it into a triple. Unfortunately I left my notes containing the scheme at home, so I'll have to send an explanation later. In the meantime, you may wish to use the traditional edge-triggered version of the operator (cribbed from Jesper's proposed ticket https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/28) (val0 , index0)+(val1, index1) = [if index1=0 then (value0+value1 , index) else (value1 , index), where index is set to 1 if index0=1 and set to index1 otherwise] -Dave On Dec 18, 2012, at 9:27 PM CST, n n wrote: > I do not actually need this functionality, but can you show example of robust code, which will work for mpi_scan in all cases? > And can you clarify, why the order of output is not preserved, as in openmpi version? > > On Wed, Dec 19, 2012 at 1:52 AM, Dave Goodell <goodell(a)mcs.anl.gov> wrote: >> This scan operator is known to be buggy, unfortunately. It will not do the correct thing for many (entirely valid) scan implementation patterns. It's something that ought to be fixed in the next version of the MPI standard (it fell through the cracks in the MPI-3 process). >> >> Do you actually need this functionality? If so, I can describe how to implement it in a way that will be robust. Alternatively, most segmented scan algorithms assume an "edge triggered" segmented scan, rather than a "level" triggered one like what is described in the MPI standard. >> >> -Dave

1 0

Account Request / Bug report MPI_Type_create_f90_real
by Harald Klimach 19 Dec '12

19 Dec '12

Hi there, I installed MPICH2 3.0rc1 using GCC 4.7.2 and found a problem with MPI_Type_create_f90_real. It is very similar to the problem I reported in OpenMPI under: https://svn.open-mpi.org/trac/ompi/ticket/3432 Running the following program: program test_mpi use mpi implicit none integer, parameter :: rk_prec = 15 integer, parameter :: rk = selected_real_kind(rk_prec) integer :: rk_mpi integer :: iError real(kind=rk) :: a_real real(kind=rk) :: res call MPI_Init(iError) call mpi_type_create_f90_real(rk_prec, MPI_UNDEFINED, rk_mpi, iError) write(*,*) 'MPI_REAL8:', MPI_REAL8 write(*,*) 'MPI_DOUBLE_PRECISION:', MPI_DOUBLE_PRECISION write(*,*) 'type_create_f90_real:', rk_mpi a_real = 1.0 call MPI_Reduce(a_real, res, 1, rk_mpi, MPI_MIN, 0, MPI_COMM_WORLD, iError) call MPI_Finalize(iError) end program test_mpi Results in the following output and error: MPI_REAL8: 1275070505 MPI_DOUBLE_PRECISION: 1275070495 type_create_f90_real: -1946157049 Fatal error in PMPI_Reduce: Invalid MPI_Op, error stack: PMPI_Reduce(1217)........: MPI_Reduce(sbuf=0x7fff43637108, rbuf=0x7fff436370f8, count=1, dtype=USER<f90_real>, MPI_MIN, root=0, MPI_COMM_WORLD) failed MPIR_MINF_check_dtype(71): MPI_Op MPI_MIN operation not defined for this datatype Further the quadruple precision data type is not properly supported: MPI_Type_create_f90_real will complain about wrong exponent, regardless of its value, while MPI_REAL16 is available and the Reduction operation does not complain, it produces wrong results. Again there is a similar problem with OpenMPI, as reported under: https://svn.open-mpi.org/trac/ompi/ticket/3433 Thanks a lot, Harald Klimach

1 0