I am using abinit v 9.6.2. I would like to use the tdep executable to obtain the IFC from a dynamic simulation. As an input, I would like to provide three separated ASCII files fcart.dat, xred.dat and
etot.dat as described here
TODO : Explain the extra input variables when the 3 ASCII files are employed.
Please, could you tell me what these variables are and what is the exact format of such ascii files? Is it necessary to provide some header in those files or it is enough to grep out forces, positions and energies and concatenate them?
Thanks a lot in advance!
Sorry. The documentation is not up to date⊠In fact you can use ASCII files in TDEP as follows :
build 3 files corresponding to the AIMD trajectory : xred.dat, fcart.dat and etot.dat are the reduced coordinates, cartesian forces and total energies as they are given in the ABINIT output file.
add 5 lines in the .abi input file. If you consider the v8/Input/t37.abi input file (corresponding to the reading of a NetCDF trajectory), and read the âechoâ at the beginning of the v8/Refs/t37.abo output file, you can infer the 5 lines to add. See below in bold these lines (for the v8/t37 test case) :
Hi François,
thanks a lot for the quick answer. Following your indications the code reads my input. However, it stops quickly with the error
â !ERROR
src_file: m_tdep_utils.F90
src_line: 297
mpi_rank: 0
message: |
The basis of atoms written in input.in file does not appear in the MD trajectory
âŠ
â !ERROR
src_file: m_tdep_utils.F90
src_line: 298
mpi_rank: 0
message: |
Perhaps, you can adjust the tolerance (tolmotif)
The error message is not clear to me: what does it refer to? I checked the source code and it looks like that it is related to the average position of the atoms but I am not an abinit developer and I donât know how this part is handled and why this check is necessary. Also, I donât know how to set tolmotif, I donât find it in the list of variables here
Hi Antonio,
There are may reasons to have such error (the input file, the MD trajectoryâŠ).
It likely come from your input file : are you sure that your motif (xred_unitcell) and the multiplicity reproduce the atom coordinates (xred.dat) in your supercell (rprimd)? I mean that the ideal reduced positions computed using xred_unitcell and multiplicity could be not equal to the average of the real reduced positions included in xred.dat.
It could also come from your MD trajectory : is there any diffusion of your atoms ? I mean that some atoms do not oscillate around average positions but move freely inside the supercell. That would say, this system does not have any average positions and you cannot compute phonons.
See if one of these answers solve your problem and let me know if not. In this case I will probably ask you to send me your data to see whatâs going on.
I have been doing several test to be sure about the origin of the problem. I am afraid that the atomic positions of the supercell that I have are shifted with respect to those generated by a-tdep by using the multiplicity. Most probably, also the scheme of replica might be different - in my case, the first atoms is replicated along a, then b then c, then second one and so on. How is the supercell created by the a-tdep code? Finally, I donât have any diffusion.
Unfortunately, I am still getting the 2 same errors than Antonio for both the 1) unit cell and 2) supercell case scenarios: âThe basis of atoms written in input.in file does not appear in the MD trajectoryâ and âPerhaps, you can adjust the tolerance (tolmotif)â.
I plotted the input original atomic positions (in atdep.abi) as well as the xred_average.xyz output positions for the unit cell to investigate what was going on. Interestingly, all positions were correct modulo the lattice cell parameter. In other words, some atoms ended up outside of the unit cell, at a position which corresponds to their periodic boundary translation in the neighbouring cell. Is this taken into account in the code or could it be the source of a distorted atoms basis, thus leading to the first error message?
Concerning the first system (only a unitcell), it seems natural that aTDEP does not work. There is no interaction shell so you cannot define any interatomic force constants.
Concerning the second one (the supercell), even it the number of shells will be really low, I donât understand why aTDEP does not work. Please, send me everything needed to run aTDEP (the abi and nc files). If the trajectory is too long, you can reduce it to a few hudreds MD time steps. Here, we donât care about the physics, just a number of configurations sufficient to build an average atomic structure.
Sorry for the delay, I was really busy. Please, send me all your input files (abi and nc files) here or by email (francois.bottin@cea.fr). If the trajectory is too long, you can reduce it to a few hudreds MD time steps. Here, we donât care about the physics, just a number of configurations sufficient to build an average atomic structure. Thanks.