Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

There is also the package Lmod, which provides similar functionality to environment modules. It is maintained by TACC. https://www.tacc.utexas.edu/research-development/tacc-projects/lmod but I think the current source code is at https://github.com/TACC/Lmod -- bennet On Thu, Sep 3, 2015 at

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

On Sep 3, 2015, at 10:43 AM, Diego Avesani wrote: > > Dear Jeff, Dear all, > I normaly use "USE MPI" > > This is the answar fro intel HPC forum: > > If you are switching between intel and openmpi you must remember not to mix > environment. You might use modules to

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

Dear all, Dear Nick, you are right. now will try to erase every time all *.mod file and *.o file. After thar recompile all *.f90 files. If I get another error I will tell you also the message. Thanks again Diego Diego On 3 September 2015 at 17:03, Nick Papior wrote:

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

Hi Diego, I think the Intel HPC forum comment is about using environment modules to manage your environment (PATH, LD_LIBRARY_PATH variables). Most HPC systems use environment modules: - Tcl ( http://modules.cvs.sourceforge.net/viewvc/modules/modules/tcl/ ) - C/Tcl (

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

Diego, did you update your code to check all MPI calls are successful ? (e.g. test ierr is MPI_SUCCES after each MPI call) can you write a short program that reproduce the same issue ? if not, is your program and input data public ally available ? Cheers, Gilles On Thursday, September 3,

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

Hello, On 09/03/15 16:52, Nick Papior wrote: When you change environment, that is change between OpenMPI and Intel MPI, or compiler, it is recommended that you recompile everything. use mpi is a module, you cannot mix these between compilers/environments, sadly the Fortran specification does

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

You still havent shown us anything about what goes wrong, you just give us the error statement and assume it is because of ill-defined type-creation, it might as well be because you call allreduce erroneously. Please give us more information... 2015-09-03 14:59 GMT+00:00 Diego Avesani

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

Dear Nick, Dear all, I use mpi. I recompile everything, every time. I do not understand what I shall do. Thanks again Diego Diego On 3 September 2015 at 16:52, Nick Papior wrote: > When you change environment, that is change between OpenMPI and Intel MPI, > or

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

Diego, basically that means "do not build with openmpi and run with intelmpi, or the other way around" and/or "do not build a part of your app with openmpi and an other part with intelmpi" "part" can be your app or the use of third party libraries. if you use intel scalapack, make you use the lib

Re: [OMPI users] tracking down what's causing a cuIpcOpenMemHandle error emitted by OpenMPI

Lev: Can you run with --mca mpi_common_cuda_verbose 100 --mca mpool_rgpusm_verbose 100 and send me (rvandeva...@nvidia.com) the output of that. Thanks, Rolf >-Original Message- >From: users [mailto:users-boun...@open-mpi.org] On Behalf Of Lev Givon >Sent: Wednesday, September 02, 2015

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

When you change environment, that is change between OpenMPI and Intel MPI, or compiler, it is recommended that you recompile everything. use mpi is a module, you cannot mix these between compilers/environments, sadly the Fortran specification does not enforce a strict module format which is why

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

Dear Jeff, Dear all, I normaly use "USE MPI" This is the answar fro intel HPC forum: *If you are switching between intel and openmpi you must remember not to mix environment. You might use modules to manage this. As the data types encodings differ, you must take care that all objects are built