COMPUTE VELOCITY DATA FROM ACCELERATIONS

Integrates acceleration time-history data from physical test records to derive velocity curves. Use this worker when velocity channels are absent from test results and must be computed from measured accelerations, optionally storing the results as a new physical test entry.

When to use

Tagged: acceleration, integration, nvh, physical_test, signal_processing, velocity.

Inputs

Label ID Type Default Required Description
Physicaltest input_pt_id remote_lookup   One or more physical test records whose acceleration channels will be integrated to compute velocity; leave empty if sourcing data from a mapping database instead.
Mapping Database input_database_id remote_lookup   One or more mapping databases that define channel-to-location mappings for the acceleration signals; leave empty if all required mappings are already embedded in the selected physical tests.
Specify Locations locations text   Comma-separated list of sensor location identifiers (e.g. ‘A1,B2,C3’) to restrict computation to specific channels; leave blank to process all available acceleration locations.
Create New Test create_new_test select no   Set to ‘yes’ to persist the computed velocity data as a new physical test record in the platform; defaults to ‘no’, which updates the existing test in place.
Test Post-fix new_test_name text no-name   Post-fix string appended to the source test name when creating a new physical test record (e.g. ‘_velocity’); only used when create_new_test is ‘yes’.

Outputs

Label ID Type Description
Physical test physicaltest_id integer Integer ID of the physical test record that now contains the computed velocity channels — either the newly created test (if create_new_test = ‘yes’) or the updated source test.

Disciplines

  • data.dataset.ingest
  • data.signal_processing
  • engineering.nvh

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