Set KIM pointer appropriately for Energy #1727
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
There are cases in lammps where
eflag_global=0
, while KIM-API would always set the global compute-energy-flag to true. This setting is due to the way that the pointer is passed to the KIM.if (KIM_SupportStatus_NotEqual(kim_model_support_for_energy, KIM_SUPPORT_STATUS_notSupported)) kimerror = kimerror || KIM_ComputeArguments_SetArgumentPointerDouble(pargs, KIM_COMPUTE_ARGUMENT_NAME_partialEnergy, &(eng_vdwl));
Here
eng_vdwl
is a double variable, and it's reference to KIM is neverNULL
. It causes extra computation of energy in model drivers in KIM.Author(s)
Yaser Afshar | Research Associate
Aerospace Engineering & Mechanics | University of Minnesota
Address: 100 Union St SE, Shepherd Labs 301,
Minneapolis, MN 55455, United States
Licensing
By submitting this pull request, I agree, that my contribution will be included in LAMMPS and redistributed under either the GNU General Public License version 2 (GPL v2) or the GNU Lesser General Public License version 2.1 (LGPL v2.1).
Backward Compatibility
The pull request will not break backward compatibility for inputs
Post Submission Checklist
Please check the fields below as they are completed after the pull request has been submitted. Delete lines that don't apply