For control purposes the main use of this package is to create new entities and connect them through signals.
Objects, which are derived from Entities (base class dynamicgraph::Entity), can be declared within the code and compiled as shared libraries (.so/.dll files). These libraries can be loaded at run-time using the PluginLoader methods, and at the same time register their class names to the Factory (see the examples in the sot-core documentation for advanced control examples).
The Factory can then create instances of these objects and subsequently register them in the Pool. From the pool they can be listed, accessed, and acted upon (see PoolStorage documentation). Basic commands defined by entities include signal connection graph file generation, help and name print, and signals. This is usually done through a scripting language such as python (see dynamic-graph-python)
The singletons made available by including the corresponding headers in this module are:
For an example of a program creating entities in C++, see the unit test test_pool.cpp (in your package source directory/tests).
A tutorial is available here. It is providing a step-by-step way of building an entity
When writing entities you might use some macros which are very useful to write your class.
The header entity-helper.h is defining a type called EntityClassName
CONSTRUCT_SIGNAL_OUT(signal_name,type) This macro is used in the constructor of the entity class handling this signal. It creates the binding to the method described previously, and set the signal name to:
where entity_name is the name of the entity currently instanciated.
DEFINE_SIGNAL_OUT_FUNCTION(signal_name, type): This macro is used when implementing the method specific to the output signal. It is used in the main body of the entity class to declare the header of the method with the following pattern: