Skip to content
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

Open
orbeckst opened this issue May 2, 2022 · 6 comments
Open

use gromologist? #218

orbeckst opened this issue May 2, 2022 · 6 comments

Comments

@orbeckst
Copy link
Member

orbeckst commented May 2, 2022

https://gitlab.com/KomBioMol/gromologist is a Python package for handling top and itp files.

@orbeckst
Copy link
Member Author

Or rather just remove ALL handling of TOP and ITP files and just leave a note for people to look at gromologist.

@jandom
Copy link
Collaborator

jandom commented Nov 11, 2023

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?

@orbeckst
Copy link
Member Author

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."

@jandom
Copy link
Collaborator

jandom commented Nov 13, 2023

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)

@orbeckst
Copy link
Member Author

Yes. Or if deps are an issue, make deps optional.

  1. Would you want to rewrite gromacs.scaling to use gromologist or is that superfluous because their website already shows an example of how to do this kind of stuff directly?

  2. Given that gromologist, exists would we want to maintain the existing ITP/TOP code and the scaling module for as long as it's feasible (i.e., leave it as long as it does not create problems, possibly add a deprecation warning) or just rip it out before a 1.0 (which would require a 0.9.0 release with deprecation warnings).

@jandom
Copy link
Collaborator

jandom commented Nov 15, 2023

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants