-
Notifications
You must be signed in to change notification settings - Fork 2
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
Automated solvation shell extraction workflow #8
base: main
Are you sure you want to change the base?
Conversation
On another note, where should we be tracking pip/conda package dependencies for this code? |
I think that goes in om-data/setup.py (i.e. the setup.py in the parent directory) |
lattices = np.array([a, b, c])[None][None] | ||
|
||
# Choose solute atom | ||
solu = universe.select_atoms(f"name {solute_atom}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I realized that this doesn't yet support multiple atoms in a single solute. I'll get on this.
…ng pipeline, need to test
… solute and solvent resname dictionary construction
In this PR, we construct a workflow for extracting diverse solvation shells from MD trajectories of electrolyte systems. This workflow operates on PDB files and outputs a directory containing xyz files organized according to solute type and coordination number.
Note: for low-concentration simulations, this workflow is likely sufficient for extracting the solvation shells we require. However, for high concentration simulations, we will need to do a network/topology analysis to extract more interesting snapshots. This will be completed in a future PR.