.. _auto_physicaltest_map_responses:

*MAP RESPONSES FROM PHYSICALTESTS*
==================================

Maps physical-test response channel names to standardised names using either a platform database lookup or a user-supplied CSV/dataset mapper. Use this worker to harmonise response labels across tests before downstream correlation or reporting steps.

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

Tagged: ``channel-rename``, ``csv``, ``database``, ``mapper``, ``mapping``, ``physicaltest``, ``response-mapping``, ``responses``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Physicaltest
     - input_pt_id
     - remote_lookup
     - —
     - ✓
     - The physical test record whose response channels will be renamed; select from the platform physical-tests registry (required).
   * - Map Database
     - map_database
     - remote_lookup
     - —
     - 
     - Optional platform database containing the from→to name mapping rules; leave blank if using a CSV/dataset mapper instead.
   * - From Header
     - database_from_header
     - text
     - name
     - 
     - Column name in the selected database that holds the original (source) response channel names; defaults to 'name'.
   * - Datasbase to Header Column
     - database_to_header
     - text
     - name
     - 
     - Column name in the selected database that holds the target (destination) response channel names; defaults to 'name'.
   * - Database Region Column
     - database_region_column
     - text
     - name
     - 
     - Column name in the database used to filter rows by region/group; defaults to 'name', leave as default if no region filtering is needed.
   * - Database Region Name
     - database_region_name
     - text
     - name
     - 
     - Value to match in the region column for row filtering; defaults to 'name', leave as default if no region filtering is needed.
   * - Map Dataset
     - map_dataset
     - dataset
     - —
     - ✓
     - CSV or tabular dataset containing the from→to mapping rules; required when not using a database source — see d3VIEW docs for expected format.
   * - Choose Source Header Columns
     - dataset_from_header
     - select
     - mapping
     - 
     - Column in the map dataset that contains the original channel names to match against; defaults to 'mapping'.
   * - Choose Destination Header Columns
     - dataset_to_header
     - select
     - name
     - 
     - Column in the map dataset that contains the replacement channel names; defaults to 'name'.
   * - Dataset Map Delimiter
     - dataset_map_delimiter
     - select
     - comma
     - 
     - Delimiter used within compound channel-name tokens in the mapping dataset; choose from comma, forward-slash, tab, or '::' — defaults to 'comma'.
   * - Perform Mapping
     - perform_mapping
     - select
     - no
     - 
     - Flag controlling whether the mapping is actually applied to the physical-test responses or only validated/previewed; set to true to commit changes.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - Physicaltest Id
     - physicaltest_id
     - integer
     - Integer ID of the physical-test record that was processed, referencing the platform physicaltest datatype.
   * - Mapping Dataset
     - mapping_dataset
     - dataset
     - Tabular dataset of the mapping rules that were resolved and applied during this run, useful for audit and reproducibility.
   * - Mapping
     - mapping
     - dataset
     - Dataset listing each response channel alongside its mapped (renamed) counterpart after the transformation has been applied.
   * - Num Mapped
     - num_mapped
     - integer
     - Count of response channels that were successfully renamed according to the mapping rules.
   * - Num Unchanged
     - num_unchanged
     - integer
     - Count of response channels that had no matching mapping rule and were therefore left with their original names.

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

- data.correlation
- data.dataset.ingest
- data.dataset.transform
- data.io.csv

.. raw:: html

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