Hi,
So I have made use of PMX for the unfolded state and used their tripeptide database for the CHARMM36 ff. However when I attempt the command pdb2gmx on the tripeptide:
gmx_mpi pdb2gmx -f tripep_V2C.pdb -o conf.pdb -p topol.top -ff charmm36m-mut -water tip3p
I get the following error:
:-) GROMACS - gmx pdb2gmx, 2023.2 (-:
Executable: /usr/local/gromacs/bin/gmx_mpi
Data prefix: /usr/local/gromacs
Working dir: /home/tammara/Documents/gmx_test
Command line:
gmx_mpi pdb2gmx -f tripep_V2C.pdb -o conf.pdb -p topol.top -ff charmm36m-mut -water tip3p
Using the Charmm36m-mut force field in directory /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff
going to rename /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.r2b
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.r2b
Reading tripep_V2C.pdb…
Read ‘’, 42 atoms
Analyzing pdb file
Splitting chemical chains based on TER records or chain id changing.
There are 1 chains and 0 blocks of water and 5 residues with 42 atoms
chain #res #atoms
1 ‘X’ 5 42
All occupancies are one
All occupancies are one
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/atomtypes.atp
Reading residue database… (Charmm36m-mut)
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.rtp
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/mutres.rtp
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/mutres_dna.rtp
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.hdb
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.n.tdb
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.c.tdb
Back Off! I just backed up topol.top to ./#topol.top.8#
Processing chain 1 ‘X’ (42 atoms, 5 residues)
Identified residue ACE1 as a starting terminus.
Identified residue CT35 as a ending terminus.
8 out of 8 lines of specbond.dat converted successfully
Start terminus ACE-1: NH3+
End terminus CT3-5: COO-
Program: gmx pdb2gmx, version 2023.2
Source file: src/gromacs/gmxpreprocess/pdb2top.cpp (line 1115)
Fatal error:
atom N not found in buiding block 1ACE while combining tdb and rtp
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
To that effect I realised I had to use the -ter option to specify the capped terminal ends, and so I added the option and selected none for both ends, however I get the following:
gmx_mpi pdb2gmx -f tripep_V2C.pdb -o conf.pdb -p topol.top -ff charmm36m-mut -water tip3p -ter
:-) GROMACS - gmx pdb2gmx, 2023.2 (-:
Executable: /usr/local/gromacs/bin/gmx_mpi
Data prefix: /usr/local/gromacs
Working dir: /home/tammara/Documents/gmx_test
Command line:
gmx_mpi pdb2gmx -f tripep_V2C.pdb -o conf.pdb -p topol.top -ff charmm36m-mut -water tip3p -ter
Using the Charmm36m-mut force field in directory /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff
going to rename /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.r2b
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.r2b
Reading tripep_V2C.pdb…
Read ‘’, 42 atoms
Analyzing pdb file
Splitting chemical chains based on TER records or chain id changing.
There are 1 chains and 0 blocks of water and 5 residues with 42 atoms
chain #res #atoms
1 ‘X’ 5 42
All occupancies are one
All occupancies are one
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/atomtypes.atp
Reading residue database… (Charmm36m-mut)
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.rtp
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/mutres.rtp
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/mutres_dna.rtp
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.hdb
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.n.tdb
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.c.tdb
Back Off! I just backed up topol.top to ./#topol.top.9#
Processing chain 1 ‘X’ (42 atoms, 5 residues)
Identified residue ACE1 as a starting terminus.
Identified residue CT35 as a ending terminus.
8 out of 8 lines of specbond.dat converted successfully
Select start terminus type for ACE-1
0: NH3+
1: NH2
2: 5TER
3: None
3
Start terminus ACE-1: None
Select end terminus type for CT3-5
0: COO-
1: COOH
2: CT2
3: 3TER
4: None
4
End terminus CT3-5: None
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/merged.arn
Opening force field file /usr/local/lib/python3.10/dist-packages/pmx/data/mutff/charmm36m-mut.ff/mutres.arn
Checking for duplicate atoms…
Generating any missing hydrogen atoms and/or adding termini.
Now there are 5 residues with 42 atoms
Making bonds…
atom HV is missing in residue V2C 3 in the pdb file
atom HV is missing in residue V2C 3 in the pdb file
You might need to add atom HV to the hydrogen database of building block V2C in the file mutres.hdb (see the manual)
You might need to add atom HV to the hydrogen database of building block V2C in the file mutres.hdb (see the manual)
Program: gmx pdb2gmx, version 2023.2
Source file: src/gromacs/gmxpreprocess/pdb2top.cpp (line 1567)
Fatal error:
There were 1 missing atoms in molecule Protein_chain_X, if you want to use
this incomplete topology anyhow, use the option -missing
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.