-
AuthorPosts
-
-
Alex RayevskiParticipantDear developers and support team,
We have already used You soft for some calculations and obtained fine results, but now we added ligand to another small membrane/protein/solvent/ligand system. Our task is a depiction of ligand localization during the channel closure. In general, the ligand should enter channel’s pore in the open state, when helices are vertical, and then block the motion of these blades – a corresponding ‘foot-in-door’ mechanism. Here we suggest, that our reference ligand should undergo some positional changes and fall below.
The open-gate channel system and genesis files were prepared with a Charmm-gui, the close-state structure was already saved in a pdb format, being a reference state for the TMD protocol. The input file of the minimization state (below) was processed with the command : mpirun -np 16 /genesis/genesis-1.7.1/bin/spdyn step6.0_minimization.inp > log
[INPUT]
topfile = ../toppar/top_all36_prot.rtf, ../toppar/top_all36_na.rtf, ../toppar/top_all36_carb.rtf, ../toppar/top_all36_lipid.rtf, ../toppar/top_all36_cgenff.rtf, ../toppar/top_interface.rtf, ../lig/lig.rtf
parfile = ../toppar/par_all36m_prot.prm, ../toppar/par_all36_na.prm, ../toppar/par_all36_carb.prm, ../toppar/par_all36_lipid.prm, ../toppar/par_all36_cgenff.prm, ../toppar/par_interface.prm, ../lig/lig.prm
strfile = ../toppar/toppar_all36_moreions.str, ../toppar/toppar_all36_nano_lig.str, ../toppar/toppar_all36_nano_lig_patch.str, ../toppar/toppar_all36_synthetic_polymer.str, ../toppar/toppar_all36_synthetic_polymer_patch.str, ../toppar/toppar_all36_polymer_solvent.str, ../toppar/toppar_water_ions.str, ../toppar/toppar_dum_noble_gases.str, ../toppar/toppar_ions_won.str, ../toppar/toppar_all36_prot_arg0.str, ../toppar/toppar_all36_prot_c36m_d_aminoacids.str, ../toppar/toppar_all36_prot_fluoro_alkanes.str, ../toppar/toppar_all36_prot_heme.str, ../toppar/toppar_all36_prot_na_combined.str, ../toppar/toppar_all36_prot_retinol.str, ../toppar/toppar_all36_prot_model.str, ../toppar/toppar_all36_prot_modify_res.str, ../toppar/toppar_all36_na_nad_ppi.str, ../toppar/toppar_all36_na_rna_modified.str, ../toppar/toppar_all36_lipid_sphingo.str, ../toppar/toppar_all36_lipid_archaeal.str, ../toppar/toppar_all36_lipid_bacterial.str, ../toppar/toppar_all36_lipid_cardiolipin.str, ../toppar/toppar_all36_lipid_cholesterol.str, ../toppar/toppar_all36_lipid_dag.str, ../toppar/toppar_all36_lipid_inositol.str, ../toppar/toppar_all36_lipid_lnp.str, ../toppar/toppar_all36_lipid_lps.str, ../toppar/toppar_all36_lipid_mycobacterial.str, ../toppar/toppar_all36_lipid_miscellaneous.str, ../toppar/toppar_all36_lipid_model.str, ../toppar/toppar_all36_lipid_prot.str, ../toppar/toppar_all36_lipid_tag.str, ../toppar/toppar_all36_lipid_yeast.str, ../toppar/toppar_all36_lipid_hmmm.str, ../toppar/toppar_all36_lipid_detergent.str, ../toppar/toppar_all36_lipid_ether.str, ../toppar/toppar_all36_carb_glycolipid.str, ../toppar/toppar_all36_carb_glycopeptide.str, ../toppar/toppar_all36_carb_imlab.str, ../toppar/toppar_all36_label_spin.str, ../toppar/toppar_all36_label_fluorophore.strpsffile = step5_input.psf # protein structure file
pdbfile = step5_input.pdb # PDB file
reffile = step5_input.pdb
localresfile = restraints/step6.0_minimization.dihe[OUTPUT]
rstfile = step6.0_minimization.rst[ENERGY]
forcefield = CHARMM # [CHARMM]
electrostatic = PME # [CUTOFF,PME]
switchdist = 10.0 # switch distance
cutoffdist = 12.0 # cutoff distance
pairlistdist = 13.5 # pair-list distance
vdw_force_switch = YES
pme_nspline = 4
contact_check = YES # avoid atomic crash[MINIMIZE]
method = SD
nsteps = 1000
rstout_period = 100[CONSTRAINTS]
rigid_bond = NO
fast_water = NO
shake_tolerance = 1.0D-10
water_model = NONE[BOUNDARY]
type = PBC # [PBC]
box_size_x = 76.9762272
box_size_y = 76.9762272
box_size_z = 106.316749[SELECTION]
group1 = (ai:1-3207) and backbone
group2 = (ai:1-3207) and not backbone and not hydrogen
group3 = ((rnam:DPPC and (an:P)))[RESTRAINTS]
nfunctions = 3function1 = POSI
constant1 = 10.0
select_index1 = 1function2 = POSI
constant2 = 5.0
select_index2 = 2function3 = POSI
direction3 = Z
constant3 = 2.5
select_index3 = 3**
While the output log file shows some topology associated errors:
GENESIS_Information> GENESIS Information
version = 1.7.1
commit ID = 1.7.1 [2021-12-09 16:48:22 +0900]
precision = double
nonbonding = CPUBuild_Information> Compiler Information
build host = root@DESKTOP-S4T47VR
fortran = GNU Fortran (Ubuntu 11.2.0-19ubuntu1) 11.2.0
option = -O3 -ffast-math -march=native -ffree-line-length-none -fallow-argument-mismatch -fallow-invalid-boz -fopenmp
C = gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
option = -O3 -ffast-math -march=native -fallow-argument-mismatch -fallow-invalid-boz -fopenmp
defined var. = -DHAVE_MPI_GENESIS -DOMP -DFFTE -DLAPACK -DDSFMT_MEXP=19937 -D__GFORTRAN__
link option = -fopenmp -llapack -lblasRuntime_Information> Machine and Library Information
date = 2022/10/15 00:34:51
cpu model = Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz
exec. host = alex22@
LD library =[STEP1] Read Control Parameters
…….
…….
[STEP3] Set Relevant Variables and StructuresInput_Top> Summary of Topfile
num_atom_class = 455 num_resi_type = 1906Input_Par> Summary of Parfile
num_bonds = 1227 num_angles = 4018
num_dihedrals = 10965 num_impropers = 273
num_atom_cls = 455 num_nbfix = 74
num_cmap_terms = 6Merge_Top> WARNING: RESI: Multiple definition: “MGU1” : will be ignored.
Merge_Top> WARNING: RESI: Multiple definition: “MGU2” : will be ignored.
Merge_Top> WARNING: RESI: Multiple definition: “CO2” : will be ignored.
Merge_Top> WARNING: RESI: Multiple definition: “THFI” : will be ignored.
Merge_Top> WARNING: RESI: Multiple definition: “THMI” : will be ignored.
Merge_Top> WARNING: RESI: Multiple definition: “THFA” : w….
….tion: “GLYC” : will be ignored.
Merge_Top> WARNING: RESI: Multiple definition: “MBUT” : will be ignored.
Read_Psf> ERROR: NUMLPH is not allowed test rank_no = 1
Read_Psf> ERROR: NUMLPH is not allowed test rank_no = 13What is the reason for these errors and how can we deal with it?
Thank You in advance,
Sincerely, Alex
-
ckobayashiModeratorHello,
From the error message, there are lone-pair bonds. The current version of GENESIS is not available for systems containing any lone-pair bonds. (I guess that the new ligand has some halogen-lone pair bonds?)
Sincerely yours,
Kobayashi
-
Alex RayevskiParticipantHello,
Yes, You are quite right, this halogen belongs to the amiloride molecule. So, if I replace it with CH3 group or simply remove it, the errors will disappear?
In addition, charmm-gui offers a number of inp files to minimize and equilibrate (em and eq) the system, while the tutorial describes a smaller system, thus, contains less files. As I understand, I should pass through the charmm-gui inp files until the production MD step, and then combine those parameters suitable for my system (suggested with a charmm-gui md.inp) with the tutorial’s TMD section… am I right?
Thank You for Your response!
-
ckobayashiModeratorHello,
As for the halogen issue, it would be solved if you re-generate a psf file without halogen.
The second half of the story may be a bit more complicated while I agree with your basic idea.
As far as I know, the CHARMM-GUI inputs are intended for GENESIS 1.X with the LEAP/VVER integrator. (But I’m not sure about very recent CHARMM-GUI, please check ‘integrator=’ in your step7_production.inp.) If you want to use RESPA(VRES) for the production run, you need to execute one more step of equilibration for RESPA. (In other words, please do not use VRES in early steps in equilibration.)
In last, we plan to update the CHARMM-GUI inputs for the recent versions of GENESIS with help of CHARMM-GUI developers.
Kobayashi
-
Alex RayevskiParticipantgood morning all ))
we conducted all equilibration simulations for several protein systems, considering Your advice on chlorine atom (Kobayashi). However, we faced another problem on the MD simulation step. Here is a test inp file for spdyn algorithm application.
[INPUT]
topfile = ../toppar/top_all36_prot.rtf, ../toppar/top_all36_na.rtf, ../toppar/top_all36_carb.rtf, ../toppar/top_all36_lipid.rtf, ../toppar/top_all36_cgenff.rtf, ../toppar/top_interface.rtf, ../lig/lig.rtf
parfile = ../toppar/par_all36m_prot.prm, ../toppar/par_all36_na.prm, ../toppar/par_all36_carb.prm, ../toppar/par_all36_lipid.prm, ../toppar/par_all36_cgenff.prm, ../toppar/par_interface.prm, ../lig/lig.prm
strfile = ../toppar/toppar_all36_moreions.str, ../toppar/toppar_all36_nano_lig.str, ../toppar/toppar_all36_nano_lig_patch.str, ../toppar/toppar_all36_synthetic_polymer.str, ../toppar/toppar_all36_synthetic_polymer_patch.str, ../toppar/toppar_all36_polymer_solvent.str, ../toppar/toppar_water_ions.str, ../toppar/toppar_dum_noble_gases.str, ../toppar/toppar_ions_won.str, ../toppar/toppar_all36_prot_arg0.str, ../toppar/toppar_all36_prot_c36m_d_aminoacids.str, ../toppar/toppar_all36_prot_fluoro_alkanes.str, ../toppar/toppar_all36_prot_heme.str, ../toppar/toppar_all36_prot_na_combined.str, ../toppar/toppar_all36_prot_retinol.str, ../toppar/toppar_all36_prot_model.str, ../toppar/toppar_all36_prot_modify_res.str, ../toppar/toppar_all36_na_nad_ppi.str, ../toppar/toppar_all36_na_rna_modified.str, ../toppar/toppar_all36_lipid_sphingo.str, ../toppar/toppar_all36_lipid_archaeal.str, ../toppar/toppar_all36_lipid_bacterial.str, ../toppar/toppar_all36_lipid_cardiolipin.str, ../toppar/toppar_all36_lipid_cholesterol.str, ../toppar/toppar_all36_lipid_dag.str, ../toppar/toppar_all36_lipid_inositol.str, ../toppar/toppar_all36_lipid_lnp.str, ../toppar/toppar_all36_lipid_lps.str, ../toppar/toppar_all36_lipid_mycobacterial.str, ../toppar/toppar_all36_lipid_miscellaneous.str, ../toppar/toppar_all36_lipid_model.str, ../toppar/toppar_all36_lipid_prot.str, ../toppar/toppar_all36_lipid_tag.str, ../toppar/toppar_all36_lipid_yeast.str, ../toppar/toppar_all36_lipid_hmmm.str, ../toppar/toppar_all36_lipid_detergent.str, ../toppar/toppar_all36_lipid_ether.str, ../toppar/toppar_all36_carb_glycolipid.str, ../toppar/toppar_all36_carb_glycopeptide.str, ../toppar/toppar_all36_carb_imlab.str, ../toppar/toppar_all36_label_spin.str, ../toppar/toppar_all36_label_fluorophore.strpsffile = step5_input.psf # protein structure file
pdbfile = step5_input.pdb # PDB filerstfile = step6.6_equilibration.rst # restart file
#localresfile is not assigned, as there is no corresponding restraint file from the charmm-gui
[OUTPUT]
rstfile = step7_production.rst
dcdfile = step7_production.dcd[ENERGY]
forcefield = CHARMM # [CHARMM]
electrostatic = PME # [CUTOFF,PME]
switchdist = 10.0 # switch distance
cutoffdist = 12.0 # cutoff distance
pairlistdist = 13.5 # pair-list distance
vdw_force_switch = YES
pme_nspline = 4[DYNAMICS]
integrator = VVER # [LEAP,VVER]
timestep = 0.002 # timestep (ps)
nsteps = 50000 # number of MD steps
crdout_period = 50000
eneout_period = 1000 # energy output period
rstout_period = 5000
nbupdate_period = 10[CONSTRAINTS]
rigid_bond = YES # constraints all bonds involving hydrogen
fast_water = YES
shake_tolerance = 1.0D-10
water_model = NONE[ENSEMBLE]
ensemble = NPT # [NVE,NVT,NPT]
tpcontrol = NHC # thermostat and barostat
temperature = 323.15
pressure = 1.0 # atm
gamma_t = 1.0
gamma_p = 0.05
isotropy = SEMI-ISO[BOUNDARY]
type = PBC # [PBC]and here is an example of the error string:
Setup_Enefunc_Angl_Constraint> Some angle paremeters are missing. rank_no = 31
taking into account the fact, that all files were prepared into automatic mode by charmm-gui server, I suppose, I made some mistakes by myself
thank You!
-
ckobayashiModeratorHello,
The reason is that ‘water_model = NONE’ and ‘fast_water = YES’ in [CONSTRAINT] section at the same time.
Please write name of water molecules in your psf file if you want to use ‘fast_water=yes’. Or, since you use CHARMM36m FF via ‘charmm-gui’ , you don’t need to write ‘water_model = ‘ in the section. (The default value is ‘TIP3″.)
Kobayashi
-
Alex RayevskiParticipantGreat, it works!
This is strange, that charmm-gui output files contain these turned on controversial options in a single section.
Is it a correct suggestion, that rmsd analysis could be provided based on any heavy atoms (ligand, nucleic acid residues), but not only protein heavy atoms? And as I understood, if I work with a dimer protein with a bound substrate and I’m interested in a substrate directed/targeted motion, I have to declare two groups : group1 = segid: PROA & segid:PROB & get and group2: mlname: LIG & het
Am I right?
Thank You
-
ckobayashiModeratorHello,
I think that the controversial options are given due to the change in recent GENESIS 2.0. Anyway, we will discuss with developers of CHARMM-GUI soon. Thank you for your report.
As for the latter part, I am not sure I understand your question correctly. I can’t answer that question because it has more to do with research design than how to use GENESIS.
But, I think you will just see a deviation of the internal structure of ligand from the reference structure if you set only ligand as the RMSD group…
Kobayashi
-
Alex RayevskiParticipantDear <span class=”bbp-author-name”>ckobayashi,</span>
Your advices have been definitely useful and I complete several simulations and analyzed them, observing the trends we expected. However, I prepared another very similar model with a charmm-gui and followed the same steps and used the same inp files (slightly modified parameter files from the CHARMM output for Genesis). I passed all minimization and equilibration stages, being sure that I’ll have no problems with the production run, but I was wrong – the log file ended with the line:
Compute_Shake> SHAKE algorithm failed to converge: indexes
Neither repeatable equilibration steps, nor production input file modification (integrator, iteration step value, temperature) gave nothing… I inspected the manual and forum, but not thoroughly enough (I missed a clash-check and ring penetration section). From these I used Chimera to identify the problem regions – two pairs of lipids from the opposite sides of the membrane intertwined suddenly, when the PBC protocol was applied to the system.
As I had all the files from CHARMM (psf, topprams, inp) I decided to change just coordinates from the last frame of the final equilibration dcd trajectory (crd_convert -> pdb file). The resulting pdb file structure was compared with the initial input pdb file from the CHARMM output. I did everything clear and tested the novel system with one of the equilibration steps.
But the production run crashed again. Do You have any suggestions, what should I do? Thank You!
-
ckobayashiModeratorHello,
First of all, I can honestly say that I have no idea from the information you have provided.
Can you at least tell us at what stage of the production run you got the shake error? The reason and solution will be completely different depending on whether it is at the 0-th step of the calculation, the 1000-th step, or after the 10-ns run.
As a general solution, you should definitely do ring penetration and clash checks.
However, I’m curious about the explanation..
> From these I used Chimera to identify the problem regions – two pairs of lipids from the opposite sides of the membrane intertwined suddenly, when the PBC protocol was applied to the system.
Since I’m not user of Chimera, I have no idea when such a phenomenon occurs. If there are no strange crashes in the structure without PBC applied, but they appear when PBC is applied, then the boxsize in input must be incorrect.
Kobayashi
-
You must be logged in to reply to this topic.