.. _auto_physicaltest_response_extractor: *EXTRACTS RESPONSE FROM A SIMULATION* ===================================== Extracts named responses (channels/KPIs) from a physical test record stored in d3VIEW. Use this worker to pull time-history or scalar response data from a physical test entry and pass it downstream for correlation, post-processing, or reporting. When to use ----------- Tagged: ``d3view``, ``kpi``, ``physical_test``, ``response_extraction``, ``time_history``, ``user``. Inputs ------ .. list-table:: :header-rows: 1 :widths: 20 20 20 20 20 20 * - Label - ID - Type - Default - Required - Description * - Physicaltest - physicaltest_id - remote_lookup - — - ✓ - Remote lookup ID referencing the target physical test record in d3VIEW (type: physicaltests); select the test whose responses you want to extract. * - Responses - responses - dataset - — - ✓ - Dataset configuration specifying which responses (channels/KPIs) to extract from the selected physical test; populated interactively via the 'Extract Response' modal — at least one response must be selected. Outputs ------- .. list-table:: :header-rows: 1 :widths: 20 20 20 20 * - Label - ID - Type - Description * - Physicaltest - pt_id - integer - Integer ID of the physical test record from which responses were extracted; can be used as a foreign key in downstream workers. * - Extracted Responses - responses - dataset - Dataset containing the extracted response data (e.g., time-history curves or scalar KPIs) for all requested channels from the physical test. * - Logs - logs - dataset - Dataset of execution log messages produced during response extraction; inspect for warnings or errors if responses are missing or incomplete. Disciplines ----------- - cae.postprocessing.extraction - cae.postprocessing.response - data.dataset.ingest .. raw:: html
Auto-generated from platform schema. Worker id: physicaltest_response_extractor. Schema hash: c212cd03a38d. Hand-curated docs in workerexamples/ override this page when present.