On Fri, 2015-03-13 at 14:31 -0400, Jonathan Gough wrote:
> It's ParmEd.... That is where the issue is...
>
> I did "clean installs" on 2 nearly identical machines. One worked, one
> didn't work. how can I trouble shoot that?
Did you by chance download the Github version of ParmEd on one of those
machines?
The thing about ParmEd is that it's Python, so there is no chance of
there being compiler weirdness causing two machines to yield different
results from the same code. If one passes tests and the other doesn't,
then the codes are different.
I suspect you replaced ParmEd on one of the machines with the version
from Github, which gives prmtops that differ according to "diff", but
not according to "sander".
The ParmEd Github repo has a test/ directory with unit tests that is not
present in the AmberTools distribution. So if
$AMBERHOME/AmberTools/src/parmed has a "test" directory, this would
explain it (and like I mentioned, both versions of ParmEd give
equivalent topologies, they just look different to dacdif).
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 Fri Mar 13 2015 - 12:30:03 PDT
