Nevermind, I found the issue, I misread the logs, it was actually failing to load the plugin due to a linking error.

yes, it is the only location where that is available beside the build folder.

Hi, I've created the CPU platform for my plugin, at runtime it finds the plugin ".so" library but `dlsym` returns a NULL handle for registerKernelFactories. I defined the function as: extern "C" OPENMM_EXPORT void registerKernelFactories() { std::cout << "Executing registerKernelFactories of CPU MBP...

I am trying to implement the CPU platform for the `mbpol_openmm_plugin`. If I am not mistaken, I need to include `CpuPlatform.h` to extend that in the `KernelFactory`, however that imports the `sfmt` library, which I noticed is built by OpenMM at compilation but not installed. Therefore I get the er...

Thanks, no, I use HOH as well, see the xml:

https://github.com/paesanilab/mbpol_ope ... /mbpol.xml

Hello, in our plugin the rigidwater flag does not work correctly. We have a simple test case of 3 water molecules, see https://github.com/sqamara/mbpol_debug/blob/master/test.py If we setup one of the OpenMM water models, like TIP5P, everything works correctly, see a plot of OH distances for the fir...

Thanks Jason,
I was actually more concerned about users that only use OpenMM C++ and don't even install the Python wrapper, do you have a feeling of what fraction of OpenMM users use only C++?

I wonder if it would be reasonable to rely on the Python wrapper, something like:

Thanks, how do I extract the current version of OpenMM at compilation time of a plugin?

Hi,

the signature for the function `computeNeighborListVoxelHash` changed in 6.3, it now requires the periodic box vectors instead of the box size.
what is the easiest way for plugins to support both versions of this function?

thanks!