Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
Settled offline. Just to record the solution. The compilation is fine but there is a pre-installed pw.x from the package manager. When running, this user is pulling /usr/bin/pw.x instead of the newly built one. Then the solution is just remove the pre-installed QE in the package manager. =

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Will DeBenedetti
Maybe take this offline? Will DeBenedetti Cornell University Sent from my iPhone On Aug 7, 2018, at 22:11, Aziz Fall mailto:af...@umich.edu>> wrote: yeah both my mpiifort and mpif90 are from intel. where do I find the psxevars.sh file On Tue, Aug 7, 2018 at 9:57 PM, Ye Luo mailto:xw111lu...

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
yeah both my mpiifort and mpif90 are from intel. where do I find the psxevars.sh file On Tue, Aug 7, 2018 at 9:57 PM, Ye Luo wrote: > /usr/lib/libblacsCinit-openmpi.so.1 seems belong to libblacs-openmpi1 > package in ubuntu. > This indicates you have openmpi and blacs installed from the package

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
/usr/lib/libblacsCinit-openmpi.so.1 seems belong to libblacs-openmpi1 package in ubuntu. This indicates you have openmpi and blacs installed from the package manager. Are you sure your parallel studio is the cluster edition and you have intel mpi? Did you source psxevars.sh form parallel studio? T

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
yeah unfortunately I get the same error again, sorry if this is taking up your time On Tue, Aug 7, 2018 at 9:40 PM, Aziz Fall wrote: > ok thanks I will try it and let you know, hopefully I dont run into any > issues this time > > On Tue, Aug 7, 2018 at 9:37 PM, Ye Luo wrote: > >> There was a ty

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
ok thanks I will try it and let you know, hopefully I dont run into any issues this time On Tue, Aug 7, 2018 at 9:37 PM, Ye Luo wrote: > There was a typo mpiifort instead of mpif90 in your case. > ./configure MPIF90=mpiifort CC=icc --with-scalapack=intel > > > === > Ye Luo, Ph.D.

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
yeah so the problem persist even after changing the MPIF90 flag On Tue, Aug 7, 2018 at 8:55 PM, Aziz Fall wrote: > I noticed that after I reconfigured and I looked at my make.inc file, my > MPI_LIBS and LAPACK_LIPS paths that I specified beforehand were erased, > will this affect the pw.x progra

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
There was a typo mpiifort instead of mpif90 in your case. ./configure MPIF90=mpiifort CC=icc --with-scalapack=intel === Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory 2018-08-07 20:36 GMT-05:00 Ye Luo : > Why don't you trust the configure? The configure

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
Why don't you trust the configure? The configure can cover most scenarios. Most users should rely on the configure instead of modifying the make.inc by hand. Linux+OpenMP/IntelMPI+Intel compiler+MKL is very common and the configure can handle it very well. I can handle BG/Q or Cray machines without

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
I noticed that after I reconfigured and I looked at my make.inc file, my MPI_LIBS and LAPACK_LIPS paths that I specified beforehand were erased, will this affect the pw.x program from running parallely after it finishes compiling, I am asking now because it will take a while to finish compiling. O

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
ok I'll try that and let you know On Tue, Aug 7, 2018 at 8:28 PM, Ye Luo wrote: > Your mpi wrapper mpif90 is using gfortran underneath from the ldd pw.x > output. > Could you add MPIF90=mpiifort in your configure line? > But I'm not sure if this is the real problem. > Ye > > > ==

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
Your mpi wrapper mpif90 is using gfortran underneath from the ldd pw.x output. Could you add MPIF90=mpiifort in your configure line? But I'm not sure if this is the real problem. Ye === Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory 2018-08-07 19:24 GMT-0

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
no I am using the same machine for the build and run, its a workstation with 32 cores On Tue, Aug 7, 2018 at 8:22 PM, Ye Luo wrote: > Did you build the code and run it on different machines? Ye > > === > Ye Luo, Ph.D. > Leadership Computing Facility > Argonne National Laboratory

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
Did you build the code and run it on different machines? Ye === Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory 2018-08-07 19:18 GMT-05:00 Aziz Fall : > ok so regardless of whether I run pw.x with mpirun or not I get the same > error saying pw.x: symbol lo

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
ok so regardless of whether I run pw.x with mpirun or not I get the same error saying pw.x: symbol lookup error: /usr/lib/libblacsCinit-openmpi.so.1: undefined symbol: ompi_mpi_comm_world when I do which mpirun I get /opt/intel/compilers_and_libraries_2018.3.222/linux/mpi/intel64/bin/mpirun so its

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
Everything seems good. I'm wondering if it is the problem of your mpirun. Could you run pw.x directly without mpirun? If you type "which mpirun" on the machine your are running, is it from the intel parallel studio folder since you said you are using Intel MPI. Ye === Ye Luo, Ph.D.

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
yeah so when I type ldd pw.x I get the following linux-vdso.so.1 => (0x7cb9e000) libmkl_scalapack_lp64.so => /opt/intel/compilers_and_libraries_2018.3.222/linux/mkl/lib/intel64_lin/libmkl_scalapack_lp64.so (0x7ffed730) libmkl_blacs_intelmpi_lp64.so => /opt/

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
$ldd pw.x. What prints out? It seems that /usr/lib/libblacsCinit-openmpi.so.1 get into your binary at a certain point. But it should not. This is the blacs from your OS used by scalapack but it is supposed to be the Intel one. Ye === Ye Luo, Ph.D. Leadership Computing Facility Argo

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
so I changed the options in configure like you suggested with the --with-scalapack=intel but I still get the same error after re-compiling. Do you have any further suggestions? On Tue, Aug 7, 2018 at 6:22 PM, Aziz Fall wrote: > No, I did not add that configuration as part of configure but I did

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
No, I did not add that configuration as part of configure but I did change the make.inc to have SCALAPACK_LIBS = -L/opt/intel/mkl/lib/intel64 -lmkl_intel_lp64 -lmkl_tbb_thread -lmkl_core -lmkl_scalapack_lp64 -lmkl_blacs_intelmpi_lp64 -lpthread -ltbb -lstdc++ -lm -ldl and MPI_LIBS = -L/opt/

Re: [QE-users] Problem when running the pw.x executable

2018-08-07 Thread Ye Luo
That seems for openmpi. Did you put --with-scalapack=intel when you run configure? Ye === Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory 2018-08-07 16:42 GMT-05:00 Aziz Fall : > Dear Quantum espresso team, > > So recently I have been trying to run the exe

[QE-users] Problem when running the pw.x executable

2018-08-07 Thread Aziz Fall
Dear Quantum espresso team, So recently I have been trying to run the executable pw.x on the bin directory. I pass in my input and output file appropriately, and I am using intel's Parallel studio compiler, with intel MPI. but when I run the program I get the following error pw.x: symbol lookup e