install error with new version
Posted: Thu Jun 05, 2014 12:11 pm
Dear developers,
I have downloaded from the web page the vtst and bader software, to use it with the VASP program (in its newest version 5.3.5). When compiling the system with these, I have found that after executing the instruction
mkbdrpro.pl bdr_changes
the resulting bdrpro.F contains, before subroutine BDRPROJ_SET and after subroutine SPHPRO_DESCRIPTION, the lines
! for projection in Bader volume
io_begin
WRITE(*,*) "FINISH DOS PROJECTION IN BADER VOLUMES"
io_end
! end of change
111111
which seem to make no sense and produce error during compilation. Should I just delete those lines in bdrpro.F or is something different needed?
I have also noted that, while in some earlier versions of the vtst software the web page indicated the need to replace in main.F a block of lines beginning with
CALL CHAIN_FORCE(T_INFO%NIONS,….
with another longer block, the new web page omits such recommendation. Is this omission a mistake, and the replacement should be done (as in the previous versions, or is the replacement no longer needed?
Thanks,
José-Carlos Conesa
I have downloaded from the web page the vtst and bader software, to use it with the VASP program (in its newest version 5.3.5). When compiling the system with these, I have found that after executing the instruction
mkbdrpro.pl bdr_changes
the resulting bdrpro.F contains, before subroutine BDRPROJ_SET and after subroutine SPHPRO_DESCRIPTION, the lines
! for projection in Bader volume
io_begin
WRITE(*,*) "FINISH DOS PROJECTION IN BADER VOLUMES"
io_end
! end of change
111111
which seem to make no sense and produce error during compilation. Should I just delete those lines in bdrpro.F or is something different needed?
I have also noted that, while in some earlier versions of the vtst software the web page indicated the need to replace in main.F a block of lines beginning with
CALL CHAIN_FORCE(T_INFO%NIONS,….
with another longer block, the new web page omits such recommendation. Is this omission a mistake, and the replacement should be done (as in the previous versions, or is the replacement no longer needed?
Thanks,
José-Carlos Conesa