Optimal Motorcycle Engine Mount Design Parameter Identification Using Robust Optimization Algorithms
Bibliographic record
Abstract
Mechanical vibrations have a significant impact on ride comfort; the driver is constantly distracted as a result. Volumetric engine inertial unbalances and road profile irregularities create mechanical vibrations. The purpose of this study is to employ optimization algorithms to identify structural elements that contribute to vibration propagation and to provide optimal solutions for reducing structural vibrations induced by engine unbalance and/or road abnormalities in a motorcycle. The powertrain assembly, swing-arm assembly, and vibration-isolating mounts make up the vibration-isolating system. Engine mounts are used to restrict transferred forces to the motorbike frame owing to engine shaking or road irregularities. Two 12-degree-of-freedom (DOF) powertrain motorcycle engine systems (PMS) were modeled and examined for design optimization in this study. The first model was used to compute engine mount parameters by reducing the transmitted load through the mounts while only considering shaking loads, whereas the second model considered both shaking and road bump loads. In both configurations, the frame is infinitely stiff. The mount stiffness, location, and orientation are considered to be the design parameters. The purpose of this study is to employ computational methods to minimize the loads induced by shaking forces. To continue the optimization process, Grey Wolf Optimizer (GWO), a meta-heuristic swarm intelligence optimization algorithm inspired by grey wolves in nature, was utilized. To demonstrate GWO’s superior performance in PMS, other optimization methods such as a Genetic Algorithm (GA) and Sequential Quadratic Programming (SQP) were used for comparison. To minimize the engine’s transmitted force, GWO was employed to determine the optimal mounting design parameters. The cost and constraint functions were formulated and optimized, and promising results were obtained and documented. The vibration modes due to shaking and road loads were decoupled for a smooth ride.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
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".