UT theoretical chemistry code forum

This is my fault. I recently tried to remove all boinc dependencies in eon and I forgot some of the potentials.
Version 2366 should have fixed this problem.

Neither of these are correct. 1. Run the neb calculation. 2. Run "vfin.pl subdir" where dir is the name of the directory to store the calculation. 3. Go into that directory "cd subdir" and make sure the calculation is sensible; you can run nebresults.pl and check the output 4. From that subdir (whic...

My guess is that you have not linked in our vtstcode into vasp. The graph that you show appears to have zero projected forces at each image, which is why the spline is so wiggly and you are getting extra extrema along the path. Start by greping your OUTCAR file for VTST - if you don't see a line say...

I can't see what is going on with this calculation. There are no OUTCARs in the 0? directories and the exts.dat file has energies of over 70 eV, which makes no sense. The way this should work is to run an NEB calculation and then simply run the neb2dim.pl script to set up a dimer calculation. There ...

The valence charge is normalized so that the sum of the values at the grid points in the CHGCAR file gives the total (valence) charge. There is no such normalization for the total charge. The integrated total charge is highly sensitive to the grid density because of the cusps at the nuclear centers....

The first calculation does not make sense in terms of the number of negative modes. I would need to see that calculation to see what might be going wrong. The typical problems are related to the displacement size, which should be on the order of 0.01 - 0.001 Ang, accurate forces with ediff=1e-8, and...

If you have an NEB calculation (even a rough one) you can use our neb2dim.pl script to generate a dimer calculation with a MODECAR file aligned along the reaction coordinate at the interpolated saddle position.

the command "bader CHGCAR -ref CHGCAR_sum" will determine the Bader volumes from the CHGCAR_sum file but then integrate the charge from the CHGCAR file in those Bader volumes. The total charge should be accurate, because the normalization of the CHGCAR file is based upon the sum of the charge densit...

There needs to be reasonable charge density files from vasp for this analysis to work. But again, I don't know what's going wrong with vasp or how to fix it - I've just seen this problem before (you can find similar posts on this forum). This problem needs to be addressed by the VASP folks - you can...

It's a problem with the core charges written in the AECCAR files. In the snapshot, you can see lines of oscillating charge density leading from the atomic cores along the grid directions. I've seen this before, but I don't know the reason. Not only does this make the Bader analysis take a very long ...

Check the message at the end of the ??/OUTCAR files:

Must set IOPT = 3 or 7 when using ISIF = 3
Alternatively, use the vasp optimizers

I don't know why you have ISIF 3 set, but unless you really know what you are doing (i.e., using the solid state NEB) switch ISIF to 2 and it should run.

There should not be any coupling between VDW and the VTST code. Did you try to converge without the VDW interactions?

If you post the calculation, I can take a look at it.

Please attach the CHGCAR, AECCAR0 and AECCAR2 files. Also, make sure the the electronic structure is converged. If it requires more than 60 iterations, increase NELM. One more thing: load up the CHGCAR_sum file in a visualization program like vesta and see if it looks physically reasonable. For some...

Every entry in that Atindex.dat file corresponds to a cell of charge density, just as would be specified in the CHGCAR file, but instead of the value of the charge density, it contains the atom number to which that cell was assigned by the Bader analysis.

If you use the "-p atom_index" or "-p bader_index" the bader code will write a charge density like file with all the points assigned to each atom or each charge density maximum.