The samples folder is present to show various features and scenarios of the Heex SDK and demonstrated some basic and more advanced functionalities.
We have created a basic sample monitors that:
awaitReady()
which will set the implementation in a waiting state until it connect to the kernel.updateValue
and updateValueBySignalName
for the supported types.
You can find it under the samples/cpp
or samples/python
folder.The advancedSampleMonitor_ConfChangedCallback
demonstrates how to create a Configurable-by-Value Monitor that overloads the onConfigurationChangedCallback
function in order to access or run specific code during an implementation’s reconfiguration. In our sample, we print our the Value Configurations and the Constant Values whenever there is a reconfiguration (also at initial configuration).
Monitor
to overload the onConfigurationChangedCallback
functionThe basicSampleRecorder
demonstrates how to create a Recorder that provides the Label position
and generates an event recording part in the form of a file that contains the timestamp of the event. The file is created for the event and demonstrate how to use some information contained in the event query.
ID
, exposes the Labels and Event Recording Part generation to the Core for identifier ID
. It stops only on SIGKILL (Ctrl-C).The advancedSampleRecorders
are samples that are showing off a specific feature.
The advancedSampleRecorder_ConfChangedCallback
demonstrates how to create a Configurable-by-Value Recorder that overloads the onConfigurationChangedCallback
function in order to access or run specific code during an implementation’s reconfiguration. In our sample, we print our the Value Configurations and the Constant Values whenever there is a reconfiguration (also at initial configuration).
The rest of the behavior is very similar to the basicSampleRecorder
Explore ready-to-use sample code located in the samples folder. Feel free to modify the ID or use the provided code as a starting point for your implementation.
This project is the example of the recommended SDK usage for a ROS2 package that implements Monitors and Recorders.
It implements logics of monitoring and recording that interface with ROS2 middleware.
This directory contains several samples demonstrating how to use MCAP file as input or output for your implementation. MCAP files can be directly analyse on the Heex Cloud without the need of downloading the recording.
The samples folder is present to show various features and scenarios of the Heex SDK and demonstrated some basic and more advanced functionalities.
We have created a basic sample monitors that:
awaitReady()
which will set the implementation in a waiting state until it connect to the kernel.updateValue
and updateValueBySignalName
for the supported types.
You can find it under the samples/cpp
or samples/python
folder.The advancedSampleMonitor_ConfChangedCallback
demonstrates how to create a Configurable-by-Value Monitor that overloads the onConfigurationChangedCallback
function in order to access or run specific code during an implementation’s reconfiguration. In our sample, we print our the Value Configurations and the Constant Values whenever there is a reconfiguration (also at initial configuration).
Monitor
to overload the onConfigurationChangedCallback
functionThe basicSampleRecorder
demonstrates how to create a Recorder that provides the Label position
and generates an event recording part in the form of a file that contains the timestamp of the event. The file is created for the event and demonstrate how to use some information contained in the event query.
ID
, exposes the Labels and Event Recording Part generation to the Core for identifier ID
. It stops only on SIGKILL (Ctrl-C).The advancedSampleRecorders
are samples that are showing off a specific feature.
The advancedSampleRecorder_ConfChangedCallback
demonstrates how to create a Configurable-by-Value Recorder that overloads the onConfigurationChangedCallback
function in order to access or run specific code during an implementation’s reconfiguration. In our sample, we print our the Value Configurations and the Constant Values whenever there is a reconfiguration (also at initial configuration).
The rest of the behavior is very similar to the basicSampleRecorder
Explore ready-to-use sample code located in the samples folder. Feel free to modify the ID or use the provided code as a starting point for your implementation.
This project is the example of the recommended SDK usage for a ROS2 package that implements Monitors and Recorders.
It implements logics of monitoring and recording that interface with ROS2 middleware.
This directory contains several samples demonstrating how to use MCAP file as input or output for your implementation. MCAP files can be directly analyse on the Heex Cloud without the need of downloading the recording.