Running VASP on 64 cores : Using executable /home/medea/MD/TaskServer/Tools/vasp6.3.1/Linux-x86_64/vasp_std running on 64 total cores distrk: each k-point on 64 cores, 1 groups distr: one band on 1 cores, 64 groups vasp.6.3.1 04May22 (build Jun 24 2022 14:24:36) complex MD_VERSION_INFO: Compiled 2022-06-24T12:52:24-UTC in mrdevlin:/home/medea/data/ build/vasp6.3.1/17134/x86_64/src/src/build/std from svn 17134 This VASP executable licensed from Materials Design, Inc. POSCAR found : 3 types and 18 ions scaLAPACK is switched off ----------------------------------------------------------------------------- | | | W W AA RRRRR N N II N N GGGG !!! | | W W A A R R NN N II NN N G G !!! | | W W A A R R N N N II N N N G !!! | | W WW W AAAAAA RRRRR N N N II N N N G GGG ! | | WW WW A A R R N NN II N NN G G | | W W A A R R N N II N N GGGG !!! | | | | For optimal performance we recommend to set | | NCORE = 2 up to number-of-cores-per-socket | | NCORE specifies how many cores store one orbital (NPAR=cpu/NCORE). | | This setting can greatly improve the performance of VASP for DFT. | | The default, NCORE=1 might be grossly inefficient on modern | | multi-core architectures or massively parallel machines. Do your | | own testing! More info at https://www.vasp.at/wiki/index.php/NCORE | | Unfortunately you need to use the default for GW and RPA | | calculations (for HF NCORE is supported but not extensively tested | | yet). | | | ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- | | | ----> ADVICE to this user running VASP <---- | | | | You have a (more or less) 'large supercell' and for larger cells it | | might be more efficient to use real-space projection operators. | | Therefore, try LREAL= Auto in the INCAR file. | | Mind: For very accurate calculation, you might also keep the | | reciprocal projection scheme (i.e. LREAL=.FALSE.). | | | ----------------------------------------------------------------------------- LDA part: xc-table for Pade appr. of Perdew ----------------------------------------------------------------------------- | | | W W AA RRRRR N N II N N GGGG !!! | | W W A A R R NN N II NN N G G !!! | | W W A A R R N N N II N N N G !!! | | W WW W AAAAAA RRRRR N N N II N N N G GGG ! | | WW WW A A R R N NN II N NN G G | | W W A A R R N N II N N GGGG !!! | | | | The distance between some ions is very small. Please check the | | nearest-neighbor list in the OUTCAR file. | | I HOPE YOU KNOW WHAT YOU ARE DOING! | | | ----------------------------------------------------------------------------- POSCAR, INCAR and KPOINTS ok, starting setup FFT: planning ... GRIDC FFT: planning ... GRID_SOFT FFT: planning ... GRID WAVECAR not read ----------------------------------------------------------------------------- | | | EEEEEEE RRRRRR RRRRRR OOOOOOO RRRRRR ### ### ### | | E R R R R O O R R ### ### ### | | E R R R R O O R R ### ### ### | | EEEEE RRRRRR RRRRRR O O RRRRRR # # # | | E R R R R O O R R | | E R R R R O O R R ### ### ### | | EEEEEEE R R R R OOOOOOO R R ### ### ### | | | | Orbital orthonormalization failed in the inversion of matrix | | LAPACK: Routine ZPOTRF failed! kpoint: 1 spin: 1 | | | | Possible solutions for this issue are: | | - Please check whether the atoms are too close to each other. | | - Decreasing POTIM might help during relaxations or MDs. | | - Deleting CHGCAR or WAVECAR if incompatible with the structure. | | - Try calculating without symmetrizing (ISYM = 0 or ISYM = -1). | | - As last resort: using a different PAW for some of the atoms. | | | | ----> I REFUSE TO CONTINUE WITH THIS SICK JOB ... BYE!!! <---- | | | -----------------------------------------------------------------------------