Closed sef43 closed 7 months ago
I just ran your test and it worked without problem. Perhaps it's a binary incompatibility of some sort in the way you built it?
Hmm, what are you running on?
Valgrind is showing invalid writes on these lines: https://github.com/openmm/openmm-xtb/blob/ee5761f3880f3a556a95cf34a74e4ca087f73117/openmmapi/src/XtbForceImpl.cpp#L78-L83
is positions
the vector of all atoms in the system?
while positionVec
is a vector of length 3*number of length of indices passed to xtbforce ?
Where is valgrind complaining? positionVec or positions?
I think you're right. Let me fix that.
The fix is in #5. Can you give it a try?
Yes thanks #5 is working for me
Please open a new issue if you have a question. This one is already closed, and your question isn't related to it.
@peastman is this supposed to work when only a subset of atoms have their force computed with xtb?
I cannot get it to work without a segfault.
Here is a testcase I would expect to work. The system contains two water molecules. The xtb force is only used for the first one. It fails with a segfault.
output: