Re: [AMBER] possible bug for reading &qmmm after &lmod

From: Scott Brozell <>
Date: Thu, 18 May 2017 14:34:07 -0400


Thanks for another bug report.


On Fri, May 19, 2017 at 12:00:01AM +0800, liu junjun wrote:
> I find out that xmin_verbosity not working if &qmmm is added after &lmod.
> Actually any lmod parameters will not be read in if &qmmm is placed after
> &lmod. However, there won't be any problem if &qmmm is placed before $lmod.
> >From the source code, I figure out the order of input section is important.
> The acceptable order should be:
> cntrl --> ewald --> pb --> qmmm --> apbs --> lmod --> amoeba --> sebomd -->
> xray
> This "order" issue is caused by the code "backspace(iun)" at line 56 of
> nmlsrc.F90. I guess it would be better if it's changed to "rewind(iun)".
> By the way, I am using AmberTools17.

AMBER mailing list
Received on Thu May 18 2017 - 12:00:03 PDT
Custom Search