Node
A single ROS 2 executable process that participates in the ROS 2 communication graph. Each node has a unique name, and can create publishers, subscribers, service servers, service clients, and action servers and clients. Process isolation between nodes is a deliberate design choice: a crash in one node does not propagate to others.
Defined in 2 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in Foundations of Robotics and Physical AI.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
A point on a lineage map representing a system, table, file, API, report, or model. This topic uses four types: source system (where data is created or first captured), transform (where data changes shape or meaning), store (where data rests between transforms), and consumer (where data is finally used to make a decision or answer a question).
A single ROS 2 executable process that participates in the ROS 2 communication graph. Each node has a unique name, and can create publishers, subscribers, service servers, service clients, and action servers and clients. Process isolation between nodes is a deliberate design choice: a crash in one node does not propagate to others.
A single executable process in the ROS 2 communication graph that owns a defined responsibility, publishes messages to topics, subscribes to topics, provides or calls services and actions, and declares parameters.
Where it is taught
The exact lessons this term appears in. The first 7 topics of every program are free with a free account.
- The lineage map: your estate's first honest picture of where its data actually comes from · The Estate Survey, AI Data Governance: The Data Chair
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.