[steadyman]

Hello Everyone

I use UBUNTU 18.04 LTS for my linux distro.

I'm trying to build SU2(7.0.5 Blackbird version) from source. I have issues about parallel build. Although I specify MPICC and MPICXX paths(shown in bashrc_mpicc_mpiccx_paths.png) in my .bashrc file,it gives that MPICC and MPICXX not found message when I run meson.py. It is shown in MPICC_and_MPICXX_fail.png

I want to give some facts regarding to problem and what I have done so far.

1.I have installed simple parallel version of SU2(7.0.5 Blackbird). It is working fine with both serial and parallel.In other words, I can run SU2 with both using parallel_computation.py and mpirun command ,seperately. No problem regarding to mpi issue I think. By the way, I use MPICH and I built it from source. Its location is given in mpi_path_in_bashrc.png . Also when I run which command on my terminal it gives me location of mpicc and mpicxx shown in mpicc_locations_seen_from_terminal.png

2. On my first attempt,it gives pkg-config not found when I run meson.py.Then,I have installed pkg-config and specified its PATH in my .bashrc(shown in pkg-config_path_in_bashrc.png in thumbnail figure). No problem regarding pkg-config I think.

3. On my second attempt, when I run meson.py. Terminal showed me that pkg-config is found message. However, it gave no MPICC and MPICXX found mesage shown in MPICC_and_MPICXX_fail.png

To sum up, although I have properly installed MPICH (and wrote PATH in .bashrc) in mpicc_locations_seen_from_terminal.png , meson.py of SU2 gives me NO MPICC and MPICXX found error.MPICC_and_MPICXX_fail.png



Could you help me for this issue ?
How can I solve MPICC issue on meson.py
I will be very thankful.

[pcg]

This is because the pkg-config dependency for mpich is not "mpi" and so the build system is looking for the wrong thing.
I've worked around this kind of issue in two ways:
1 - Specify -Dcustom-mpi=true in your call to meson.py, and do "export CC=$MPICC; export CXX=$MPICXX" before calling meson. (with Intel MPI this works without extra environment variables, I have not tried mpich this way)

2 - Edit the file SU2/meson.build, replace:
mpi_dep = [dependency('mpi', language:'c', required : get_option('with-mpi')),
dependency('mpi', language:'cpp', required : get_option('with-mpi'))]
with:
mpi_dep = [dependency('mpich', required : get_option('with-mpi'))]

[steadyman]

Originally Posted by pcg

This is because the pkg-config dependency for mpich is not "mpi" and so the build system is looking for the wrong thing.
I've worked around this kind of issue in two ways:
1 - Specify -Dcustom-mpi=true in your call to meson.py, and do "export CC=$MPICC; export CXX=$MPICXX" before calling meson. (with Intel MPI this works without extra environment variables, I have not tried mpich this way)

2 - Edit the file SU2/meson.build, replace:
mpi_dep = [dependency('mpi', language:'c', required : get_option('with-mpi')),
dependency('mpi', language:'cpp', required : get_option('with-mpi'))]
with:
mpi_dep = [dependency('mpich', required : get_option('with-mpi'))]

Thanks I'll try it
and I think Openmpi is less problematic to these kind of things I will also try that

[hyunko]

hi steadyman

I have same issues for compiling SU2.
Do you have any update for that?

[steadyman]

Originally Posted by hyunko

hi steadyman

I have same issues for compiling SU2.
Do you have any update for that?

Hello Hyunko I cannot run SU2 with OPENMPI. Now I'll try MPICH built from source you can visit my other post I mention this problem also there but with MPICH
SU2 paralllel Build from source ninja failed on ubuntu 18.04

[hyunko]

Originally Posted by steadyman

Hello Hyunko I cannot run SU2 with OPENMPI. Now I'll try MPICH built from source you can visit my other post I mention this problem also there but with MPICH
SU2 paralllel Build from source ninja failed on ubuntu 18.04

Hello stradyman

You mean that you still have a problem to build SU2 by mpich?

I have a same problem to compile SU2 with mpich.
I have tried two ways within this thread. But not successful.

[steadyman]

Originally Posted by pcg

This is because the pkg-config dependency for mpich is not "mpi" and so the build system is looking for the wrong thing.
I've worked around this kind of issue in two ways:
1 - Specify -Dcustom-mpi=true in your call to meson.py, and do "export CC=$MPICC; export CXX=$MPICXX" before calling meson. (with Intel MPI this works without extra environment variables, I have not tried mpich this way)

2 - Edit the file SU2/meson.build, replace:
mpi_dep = [dependency('mpi', language:'c', required : get_option('with-mpi')),
dependency('mpi', language:'cpp', required : get_option('with-mpi'))]
with:
mpi_dep = [dependency('mpich', required : get_option('with-mpi'))]

Hello pcg

I have performed 2. option you recommended but it gives error shown in meson_prefix.png In this I have used prefix option.
In my 2nd attempt , I do not use prefix just use ./meson.py build and it gives meson_witout_prefix.png

[averis007]

Even with intel mpi, I'm facing the same issues. Can anyone help?

[Zen]

Hi all,

I had the same issue in Ubuntu 16.04 , namely that pkg-config could not find mpicc and mpicxx. I have solved the problem following the recommendation from pcg:

