The Effects of Catalytic Converter Location and Palladium Loading on Tailpipe Emissions
Bibliographic record
Abstract
Meeting regulated tailpipe emission standards requires a full system approach by automotive engineers encompassing: engine design, combustion system metrics, exhaust heat management, aftertreatment design and exhaust system packaging. Engine and combustion system design targets define desired engine out exhaust constituents, exhaust gas temperatures and oil consumption rates. Protecting required catalytic converter volume in the engine bay for stricter tailpipe emission standards is becoming more difficult. Future fuel economy mandates are leading to vehicle downsizing which is affecting all aspects of vehicle component packaging. In this study, we set out to determine the potential palladium (Pd) cost penalty as a result of increased light-off time required as a catalyst is positioned further away from the engine. Two aged converter systems with different Pd loadings were considered, and EPA FTP-75 emission tested at six different catalyst positions. Testing began with the front face of the close-coupled catalyst 469 mm from the cylinder head, which is 228 mm from exhaust manifold pierce point (P-point, Figure 2), and increased in five additional increments of 75 mm. Exhaust gas temperatures were measured at every 25 mm. The negative impact on NMHC emissions as the catalyst sets moved further from the exhaust manifold were investigated. Likewise the effect of increasing Pd loading in offsetting the delayed light-off times associated with increased catalyst distance from the engine was studied. As a result, an attempt was made to develop a cost model of increasing the catalyst distance from the exhaust manifold in order to achieve equal NMHC EPA FTP-75 emission performance.
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.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 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".