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

Distinguish between unsolvated and solvated models #52

Open
jchodera opened this issue Apr 14, 2020 · 2 comments
Open

Distinguish between unsolvated and solvated models #52

jchodera opened this issue Apr 14, 2020 · 2 comments

Comments

@jchodera
Copy link
Contributor

@Lnaden:

It would be useful to distinguish between unsolvated models in the "Models" section that is associated with each Structure, as well as on the Models page. For example:
image
The explicitly solvated snapshot may be useful for MD simulations, but is more likely important for provenance tracking purposes with the associated simulation dataset that contains trajectories since very few modeling applications can use the solvated snapshot.

By contrast, the unsolvated protein models---into which missing loops have been built, structural modeling errors have been corrected, misperceived structural ions have been corrected, etc. can be used in essentially all modeling workflows.

I would suggest we move the solvated snapshots to be associated with their relevant simulation trajectories into "Simulations", and reserve "Models" for pre-solvated models that have corrected issues with the original structural data.

@Lnaden
Copy link
Collaborator

Lnaden commented Apr 15, 2020

I like this idea, it would help simplfy what people are looking for. What is the proposal for when someone only has the fully solvated model? Do we find a way to take it in and de-solvate it?

@jchodera
Copy link
Contributor Author

I think modellers like @tristanic will be preparing models that don't have (unresolved) solvent, and that these are the most flexible models to start with for any modeling.

Solvated models are almost certainly going to be associated with a simulation dataset, so it makes sense to keep them associated together under "Simulations" for purposes of provenance.

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

No branches or pull requests

2 participants