Feature #2585: Infrastructure supporting external API
MD signaling API
Allow client code, such as modules implementing MD support code, to issue runtime simulation signals.
gmxapi milestone 10 as described at #2585
A signal manager must be provided to applicable simulation methods to allow binding to various control flow signals. The signal manager is one of several resources owned by client code (or other code external to the actual simulation method implementation) and likely dependent on the runtime environment that requires infrastructure from gmxapi milestone 5 (issue #2587).
Further develops resources from milestone 23.
Relates to issue #2224
Add gmxapi session resources.
Allow simulation support code to access resources from the running
session. Provide some abstraction for resources implemented or
managed differently in different execution environments or API contexts.
Examples of resources are input and output data streams or simulation
Support gmxapi milestone 10
Allow API access to simulation signals.
Refs #2620 for gmxapi milestone 10
Provide API client access to issue stop signals through simulation
Session resources. Stop conditions will be discovered by the simulation
when checked from within the MD loop.
Also relates to #2224 and various other works in progress.