.. _auto_physical_create_from_responses:

*CREATE PHYSICALTEST FROM RESPONSES*
====================================

Creates a new physical-test record in the d3VIEW platform by assembling a set of user-supplied responses (curves, scalars, views, and text) together with test metadata such as location, type, product, and environmental conditions. Use this worker whenever a physical test result needs to be registered and linked to a project or response template within a workflow.

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

Tagged: ``create``, ``curve_responses``, ``ingest``, ``physical_test``, ``physicaltest``, ``responses``, ``scalar_responses``, ``test_metadata``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Name
     - input_name
     - text
     - —
     - ✓
     - Human-readable name for the new physical-test record; required and used as the primary display label in the platform.
   * - Description
     - input_desc
     - textarea
     - —
     - ✓
     - Free-text description of the physical test, e.g. test objective, specimen details, or notes; required.
   * - Tags
     - tags
     - text
     - —
     - 
     - Comma-separated keyword tags to aid search and filtering of the physical-test record; optional, leave blank if no tagging is needed.
   * - Files
     - files
     - file
     - —
     - 
     - One or more supporting files (raw data, photos, reports) to attach to the physical-test record; optional, repeatable.
   * - Curve Responses
     - vector_responses
     - vector
     - —
     - 
     - One or more curve (time-history or X-Y) responses to attach to the test; each entry should specify a name and label; optional, repeatable.
   * - Scalar Responses
     - scalar_responses
     - scalar
     - —
     - 
     - One or more scalar (single-value) responses such as peak force or energy to attach to the test; each entry should specify a name and label; optional, repeatable.
   * - View Responses
     - view_responses
     - view
     - —
     - 
     - One or more view (image or rendered-plot) responses to attach to the test; each entry should specify a name and label; optional, repeatable.
   * - Text Responses
     - text_responses
     - textarea
     - —
     - 
     - One or more free-text responses (observations, qualitative notes) to attach to the test; each entry should specify a name and label; optional, repeatable.
   * - Test Location
     - test_location
     - text
     - —
     - 
     - Name or identifier of the facility where the physical test was conducted; optional, e.g. 'Lab A – Detroit'.
   * - Test Type
     - test_type
     - text
     - —
     - 
     - Classification of the test protocol, e.g. 'FMVSS 214', 'tensile', or 'drop-tower'; optional.
   * - Product Type
     - product_type
     - text
     - —
     - 
     - Category of the product under test, e.g. 'door panel', 'battery module'; optional.
   * - Product Name
     - product_name
     - text
     - —
     - 
     - Specific product name or part number being tested; optional.
   * - Serial Number
     - serial_number
     - text
     - —
     - 
     - Serial or lot number of the specimen or product under test for traceability; optional.
   * - Test Temperature
     - test_temperature
     - text
     - —
     - 
     - Ambient or controlled temperature during the test (include units, e.g. '23 °C'); optional.
   * - Test Speed
     - test_speed
     - text
     - —
     - 
     - Test speed or loading rate (include units, e.g. '56 km/h' or '10 mm/min'); optional.
   * - Test Software
     - test_software
     - text
     - —
     - 
     - Data-acquisition or analysis software used during the test, e.g. 'nCode 2023'; optional.
   * - Test Hardware
     - test_hardware
     - text
     - —
     - 
     - Test rig, load cell, or instrumentation hardware used, e.g. 'MTS 322 frame'; optional.
   * - Responsetemplate
     - responsetemplate_id
     - remote_lookup
     - —
     - 
     - Platform response-template ID to apply to the new physical-test record, pre-populating expected response slots; optional, resolved via remote lookup.
   * - Project
     - project_id
     - remote_lookup
     - —
     - 
     - Platform project ID to which the physical-test record will be linked; optional, resolved via remote lookup.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - Output 01
     - output_01
     - integer
     - Integer primary-key ID of the newly created physical-test record in the d3VIEW platform (dataType: physicaltests), used by downstream workers to reference or query this test.

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

- cae.postprocessing.response
- data.dataset.ingest
- platform.workflow

.. raw:: html

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