Bader code paused during an analysis
Posted: Tue Jun 26, 2018 6:26 am
Dear all and especially Prof. Graeme,
I tried to analyze the Bader charges of a Ce16O31 cluster in a 20x20x20 cubic box. In this job, only the gamma point was used for k-point sampling.
After I issued the command "bader -b weight CHGCAR -ref CHGCAR_sum", the code paused at a point and never went further, as shown in the following:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GRID BASED BADER ANALYSIS (Version 0.95 11/17/15)
OPEN ... CHGCAR
VASP5-STYLE INPUT FILE
DENSITY-GRID: 196 x 196 x 196
CLOSE ... CHGCAR
RUN TIME: 3.12 SECONDS
OPEN ... CHGCAR_sum
VASP5-STYLE INPUT FILE
DENSITY-GRID: 196 x 196 x 196
CLOSE ... CHGCAR_sum
RUN TIME: 2.99 SECONDS
SORTING CHARGE VALUES ... DONE
CALCULATING FLUX ... DONE
INTEGRATING CHARGES
0 10 25 50 75 100
PERCENT DONE: **
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I issued the command on the login node of a HPC center. One reason I can think of is that the box is so large that its needs for memory exceed what the login node can provide. Could this be the reason? If not, what could be the reason?
I have attached the four input files of the job (when you use them, simply delete the ".txt" part of the file names). It is greatly appreciated if someone could run and check it for me. Thanks in advance.
I tried to analyze the Bader charges of a Ce16O31 cluster in a 20x20x20 cubic box. In this job, only the gamma point was used for k-point sampling.
After I issued the command "bader -b weight CHGCAR -ref CHGCAR_sum", the code paused at a point and never went further, as shown in the following:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GRID BASED BADER ANALYSIS (Version 0.95 11/17/15)
OPEN ... CHGCAR
VASP5-STYLE INPUT FILE
DENSITY-GRID: 196 x 196 x 196
CLOSE ... CHGCAR
RUN TIME: 3.12 SECONDS
OPEN ... CHGCAR_sum
VASP5-STYLE INPUT FILE
DENSITY-GRID: 196 x 196 x 196
CLOSE ... CHGCAR_sum
RUN TIME: 2.99 SECONDS
SORTING CHARGE VALUES ... DONE
CALCULATING FLUX ... DONE
INTEGRATING CHARGES
0 10 25 50 75 100
PERCENT DONE: **
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I issued the command on the login node of a HPC center. One reason I can think of is that the box is so large that its needs for memory exceed what the login node can provide. Could this be the reason? If not, what could be the reason?
I have attached the four input files of the job (when you use them, simply delete the ".txt" part of the file names). It is greatly appreciated if someone could run and check it for me. Thanks in advance.