GitLab

argument.

Update the Python application layer to use both force constants when building
the AmoebaStretchBendForce.

one in the Reference platform (pulled over via meld to limit possible mistakes).

stretch-bend test correctly.

The potential energy calculation done in the ReferenceStretchBendTest file was
updated to mirror that of the Reference kernel, but first I made sure that the
test passed *before* updating to the new energy expression, just to make sure
that the energies and forces didn't *change* with the new expression.

of just 1.  Backwards compatibility is provided by making the 2nd force constant
default to -1, which is reinterpreted as "copy the first force constant".

Updates both the reference and CUDA kernels.

to 0 here as well.

} else { -->
}
else {

However, these were not my additions originally, but rather part of the Amoeba
test cases that have been around for awhile. I figured while I was at it, I
might as well update these styles as well.

function call.

typo fix

typo fix

typo fix

typo fix

typo fix

@rmcgibbo and @mpharrigan convinced me I should have just fixed it myself.