Hi everyone:
[This is second posting of our AmberTools25 deadlines. I'm including extra
people on the list, so some of you (who don't subscribe to or read the
amber-developers mailing list) may be getting this for the first time.]
This is an odd-numbered year, so there will be no release of Amber (i.e.
pmemd) this year.
We *will*, however, have our usual yearly release of AmberTools25. The
deadline to get code into the gitlab repository is *March 19*. As in
previous years, updates to the Amber25 Reference Manual can be a bit later,
up until *April 14*.
Please, please try to get contributions in as soon as you can. Based on many
years of experience, I understand that many of you will interpret a March 19
deadline as meaning you can wait until about March 20 to think about any of
this. But I am getting crabbier in my old age, and I have a fair amount of
travel scheduled in March and April. It is simply not fair to others to
assume that the rules don't apply to you.
Note also that we need force field updates as well as code updates. (Tom:
can you work on DNA OL24?) And we can really use updates and clarifications
in the force field documentation section -- much of the information there
now is far outdated. Anything that you can contribute along these lines,
and the sooner the better, would be appricated.
Note that the annual developers' meeting will be after the AmberTools25
release. I will be asking a number of you to assist in technical aspects of
getting the release ready. If you would like to volunteer to help out with
this, let me know, and I will add your name to the email list about this
aspect.
Finally: if you have plans for any significant contributions to AmberTools25
that are not already in the master branch at gitlab.ambermd.org, please send
me an email describing your plans.
...thanks...dac
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sun Mar 02 2025 - 08:00:02 PST
