On Wed, Jul 8, 2015 at 10:26 AM, Juan Eiros Zamora <
j.eiros-zamora14.imperial.ac.uk> wrote:
>
> > Not necessarily a mistake. Look at config.h and search for the PYTHON
> > variable. What does it point to?
> >
> 192 #Python interpreter we are using
> 193 PYTHON=/home/je714/anaconda3/envs/py27/bin/python2.7
> 194
> 195 #Type of Amber_Phenix build and python include file
> 196 AMBERPHENIX=no
> 197 INCLUDE_PY=/home/je714/anaconda3/envs/py27/include/python2.7
> 198 PYTHON_VER=2.7
> 199 PHENIX_INC=
> 200 PHENIX_REPO=
>
> So it seems to have picked it up correctly.
>
> But the first line of the mdout_analyzer.py script is setting up a wrong
> python I think:
>
Hmm. Try deleting $AMBERHOME/bin/mdout_analyzer.py and going to
$AMBERHOME/AmberTools/src/etc and running "make python".
I wonder if setup.py just thought that since
$AMBERHOME/bin/mdout_analyzer.py was newer it didn't need to be
"reinstalled". If that's the case, deleting the mdout_analyzer.py script
will fix that problem.
HTH,
Jason
--
Jason M. Swails
BioMaPS,
Rutgers University
Postdoctoral Researcher
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Wed Jul 08 2015 - 12:30:02 PDT
