.. _auto_simulation_has_response_by_name: *CHECKS IF A SIMULATION HAS A RESPONSE BY NAME* =============================================== Checks whether a given simulation already contains a response matching a specified name, type, and name-match rule (contains, starts_with, ends_with, excludes). Use this worker in workflow branching logic to gate downstream steps on the presence or absence of a particular response. When to use ----------- Tagged: ``branching``, ``check``, ``exists``, ``lookup``, ``response``, ``simulation``. Inputs ------ .. list-table:: :header-rows: 1 :widths: 20 20 20 20 20 20 * - Label - ID - Type - Default - Required - Description * - Simulation - simulation_id - remote_lookup - — - ✓ - The simulation to query — select from the remote lookup dropdown; required to identify which simulation's response list is searched. * - Response Name - response_name - textarea - — - ✓ - The name string to search for among the simulation's responses; matched against response names using the rule specified in the 'location' input. * - Type - type - select - vector - ✓ - Response type to filter on — one of 'vector', 'scalar', 'view', or 'dataset'; defaults to 'vector'. * - Location - location - select - contains - ✓ - String-match rule applied to response_name — one of 'contains' (default), 'starts_with', 'ends_with', or 'excludes'. Outputs ------- .. list-table:: :header-rows: 1 :widths: 20 20 20 20 * - Label - ID - Type - Description * - Simulation Id - simulation_id - integer - Integer ID of the queried simulation, passed through for use by downstream workers. * - Result - result - scalar - Boolean-like scalar flag (1 = match found, 0 = no match) indicating whether a response satisfying the name/type/location criteria exists in the simulation. Disciplines ----------- - cae.postprocessing.response - platform.workflow .. raw:: html
Auto-generated from platform schema. Worker id: simulation_has_response_by_name. Schema hash: 62a51674073f. Hand-curated docs in workerexamples/ override this page when present.