Node development

Every component of the simulator should be a separate node. The nodes have to publish a HEARTBEAT message according to Heartbeat/Connection Protocol.

Example repository

There are multiple examples of ready-made nodes and utility functions in the marsh-sim/sim-nodes repository.

The names of scripts should hint at the type of component from MARSH_COMPONENT. These are at the end of the name, and the beginning something unique, to make running a given script easier from terminal with Tab-completion.

Message choice

For communicating any node-specific feature the workflow is as follows:

1. Check if there is already a relevant convention for a feature in Microservices section of Dev Guide
   • If nothing was found, search the Common Message Set
2. Read documentation for the service: e.g. Parameter Protocol
3. Read documentation for specific messages: e.g. SIM_STATE (#108)