While I was at the University of Cambridge, working with CCPN and building a web portal for handling NMR data, I've created ACPYPE, a tool to generate topologies for chemical compounds and to interface with others python applications like CCPN or ARIA, but it ended being a hit with GROMACS user community and I became a fan of AMBER forcefields.
Well, it happened I did work a lot with GROMACS as a graduating student back then in Rio de Janeiro, a time where I was doing a bit of everything, from compiling specific Linux kernels to studying HIV protease in silico.
It's a niche application, I know, and If not for Wim Vranken, ACPYPE would probably never have come to see the light of the day. But we came to realise it was a good thing, so I made a web portal for it as well, firstly, hosted at Cambridge, and now being hosted at Bio2Byte, Wim's group at VUB, thanks to the help of Luciano Kagami.
Yet, after CCPN, I went to work for nine years at Uniprot and ACPYPE went into a minimal maintenance mode, where I tried to keep it up with AMBER and GROMACS updates. So, after this intense time at EBI, our family took a break and went to "experiment" life in the continent. Then enters COVID... you know the rest.
I'm now in Brittany, France, working mostly as a freelance, considering going back to Cambridge, at some point, but we may try to resume our nomad life in Europe and go to Portugal, who knows.
Plans for ACPYPE
(not necessarily in order of importance)
- Automatise GROMACS residue creation (
rtp
file):
so, you have a small molecule and want to convert it in a residue-like for exoteric protein simulations... - Evaluation Amber forcefields 14SB and 19SB:
I may end up needing to use old GROMACS versions as the modern ones don't do vacuum calculations anymore and I need it for FF validations - Improve
amber2gmx
direct conversion functionality:
I realised solvents may have some issues - Review the whole code and bring it up to modern Python3 usage:
For example, I may considertyping
, as it may easier the integration with modern web frameworks - Rerun ACPYPE against thousands of small compounds again:
As we did in the original article
...
Sponsorship
One-off contributions are, obviously, welcome. Any recurring contributions are more than welcome. Any value is appreciated and feel free to add you requests to my TODO list.
It should not come as a surprise if I'm usually inclined to give more attention where the money is but ACPYPE reliability is the most important thing for me.
I'm opened for consultancy and contract works as well, just drop me an email.
Many thanks,
Alan Silva π²πββπββπ§π·π«π·π¬π§
1 sponsor has funded alanwilterβs work.
Featured work
-
alanwilter/acpype
OFFICIAL: AnteChamber PYthon Parser interfacE
Python 207
0% towards 2 monthly sponsors goal
Be the first to sponsor this goal!
$2 a month
SelectThanks!
Honestly. I leave to you to decide which kind of retribution you'd wish. It can be a simple "thanks" , a mention in my acknowledgement or sponsorship page, up to some time of exclusive support for your projects related to ACPYPE. All negotiable.
So pick whatever tier you'd like for whatever reason, be it for what's already done or for the the new features you'd like to see. A badge goes by default.
$5 a month
SelectMuito obrigado!
$10 a month
SelectMerci beaucoup !
$20 a month
SelectMany thanks!
$50 a month
SelectThank you kindly!
$100 a month
SelectThank you very much!
$200 a month
SelectThanks a lot!
$500 a month
SelectMuch obliged!
$1,000 a month
SelectThanks a million!
$2,000 a month
SelectI can't really thank you enough!