-
Notifications
You must be signed in to change notification settings - Fork 15
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
LAMMPS: Implement calculate() function #1446
Conversation
Pull Request Test Coverage Report for Build 9444291497Details
💛 - Coveralls |
pyiron_atomistics/lammps/base.py
Outdated
"files_to_copy": files_to_copy, | ||
} | ||
|
||
def write_input(self): |
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.
Shouldn't this go to AtomisticGenericJob
?
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, the corresponding pull request is already open on pyiron_base
pyiron/pyiron_base#1472 .
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.
Then why is a copy here?
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.
This is primarily for historic reasons, this was the first pull request, before the one in pyiron_base
. The copy is removed in #1451
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.
But doesn't it make more sense to not add it in the first place in this PR?
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.
Unless a new version of base is released the tests fail without this temporary function.
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 ok with it, but it seems to me like a bigger evil to copy and paste lines of code only to be deleted in the next PR if the sole reason to do it is you want to merge it earlier, because it's gonna stay in the commit history and might confuse the future developers. Maybe someone like @pmrv or @liamhuber has an opinion?
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.
@samwaseda, what you are saying sounds perfectly reasonable to me. If this PR ought to depend on a PR in base, unless there is some pressing need to get it merged and released, just wait for what's needed to be available in base.
Pull Request Test Coverage Report for Build 9471820921Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9476628334Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9476697150Details
💛 - Coveralls |
Merge main
Merge main
Lammps submit to executor
This comment is no longer valid. |
Waiting for pyiron/pyiron_base#1477 |
Pull Request Test Coverage Report for Build 9477283041Details
💛 - Coveralls |
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.
lgtm
…alculate_with_base
…lculate # Conflicts: # pyiron_atomistics/lammps/base.py
…alculate # Conflicts: # pyiron_atomistics/lammps/base.py
Pull Request Test Coverage Report for Build 9609063823Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9609156113Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9609216747Details
💛 - Coveralls |
Switch the LAMMPS job to the
calculate()
function as it is introduced in pyiron/pyiron_base#1477 . The pull request is expected to fail until pyiron/pyiron_base#1477 is merged.With these new changes it is possible to evaluate LAMMPS jobs as functions. For a classical LAMMPS job you would use:
This still works, but in addition you can also use an external executor: