If we distribute both leap and sleap, we have the obligation to ensure
that they both work. Plus, there is constant need to add new critical
functions when force field is developed. So, some minimum maintenance of
leap and sleap is required.
In the mean time, there is also the motivation to develop a
professional-grade model-building tool. We really do not have to limit to
one approach. Those of you who want to start from scratch, you are welcome
to start right now. Those who want to modernize leap/sleap, you are more
than welcome to do so too. These two goals are not in conflict in any way.
Rather, I see them as complementary.
But, more importantly, please act. Pick one approach that you like most
and start work on it. Nothing should prevent you from working on a project
that you feel so passionate about.
Yong
On 11/7/11 4:41 PM, "Wei Zhang" <zgjzweig.gmail.com> wrote:
>Hi Ben,
>
> The best way I can think of is: maintain tleap, and try to add things
>that sleap does better
>then tleap. That seems to be the most managable solution.
>
> Sincerely,
>
> Wei
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Mon Nov 07 2011 - 18:00:03 PST
