Virtual Accelerometer Approach to Create Vibration Profile for Automotive Component Shake Test
Bibliographic record
Abstract
Vibration shaker testing is a great tool of validating the vibration fatigue performance of automotive components & systems. However, the representative vibration schedule requires a pre-knowledge of the acceleration history for the test object, which usually is not available until the later development phase of a vehicle program when physical properties are available. Sometimes, a generic vibration schedule developed from the worst-case loading profiles are used with risk of lacking correlation with later full vehicle durability test such as Road Test Simulator (RTS) or Proving Ground (PG) road test due to the higher loading amplitude. This paper proposes a virtual accelerometer approach to collect acceleration responses of a component from a virtual vehicle model. First, a multiple body dynamic model will be produced for virtual load calculation over a series of digitalized virtual proving ground road profiles. These loads will be then applied on the virtual vehicle CAE model with all representative components & subsystems. Acceleration response for the system of interest is then extracted from modal transient dynamic analysis. Later, the acceleration history is converted to frequency domain, and the associated spectral damage calculation is conducted. The final vibration profile is developed based on the equivalent damage concept. The virtual acceleration acquisition and physical acceleration acquisition show good agreement in both time domain and frequency domain. The profile generated from virtual acceleration acquisition covers very well for the physical acceleration acquisition. Overall, virtual acceleration-based profile ensures the conservative shake test results for the example studied. Compared to the physical accelerometer, the virtual accelerometer can provide acceleration data economically and quickly in the early phase of the product development. The proposed approach will ensure the component shaker test is conducted using the meaningful and representative vibration load.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".