QUANT-NET Agent

The QUANT-NET Agent that registers resources, interfaces with devices, and interprets protocol commands from the Controller.

quantnet_agent

Usage

quantnet_agent [OPTIONS]

Options

-c, --config <config>

Main configuration file

-n, --node-config <node_config>

Node configuration file

-a, --agent_id <agent_id>

Specify an agent identifier

Default:

'runnervmeorf1.tlak4pom5pbudklwnuq3z0zq0h.ex.internal.cloudapp.net'

--mq-broker-host <mq_broker_host>

Message queue broker host

--mq-broker-port <mq_broker_port>

Message queue broker port

-d, --debug

Enable debug logging

Default:

False

--interpreter-path <interpreter_path>

Location of additional command interpreters

--schema-path <schema_path>

Specify a path containing additional schema files

Monitoring Events

The agent scheduler publishes MonitorEvent messages to the monitor topic as tasks complete. Each event includes:

• eventType: "agentTaskResult" — identifies the message as a local task result (distinct from a full experiment result).

• value.name: the task name.

• value.exp_id: the experiment/task ID, used by the controller to correlate results when queried via getTasks.

• value.result: the task result payload (when present).

Configuration

The agent reads its configuration from an INI file. A path can be provided explicitly with the -c/--config CLI flag; if the file does not exist the agent exits immediately with an error.

Without -c, the config path depends on the environment:

• If $QUANTNET_HOME is set: $QUANTNET_HOME/etc/agent.cfg

• Otherwise: /etc/quantnet/agent.cfg

If no config file is found the agent continues with defaults and logs a warning. Message broker log output is suppressed to warning level by default.