From: Marcelo C. R. Melo (melomcr_at_gmail.com)
Date: Tue Oct 27 2020 - 09:39:21 CDT
Hi Asma,
You need a licence to use MOPAC, there is no way around it. Make sure you
provide them with an academic email in order to get an academic licence
(not a *yahoo* email account).
Regarding running it in Windows, I am absolutely sure that was not tested,
and am pretty sure it will not work due to the code that manages the
interaction between NAMD and the QM engines.
Best,
Marcelo
On Tue, 27 Oct 2020 at 05:42, Asmi Mahmood <asmi_mahmood_at_remove_yahoo.com>
wrote:
> Hi
>
> Thanks for the guiding. I studied the tutorial and yes it could help me.
> But one thing, i tried to download MOPAC from their site and set email for
> academic license twice but still no reply from them. Its been more than 10
> days. Plz guide me now how to download MOPAC without getting license.
> One more thing if i would download all the required softwares in windows
> 10, would it work to calculate MM/QM.
>
> Regards
>
> Thanks in advance
>
> Asma
>
>
> On Friday, 16 October 2020, 10:32:08 pm GMT+5, Marcelo C. R. Melo <
> melomcr_at_gmail.com> wrote:
>
>
> Yes, you are most likely seeing the link atoms added to the QM calculation
> (even though they are not part of the original system).
>
> I did not work on the Gaussian script, and have never used Gaussian for
> QM/MM, so I cannot tell the specifics of that calculation.
> Maybe people here more knowledgeable in Gaussian output could help, or the
> original author of that script.
>
> Best,
> Marcelo
>
>
>
> On Fri, 16 Oct 2020 at 10:39, jing liang <jingliang2015_at_gmail.com> wrote:
>
> Marcelo,
>
> thank you for the information, I tried already the script:
>
> http://www.ks.uiuc.edu/Research/qmmm/Scripts/run_gaussian.py
>
> However, I observed that the resulting input script for Gaussian contains
> additional lines for other atoms than the
> QM ones and this caused a problem for Gaussian which crashed because of
> them. Therefore, I commented out
> the line 119. In this way, only the QM atoms are listed in the Gaussian
> input script. However, I don't know why
> this line is needed?
>
> After that modification, other two atoms are listed in the Gaussian input
> script and I am almost sure that these
> are the link atoms, right? I got the psf and pdb file from the example:
>
> http://www.ks.uiuc.edu/Research/qmmm/Examples/Example1.tar.gz
>
> where, I think, that the link atoms have already been set.
>
> Also, there were some lines that seemed to look for the "Self energy"
> string in the Gaussian log file. In a first converged
> run Gaussian09 didn't print that line and this caused an error. Therefore,
> I commented out the lines 236-240. Do you
> know why this line is required?
>
> Doing all these modifications, NAMD works with Gaussian but I don't know
> if what I am doing is correct. Any comment
> would be welcome.
>
> Thank you.
>
>
>
>
>
>
>
>
>
> El jue., 15 oct. 2020 a las 19:03, Marcelo C. R. Melo (<melomcr_at_gmail.com>)
> escribió:
>
> Hello Jing Liang and Asmi Mahmood,
> Since you both asked similar questions on the list today, I'll answer both
> at the same time.
>
> In the website for NAMD QMMM (http://www.ks.uiuc.edu/Research/QMMM/),
> under the "Tutorial" heading, you will find a basic tutorial to get you
> started, which uses QwikMD to setup the QM/MM simulation in its most
> standard format.
> For a slightly more advanced approach, there is also an example showing a
> TCL script that can help you fine tune your QM region selection.
> Finally, there is an advanced tutorial based on a Jupyter notebook that
> helps you set up a free energy estimate based on QM/MM calculations.
>
> Of course, in NAMD's user guide you will also find explanations and a
> complete list of keywords and their functions.
>
> Regarding NAMD-Gaussian simulations, you will be setting the *qmSoftware* keyword
> to "custom" and will need to point *qmExecPath* to your wrapper script
> (which you seem to have found already). You should adapt that script for
> your particular case in order to create a Gaussian input file. To make it
> clear, the *qmConfigLine* keyword only works with the native interfaces
> for MOPAC and ORCA, so you won't need to set it.
>
> I would *strongly suggest* starting with a simple simulation using QwikMD,
> studying the inputs that are created, and then adapting those to your
> particular case.
>
> Best,
> Marcelo
>
> On Thu, 15 Oct 2020 at 09:07, Asmi Mahmood <asmi_mahmood_at_remove_yahoo.com>
> wrote:
>
> Hi
>
> I need to run MM/QM using namd with orca. Is there any available protocol
> or tutorial available for it.
>
> Is there any other means to calculate QM for the active site only and MM
> for the remaining protein in namd. If any better way to do plz suggest
>
> Regards
>
> Sent from Yahoo Mail on Android
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
>
>
This archive was generated by hypermail 2.1.6 : Thu Dec 31 2020 - 23:17:14 CST