QuantumATK > Installation and License Questions

U-2022.12-SP1 installation problem

<< < (2/2)

Anders Blom:
Yes, that is the point. The new version handles MPI libraries differently. It might be that 2018 Intel MPI is too old for U-version, so either try to use a newer version, or switch to using the ones we ship by not using your own MPI module. However, you may then also need to define

MPIBIN=/path/to/QuantumATK/QuantumATK-U-2022.12-SP1/mpi/bin
MPILIB=/path/to/QuantumATK/QuantumATK-U-2022.12-SP1/mpi/lib

PATH=$MPIBIN:$PATH
LD_LIBRARY_PATH=$MPILIB:$LD_LIBRARY_PATH

The difference between the new and old versions is that in U-2022.12, our MPI libraries are placed LAST in the PATH, This is done on purpose so that we don't override your own libraries if you want to use them. The old version had our libraries in the FRONT of the PATH, meaning they took precedence no matter which library you had, so it was very hard to use your own.

Dongzhe:
Dear Anders,
I have tried using the MPI library from QATK (see below).
However, I am facing the same problem. The job was completed without errors, but it did not calculate anything...
Any further suggestions?
Thanks,
Dongzhe
CNRS in Toulouse

------------------------------------------------------------------------
#var environnements
export OMP_NUM_THREADS=1

#export I_MPI_DAPL_TRANSLATION_CACHE=0
export PATH=/usr/local/QuantumATK/QuantumATK-U-2022.12-SP1/bin:$PATH
export MPILIB=/usr/local/QuantumATK/QuantumATK-U-2022.12-SP1/mpi/lib
export MPIBIN=/usr/local/QuantumATK/QuantumATK-U-2022.12-SP1/mpi/bin

export PATH=$MPIBIN:$PATH
export LD_LIBRARY_PATH=$MPILIB:$LD_LIBRARY_PATH

which mpiexec

echo Time is `date`
echo Directory is `pwd`
date
which atkpython

mpiexec -np 1 atkpython < test.py >> test.out
------------------------------------------------------------------------

filipr:

--- Code: ---mpiexec -np 1 atkpython < test.py >> test.out

--- End code ---

You are piping the file test.py into the standard input (stdin) of the atkpython program. That is not how atkpython (or normal python) works. Instead you should simply pass the script file as an argument to the atkpython program:


--- Code: ---mpiexec -np 1 atkpython test.py >> test.out

--- End code ---

You can see the expected way to run the program by executing atkpython --help

Dongzhe:
Dear,
OK, thanks, it is indeed working.

I have been using the following line for other ATK versions without any problems.
mpiexec -np 1 atkpython < test.py >> test.out

It makes only problems for "U-2022.12-SP1"...

Any further explication?
Best regards,
Dongzhe

Anders Blom:
bin/atkpython is actually a bash script which under the hood calls the actual python binary. This wrapper changed structure in U-version so the "piping in" which worked before (but still was not considered the "proper" way) will not work anymore.

Navigation

[0] Message Index

[*] Previous page