-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use gromologist? #218
Comments
Or rather just remove ALL handling of TOP and ITP files and just leave a note for people to look at gromologist. |
I've only had a cursory look at Gromologist but i'm pretty impressed: the documentation seems really extensive, and there are tests (!!). Academic code has gotten better lately :D For example, check out this bit about REST2 – it would have saved me weeks of awk scripting during my PhD... Putting on my startup hat: we can choose to invest time in these features and try to catch-up but it'd be a considerable investment. The typical strategy is to "pivot" into an area where we have an advantage: idk what that would be, maybe ability to run gromacs from python? |
Given limited resources I'd rather specialize on the "provide a working Python-like interface to GROMACS tools that may allow you to run the same script with different versions of the GROMACS tools." |
Agreed – what could change this decision? Perhaps if it turns out that Gromologist is riddled with bugs, or otherwise hard to integrate with (has monster dependencies) |
Yes. Or if deps are an issue, make deps optional.
|
I just looked at gromacs.scaling and I swear I have no memory of writing that :D Not sure what's the best 1st step - could try to re-write that and see how easy that is. I think some scouting work (by me) is needed to inform the decision. I would probably rip out, knowing what I know today, because it's less work and it's not clear how many people depend on this (probably not many). |
https://gitlab.com/KomBioMol/gromologist is a Python package for handling top and itp files.
The text was updated successfully, but these errors were encountered: