.. _auto_js3d_responses:

*EXTRACT THE RESPONSES FROM JS3D*
=================================

Extracts named response channels from a JS3D result file and returns them as a structured dataset. Use this worker when you need to pull specific KPI or time-history responses out of a JS3D output for downstream post-processing or reporting.

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

Classification: **process**.

Tagged: ``js3d``, ``post_processing``, ``response_extraction``, ``transformations``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - File Name
     - filename
     - view
     - —
     - 
     - Path or view reference to the JS3D result file to read; leave blank if the file is resolved automatically from an upstream workflow connection.
   * - Response Names To Extract
     - responsenamestoextract
     - view
     - —
     - 
     - Comma-separated list of response channel names to extract from the JS3D file (e.g. 'Head_HIC,Chest_3ms,Femur_Left'); leave blank to extract all available responses.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - js3d_responses_output_1
     - js3d_responses_output_1
     - dataset
     - Tabular dataset containing one column per extracted response channel and one row per time step or result record found in the JS3D file.

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

- cae.postprocessing.extraction
- cae.postprocessing.response

.. raw:: html

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