.. _auto_responsetemplate_gather_sensors:

*GATHER SENSORS FROM A RESPONSETEMPLATE*
========================================

Retrieves all sensors defined within a specified response template and exposes them as a structured dataset. Use this worker when you need to programmatically inspect or downstream-process the sensor list associated with a given response template.

When to use
-----------

Tagged: ``files``, ``gather``, ``responsetemplate``, ``sensors``, ``templates``.

Inputs
------

.. list-table::
   :header-rows: 1
   :widths: 20 20 20 20 20 20

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Responsetemplate
     - rt_id
     - remote_lookup
     - —
     - 
     - The response template to query; select from the remote template registry. Leave as default (null) only if the template ID will be supplied at runtime by an upstream worker.

Outputs
-------

.. list-table::
   :header-rows: 1
   :widths: 20 20 20 20

   * - Label
     - ID
     - Type
     - Description
   * - Rt Id
     - rt_id
     - scalar
     - Pass-through of the resolved response template identifier (templates dataType), confirming which template was queried.
   * - Sensors
     - sensors
     - dataset
     - Tabular dataset containing all sensors defined in the response template — each row represents one sensor with its associated metadata (name, type, location, etc.).

Disciplines
-----------

- cae.postprocessing.response

.. raw:: html

   <hr style="margin-top:2em">
   <p style="font-size:11px;color:#888">
   Auto-generated from <code>platform</code> schema. Worker id: <code>responsetemplate_gather_sensors</code>. Schema hash: <code>9eb1eef5a3e9</code>. Hand-curated docs in <code>workerexamples/</code> override this page when present.
   </p>