1 - Specify -Dcustom-mpi=true in your call to meson.py, and do "export CC=$MPICC; export CXX=$MPICXX" before calling meson

Specifically, I have done the following:

export MPICC=/usr/bin/mpicc (your path/to/mpicc may be different)
export MPICXX=/usr/bin/mpicxx
export CC=$MPICC
export CXX=$MPICXX
./meson.py build -Dcustom-mpi=true
./ninja -C build install

hope this helps,

Z

[steadyman]

Originally Posted by Zen

Hi all,

I had the same issue in Ubuntu 16.04 , namely that pkg-config could not find mpicc and mpicxx. I have solved the problem following the recommendation from pcg:



Specifically, I have done the following:

export MPICC=/usr/bin/mpicc (your path/to/mpicc may be different)
export MPICXX=/usr/bin/mpicxx
export CC=$MPICC
export CXX=$MPICXX
./meson.py build -Dcustom-mpi=true
./ninja -C build install

hope this helps,

Z

Hello Zen
Do you perform "export" issues on your .bashrc ?
Thanks in advance

[steadyman]

Originally Posted by Zen

Hi all,

I had the same issue in Ubuntu 16.04 , namely that pkg-config could not find mpicc and mpicxx. I have solved the problem following the recommendation from pcg:



Specifically, I have done the following:

export MPICC=/usr/bin/mpicc (your path/to/mpicc may be different)
export MPICXX=/usr/bin/mpicxx
export CC=$MPICC
export CXX=$MPICXX
./meson.py build -Dcustom-mpi=true
./ninja -C build install

hope this helps,

Z

Thanks zen
It worked.

[averis007]

Hi, I followed the instructions given by Zen and the installation was successful. I also included the required paths in my bashrc file. But unfortunately, my parallel cases are still not running as desired.

Specifically, when I do

parallel_computation.py -n 10 -f turb_ONERAM6.cfg

on the test case (Turb ONERA M), it's doing everything 10 times (once each on 10 cores), instead of distributing over 10 cores. For, reference, this is what I put in my .bashrc file:


export SU2_RUN="/usr/local/bin"
export SU2_HOME="/home/avi/Downloads/SU2/su2code-SU2-d0e10f8"
export PATH=$PATH:$SU2_RUN
export PYTHONPATH=$PYTHONPATH:$SU2_RUN


Am I missing something here?

[steadyman]

Originally Posted by averis007

Hi, I followed the instructions given by Zen and the installation was successful. I also included the required paths in my bashrc file. But unfortunately, my parallel cases are still not running as desired.

Specifically, when I do

parallel_computation.py -n 10 -f turb_ONERAM6.cfg

on the test case (Turb ONERA M), it's doing everything 10 times (once each on 10 cores), instead of distributing over 10 cores. For, reference, this is what I put in my .bashrc file:


export SU2_RUN="/usr/local/bin"
export SU2_HOME="/home/avi/Downloads/SU2/su2code-SU2-d0e10f8"
export PATH=$PATH:$SU2_RUN
export PYTHONPATH=$PYTHONPATH:$SU2_RUN


Am I missing something here?

Suggestion:
When I used openmpi I faced this issue,maybe installing "mpi4py" will help.If you use ubuntu I recommend you to use synaptics installation manager to install openmpi.
Summary:
I cannot solve this wrong parallellization issue with openmpi.I installed Mpich and it is solved by zen 's feedbacks.

[pcg]

The "repeated output" problem is due to one of two problems:
You did not actually compile the parallel version,
The version of mpi used to run the code is different from the one used to compile it.
Given that you specified "custom-mpi" the latter is more likely.

Try running the code with /full/path/to/mpirun -n 10 SU2_CFD ...

[averis007]

Originally Posted by pcg

The "repeated output" problem is due to one of two problems:
You did not actually compile the parallel version,
The version of mpi used to run the code is different from the one used to compile it.
Given that you specified "custom-mpi" the latter is more likely.

Try running the code with /full/path/to/mpirun -n 10 SU2_CFD ...

Yes, the second option worked for me. Thanks a ton.

[Kusy]

Originally Posted by averis007

Yes, the second option worked for me. Thanks a ton.

So what versionof OpenMPI should I use for SU2 v7Blackbird? I've got the mpirun --version 3.4.1 and gcc 4.8.3 - same issue...

[pcg]

You need to upgrade your compiler. Namely for something with complete C++11 support.
gcc 4.8.5+, but since you are upgrading you might as well get the newest possible.

[Kusy]

I installed gcc 4.9.3 but it still starts many solver at once... Anything else? Some options to solve it?
I'm using SU2 from file - i can't make it from source becouse meson.py doesn't work offline. Maybe i've got wrong paths to mpich?

[pcg]

If you are using a precompiled binary you need mpich, not openmpi (see https://su2code.github.io/docs_v7/SU...-parallel-mode)

Once you install mpich you need to make sure "mpirun" is the mpirun of MPICH, for example by using the full path.
I'll try to make meson work offline.

[Kusy]

I made that, I've got full PATH to mpich, SU2_RUN etc...
I don't know where other to find the issue with combine SU2-MPICH.
Maybe it's old Python's version? I've got Python 3.4.1 as default