Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-3330-g213b2ab

i did forget that indeed ... and i just pushed it Cheers, Gilles On 1/7/2016 12:33 AM, Ralph Castain wrote: Hmmm…I don’t see a second commit message anywhere. Did you perhaps forget to push it? Thanks for the explanation! Ralph On Jan 6, 2016, at 2:30 AM, Gilles Gouaillardet

[OMPI devel] Contributing to mpi

All, I am looking forward in contributing towards the development of Open-Mpi , I am an ECE undergrad and have some free time. Can anyone involve me into some project. As far as programming skills are concerned I have some 1k line of code in Octave -- I know it's not very relevant but it shows tha

Re: [OMPI devel] Open MPI and NAG Fortran

Paul -- Awesome; thanks for reporting this. I've filed a ticket for this: https://github.com/open-mpi/ompi/issues/1284 This is unlikely to get fixed for the v1.10.2 release, but I want to track the issue to make sure it does eventually get solved. > On Jan 2, 2016, at 9:15 PM, Paul Hargr

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-3330-g213b2ab

Hmmm…I don’t see a second commit message anywhere. Did you perhaps forget to push it? Thanks for the explanation! Ralph > On Jan 6, 2016, at 2:30 AM, Gilles Gouaillardet > wrote: > > Hi Ralph, > > That solves the multiple mtt failures that occurred with inter communicators > and mpi_procs_c

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-3330-g213b2ab

Hi Ralph, That solves the multiple mtt failures that occurred with inter communicators and mpi_procs_cutoff. You can reproduce this with allgather_inter from ibm/collective, --mca mpi_procs_cutoff 0, 8 tasks and two nodes. Basically, a proc_list[i] can be a sentinel, so it is not always correct to

Re: [OMPI devel] [OMPI commits] Git: open-mpi/ompi branch master updated. dev-3330-g213b2ab

Hi Gilles Could you please explain this one - I honestly don’t understand the change, and haven’t encountered a problem. Thanks Ralph > On Jan 5, 2016, at 11:22 PM, [email protected] wrote: > > This is an automated email from the git hooks/post-receive script. It was > generated because a r