Skip to main content

Necessary mol2 file editing for protonated systems

 In the previous post I mentioned about using mol2 file for parameter file generation for protonated systems like this.


I mentioned how it is easier to work with mol2 files in this case over prepin files. I ended up creating a mol2 file which appeared sensible consider the definitions of different atoms in the molecule.

I missed one thing then, which I rectified to get calculations going ahead.

After I created the parameter files and started working with them, I realised there is a small issue with the molecule. I found out that the extra proton on oxygen  although is located close to the desired oxygen, it does not show any bond between the proton and the oxygen. Initially I was went impression that this could be an issue with xleap in visualization. But this actually is a problem. If not immediately you will realise it sooner when calculations start giving odd results or crash instantaneously.

Three things need to be carefully checked:

First the extra proton some times is represented as dummy atom by symbol DU, it needs to be replaced by proper atom type.

Second, charge need to be rechecked

third, scrolling down to the region defining the position w.r.t neighbouring atoms, (bond, angle is mostly missing). Manually add an extra line referring to the extra proton properly defining its bond to the oxygen and angle with respect to an adjacent atom to oxygen.

This should take care of proper representation of extra added proton to the molecule on oxygen, making it triply bonded.



      32 H14        -2.6230    1.2220   -2.7900 ha        1 SNP      0.198000
--> 33 H15         1.5800    0.7770   -1.1740 DU        1 SNP      0.251000
@<TRIPOS>BOND
     1    1    2 1
     2    1    6 1
.
.
.
.


Comments

Popular posts from this blog

AutoDock Vina protocol: For Molecular Docking

There are many softwares available for carrying out molecular docking calculations. Many of these softwares are paid, while some of them are free. AutoDock is one such freely available software. Earlier, there was AutoDock 4.0 version available. One of the problem with the software was the space it would occupy, if you attempt to do multi docking. Recently, there is another algorithm made available under autodock. It is called AutoDock Vina. This is more efficient, robust and fast algorithm. There are many tutorials available to learn AutoDock Vina including: http://autodock.scripps.edu/faqs-help/tutorial/using-autodock-4-with-autodocktools/2012_ADTtut.pdf and also a video tutorial http://vina.scripps.edu/tutorial.html    But for some reason, few changes or explanation in little detail is always required to make it understandable for a beginner to follow.  Here is a protocol designed in our group, which our Master's student follow to get acquainted to Molecular Docking s

Material Studio - selective molecule movement

So, working with Material Studio is awesome. You get to handle bigger, complicated and even unimaginable system. But I am facing problems in very minute functioning. I recently faced two problems, but managed to resolve on my own. Somehow, tutorials doesn't help in resolving them and you end up doing some exercise on your own to get the solution. Among these, the problem of bringing two molecular structures in one window and then adjusting one molecule by moving it around, while other structure remains untouched, as it is. Actually, this should not be a problem to do. There is a simple way of doing this. Select the molecule to be moved and then there is a symbol (button) to select, which allows you to selectively move that molecule only. This is the same way it can be done in Material studio too.  But among all the dozens of symbols, the new person handling MS, kind of gets lost. So, what he does is check the tutorials, for any help. But the tutorials don't talk about suc

xleap to generate prmtop and inpcrd files

Now that we have the lib file with the information for all the molecules we need to include and also the corresponding combined pdb file, creating prmtop and inpcrd files should not be a difficult task. So, to begin with we have a lib file name: molecule.lib a pdb file for 4 molecules name: four.pdb The  task is to generate a prmtop and inpcrd file. Initiate xleap using: $AMBERHOME/exe/xleap -s -f $AMBERHOME/dat/leap/cmd/leaprc.ff99 In xleap window > source leaprc.gaff # load the lib file by: > loadoff molecule.lib I am not sure but some times it helps to also load the frcmod files we created for the four molecules the information of which is stored in the lib file. > loadamberparams aldehyde.frcmod # Load the pdb file: > P=loadpdb four.pdb You should see some thing like this in the xleap window now: ------------------- > P=loadpdb four.pdb Loading PDB file: ./four.pdb Warning: name change in pdb file residue 1 ;  this residue is split i