Re: [AMBER] QM/MM with Orca: selected input parameters not taken into account

From: Ruth Helena Tichauer <rhtichau.laas.fr>
Date: Thu, 08 Mar 2018 23:11:55 +0100

Dear Andy,

Thank you for the information.
Best regards,

Ruth 

On Thursday, March 08, 2018 21:01 CET, "Goetz, Andreas" <agoetz.sdsc.edu> wrote:
 Dear Ruth,

You have to provide all settings in the template input file. The settings from the &orc namelist will not be transfered to the template input file. I will add a note to the manual as this does not seem to be clear.

All the best,
Andy


Dr. Andreas W. Goetz
Assistant Research Scientist
San Diego Supercomputer Center
Tel: +1-858-822-4771
Email: agoetz.sdsc.edu
Web: www.awgoetz.de

> On Mar 8, 2018, at 1:54 AM, Ruth Helena Tichauer <rhtichau.laas.fr> wrote:
>
> Dear Amber users and developers,
>
> I’m trying to perform a QM/MM molecular dynamics simulation of a protein complex using the following input files:
>
> _min.in:
> M/MM minimization using Orca
> &cntrl
> imin=1,
> maxcyc=10000, ncyc=9000,
> ntpr=20, ntwx=20, ntwr=2000, ioutfm=1,
> cut=12.0,
> ntb=1,
> ntr=1, restraint_wt = 5.0,
> restraintmask = ':170,185,@CA,C,N',
> ifqnt=1
> /
> &qmmm
> qmmask=':168,169,195-196',
> qmcharge=-2,
> qm_theory='EXTERN',
> qmshake=0,
> qmcut=17.0,
> qm_ewald=0,
> /
> &orc
> method='PBE',
> basis='def2-SVP',
> cbasis='def2-SVP',
> jbasis='def2-SVP',
> num_threads=1,
> convkey='SLOPPYSCF',
> dipole=1,
> maxiter=500,
> use_template=1,
> /
>
> _orc_job.tpl:
> #ORCA input file
> %scf
> SOSCFStart 0.00033
> end
>
> I’m puzzled since in the mdout file, the chosen parameters are correct:
> &orc
> | basis = DEF2-SVP
> | cbasis = DEF2-SVP
> | jbasis = DEF2-SVP
> | method = PBE
> | convkey = SLOPPYSCF
> | guess = read
> | scfconv = -1
> | grid = 4
> | finalgrid = 6
> | maxiter = 500
> | maxcore = 1024
> | ntpr = 20
> | num_threads = 1
> | debug = 0
> | dipole = T
> | use_template = T
> | /
>
> but when I look at the orc_job.dat file, because the simulation crashes with the following error message:
>
> ERROR
> This SCF-wavefunction IS NOT FULLY CONVERGED!
> You can't use it for properties or numerical calculations !
> Aborting the run ...
> Please restart calculation (with larger maxiter/different convergence flags)
>
> I see that the SCF stopped after 125 cycles and that the energy threshold is not the one I have selected:
>
> *****************************************************
> * ERROR *
> * SCF NOT CONVERGED AFTER 125 CYCLES *
> *****************************************************
> ---------------
> SCF CONVERGENCE
> ---------------
>
> Last Energy change ... 3.4826e-05 Tolerance : 1.0000e-08
> Last MAX-Density change ... 1.7469e-03 Tolerance : 1.0000e-07
> Last RMS-Density change ... 1.0077e-05 Tolerance : 5.0000e-09
> Last DIIS Error ... 1.1837e-03 Tolerance : 5.0000e-07
>
> **** DENSITY FILE WAS UPDATED (orc_job.scfp.tmp) ****
> **** ENERGY FILE WAS UPDATED (orc_job.en.tmp) ****
>
> --------------------------------------------------------------------
> WARNING
> The wavefunction IS NOT YET CONVERGED! It shows however signs of
> convergence. Therefore the wavefunction will be stored and can be
> used as input for another calculation.
> DO NOT USE THIS WAVEFUNCTION FOR ANYHTING ELSE. It is NOT RELIABLE
>
> What should I do in order for Orca to take into account the parameters I select with my input files and not the default ones? If I provide the orc_job.tpl file, should I re-define all my parameters in it (and not only the additional ones)?
>
> Thank you for any insight into this matter.
>
> Sincerely,
>
> Ruth
> _______________________________________________
> AMBER mailing list
> AMBER.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber

_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
 


 
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Thu Mar 08 2018 - 14:30:03 PST
Custom Search