Dear Amber List members,
Many thanks to all of you for the problem solution advices.
Unfortunately, I failed to apply any variant of the Amber Tools upgrade
from
14 to 15.
Finally I have deleted the amber14 directory
and reinstalled from scratch both Amber14 and AmberTools15
from compressed files following the amber user manual.
Everything works OK now.
All the best,
Michael
*****************************
Michael Shokhen, PhD
Associate Professor
Department of Chemistry
Bar Ilan University,
Ramat Gan, 52900
Israel
email: michael.shokhen.gmail.com
email: shokhen.mail.biu.ac.il
On Mon, May 4, 2015 at 7:57 PM, David A Case <case.biomaps.rutgers.edu>
wrote:
> On Mon, May 04, 2015, David A Case wrote:
> >
> > It is best to untar the AmberTools15 distribution into a clean
> > (newly-created) directory. I also recommend following common-sense
> > precautions: don't delete your current installation of AmberTools14
> > until you are satsified that AmberTools15 is working.
> >
>
> Just to expand on seemingly conflicting advice about this subject: if you
> have
> a good disk backup scheme in place (and I hope you do...) you can do things
> like untarring the new distribution "on top of" the older one. This saves
> some steps if you also have Amber14 installed, and is essentially what the
> --upgrade option is doing.
>
> But using a fresh directory will be of particular interest to those of you
> who have made revisions to the code, and to anyone with a healthy respect
> for Murphy's law. Just take care to not get confused about which version
> you are running (e.g. which version is first in your PATH.)
>
> ....dac
>
> _______________________________________________
> 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 May 07 2015 - 04:00:04 PDT
