.. _auto_physicaltest_import_unv_data:

*IMPORT DATA FROM UNV*
======================

Ingests a Universal File Format (UNV) test data file into the d3VIEW physical-test database, mapping channels via a companion map file and registering all responses under a named test record. Use this worker to import NVH or structural measurement data exported from data-acquisition systems in the UNV format.

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

Tagged: ``channel_mapping``, ``data_acquisition``, ``import``, ``nvh``, ``physical_test``, ``test_data``, ``universal_file_format``, ``unv``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Test Name
     - test_name
     - text
     - Test - <%UID%>
     - ✓
     - Human-readable label assigned to the new physical-test record in the database; defaults to 'Test - <UID>' if left unchanged.
   * - UNV File
     - unv_file
     - file
     - —
     - ✓
     - The Universal File Format (.unv) file containing raw measurement data (time histories, frequency responses, etc.) to be imported.
   * - UNV Map File
     - unv_map_file
     - file
     - 0
     - ✓
     - Companion channel-mapping file that defines how UNV dataset/channel identifiers are translated to d3VIEW response names and units; required for correct channel resolution.
   * - Media File
     - media_file
     - file
     - —
     - 
     - Optional supplementary media file (e.g., test photo or video) to be attached to the physical-test record; leave empty if not available.
   * - Remove If Exists
     - remove_if_exists
     - select
     - yes
     - 
     - When set to 'yes' (default), any existing physical-test record with the same name is deleted before import, preventing duplicate entries; set to 'no' to preserve existing records.
   * - Store UNV And Map File
     - store_unv_and_map_file
     - select
     - yes
     - 
     - When set to 'yes' (default), the original UNV and map files are stored as attachments on the physical-test record for traceability; set to 'no' to skip file storage.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - Physicaltest Id
     - physicaltest_id
     - integer
     - Integer primary-key ID of the newly created (or replaced) physical-test record in the d3VIEW database.
   * - Num Attachments
     - num_attachments
     - integer
     - Count of files attached to the physical-test record after import (includes UNV, map, and any media files if storage is enabled).
   * - Num Responses
     - num_responses
     - integer
     - Total number of response channels successfully parsed from the UNV file and registered against the test record.
   * - Responses
     - responses
     - dataset
     - Dataset containing the imported response records (channel metadata and time/frequency data) linked to the physical test.
   * - Template Id
     - template_id
     - responsetemplate
     - ID of the response template automatically generated or matched for this test, used for downstream KPI rollup and comparison workflows.
   * - Transformed Responses
     - transformed_responses
     - dataset
     - Dataset of responses after any unit conversions or channel-mapping transformations defined in the map file have been applied.

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

- cae.postprocessing.response
- data.dataset.ingest
- engineering.nvh

.. 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_import_unv_data</code>. Schema hash: <code>462101b60485</code>. Hand-curated docs in <code>workerexamples/</code> override this page when present.
   </p>