If you want go for simple dynamics of homology modeled protein structure to energy minimizing and confirmation stability, there is a basic protocol/steps described at Rizzo Lab Wiki (follow the link).
For mdp parameters you can reference the Gromacs MDP option (follow the link).
To add new residue to topology follow this steps:
#Adding a new residue:-
If you have the need to introduce a new residue into an existing force field so that you can use pdb2gmx, or modify an existing one, there are several files you will need to modify. You must consult the manual for description of the required format. Follow these steps:
Add the residue to the .rtp file for your chosen force field. You might be able to copy an existing residue, rename it and modify it suitably, or you may need to use an external topology generation tool and adapt the results to the .rtp format.
If you need hydrogens to be able to be added to your residue, create an entry in the relevant .hdb file.
If you are introducing new atom types, add them to the atomtypes.atp and ffnonbonded.itp files.
If you require any new bonded types, add them to ffbonded.itp.
Add your residue to residuetypes.dat with the appropriate specification (Protein, DNA, Ion, etc).
If the residue involves special connectivity to other residues, update specbond.dat.
Note that if all you are doing is simulating some weird ligand in water, or some weird ligand with a normal protein, then the above is more work than generating a standalone .itp file containing a [moleculetype] (for example, by modifying the .top produced by some parameterization server), and inserting an #include of that .itp file into a .top generated for the system without that weird ligand.
#Modifying a force field:-
In GROMACS 4.5 and later, modifying a force field is best done by making a full copy of the installed forcefield directory and residuetypes.dat into your local working directory:
Then, modify those local copies as above. pdb2gmx will then find both the original and modified version and you can choose the modified version interactively from the list, or if you use the pdb2gmx -ffoption the local version will override the system version.
Parametrization protocols vary depending on which force field you're using. The implementation of the parameters is fairly straightforward, just see Chapter 5 of the GROMACS manual. The hard work is in obtaining the parameters, for which you'll have to refer to the primary literature for your chosen force field.
If you want go for simple dynamics of homology modeled protein structure to energy minimizing and confirmation stability, there is a basic protocol/steps described at Rizzo Lab Wiki (follow the link).
For mdp parameters you can reference the Gromacs MDP option (follow the link).
To add new residue to topology follow this steps:
#Adding a new residue:-
If you have the need to introduce a new residue into an existing force field so that you can use pdb2gmx, or modify an existing one, there are several files you will need to modify. You must consult the manual for description of the required format. Follow these steps:
Add the residue to the .rtp file for your chosen force field. You might be able to copy an existing residue, rename it and modify it suitably, or you may need to use an external topology generation tool and adapt the results to the .rtp format.
If you need hydrogens to be able to be added to your residue, create an entry in the relevant .hdb file.
If you are introducing new atom types, add them to the atomtypes.atp and ffnonbonded.itp files.
If you require any new bonded types, add them to ffbonded.itp.
Add your residue to residuetypes.dat with the appropriate specification (Protein, DNA, Ion, etc).
If the residue involves special connectivity to other residues, update specbond.dat.
Note that if all you are doing is simulating some weird ligand in water, or some weird ligand with a normal protein, then the above is more work than generating a standalone .itp file containing a [moleculetype] (for example, by modifying the .top produced by some parameterization server), and inserting an #include of that .itp file into a .top generated for the system without that weird ligand.
#Modifying a force field:-
In GROMACS 4.5 and later, modifying a force field is best done by making a full copy of the installed forcefield directory and residuetypes.dat into your local working directory:
Then, modify those local copies as above. pdb2gmx will then find both the original and modified version and you can choose the modified version interactively from the list, or if you use the pdb2gmx -ffoption the local version will override the system version.
This file won't work as a pdb2gmx input because the atom names aren't unique. You also need to provide the text of the .rtp entry; I can't diagnose the problem at all without it. The coordinate file alone is not enough.
OK, you need unique atom names. Your .rtp also does not specify bonds, which are mandatory. Of course now you will see the problem - how do you define the bonded connectivity unambiguously? You can't unless you correct both the coordinates and the .rtp file, otherwise there is no way to tell that the first C is different from the second C, etc.
PRODRG produces topologies with many errors; I do not recommend it. A lot of software programs produce PDB files that are sub-standard; therefore, no, a direct transfer from Avogadro to GROMACS will not work without many correction of the issues in the coordinate file.