This brings up a question. The wiki regarding amber test errors -- we
should only update this for the RCs, no? How do you want us reporting
on that?
On Sun, Mar 28, 2010 at 10:52 PM, case <case.biomaps.rutgers.edu> wrote:
> Hi everyone:
>
> I have placed the latest release candidates here:
>
> http://ambermd.org/downloads/AmberTools.28mar10.tar.bz2
> http://ambermd.org/downloads/Amber11.28mar10.tar.bz2
>
> Notes:
>
> 1. AmberTools can stand on its own, but Amber11 requires you to first download
> and untar AmberTools. Note: you don't need to *compile* AmberTools, but you
> do need to untar and configure it.
>
> If you don't want to read the instructions: go to amber11/AmberTools/src
> and run configure from there. This will create a config.h file that is used
> by both AmberTools and Amber11.
>
> 2. I left out the 2_million_atom and cuda test suites: these take up 200
> Mbytes, and won't be used by most people. I'm thinking of distributing
> these in a separate tar file. Many people have to download Amber over pretty
> slow internet connections.
>
> 3. The code in CVS no longer corresponds to the release candidates, but the
> differences are few. I still encourage people to update the documentation,
> and commits can still be made in the amber11/doc subdirectory.
>
> ...thx...dac
>
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
>
--
---------------------------------------
Jason M. Swails
Quantum Theory Project,
University of Florida
Ph.D. Graduate Student
352-392-4032
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sun Mar 28 2010 - 21:00:02 PDT
