In this case, the input structure to pdb2gmx has hydrogen atoms whose naming differs from that given in the .rtp file of the force field.
The .rtp file contains amino acid specific information - the atoms that constitute it, their charge (masses are retrieved from the atomtypes.atp file using the atom name) and the bonded potentials (bond, angle, dihedral, impropers) used to model the amino acid. The coordinates in the pdb file along with the cognate force field information in the .rtp and ffnonbonded.itp files contain all the information required to start a simulation.
This specific naming convention is what gromacs expects when it encounters a given amino acid in a pdb file. As the input in this case does not comply with this, pdb2gmx throws an error.
The hydrogen atoms in the input structure can be ignored by using the -ignh flag of pdb2gmx. If this flag is used, the positions of the hydrogen atoms to be added will be guessed by pdb2gmx. If the hydrogen positions need to be retained, the names in the input pdb file must be changed to match those in the rtp file.
In this case, the input structure to pdb2gmx has hydrogen atoms whose naming differs from that given in the .rtp file of the force field.
The .rtp file contains amino acid specific information - the atoms that constitute it, their charge (masses are retrieved from the atomtypes.atp file using the atom name) and the bonded potentials (bond, angle, dihedral, impropers) used to model the amino acid. The coordinates in the pdb file along with the cognate force field information in the .rtp and ffnonbonded.itp files contain all the information required to start a simulation.
This specific naming convention is what gromacs expects when it encounters a given amino acid in a pdb file. As the input in this case does not comply with this, pdb2gmx throws an error.
The hydrogen atoms in the input structure can be ignored by using the -ignh flag of pdb2gmx. If this flag is used, the positions of the hydrogen atoms to be added will be guessed by pdb2gmx. If the hydrogen positions need to be retained, the names in the input pdb file must be changed to match those in the rtp file.
Warnings given by gromacs indicate some important issue. If you think that it is fine to proceed, then use the -maxwarn flag. The argument is the number of warnings that you want grompp to overlook, in this case 1 (-maxwarn 1)
To get a better idea of the whole process of setting up simulations, you can look at the following tutorials by Dr. Justin Lemkul.
What can I do if the problem of atom is about carbon? I redefined the atoms and checked there is no mismatch between them. The gromacs still give me this error when I tried to convert pdb file using gmx pdb2gmx just like Malathi I assume. The error is following:
Atom CT3x in residue EthB 1 was not found in rtp entry EthB with 7 atoms
while sorting atoms.
Ps. I tried to use Gromacs for polymers and the residues are not standard protein residue but defined as building blocks.
error: atom N not found in building block 1ACE while combining tdb and rtp
This is one of the advices I got from net (Thanks to Justin Lemkul):
Nowhere in the explanation of the error does it suggest that you should alter the .rtp file in this instance. You have atoms in your structure that are not in the .rtp entry. Specifically, your structure file has an N atom in ACE, but ACE only contains CA, C, and O. The N atom should be the first atom in the next residue, not ACE.
But I have no idea how to deal with this problem. Because it just explains the issue without any solution.