-
Notifications
You must be signed in to change notification settings - Fork 103
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
Support two different makers for DoubleRelaxMaker #32
Conversation
I think this is a reasonable approach to take. Am I ok to merge? |
I actually think |
Got it! I'll make that consistent throughout (eg in the tests too). |
Also, sorry about the hacky commits here. I'm coding in quick bursts at the airport 😅 I'll get it sorted out and ready to merge soon though. |
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.
Sorry, you might still be editing but noticed a couple of things.
@utf, yup I'm still editing. I pushed the change because I have some questions. The tests fail due to the LREAL assertion. Do you know why this might be? I'm having trouble pinpoint it. Definitely a (useful) learning process! Edit: And don't worry, I'll squash all the commits before the PR. I mainly wanted to prematurely push here so you could see where I was struggling. |
@utf, okay the tests finally pass now. However, could I ask you to take care of the symlinking? I am on Windows and am worried that it's going to wreak havoc on things. The only files that need to be kept as an actual file are the |
Codecov Report
@@ Coverage Diff @@
## main #32 +/- ##
==========================================
- Coverage 70.39% 70.38% -0.02%
==========================================
Files 45 45
Lines 3804 3809 +5
Branches 576 576
==========================================
+ Hits 2678 2681 +3
- Misses 979 981 +2
Partials 147 147
|
Fantastic, thank you! |
Summary
Addresses #30, wherein the
DoubleRelaxMaker
flow can now take in two separateBaseVaspMaker
args in case the user wants the first or second relax job to have different settings. A common use-case could be to setuser_kpoint_settings
in the first relax maker to be half the usual value. Ideally, there'd be an optional parameter calledhalf_kpts_first_relax
that could do this automatically, but I had some trouble figuring out the best way to modify the k-point density of the first job in a clean way that accounts forKSPACING
vs. the other k-point generation schemes.Edit: In hindsight, I guess the user could always have just defined the flow first and then edited the desired
job.maker.input_set_generator
afterwards... hmm...