-
Notifications
You must be signed in to change notification settings - Fork 14
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
Repex submission new #222
Repex submission new #222
Conversation
…s with proper conformations
Will check it out later! |
Codecov Report
@@ Coverage Diff @@
## release3 #222 +/- ##
============================================
- Coverage 54.63% 54.54% -0.10%
============================================
Files 92 92
Lines 13884 13902 +18
============================================
- Hits 7586 7583 -3
- Misses 6298 6319 +21
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
pygromos/files/blocks/imd_blocks.py
Outdated
setattr(self, "NRET", int(content[3].split()[0])) | ||
T_values = list(map(float, content[5].split())) | ||
if(len(T_values)== self.NRET): | ||
setattr(self, "RET", T_values) | ||
else: | ||
raise IOError("REPLICA: NRET was not equal to the number of Temperatures (RET) in IMD!") | ||
setattr(self, "LRESCALE", int(content[7].split()[0])) | ||
print (content[7]) |
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.
Is this a debug print?
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.
yes forgot to remove this one
… depending on multi node / single node setup
…osTools into repex_submission_new
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.
My local tests run as well (I don't do much REPEX). However, I am against the change:
initialize_first_run= True
I believe it makes PyGromos more unpredictable.
@@ -21,7 +21,7 @@ def do(in_simSystem: Gromos_System, | |||
simulation_run_num: int, | |||
equilibration_run_num: int = 0, | |||
work_dir: str = None, | |||
initialize_first_run= False, reinitialize_every_run= False, | |||
initialize_first_run= True, reinitialize_every_run= False, |
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.
I'm against this change. I believe PyGromos should by default not change anything.
@pultar Very good to hear that your simulations are unaffected and still run well with these changes. Concerning the But I don't have particularly strong feelings about it either. I just know that one (and maybe more) of the downstream functions such as those in As long as all functions with they argument have the same default then I am happy. |
note: I only fixed some merge conflicts in this previous merge. I still have a few more things to do on this branch so it should not be merged just yet. |
I am closing the pull request as I re-implemented these changes (with slight improvements in a different branch, see #288) |
Description
This pull request includes the addition of code to submit replica exchange (Temperature, Hamiltonian, and RE-EDS) simulations using the exact same convention as for normal simulations.
In short the call to the code in
schedule_MD_job.py
written by the simulation scheduler will automtaically adjust everything it needs to dispatch the calculation to eithermd
,md_mpi
orrepex_mpi
.The waiting for output files was adjusted to wait for all N (number of replicas) output cnfs. Similarly the path provided is slightly adjusted to match the convention of gromos for replica exchange depending on the presence / absence of the CONT keyword.
The code was also tested with regular MD simulations, and there was no problem in submitting / zipping files for those.
@MTLehner @pultar As you might be the most frequent users of pyGromos at the moment you might want to checkout my branch and see if the submission for your systems still works fine!
Todos
Status