.. _auto_response_finder:

*RESPONSE FINDER*
=================

Searches the d3VIEW response library and returns a filtered set of simulation or physical-test responses. Use this worker to locate and retrieve stored responses by applying metadata-based filters before passing them downstream for post-processing or correlation.

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

Tagged: ``filter``, ``response_finder``, ``responses``, ``search``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Choose Filters
     - filters
     - filters
     - —
     - ✓
     - One or more metadata filters (e.g. simulation ID, channel name, load case, date range) drawn from the /api/app/get_filters?type=response endpoint; at least one filter is required to scope the response search.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - Responses
     - responses
     - dataset
     - Dataset of matched response records (type: responses) returned by the filter query, ready for downstream post-processing, curve operations, or correlation tasks.

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

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

.. raw:: html

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