AVERAGE DATA FROM RUNS

Averages time-history or frequency-response data across multiple physical-test runs, optionally creating a new physical test record to store the averaged result. Use this worker in NVH post-processing workflows where repeated test runs need to be consolidated into a single representative dataset.

When to use

Tagged: average, files, nvh, physical_test, runs, test_averaging.

Inputs

Label ID Type Default Required Description
Physicaltest input_pt_id remote_lookup   One or more physical test records whose runs will be averaged; repeatable remote lookup — leave empty if sourcing runs solely from a mapped database.
Mapping Database input_database_id remote_lookup   One or more mapping databases that define the channel/signal layout for the runs being averaged; repeatable remote lookup — required when the runs reside in a database rather than a direct physical test.
CRNTAD runs_to_average text   Comma-separated run names (CRNTAD identifiers) to include in the average; leave blank to average all runs found in the selected physical test or database.
Create New Test create_new_test select no   Set to ‘yes’ to persist the averaged result as a new physical test record; default ‘no’ writes results back into the existing test.
Test Post-fix new_test_name text no-name   Post-fix string appended to the new physical test name when create_new_test is ‘yes’; default is ‘no-name’ — provide a meaningful label such as ‘AVG’ to identify the averaged record.

Outputs

Label ID Type Description
Physical test physicaltest_id integer Integer ID of the physical test record that holds the averaged run data — either the newly created test (if create_new_test=’yes’) or the updated source test.

Disciplines

  • data.dataset.ingest
  • data.dataset.transform
  • data.statistics
  • engineering.nvh

Auto-generated from platform schema. Worker id: nvh_average_runs. Schema hash: 8a51bc0b12d6. Hand-curated docs in workerexamples/ override this page when present.