Afraid I would have no idea - all I could tell them is that there was a bug and
it has been fixed
On Nov 2, 2020, at 12:18 AM, Andrea Piacentini via users
mailto:users@lists.open-mpi.org> > wrote:
I installed version 4.0.5 and the problem appears to be fixed.
Can you please help us explaini
I installed version 4.0.5 and the problem appears to be fixed.
Can you please help us explaining it to our users pointing to the commit
(at least to the first release tag) solving this issue?
Thank you very much
Andrea Piacentini
--
Andrea Piacentini
piacentini.p...@gmail.com
Tel. +39/33560075
Hi Ralph,
I am using 4.0.0
Another used in the group tested with 4.0.3 and had the same behaviour
Thanks
Andrea
--
Andrea Piacentini
piacentini.p...@gmail.com
Tel. +39/3356007579
skype: andrea3.14
Could you please tell us what version of OMPI you are using?
On Oct 28, 2020, at 11:16 AM, Andrea Piacentini via users
mailto:users@lists.open-mpi.org> > wrote:
Good morning we need to launch a MPMD application with two fortran excutables
and one interpreted python (mpi4py) application.
Good morning we need to launch a MPMD application with two fortran
excutables and one interpreted python (mpi4py) application.
The natural ordering in the resulting comm_world would come from
mpirun -np 4 fortranexe_1 : -np 4 python3 pyapp.py : -np 2 fortranexe_2
but openmpi seems to neglect (
