Closed timcnicholls closed 6 months ago
Thanks for the feedback: here's an example for some better context.
The intention was to implement a simple flat container for parameters as member variables, allowing (de)/serialisation to/from JSON, i.e. parameter payloads in IPC messages. It's a bit like a flat parameter tree but without external or explicit setters/getters, hence the comments above. The container fields can be used locally to e.g. store configuration parameters, updated from a IPC config message and retrieved when the config is requested. Does that make more sense?
Thanks for the feedback: here's an example for some better context.
Ah OK yes this looks neat.
This PR adds support to odin-data to facilitate external camera-based and DPDK-accelerated FP plugin development. This includes:
ParamContainer
class to the common library, to allow simple parameter handling for e.g. camera configurationIpcMessage
to allow serialisation/deserialisation of ParmContainer parameters to/from IPC messages