I just installed AMBER in a few Centos 7 workstations and thought it would be helpful to share a few comments on my experience. I’m also going to reiterate a few things from a message from a couple of weeks ago (adventures …) for completeness sake.
1. It is worthy in the end, but AMBER is by a good margin the most painful program I have had to deal with in regard to installation. I’m assuming there are good reasons for that, and part of it must be my fault since my background may not be adequate, but still, even when all goes well it is very time consuming.
2. Best practices I’ll adopt in the future to avoid problems (most can be found in the manual and comments, but some differ):
* Download and extract latest cmake.
* I’ll stick to bash for installation (most do, but we default to csh for convenience) and start by defining PATH as follows: “export PATH=”/usr/bin/:/usr/localbin/:'path-to-cmake/bin” (I wasted a LOT of time due to some interference in one of our machines causing a problem with libSM that would abort installation at 95%!). Once installation is completed I’ll allow general PATH definitions in .bashrc/.cshrc files.
* For parallel I won’t have openmpi installed with yum (I’ll erase it if it is). I mentioned previously that the tests for dhfr and ris3d stalled and was due to that. I tried mpich as recommended, however it failed on configuration for me. I succeeded with the latest openmpi (extracted to AmberTools/src) and ./configure_openmpi.
3. As mentioned previously, amber.csh doesn’t work properly to detect the shell (csh/tcsh) nor to set AMBERHOME. I fixed by setting AMBERHOME manually and changing the conditional for shell to “if $0 !~ (‘*csh’)”.
Best,
Hugo
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Sat May 08 2021 - 10:30:02 PDT
