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

tleap ToDo #51

Closed
2 tasks
nhenriksen opened this issue Apr 3, 2018 · 2 comments
Closed
2 tasks

tleap ToDo #51

nhenriksen opened this issue Apr 3, 2018 · 2 comments

Comments

@nhenriksen
Copy link
Collaborator

nhenriksen commented Apr 3, 2018

  • if pbc_type is None there is very little filtering of template lines. We probably need to at least get rid of quit lines. Also, if output_prefix is not None we should probably get rid of saveamberparm in template_lines
  • Write tleap output to a log file in each window. We also need to figure out what to do for organized logging overall, but I think this should definitely go in each window subdir ... for reference purposes.
@slochower
Copy link
Member

Okay. Should we have the ability to write a default salvation input file, if there is no template and no template list of strings? In other words, should we expect everyone who uses paprika know how to use tleap?

@nhenriksen
Copy link
Collaborator Author

Seems like a good idea, but how would it work? You have to have a force field (leaprc) plus solute frcmods and mol2s at minimum. Those are always different. I think we have to expect that anyone who uses paprika.tleap will know how to use tleap.

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